Action not permitted
Modal body text goes here.
Modal Title
Modal Body
CVE-2024-47659 (GCVE-0-2024-47659)
Vulnerability from cvelistv5 – Published: 2024-10-09 14:02 – Updated: 2026-08-05 11:39| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
07feee8f812f7327a46186f7604df312c8c81962 , < d3f56c653c65f170b172d3c23120bc64ada645d8
(git)
Affected: 07feee8f812f7327a46186f7604df312c8c81962 , < 5b4b304f196c070342e32a4752e1fa2e22fc0671 (git) Affected: 07feee8f812f7327a46186f7604df312c8c81962 , < a948ec993541db4ef392b555c37a1186f4d61670 (git) Affected: 07feee8f812f7327a46186f7604df312c8c81962 , < 0aea09e82eafa50a373fc8a4b84c1d4734751e2c (git) Affected: 07feee8f812f7327a46186f7604df312c8c81962 , < 0776bcf9cb6de46fdd94d10118de1cf9b05f83b9 (git) Affected: 07feee8f812f7327a46186f7604df312c8c81962 , < 4be9fd15c3c88775bdf6fa37acabe6de85beebff (git) Affected: 07feee8f812f7327a46186f7604df312c8c81962 , < d3703fa94116fed91f64c7d1c7d284fb4369070f (git) Affected: 07feee8f812f7327a46186f7604df312c8c81962 , < 2fe209d0ad2e2729f7e22b9b31a86cc3ff0db550 (git) |
guessed | |
| Linux | Linux |
Affected:
2.6.30
Unaffected: 0 , < 2.6.30 (semver) Unaffected: 4.19.322 , ≤ 4.19.* (semver) Unaffected: 5.4.284 , ≤ 5.4.* (semver) Unaffected: 5.10.226 , ≤ 5.10.* (semver) Unaffected: 5.15.167 , ≤ 5.15.* (semver) Unaffected: 6.1.109 , ≤ 6.1.* (semver) Unaffected: 6.6.50 , ≤ 6.6.* (semver) Unaffected: 6.10.9 , ≤ 6.10.* (semver) Unaffected: 6.11 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2024-47659",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2024-10-10T13:23:30.727932Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2024-10-10T13:23:46.221Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
},
{
"providerMetadata": {
"dateUpdated": "2025-11-03T22:20:23.105Z",
"orgId": "af854a3a-2127-422b-91ae-364da2661108",
"shortName": "CVE"
},
"references": [
{
"url": "https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html"
}
],
"title": "CVE Program Container"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"security/smack/smack_lsm.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "d3f56c653c65f170b172d3c23120bc64ada645d8",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
},
{
"lessThan": "5b4b304f196c070342e32a4752e1fa2e22fc0671",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
},
{
"lessThan": "a948ec993541db4ef392b555c37a1186f4d61670",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
},
{
"lessThan": "0aea09e82eafa50a373fc8a4b84c1d4734751e2c",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
},
{
"lessThan": "0776bcf9cb6de46fdd94d10118de1cf9b05f83b9",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
},
{
"lessThan": "4be9fd15c3c88775bdf6fa37acabe6de85beebff",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
},
{
"lessThan": "d3703fa94116fed91f64c7d1c7d284fb4369070f",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
},
{
"lessThan": "2fe209d0ad2e2729f7e22b9b31a86cc3ff0db550",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"security/smack/smack_lsm.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "2.6.30"
},
{
"lessThan": "2.6.30",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "4.19.*",
"status": "unaffected",
"version": "4.19.322",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.4.*",
"status": "unaffected",
"version": "5.4.284",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.10.*",
"status": "unaffected",
"version": "5.10.226",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.15.*",
"status": "unaffected",
"version": "5.15.167",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.109",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.50",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.10.*",
"status": "unaffected",
"version": "6.10.9",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "6.11",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "4.19.322",
"versionStartIncluding": "2.6.30",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.4.284",
"versionStartIncluding": "2.6.30",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.10.226",
"versionStartIncluding": "2.6.30",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.15.167",
"versionStartIncluding": "2.6.30",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.1.109",
"versionStartIncluding": "2.6.30",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.6.50",
"versionStartIncluding": "2.6.30",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.10.9",
"versionStartIncluding": "2.6.30",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.11",
"versionStartIncluding": "2.6.30",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsmack: tcp: ipv4, fix incorrect labeling\n\nCurrently, Smack mirrors the label of incoming tcp/ipv4 connections:\nwhen a label \u0027foo\u0027 connects to a label \u0027bar\u0027 with tcp/ipv4,\n\u0027foo\u0027 always gets \u0027foo\u0027 in returned ipv4 packets. So,\n1) returned packets are incorrectly labeled (\u0027foo\u0027 instead of \u0027bar\u0027)\n2) \u0027bar\u0027 can write to \u0027foo\u0027 without being authorized to write.\n\nHere is a scenario how to see this:\n\n* Take two machines, let\u0027s call them C and S,\n with active Smack in the default state\n (no settings, no rules, no labeled hosts, only builtin labels)\n\n* At S, add Smack rule \u0027foo bar w\u0027\n (labels \u0027foo\u0027 and \u0027bar\u0027 are instantiated at S at this moment)\n\n* At S, at label \u0027bar\u0027, launch a program\n that listens for incoming tcp/ipv4 connections\n\n* From C, at label \u0027foo\u0027, connect to the listener at S.\n (label \u0027foo\u0027 is instantiated at C at this moment)\n Connection succeedes and works.\n\n* Send some data in both directions.\n* Collect network traffic of this connection.\n\nAll packets in both directions are labeled with the CIPSO\nof the label \u0027foo\u0027. Hence, label \u0027bar\u0027 writes to \u0027foo\u0027 without\nbeing authorized, and even without ever being known at C.\n\nIf anybody cares: exactly the same happens with DCCP.\n\nThis behavior 1st manifested in release 2.6.29.4 (see Fixes below)\nand it looks unintentional. At least, no explanation was provided.\n\nI changed returned packes label into the \u0027bar\u0027,\nto bring it into line with the Smack documentation claims."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 9.1,
"baseSeverity": "CRITICAL",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
"version": "3.1"
},
"scenarios": [
{
"lang": "en",
"value": "AV:N - The flaw is in the `inet_conn_request` LSM hook reached from `tcp_v4_route_req()`/`tcp_conn_request()` on receipt of a TCP/IPv4 SYN, plus the syncookie and DCCP paths, so a remote peer triggers it by connecting over routable IPv4. The attacker-supplied CIPSO tag in the incoming packet is what selects the wrong label, making the attack entirely remote and packet-driven.\nAC:L - The mislabeling is deterministic \u2014 no race, no memory-layout dependence, no timing window; every accepted TCP/IPv4 connection from a host absent from the netlabel host list (the default Smack state) is mislabeled. CIPSO labeling is enabled by default at smackfs init and the built-in labels are pre-populated, so no unusual tuning is needed beyond Smack being the active LSM.\nPR:N - The hook runs during SYN processing, before the three-way handshake completes and long before any application-level authentication, so the attacker holds no credentials on the target. The attacker further chooses the CIPSO label presented (e.g. the built-in `@`/web label, which `smk_access()` grants against any object), so no policy-granted standing is required either.\nUI:N - Exploitation needs only a listening socket on the target; no administrator or user on the victim system must open, mount, or click anything. The connection and all subsequent mislabeled traffic are driven entirely by the attacker.\nS:U - The mislabeling and the resulting authorization failure both occur within the kernel\u0027s Smack MAC enforcement, the same security authority that owns the vulnerable code. No virtualization, IOMMU, or hypervisor boundary is crossed.\nC:H - All data the server sends is stamped with an attacker-chosen label instead of the server process\u0027s real label, so the peer\u0027s receive-side `smk_access()` check and any CIPSO-aware network enforcement are bypassed and data from a confined or high-sensitivity domain is delivered to a domain with no authorization to read it. With the built-in `@` (web) label the emitted data becomes readable by every subject, a total loss of the confidentiality control for that connection.\nI:H - Because the reply packets carry the receiver\u0027s own label, `smk_access(skp, ssp-\u003esmk_in, MAY_WRITE)` is satisfied by Smack\u0027s unconditional same-label rule, so a policy rule forbidding the server domain from writing to the client domain is completely bypassed \u2014 the commit states \"\u0027bar\u0027 can write to \u0027foo\u0027 without being authorized to write.\" Arbitrary data is injected into a MAC domain that must not be written to, a total failure of the integrity control for that flow.\nA:N - The bug causes packets to carry the wrong security label; it produces no crash, oops, hang, deadlock, or resource exhaustion. Connections continue to operate normally \u2014 indeed more permissively than policy intends."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-05T11:39:15.379Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/d3f56c653c65f170b172d3c23120bc64ada645d8"
},
{
"url": "https://git.kernel.org/stable/c/5b4b304f196c070342e32a4752e1fa2e22fc0671"
},
{
"url": "https://git.kernel.org/stable/c/a948ec993541db4ef392b555c37a1186f4d61670"
},
{
"url": "https://git.kernel.org/stable/c/0aea09e82eafa50a373fc8a4b84c1d4734751e2c"
},
{
"url": "https://git.kernel.org/stable/c/0776bcf9cb6de46fdd94d10118de1cf9b05f83b9"
},
{
"url": "https://git.kernel.org/stable/c/4be9fd15c3c88775bdf6fa37acabe6de85beebff"
},
{
"url": "https://git.kernel.org/stable/c/d3703fa94116fed91f64c7d1c7d284fb4369070f"
},
{
"url": "https://git.kernel.org/stable/c/2fe209d0ad2e2729f7e22b9b31a86cc3ff0db550"
}
],
"title": "smack: tcp: ipv4, fix incorrect labeling",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2024-47659",
"datePublished": "2024-10-09T14:02:54.070Z",
"dateReserved": "2024-09-30T16:00:12.935Z",
"dateUpdated": "2026-08-05T11:39:15.379Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2024-47659",
"date": "2026-09-17",
"epss": "0.00775",
"percentile": "0.54095"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"security/smack/smack_lsm.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "d3f56c653c65f170b172d3c23120bc64ada645d8",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
},
{
"lessThan": "5b4b304f196c070342e32a4752e1fa2e22fc0671",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
},
{
"lessThan": "a948ec993541db4ef392b555c37a1186f4d61670",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
},
{
"lessThan": "0aea09e82eafa50a373fc8a4b84c1d4734751e2c",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
},
{
"lessThan": "0776bcf9cb6de46fdd94d10118de1cf9b05f83b9",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
},
{
"lessThan": "4be9fd15c3c88775bdf6fa37acabe6de85beebff",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
},
{
"lessThan": "d3703fa94116fed91f64c7d1c7d284fb4369070f",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
},
{
"lessThan": "2fe209d0ad2e2729f7e22b9b31a86cc3ff0db550",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"security/smack/smack_lsm.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "2.6.30"
},
{
"lessThan": "2.6.30",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "4.19.*",
"status": "unaffected",
"version": "4.19.322",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.4.*",
"status": "unaffected",
"version": "5.4.284",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.10.*",
"status": "unaffected",
"version": "5.10.226",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.15.*",
"status": "unaffected",
"version": "5.15.167",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.109",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.50",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.10.*",
"status": "unaffected",
"version": "6.10.9",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "6.11",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "29162FB8-5FA4-4DC4-86CE-5EB0CAEEF2F3",
"versionEndExcluding": "4.19.322",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "6265A402-9C3C-438F-BFC5-4194B2568B85",
"versionEndExcluding": "5.4.284",
"versionStartIncluding": "4.20",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "864FC17C-501A-4823-A643-6F35D65D8A97",
"versionEndExcluding": "5.10.226",
"versionStartIncluding": "5.5",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "043405A4-25FE-45D4-A7BB-2A0C3B7D17C1",
"versionEndExcluding": "5.15.167",
"versionStartIncluding": "5.11",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "790F505A-7933-48F1-B038-380A8BC5C153",
"versionEndExcluding": "6.1.109",
"versionStartIncluding": "5.16",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "A56A0460-B122-44D6-B0E6-26CE9C891536",
"versionEndExcluding": "6.6.50",
"versionStartIncluding": "6.2",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "F4469C96-A86B-4CC3-B2D5-C21B6B72641B",
"versionEndExcluding": "6.10.9",
"versionStartIncluding": "6.7",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsmack: tcp: ipv4, fix incorrect labeling\n\nCurrently, Smack mirrors the label of incoming tcp/ipv4 connections:\nwhen a label \u0027foo\u0027 connects to a label \u0027bar\u0027 with tcp/ipv4,\n\u0027foo\u0027 always gets \u0027foo\u0027 in returned ipv4 packets. So,\n1) returned packets are incorrectly labeled (\u0027foo\u0027 instead of \u0027bar\u0027)\n2) \u0027bar\u0027 can write to \u0027foo\u0027 without being authorized to write.\n\nHere is a scenario how to see this:\n\n* Take two machines, let\u0027s call them C and S,\n with active Smack in the default state\n (no settings, no rules, no labeled hosts, only builtin labels)\n\n* At S, add Smack rule \u0027foo bar w\u0027\n (labels \u0027foo\u0027 and \u0027bar\u0027 are instantiated at S at this moment)\n\n* At S, at label \u0027bar\u0027, launch a program\n that listens for incoming tcp/ipv4 connections\n\n* From C, at label \u0027foo\u0027, connect to the listener at S.\n (label \u0027foo\u0027 is instantiated at C at this moment)\n Connection succeedes and works.\n\n* Send some data in both directions.\n* Collect network traffic of this connection.\n\nAll packets in both directions are labeled with the CIPSO\nof the label \u0027foo\u0027. Hence, label \u0027bar\u0027 writes to \u0027foo\u0027 without\nbeing authorized, and even without ever being known at C.\n\nIf anybody cares: exactly the same happens with DCCP.\n\nThis behavior 1st manifested in release 2.6.29.4 (see Fixes below)\nand it looks unintentional. At least, no explanation was provided.\n\nI changed returned packes label into the \u0027bar\u0027,\nto bring it into line with the Smack documentation claims."
},
{
"lang": "es",
"value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: smack: tcp: ipv4, corregir etiquetado incorrecto Actualmente, Smack refleja la etiqueta de las conexiones entrantes tcp/ipv4: cuando una etiqueta \u0027foo\u0027 se conecta a una etiqueta \u0027bar\u0027 con tcp/ipv4, \u0027foo\u0027 siempre obtiene \u0027foo\u0027 en los paquetes ipv4 devueltos. Por lo tanto, 1) los paquetes devueltos est\u00e1n etiquetados incorrectamente (\u0027foo\u0027 en lugar de \u0027bar\u0027) 2) \u0027bar\u0027 puede escribir en \u0027foo\u0027 sin estar autorizado para escribir. Aqu\u00ed hay un escenario para ver esto: * Tome dos m\u00e1quinas, llam\u00e9moslas C y S, con Smack activo en el estado predeterminado (sin configuraciones, sin reglas, sin hosts etiquetados, solo etiquetas incorporadas) * En S, agregue la regla de Smack \u0027foo bar w\u0027 (las etiquetas \u0027foo\u0027 y \u0027bar\u0027 est\u00e1n instanciadas en S en este momento) * En S, en la etiqueta \u0027bar\u0027, inicie un programa que escuche conexiones entrantes tcp/ipv4 * Desde C, en la etiqueta \u0027foo\u0027, con\u00e9ctese al oyente en S. (la etiqueta \u0027foo\u0027 est\u00e1 instanciada en C en este momento) La conexi\u00f3n es exitosa y funciona. * Env\u00ede algunos datos en ambas direcciones. * Recolecte tr\u00e1fico de red de esta conexi\u00f3n. Todos los paquetes en ambas direcciones est\u00e1n etiquetados con el CIPSO de la etiqueta \u0027foo\u0027. Por lo tanto, la etiqueta \u0027bar\u0027 escribe en \u0027foo\u0027 sin estar autorizada, e incluso sin ser conocida en C. Si a alguien le importa: exactamente lo mismo sucede con DCCP. Este comportamiento se manifest\u00f3 por primera vez en la versi\u00f3n 2.6.29.4 (ver Correcciones a continuaci\u00f3n) y parece no ser intencional. Al menos, no se proporcion\u00f3 ninguna explicaci\u00f3n. Cambi\u00e9 la etiqueta de los paquetes devueltos por \"barra\" para que coincida con lo que afirma la documentaci\u00f3n de Smack."
}
],
"id": "CVE-2024-47659",
"lastModified": "2026-08-04T11:20:36.587",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 9.1,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.2,
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"type": "Secondary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 5.9,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2024-47659",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2024-10-10T13:23:30.727932Z",
"version": "2.0.3"
}
}
]
},
"published": "2024-10-09T14:15:07.660",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/0776bcf9cb6de46fdd94d10118de1cf9b05f83b9"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/0aea09e82eafa50a373fc8a4b84c1d4734751e2c"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/2fe209d0ad2e2729f7e22b9b31a86cc3ff0db550"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/4be9fd15c3c88775bdf6fa37acabe6de85beebff"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/5b4b304f196c070342e32a4752e1fa2e22fc0671"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/a948ec993541db4ef392b555c37a1186f4d61670"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/d3703fa94116fed91f64c7d1c7d284fb4369070f"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/d3f56c653c65f170b172d3c23120bc64ada645d8"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"url": "https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Modified",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "NVD-CWE-noinfo"
}
],
"source": "nvd@nist.gov",
"type": "Primary"
}
]
}
},
"redhat_vex": {
"aggregate_severity": "Important",
"current_release_date": "2026-08-05T03:21:13+00:00",
"cve": "CVE-2024-47659",
"id": "CVE-2024-47659",
"initial_release_date": "2024-10-09T00:00:00+00:00",
"product_status:known_not_affected": "198",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: smack: tcp: ipv4, fix incorrect labeling",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2024/cve-2024-47659.json",
"version": "3"
},
"vulnrichment": {
"containers": {
"adp": [
{
"providerMetadata": {
"dateUpdated": "2025-11-03T22:20:23.105Z",
"orgId": "af854a3a-2127-422b-91ae-364da2661108",
"shortName": "CVE"
},
"references": [
{
"url": "https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html"
}
],
"title": "CVE Program Container"
},
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2024-47659",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2024-10-10T13:23:30.727932Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2024-10-10T13:23:34.501Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"security/smack/smack_lsm.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "d3f56c653c65f170b172d3c23120bc64ada645d8",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
},
{
"lessThan": "5b4b304f196c070342e32a4752e1fa2e22fc0671",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
},
{
"lessThan": "a948ec993541db4ef392b555c37a1186f4d61670",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
},
{
"lessThan": "0aea09e82eafa50a373fc8a4b84c1d4734751e2c",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
},
{
"lessThan": "0776bcf9cb6de46fdd94d10118de1cf9b05f83b9",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
},
{
"lessThan": "4be9fd15c3c88775bdf6fa37acabe6de85beebff",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
},
{
"lessThan": "d3703fa94116fed91f64c7d1c7d284fb4369070f",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
},
{
"lessThan": "2fe209d0ad2e2729f7e22b9b31a86cc3ff0db550",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"security/smack/smack_lsm.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "2.6.30"
},
{
"lessThan": "2.6.30",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "4.19.*",
"status": "unaffected",
"version": "4.19.322",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.4.*",
"status": "unaffected",
"version": "5.4.284",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.10.*",
"status": "unaffected",
"version": "5.10.226",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.15.*",
"status": "unaffected",
"version": "5.15.167",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.109",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.50",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.10.*",
"status": "unaffected",
"version": "6.10.9",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "6.11",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "4.19.322",
"versionStartIncluding": "2.6.30",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.4.284",
"versionStartIncluding": "2.6.30",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.10.226",
"versionStartIncluding": "2.6.30",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.15.167",
"versionStartIncluding": "2.6.30",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.1.109",
"versionStartIncluding": "2.6.30",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.6.50",
"versionStartIncluding": "2.6.30",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.10.9",
"versionStartIncluding": "2.6.30",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.11",
"versionStartIncluding": "2.6.30",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsmack: tcp: ipv4, fix incorrect labeling\n\nCurrently, Smack mirrors the label of incoming tcp/ipv4 connections:\nwhen a label \u0027foo\u0027 connects to a label \u0027bar\u0027 with tcp/ipv4,\n\u0027foo\u0027 always gets \u0027foo\u0027 in returned ipv4 packets. So,\n1) returned packets are incorrectly labeled (\u0027foo\u0027 instead of \u0027bar\u0027)\n2) \u0027bar\u0027 can write to \u0027foo\u0027 without being authorized to write.\n\nHere is a scenario how to see this:\n\n* Take two machines, let\u0027s call them C and S,\n with active Smack in the default state\n (no settings, no rules, no labeled hosts, only builtin labels)\n\n* At S, add Smack rule \u0027foo bar w\u0027\n (labels \u0027foo\u0027 and \u0027bar\u0027 are instantiated at S at this moment)\n\n* At S, at label \u0027bar\u0027, launch a program\n that listens for incoming tcp/ipv4 connections\n\n* From C, at label \u0027foo\u0027, connect to the listener at S.\n (label \u0027foo\u0027 is instantiated at C at this moment)\n Connection succeedes and works.\n\n* Send some data in both directions.\n* Collect network traffic of this connection.\n\nAll packets in both directions are labeled with the CIPSO\nof the label \u0027foo\u0027. Hence, label \u0027bar\u0027 writes to \u0027foo\u0027 without\nbeing authorized, and even without ever being known at C.\n\nIf anybody cares: exactly the same happens with DCCP.\n\nThis behavior 1st manifested in release 2.6.29.4 (see Fixes below)\nand it looks unintentional. At least, no explanation was provided.\n\nI changed returned packes label into the \u0027bar\u0027,\nto bring it into line with the Smack documentation claims."
}
],
"providerMetadata": {
"dateUpdated": "2026-01-05T10:53:46.120Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/d3f56c653c65f170b172d3c23120bc64ada645d8"
},
{
"url": "https://git.kernel.org/stable/c/5b4b304f196c070342e32a4752e1fa2e22fc0671"
},
{
"url": "https://git.kernel.org/stable/c/a948ec993541db4ef392b555c37a1186f4d61670"
},
{
"url": "https://git.kernel.org/stable/c/0aea09e82eafa50a373fc8a4b84c1d4734751e2c"
},
{
"url": "https://git.kernel.org/stable/c/0776bcf9cb6de46fdd94d10118de1cf9b05f83b9"
},
{
"url": "https://git.kernel.org/stable/c/4be9fd15c3c88775bdf6fa37acabe6de85beebff"
},
{
"url": "https://git.kernel.org/stable/c/d3703fa94116fed91f64c7d1c7d284fb4369070f"
},
{
"url": "https://git.kernel.org/stable/c/2fe209d0ad2e2729f7e22b9b31a86cc3ff0db550"
}
],
"title": "smack: tcp: ipv4, fix incorrect labeling",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2024-47659",
"datePublished": "2024-10-09T14:02:54.070Z",
"dateReserved": "2024-09-30T16:00:12.935Z",
"dateUpdated": "2026-01-05T10:53:46.120Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
FKIE_CVE-2024-47659
Vulnerability from fkie_nvd - Published: 2024-10-09 14:15 - Updated: 2026-08-04 11:208.8 (High) - CVSS:3.1/
| Vendor | Product | Version | |
|---|---|---|---|
| linux | linux_kernel | * | |
| linux | linux_kernel | * | |
| linux | linux_kernel | * | |
| linux | linux_kernel | * | |
| linux | linux_kernel | * | |
| linux | linux_kernel | * | |
| linux | linux_kernel | * |
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"security/smack/smack_lsm.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "d3f56c653c65f170b172d3c23120bc64ada645d8",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
},
{
"lessThan": "5b4b304f196c070342e32a4752e1fa2e22fc0671",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
},
{
"lessThan": "a948ec993541db4ef392b555c37a1186f4d61670",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
},
{
"lessThan": "0aea09e82eafa50a373fc8a4b84c1d4734751e2c",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
},
{
"lessThan": "0776bcf9cb6de46fdd94d10118de1cf9b05f83b9",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
},
{
"lessThan": "4be9fd15c3c88775bdf6fa37acabe6de85beebff",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
},
{
"lessThan": "d3703fa94116fed91f64c7d1c7d284fb4369070f",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
},
{
"lessThan": "2fe209d0ad2e2729f7e22b9b31a86cc3ff0db550",
"status": "affected",
"version": "07feee8f812f7327a46186f7604df312c8c81962",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"security/smack/smack_lsm.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "2.6.30"
},
{
"lessThan": "2.6.30",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "4.19.*",
"status": "unaffected",
"version": "4.19.322",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.4.*",
"status": "unaffected",
"version": "5.4.284",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.10.*",
"status": "unaffected",
"version": "5.10.226",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.15.*",
"status": "unaffected",
"version": "5.15.167",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.109",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.50",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.10.*",
"status": "unaffected",
"version": "6.10.9",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "6.11",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "29162FB8-5FA4-4DC4-86CE-5EB0CAEEF2F3",
"versionEndExcluding": "4.19.322",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "6265A402-9C3C-438F-BFC5-4194B2568B85",
"versionEndExcluding": "5.4.284",
"versionStartIncluding": "4.20",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "864FC17C-501A-4823-A643-6F35D65D8A97",
"versionEndExcluding": "5.10.226",
"versionStartIncluding": "5.5",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "043405A4-25FE-45D4-A7BB-2A0C3B7D17C1",
"versionEndExcluding": "5.15.167",
"versionStartIncluding": "5.11",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "790F505A-7933-48F1-B038-380A8BC5C153",
"versionEndExcluding": "6.1.109",
"versionStartIncluding": "5.16",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "A56A0460-B122-44D6-B0E6-26CE9C891536",
"versionEndExcluding": "6.6.50",
"versionStartIncluding": "6.2",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "F4469C96-A86B-4CC3-B2D5-C21B6B72641B",
"versionEndExcluding": "6.10.9",
"versionStartIncluding": "6.7",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsmack: tcp: ipv4, fix incorrect labeling\n\nCurrently, Smack mirrors the label of incoming tcp/ipv4 connections:\nwhen a label \u0027foo\u0027 connects to a label \u0027bar\u0027 with tcp/ipv4,\n\u0027foo\u0027 always gets \u0027foo\u0027 in returned ipv4 packets. So,\n1) returned packets are incorrectly labeled (\u0027foo\u0027 instead of \u0027bar\u0027)\n2) \u0027bar\u0027 can write to \u0027foo\u0027 without being authorized to write.\n\nHere is a scenario how to see this:\n\n* Take two machines, let\u0027s call them C and S,\n with active Smack in the default state\n (no settings, no rules, no labeled hosts, only builtin labels)\n\n* At S, add Smack rule \u0027foo bar w\u0027\n (labels \u0027foo\u0027 and \u0027bar\u0027 are instantiated at S at this moment)\n\n* At S, at label \u0027bar\u0027, launch a program\n that listens for incoming tcp/ipv4 connections\n\n* From C, at label \u0027foo\u0027, connect to the listener at S.\n (label \u0027foo\u0027 is instantiated at C at this moment)\n Connection succeedes and works.\n\n* Send some data in both directions.\n* Collect network traffic of this connection.\n\nAll packets in both directions are labeled with the CIPSO\nof the label \u0027foo\u0027. Hence, label \u0027bar\u0027 writes to \u0027foo\u0027 without\nbeing authorized, and even without ever being known at C.\n\nIf anybody cares: exactly the same happens with DCCP.\n\nThis behavior 1st manifested in release 2.6.29.4 (see Fixes below)\nand it looks unintentional. At least, no explanation was provided.\n\nI changed returned packes label into the \u0027bar\u0027,\nto bring it into line with the Smack documentation claims."
},
{
"lang": "es",
"value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: smack: tcp: ipv4, corregir etiquetado incorrecto Actualmente, Smack refleja la etiqueta de las conexiones entrantes tcp/ipv4: cuando una etiqueta \u0027foo\u0027 se conecta a una etiqueta \u0027bar\u0027 con tcp/ipv4, \u0027foo\u0027 siempre obtiene \u0027foo\u0027 en los paquetes ipv4 devueltos. Por lo tanto, 1) los paquetes devueltos est\u00e1n etiquetados incorrectamente (\u0027foo\u0027 en lugar de \u0027bar\u0027) 2) \u0027bar\u0027 puede escribir en \u0027foo\u0027 sin estar autorizado para escribir. Aqu\u00ed hay un escenario para ver esto: * Tome dos m\u00e1quinas, llam\u00e9moslas C y S, con Smack activo en el estado predeterminado (sin configuraciones, sin reglas, sin hosts etiquetados, solo etiquetas incorporadas) * En S, agregue la regla de Smack \u0027foo bar w\u0027 (las etiquetas \u0027foo\u0027 y \u0027bar\u0027 est\u00e1n instanciadas en S en este momento) * En S, en la etiqueta \u0027bar\u0027, inicie un programa que escuche conexiones entrantes tcp/ipv4 * Desde C, en la etiqueta \u0027foo\u0027, con\u00e9ctese al oyente en S. (la etiqueta \u0027foo\u0027 est\u00e1 instanciada en C en este momento) La conexi\u00f3n es exitosa y funciona. * Env\u00ede algunos datos en ambas direcciones. * Recolecte tr\u00e1fico de red de esta conexi\u00f3n. Todos los paquetes en ambas direcciones est\u00e1n etiquetados con el CIPSO de la etiqueta \u0027foo\u0027. Por lo tanto, la etiqueta \u0027bar\u0027 escribe en \u0027foo\u0027 sin estar autorizada, e incluso sin ser conocida en C. Si a alguien le importa: exactamente lo mismo sucede con DCCP. Este comportamiento se manifest\u00f3 por primera vez en la versi\u00f3n 2.6.29.4 (ver Correcciones a continuaci\u00f3n) y parece no ser intencional. Al menos, no se proporcion\u00f3 ninguna explicaci\u00f3n. Cambi\u00e9 la etiqueta de los paquetes devueltos por \"barra\" para que coincida con lo que afirma la documentaci\u00f3n de Smack."
}
],
"id": "CVE-2024-47659",
"lastModified": "2026-08-04T11:20:36.587",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 9.1,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.2,
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"type": "Secondary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 5.9,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2024-47659",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2024-10-10T13:23:30.727932Z",
"version": "2.0.3"
}
}
]
},
"published": "2024-10-09T14:15:07.660",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/0776bcf9cb6de46fdd94d10118de1cf9b05f83b9"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/0aea09e82eafa50a373fc8a4b84c1d4734751e2c"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/2fe209d0ad2e2729f7e22b9b31a86cc3ff0db550"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/4be9fd15c3c88775bdf6fa37acabe6de85beebff"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/5b4b304f196c070342e32a4752e1fa2e22fc0671"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/a948ec993541db4ef392b555c37a1186f4d61670"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/d3703fa94116fed91f64c7d1c7d284fb4369070f"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/d3f56c653c65f170b172d3c23120bc64ada645d8"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"url": "https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Modified",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "NVD-CWE-noinfo"
}
],
"source": "nvd@nist.gov",
"type": "Primary"
}
]
}
GHSA-753J-68H2-88XF
Vulnerability from github – Published: 2024-10-09 15:32 – Updated: 2025-11-04 00:31In the Linux kernel, the following vulnerability has been resolved:
smack: tcp: ipv4, fix incorrect labeling
Currently, Smack mirrors the label of incoming tcp/ipv4 connections: when a label 'foo' connects to a label 'bar' with tcp/ipv4, 'foo' always gets 'foo' in returned ipv4 packets. So, 1) returned packets are incorrectly labeled ('foo' instead of 'bar') 2) 'bar' can write to 'foo' without being authorized to write.
Here is a scenario how to see this:
-
Take two machines, let's call them C and S, with active Smack in the default state (no settings, no rules, no labeled hosts, only builtin labels)
-
At S, add Smack rule 'foo bar w' (labels 'foo' and 'bar' are instantiated at S at this moment)
-
At S, at label 'bar', launch a program that listens for incoming tcp/ipv4 connections
-
From C, at label 'foo', connect to the listener at S. (label 'foo' is instantiated at C at this moment) Connection succeedes and works.
-
Send some data in both directions.
- Collect network traffic of this connection.
All packets in both directions are labeled with the CIPSO of the label 'foo'. Hence, label 'bar' writes to 'foo' without being authorized, and even without ever being known at C.
If anybody cares: exactly the same happens with DCCP.
This behavior 1st manifested in release 2.6.29.4 (see Fixes below) and it looks unintentional. At least, no explanation was provided.
I changed returned packes label into the 'bar', to bring it into line with the Smack documentation claims.
{
"affected": [],
"aliases": [
"CVE-2024-47659"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-10-09T14:15:07Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nsmack: tcp: ipv4, fix incorrect labeling\n\nCurrently, Smack mirrors the label of incoming tcp/ipv4 connections:\nwhen a label \u0027foo\u0027 connects to a label \u0027bar\u0027 with tcp/ipv4,\n\u0027foo\u0027 always gets \u0027foo\u0027 in returned ipv4 packets. So,\n1) returned packets are incorrectly labeled (\u0027foo\u0027 instead of \u0027bar\u0027)\n2) \u0027bar\u0027 can write to \u0027foo\u0027 without being authorized to write.\n\nHere is a scenario how to see this:\n\n* Take two machines, let\u0027s call them C and S,\n with active Smack in the default state\n (no settings, no rules, no labeled hosts, only builtin labels)\n\n* At S, add Smack rule \u0027foo bar w\u0027\n (labels \u0027foo\u0027 and \u0027bar\u0027 are instantiated at S at this moment)\n\n* At S, at label \u0027bar\u0027, launch a program\n that listens for incoming tcp/ipv4 connections\n\n* From C, at label \u0027foo\u0027, connect to the listener at S.\n (label \u0027foo\u0027 is instantiated at C at this moment)\n Connection succeedes and works.\n\n* Send some data in both directions.\n* Collect network traffic of this connection.\n\nAll packets in both directions are labeled with the CIPSO\nof the label \u0027foo\u0027. Hence, label \u0027bar\u0027 writes to \u0027foo\u0027 without\nbeing authorized, and even without ever being known at C.\n\nIf anybody cares: exactly the same happens with DCCP.\n\nThis behavior 1st manifested in release 2.6.29.4 (see Fixes below)\nand it looks unintentional. At least, no explanation was provided.\n\nI changed returned packes label into the \u0027bar\u0027,\nto bring it into line with the Smack documentation claims.",
"id": "GHSA-753j-68h2-88xf",
"modified": "2025-11-04T00:31:33Z",
"published": "2024-10-09T15:32:20Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47659"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/0776bcf9cb6de46fdd94d10118de1cf9b05f83b9"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/0aea09e82eafa50a373fc8a4b84c1d4734751e2c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/2fe209d0ad2e2729f7e22b9b31a86cc3ff0db550"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/4be9fd15c3c88775bdf6fa37acabe6de85beebff"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5b4b304f196c070342e32a4752e1fa2e22fc0671"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a948ec993541db4ef392b555c37a1186f4d61670"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d3703fa94116fed91f64c7d1c7d284fb4369070f"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d3f56c653c65f170b172d3c23120bc64ada645d8"
},
{
"type": "WEB",
"url": "https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
ICSA-25-226-07
Vulnerability from csaf_cisa - Published: 2025-08-12 00:00 - Updated: 2026-02-25 07:00OESA-2024-2325 (CVE-2023-52917)
Vulnerability from osv_openeuler – Published: 2024-11-01 11:07 – Updated: 2026-08-06 11:07 – Source websiteThe Linux Kernel, the operating system core itself.
Security Fix(es):
In the Linux kernel, the following vulnerability has been resolved: ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir() The debugfs_create_dir() function returns error pointers. It never returns NULL. So use IS_ERR() to check it.(CVE-2023-52917)
In the Linux kernel, the following vulnerability has been resolved: media: pci: cx23885: check cx23885_vdev_init() return cx23885_vdev_init() can return a NULL pointer, but that pointer is used in the next line without a check. Add a NULL pointer check and go to the error unwind if it is NULL.(CVE-2023-52918)
In the Linux kernel, the following vulnerability has been resolved:
btrfs: make sure that WRITTEN is set on all metadata blocks
We previously would call btrfs_check_leaf() if we had the check integrity code enabled, which meant that we could only run the extended leaf checks if we had WRITTEN set on the header flags.
This leaves a gap in our checking, because we could end up with corruption on disk where WRITTEN isn't set on the leaf, and then the extended leaf checks don't get run which we rely on to validate all of the item pointers to make sure we don't access memory outside of the extent buffer.
However, since 732fab95abe2 ("btrfs: check-integrity: remove CONFIG_BTRFS_FS_CHECK_INTEGRITY option") we no longer call btrfs_check_leaf() from btrfs_mark_buffer_dirty(), which means we only ever call it on blocks that are being written out, and thus have WRITTEN set, or that are being read in, which should have WRITTEN set.
Add checks to make sure we have WRITTEN set appropriately, and then make sure __btrfs_check_leaf() always does the item checking. This will protect us from file systems that have been corrupted and no longer have WRITTEN set on some of the blocks.
This was hit on a crafted image tweaking the WRITTEN bit and reported by KASAN as out-of-bound access in the eb accessors. The example is a dir item at the end of an eb.
[2.042] BTRFS warning (device loop1): bad eb member start: ptr 0x3fff start 30572544 member offset 16410 size 2 [2.040] general protection fault, probably for non-canonical address 0xe0009d1000000003: 0000 [#1] PREEMPT SMP KASAN NOPTI [2.537] KASAN: maybe wild-memory-access in range [0x0005088000000018-0x000508800000001f] [2.729] CPU: 0 PID: 2587 Comm: mount Not tainted 6.8.2 #1 [2.729] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 [2.621] RIP: 0010:btrfs_get_16+0x34b/0x6d0 [2.621] RSP: 0018:ffff88810871fab8 EFLAGS: 00000206 [2.621] RAX: 0000a11000000003 RBX: ffff888104ff8720 RCX: ffff88811b2288c0 [2.621] RDX: dffffc0000000000 RSI: ffffffff81dd8aca RDI: ffff88810871f748 [2.621] RBP: 000000000000401a R08: 0000000000000001 R09: ffffed10210e3ee9 [2.621] R10: ffff88810871f74f R11: 205d323430333737 R12: 000000000000001a [2.621] R13: 000508800000001a R14: 1ffff110210e3f5d R15: ffffffff850011e8 [2.621] FS: 00007f56ea275840(0000) GS:ffff88811b200000(0000) knlGS:0000000000000000 [2.621] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [2.621] CR2: 00007febd13b75c0 CR3: 000000010bb50000 CR4: 00000000000006f0 [2.621] Call Trace: [2.621] <TASK> [2.621] ? show_regs+0x74/0x80 [2.621] ? die_addr+0x46/0xc0 [2.621] ? exc_general_protection+0x161/0x2a0 [2.621] ? asm_exc_general_protection+0x26/0x30 [2.621] ? btrfs_get_16+0x33a/0x6d0 [2.621] ? btrfs_get_16+0x34b/0x6d0 [2.621] ? btrfs_get_16+0x33a/0x6d0 [2.621] ? __pfx_btrfs_get_16+0x10/0x10 [2.621] ? __pfx_mutex_unlock+0x10/0x10 [2.621] btrfs_match_dir_item_name+0x101/0x1a0 [2.621] btrfs_lookup_dir_item+0x1f3/0x280 [2.621] ? __pfx_btrfs_lookup_dir_item+0x10/0x10 [2.621] btrfs_get_tree+0xd25/0x1910
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: ISO: Fix not validating setsockopt user input
Check user input length before copying data.(CVE-2024-35964)
In the Linux kernel, the following vulnerability has been resolved:
iommu/arm-smmu: Use the correct type in nvidia_smmu_context_fault()
This was missed because of the function pointer indirection.
nvidia_smmu_context_fault() is also installed as a irq function, and the 'void *' was changed to a struct arm_smmu_domain. Since the iommu_domain is embedded at a non-zero offset this causes nvidia_smmu_context_fault() to miscompute the offset. Fixup the types.
Unable to handle kernel NULL pointer dereference at virtual address 0000000000000120 Mem abort info: ESR = 0x0000000096000004 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x04: level 0 translation fault Data abort info: ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000 CM = 0, WnR = 0, TnD = 0, TagAccess = 0 GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 user pgtable: 4k pages, 48-bit VAs, pgdp=0000000107c9f000 [0000000000000120] pgd=0000000000000000, p4d=0000000000000000 Internal error: Oops: 0000000096000004 [#1] SMP Modules linked in: CPU: 1 PID: 47 Comm: kworker/u25:0 Not tainted 6.9.0-0.rc7.58.eln136.aarch64 #1 Hardware name: Unknown NVIDIA Jetson Orin NX/NVIDIA Jetson Orin NX, BIOS 3.1-32827747 03/19/2023 Workqueue: events_unbound deferred_probe_work_func pstate: 604000c9 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : nvidia_smmu_context_fault+0x1c/0x158 lr : __free_irq+0x1d4/0x2e8 sp : ffff80008044b6f0 x29: ffff80008044b6f0 x28: ffff000080a60b18 x27: ffffd32b5172e970 x26: 0000000000000000 x25: ffff0000802f5aac x24: ffff0000802f5a30 x23: ffff0000802f5b60 x22: 0000000000000057 x21: 0000000000000000 x20: ffff0000802f5a00 x19: ffff000087d4cd80 x18: ffffffffffffffff x17: 6234362066666666 x16: 6630303078302d30 x15: ffff00008156d888 x14: 0000000000000000 x13: ffff0000801db910 x12: ffff00008156d6d0 x11: 0000000000000003 x10: ffff0000801db918 x9 : ffffd32b50f94d9c x8 : 1fffe0001032fda1 x7 : ffff00008197ed00 x6 : 000000000000000f x5 : 000000000000010e x4 : 000000000000010e x3 : 0000000000000000 x2 : ffffd32b51720cd8 x1 : ffff000087e6f700 x0 : 0000000000000057 Call trace: nvidia_smmu_context_fault+0x1c/0x158 __free_irq+0x1d4/0x2e8 free_irq+0x3c/0x80 devm_free_irq+0x64/0xa8 arm_smmu_domain_free+0xc4/0x158 iommu_domain_free+0x44/0xa0 iommu_deinit_device+0xd0/0xf8 __iommu_group_remove_device+0xcc/0xe0 iommu_bus_notifier+0x64/0xa8 notifier_call_chain+0x78/0x148 blocking_notifier_call_chain+0x4c/0x90 bus_notify+0x44/0x70 device_del+0x264/0x3e8 pci_remove_bus_device+0x84/0x120 pci_remove_root_bus+0x5c/0xc0 dw_pcie_host_deinit+0x38/0xe0 tegra_pcie_config_rp+0xc0/0x1f0 tegra_pcie_dw_probe+0x34c/0x700 platform_probe+0x70/0xe8 really_probe+0xc8/0x3a0 __driver_probe_device+0x84/0x160 driver_probe_device+0x44/0x130 __device_attach_driver+0xc4/0x170 bus_for_each_drv+0x90/0x100 __device_attach+0xa8/0x1c8 device_initial_probe+0x1c/0x30 bus_probe_device+0xb0/0xc0 deferred_probe_work_func+0xbc/0x120 process_one_work+0x194/0x490 worker_thread+0x284/0x3b0 kthread+0xf4/0x108 ret_from_fork+0x10/0x20 Code: a9b97bfd 910003fd a9025bf5 f85a0035 (b94122a1)(CVE-2024-36884)
In the Linux kernel, the following vulnerability has been resolved:
dev/parport: fix the array out-of-bounds risk
Fixed array out-of-bounds issues caused by sprintf by replacing it with snprintf for safer data copying, ensuring the destination buffer is not overflowed.
Below is the stack trace I encountered during the actual issue:
[ 66.575408s] [pid:5118,cpu4,QThread,4]Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: do_hardware_base_addr+0xcc/0xd0 [parport] [ 66.575408s] [pid:5118,cpu4,QThread,5]CPU: 4 PID: 5118 Comm: QThread Tainted: G S W O 5.10.97-arm64-desktop #7100.57021.2 [ 66.575439s] [pid:5118,cpu4,QThread,6]TGID: 5087 Comm: EFileApp [ 66.575439s] [pid:5118,cpu4,QThread,7]Hardware name: HUAWEI HUAWEI QingYun PGUX-W515x-B081/SP1PANGUXM, BIOS 1.00.07 04/29/2024 [ 66.575439s] [pid:5118,cpu4,QThread,8]Call trace: [ 66.575469s] [pid:5118,cpu4,QThread,9] dump_backtrace+0x0/0x1c0 [ 66.575469s] [pid:5118,cpu4,QThread,0] show_stack+0x14/0x20 [ 66.575469s] [pid:5118,cpu4,QThread,1] dump_stack+0xd4/0x10c [ 66.575500s] [pid:5118,cpu4,QThread,2] panic+0x1d8/0x3bc [ 66.575500s] [pid:5118,cpu4,QThread,3] __stack_chk_fail+0x2c/0x38 [ 66.575500s] [pid:5118,cpu4,QThread,4] do_hardware_base_addr+0xcc/0xd0 parport
In the Linux kernel, the following vulnerability has been resolved:
jfs: Fix array-index-out-of-bounds in diFree(CVE-2024-43858)
In the Linux kernel, the following vulnerability has been resolved:
drm/nouveau: prime: fix refcount underflow
Calling nouveau_bo_ref() on a nouveau_bo without initializing it (and hence the backing ttm_bo) leads to a refcount underflow.
Instead of calling nouveau_bo_ref() in the unwind path of drm_gem_object_init(), clean things up manually.
(cherry picked from commit 1b93f3e89d03cfc576636e195466a0d728ad8de5)(CVE-2024-43867)
In the Linux kernel, the following vulnerability has been resolved:
devres: Fix memory leakage caused by driver API devm_free_percpu()
It will cause memory leakage when use driver API devm_free_percpu() to free memory allocated by devm_alloc_percpu(), fixed by using devres_release() instead of devres_destroy() within devm_free_percpu().(CVE-2024-43871)
In the Linux kernel, the following vulnerability has been resolved:
drm/msm/dpu: cleanup FB if dpu_format_populate_layout fails
If the dpu_format_populate_layout() fails, then FB is prepared, but not cleaned up. This ends up leaking the pin_count on the GEM object and causes a splat during DRM file closure:
msm_obj->pin_count WARNING: CPU: 2 PID: 569 at drivers/gpu/drm/msm/msm_gem.c:121 update_lru_locked+0xc4/0xcc [...] Call trace: update_lru_locked+0xc4/0xcc put_pages+0xac/0x100 msm_gem_free_object+0x138/0x180 drm_gem_object_free+0x1c/0x30 drm_gem_object_handle_put_unlocked+0x108/0x10c drm_gem_object_release_handle+0x58/0x70 idr_for_each+0x68/0xec drm_gem_release+0x28/0x40 drm_file_free+0x174/0x234 drm_release+0xb0/0x160 __fput+0xc0/0x2c8 __fput_sync+0x50/0x5c __arm64_sys_close+0x38/0x7c invoke_syscall+0x48/0x118 el0_svc_common.constprop.0+0x40/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x4c/0x120 el0t_64_sync_handler+0x100/0x12c el0t_64_sync+0x190/0x194 irq event stamp: 129818 hardirqs last enabled at (129817): [<ffffa5f6d953fcc0>] console_unlock+0x118/0x124 hardirqs last disabled at (129818): [<ffffa5f6da7dcf04>] el1_dbg+0x24/0x8c softirqs last enabled at (129808): [<ffffa5f6d94afc18>] handle_softirqs+0x4c8/0x4e8 softirqs last disabled at (129785): [<ffffa5f6d94105e4>] __do_softirq+0x14/0x20
Patchwork: https://patchwork.freedesktop.org/patch/600714/(CVE-2024-44982)
In the Linux kernel, the following vulnerability has been resolved:
net: ethernet: mtk_wed: fix use-after-free panic in mtk_wed_setup_tc_block_cb()
When there are multiple ap interfaces on one band and with WED on, turning the interface down will cause a kernel panic on MT798X.
Previously, cb_priv was freed in mtk_wed_setup_tc_block() without marking NULL,and mtk_wed_setup_tc_block_cb() didn't check the value, too.
Assign NULL after free cb_priv in mtk_wed_setup_tc_block() and check NULL in mtk_wed_setup_tc_block_cb().
Unable to handle kernel paging request at virtual address 0072460bca32b4f5 Call trace: mtk_wed_setup_tc_block_cb+0x4/0x38 0xffffffc0794084bc tcf_block_playback_offloads+0x70/0x1e8 tcf_block_unbind+0x6c/0xc8 ... ---------(CVE-2024-44997)
In the Linux kernel, the following vulnerability has been resolved:
usb: dwc3: core: Prevent USB core invalid event buffer address access
This commit addresses an issue where the USB core could access an invalid event buffer address during runtime suspend, potentially causing SMMU faults and other memory issues in Exynos platforms. The problem arises from the following sequence. 1. In dwc3_gadget_suspend, there is a chance of a timeout when moving the USB core to the halt state after clearing the run/stop bit by software. 2. In dwc3_core_exit, the event buffer is cleared regardless of the USB core's status, which may lead to an SMMU faults and other memory issues. if the USB core tries to access the event buffer address.
To prevent this hardware quirk on Exynos platforms, this commit ensures that the event buffer address is not cleared by software when the USB core is active during runtime suspend by checking its status before clearing the buffer address.(CVE-2024-46675)
In the Linux kernel, the following vulnerability has been resolved:
gtp: fix a potential NULL pointer dereference
When sockfd_lookup() fails, gtp_encap_enable_socket() returns a NULL pointer, but its callers only check for error pointers thus miss the NULL pointer case.
Fix it by returning an error pointer with the error code carried from sockfd_lookup().
(I found this bug during code inspection.)(CVE-2024-46677)
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number
Check the fb_channel_number range to avoid the array out-of-bounds read error(CVE-2024-46724)
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: btnxpuart: Fix Null pointer dereference in btnxpuart_flush()
This adds a check before freeing the rx->skb in flush and close functions to handle the kernel crash seen while removing driver after FW download fails or before FW download completes.
dmesg log: [ 54.634586] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000080 [ 54.643398] Mem abort info: [ 54.646204] ESR = 0x0000000096000004 [ 54.649964] EC = 0x25: DABT (current EL), IL = 32 bits [ 54.655286] SET = 0, FnV = 0 [ 54.658348] EA = 0, S1PTW = 0 [ 54.661498] FSC = 0x04: level 0 translation fault [ 54.666391] Data abort info: [ 54.669273] ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000 [ 54.674768] CM = 0, WnR = 0, TnD = 0, TagAccess = 0 [ 54.674771] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [ 54.674775] user pgtable: 4k pages, 48-bit VAs, pgdp=0000000048860000 [ 54.674780] [0000000000000080] pgd=0000000000000000, p4d=0000000000000000 [ 54.703880] Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP [ 54.710152] Modules linked in: btnxpuart(-) overlay fsl_jr_uio caam_jr caamkeyblob_desc caamhash_desc caamalg_desc crypto_engine authenc libdes crct10dif_ce polyval_ce polyval_generic snd_soc_imx_spdif snd_soc_imx_card snd_soc_ak5558 snd_soc_ak4458 caam secvio error snd_soc_fsl_micfil snd_soc_fsl_spdif snd_soc_fsl_sai snd_soc_fsl_utils imx_pcm_dma gpio_ir_recv rc_core sch_fq_codel fuse [ 54.744357] CPU: 3 PID: 72 Comm: kworker/u9:0 Not tainted 6.6.3-otbr-g128004619037 #2 [ 54.744364] Hardware name: FSL i.MX8MM EVK board (DT) [ 54.744368] Workqueue: hci0 hci_power_on [ 54.757244] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 54.757249] pc : kfree_skb_reason+0x18/0xb0 [ 54.772299] lr : btnxpuart_flush+0x40/0x58 [btnxpuart] [ 54.782921] sp : ffff8000805ebca0 [ 54.782923] x29: ffff8000805ebca0 x28: ffffa5c6cf1869c0 x27: ffffa5c6cf186000 [ 54.782931] x26: ffff377b84852400 x25: ffff377b848523c0 x24: ffff377b845e7230 [ 54.782938] x23: ffffa5c6ce8dbe08 x22: ffffa5c6ceb65410 x21: 00000000ffffff92 [ 54.782945] x20: ffffa5c6ce8dbe98 x19: ffffffffffffffac x18: ffffffffffffffff [ 54.807651] x17: 0000000000000000 x16: ffffa5c6ce2824ec x15: ffff8001005eb857 [ 54.821917] x14: 0000000000000000 x13: ffffa5c6cf1a02e0 x12: 0000000000000642 [ 54.821924] x11: 0000000000000040 x10: ffffa5c6cf19d690 x9 : ffffa5c6cf19d688 [ 54.821931] x8 : ffff377b86000028 x7 : 0000000000000000 x6 : 0000000000000000 [ 54.821938] x5 : ffff377b86000000 x4 : 0000000000000000 x3 : 0000000000000000 [ 54.843331] x2 : 0000000000000000 x1 : 0000000000000002 x0 : ffffffffffffffac [ 54.857599] Call trace: [ 54.857601] kfree_skb_reason+0x18/0xb0 [ 54.863878] btnxpuart_flush+0x40/0x58 [btnxpuart] [ 54.863888] hci_dev_open_sync+0x3a8/0xa04 [ 54.872773] hci_power_on+0x54/0x2e4 [ 54.881832] process_one_work+0x138/0x260 [ 54.881842] worker_thread+0x32c/0x438 [ 54.881847] kthread+0x118/0x11c [ 54.881853] ret_from_fork+0x10/0x20 [ 54.896406] Code: a9be7bfd 910003fd f9000bf3 aa0003f3 (b940d400) [ 54.896410] ---[ end trace 0000000000000000 ]---(CVE-2024-46749)
In the Linux kernel, the following vulnerability has been resolved:
hwmon: (nct6775-core) Fix underflows seen when writing limit attributes
DIV_ROUND_CLOSEST() after kstrtol() results in an underflow if a large negative number such as -9223372036854775808 is provided by the user. Fix it by reordering clamp_val() and DIV_ROUND_CLOSEST() operations.(CVE-2024-46757)
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Validate function returns
[WHAT & HOW] Function return values must be checked before data can be used in subsequent functions.
This fixes 4 CHECKED_RETURN issues reported by Coverity.(CVE-2024-46775)
In the Linux kernel, the following vulnerability has been resolved:
ila: call nf_unregister_net_hooks() sooner
syzbot found an use-after-free Read in ila_nf_input [1]
Issue here is that ila_xlat_exit_net() frees the rhashtable, then call nf_unregister_net_hooks().
It should be done in the reverse way, with a synchronize_rcu().
This is a good match for a pre_exit() method.
[1] BUG: KASAN: use-after-free in rht_key_hashfn include/linux/rhashtable.h:159 [inline] BUG: KASAN: use-after-free in __rhashtable_lookup include/linux/rhashtable.h:604 [inline] BUG: KASAN: use-after-free in rhashtable_lookup include/linux/rhashtable.h:646 [inline] BUG: KASAN: use-after-free in rhashtable_lookup_fast+0x77a/0x9b0 include/linux/rhashtable.h:672 Read of size 4 at addr ffff888064620008 by task ksoftirqd/0/16
CPU: 0 UID: 0 PID: 16 Comm: ksoftirqd/0 Not tainted 6.11.0-rc4-syzkaller-00238-g2ad6d23f465a #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 Call Trace: <TASK> __dump_stack lib/dump_stack.c:93 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119 print_address_description mm/kasan/report.c:377 [inline] print_report+0x169/0x550 mm/kasan/report.c:488 kasan_report+0x143/0x180 mm/kasan/report.c:601 rht_key_hashfn include/linux/rhashtable.h:159 [inline] __rhashtable_lookup include/linux/rhashtable.h:604 [inline] rhashtable_lookup include/linux/rhashtable.h:646 [inline] rhashtable_lookup_fast+0x77a/0x9b0 include/linux/rhashtable.h:672 ila_lookup_wildcards net/ipv6/ila/ila_xlat.c:132 [inline] ila_xlat_addr net/ipv6/ila/ila_xlat.c:652 [inline] ila_nf_input+0x1fe/0x3c0 net/ipv6/ila/ila_xlat.c:190 nf_hook_entry_hookfn include/linux/netfilter.h:154 [inline] nf_hook_slow+0xc3/0x220 net/netfilter/core.c:626 nf_hook include/linux/netfilter.h:269 [inline] NF_HOOK+0x29e/0x450 include/linux/netfilter.h:312 __netif_receive_skb_one_core net/core/dev.c:5661 [inline] __netif_receive_skb+0x1ea/0x650 net/core/dev.c:5775 process_backlog+0x662/0x15b0 net/core/dev.c:6108 __napi_poll+0xcb/0x490 net/core/dev.c:6772 napi_poll net/core/dev.c:6841 [inline] net_rx_action+0x89b/0x1240 net/core/dev.c:6963 handle_softirqs+0x2c4/0x970 kernel/softirq.c:554 run_ksoftirqd+0xca/0x130 kernel/softirq.c:928 smpboot_thread_fn+0x544/0xa30 kernel/smpboot.c:164 kthread+0x2f0/0x390 kernel/kthread.c:389 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 </TASK>
The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x64620 flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff) page_type: 0xbfffffff(buddy) raw: 00fff00000000000 ffffea0000959608 ffffea00019d9408 0000000000000000 raw: 0000000000000000 0000000000000003 00000000bfffffff 0000000000000000 page dumped because: kasan: bad access detected page_owner tracks the page as freed page last allocated via order 3, migratetype Unmovable, gfp_mask 0x52dc0(GFP_KERNEL|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_ZERO), pid 5242, tgid 5242 (syz-executor), ts 73611328570, free_ts 618981657187 set_page_owner include/linux/page_owner.h:32 [inline] post_alloc_hook+0x1f3/0x230 mm/page_alloc.c:1493 prep_new_page mm/page_alloc.c:1501 [inline] get_page_from_freelist+0x2e4c/0x2f10 mm/page_alloc.c:3439 __alloc_pages_noprof+0x256/0x6c0 mm/page_alloc.c:4695 __alloc_pages_node_noprof include/linux/gfp.h:269 [inline] alloc_pages_node_noprof include/linux/gfp.h:296 [inline] kmalloclarge_node+0x8b/0x1d0 mm/slub.c:4103 kmalloc_large_node_noprof+0x1a/0x80 mm/slub.c:4130 __do_kmalloc_node mm/slub.c:4146 [inline] __kmalloc_node_noprof+0x2d2/0x440 mm/slub.c:4164 __kvmalloc_node_noprof+0x72/0x190 mm/util.c:650 bucket_table_alloc lib/rhashtable.c:186 [inline] rhashtable_init_noprof+0x534/0xa60 lib/rhashtable.c:1071 ila_xlat_init_net+0xa0/0x110 net/ipv6/ila/ila_xlat.c:613 ops_ini ---truncated---(CVE-2024-46782)
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: added NULL check at start of dc_validate_stream
[Why] prevent invalid memory access
[How] check if dc and stream are NULL(CVE-2024-46802)
In the Linux kernel, the following vulnerability has been resolved:
spi: nxp-fspi: fix the KASAN report out-of-bounds bug
Change the memcpy length to fix the out-of-bounds issue when writing the data that is not 4 byte aligned to TX FIFO.
To reproduce the issue, write 3 bytes data to NOR chip.
dd if=3b of=/dev/mtd0 [ 36.926103] ================================================================== [ 36.933409] BUG: KASAN: slab-out-of-bounds in nxp_fspi_exec_op+0x26ec/0x2838 [ 36.940514] Read of size 4 at addr ffff00081037c2a0 by task dd/455 [ 36.946721] [ 36.948235] CPU: 3 UID: 0 PID: 455 Comm: dd Not tainted 6.11.0-rc5-gc7b0e37c8434 #1070 [ 36.956185] Hardware name: Freescale i.MX8QM MEK (DT) [ 36.961260] Call trace: [ 36.963723] dump_backtrace+0x90/0xe8 [ 36.967414] show_stack+0x18/0x24 [ 36.970749] dump_stack_lvl+0x78/0x90 [ 36.974451] print_report+0x114/0x5cc [ 36.978151] kasan_report+0xa4/0xf0 [ 36.981670] __asan_report_load_n_noabort+0x1c/0x28 [ 36.986587] nxp_fspi_exec_op+0x26ec/0x2838 [ 36.990800] spi_mem_exec_op+0x8ec/0xd30 [ 36.994762] spi_mem_no_dirmap_read+0x190/0x1e0 [ 36.999323] spi_mem_dirmap_write+0x238/0x32c [ 37.003710] spi_nor_write_data+0x220/0x374 [ 37.007932] spi_nor_write+0x110/0x2e8 [ 37.011711] mtd_write_oob_std+0x154/0x1f0 [ 37.015838] mtd_write_oob+0x104/0x1d0 [ 37.019617] mtd_write+0xb8/0x12c [ 37.022953] mtdchar_write+0x224/0x47c [ 37.026732] vfs_write+0x1e4/0x8c8 [ 37.030163] ksys_write+0xec/0x1d0 [ 37.033586] __arm64_sys_write+0x6c/0x9c [ 37.037539] invoke_syscall+0x6c/0x258 [ 37.041327] el0_svc_common.constprop.0+0x160/0x22c [ 37.046244] do_el0_svc+0x44/0x5c [ 37.049589] el0_svc+0x38/0x78 [ 37.052681] el0t_64_sync_handler+0x13c/0x158 [ 37.057077] el0t_64_sync+0x190/0x194 [ 37.060775] [ 37.062274] Allocated by task 455: [ 37.065701] kasan_save_stack+0x2c/0x54 [ 37.069570] kasan_save_track+0x20/0x3c [ 37.073438] kasan_save_alloc_info+0x40/0x54 [ 37.077736] __kasan_kmalloc+0xa0/0xb8 [ 37.081515] __kmalloc_noprof+0x158/0x2f8 [ 37.085563] mtd_kmalloc_up_to+0x120/0x154 [ 37.089690] mtdchar_write+0x130/0x47c [ 37.093469] vfs_write+0x1e4/0x8c8 [ 37.096901] ksys_write+0xec/0x1d0 [ 37.100332] __arm64_sys_write+0x6c/0x9c [ 37.104287] invoke_syscall+0x6c/0x258 [ 37.108064] el0_svc_common.constprop.0+0x160/0x22c [ 37.112972] do_el0_svc+0x44/0x5c [ 37.116319] el0_svc+0x38/0x78 [ 37.119401] el0t_64_sync_handler+0x13c/0x158 [ 37.123788] el0t_64_sync+0x190/0x194 [ 37.127474] [ 37.128977] The buggy address belongs to the object at ffff00081037c2a0 [ 37.128977] which belongs to the cache kmalloc-8 of size 8 [ 37.141177] The buggy address is located 0 bytes inside of [ 37.141177] allocated 3-byte region [ffff00081037c2a0, ffff00081037c2a3) [ 37.153465] [ 37.154971] The buggy address belongs to the physical page: [ 37.160559] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x89037c [ 37.168596] flags: 0xbfffe0000000000(node=0|zone=2|lastcpupid=0x1ffff) [ 37.175149] page_type: 0xfdffffff(slab) [ 37.179021] raw: 0bfffe0000000000 ffff000800002500 dead000000000122 0000000000000000 [ 37.186788] raw: 0000000000000000 0000000080800080 00000001fdffffff 0000000000000000 [ 37.194553] page dumped because: kasan: bad access detected [ 37.200144] [ 37.201647] Memory state around the buggy address: [ 37.206460] ffff00081037c180: fa fc fc fc fa fc fc fc fa fc fc fc fa fc fc fc [ 37.213701] ffff00081037c200: fa fc fc fc 05 fc fc fc 03 fc fc fc 02 fc fc fc [ 37.220946] >ffff00081037c280: 06 fc fc fc 03 fc fc fc fc fc fc fc fc fc fc fc [ 37.228186] ^ [ 37.232473] ffff00081037c300: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc [ 37.239718] ffff00081037c380: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc [ 37.246962] ============================================================== ---truncated---(CVE-2024-46853)
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Correct the defined value for AMDGPU_DMUB_NOTIFICATION_MAX
[Why & How] It actually exposes '6' types in enum dmub_notification_type. Not 5. Using smaller number to create array dmub_callback & dmub_thread_offload has potential to access item out of array bound. Fix it.(CVE-2024-46871)
In the Linux kernel, the following vulnerability has been resolved:
smack: tcp: ipv4, fix incorrect labeling
Currently, Smack mirrors the label of incoming tcp/ipv4 connections: when a label 'foo' connects to a label 'bar' with tcp/ipv4, 'foo' always gets 'foo' in returned ipv4 packets. So, 1) returned packets are incorrectly labeled ('foo' instead of 'bar') 2) 'bar' can write to 'foo' without being authorized to write.
Here is a scenario how to see this:
-
Take two machines, let's call them C and S, with active Smack in the default state (no settings, no rules, no labeled hosts, only builtin labels)
-
At S, add Smack rule 'foo bar w' (labels 'foo' and 'bar' are instantiated at S at this moment)
-
At S, at label 'bar', launch a program that listens for incoming tcp/ipv4 connections
-
From C, at label 'foo', connect to the listener at S. (label 'foo' is instantiated at C at this moment) Connection succeedes and works.
-
Send some data in both directions.
- Collect network traffic of this connection.
All packets in both directions are labeled with the CIPSO of the label 'foo'. Hence, label 'bar' writes to 'foo' without being authorized, and even without ever being known at C.
If anybody cares: exactly the same happens with DCCP.
This behavior 1st manifested in release 2.6.29.4 (see Fixes below) and it looks unintentional. At least, no explanation was provided.
I changed returned packes label into the 'bar', to bring it into line with the Smack documentation claims.(CVE-2024-47659)
In the Linux kernel, the following vulnerability has been resolved:
fsnotify: clear PARENT_WATCHED flags lazily
In some setups directories can have many (usually negative) dentries. Hence __fsnotify_update_child_dentry_flags() function can take a significant amount of time. Since the bulk of this function happens under inode->i_lock this causes a significant contention on the lock when we remove the watch from the directory as the __fsnotify_update_child_dentry_flags() call from fsnotify_recalc_mask() races with __fsnotify_update_child_dentry_flags() calls from __fsnotify_parent() happening on children. This can lead upto softlockup reports reported by users.
Fix the problem by calling fsnotify_update_children_dentry_flags() to set PARENT_WATCHED flags only when parent starts watching children.
When parent stops watching children, clear false positive PARENT_WATCHED flags lazily in __fsnotify_parent() for each accessed child.(CVE-2024-47660)
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Avoid overflow from uint32_t to uint8_t
[WHAT & HOW] dmub_rb_cmd's ramping_boundary has size of uint8_t and it is assigned 0xFFFF. Fix it by changing it to uint8_t with value of 0xFF.
This fixes 2 INTEGER_OVERFLOW issues reported by Coverity.(CVE-2024-47661)
In the Linux kernel, the following vulnerability has been resolved:
PCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0)
Errata #i2037 in AM65x/DRA80xM Processors Silicon Revision 1.0 (SPRZ452D_July 2018_Revised December 2019 [1]) mentions when an inbound PCIe TLP spans more than two internal AXI 128-byte bursts, the bus may corrupt the packet payload and the corrupt data may cause associated applications or the processor to hang.
The workaround for Errata #i2037 is to limit the maximum read request size and maximum payload size to 128 bytes. Add workaround for Errata #i2037 here.
The errata and workaround is applicable only to AM65x SR 1.0 and later versions of the silicon will have this fixed.
[1] -> https://www.ti.com/lit/er/sprz452i/sprz452i.pdf(CVE-2024-47667)
In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7996: fix NULL pointer dereference in mt7996_mcu_sta_bfer_he Fix the NULL pointer dereference in mt7996_mcu_sta_bfer_he routine adding an sta interface to the mt7996 driver. Found by code review.(CVE-2024-47681)
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Skip Recompute DSC Params if no Stream on Link [why] Encounter NULL pointer dereference uner mst + dsc setup. BUG: kernel NULL pointer dereference, address: 0000000000000008 PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP NOPTI CPU: 4 PID: 917 Comm: sway Not tainted 6.3.9-arch1-1 #1 124dc55df4f5272ccb409f39ef4872fc2b3376a2 Hardware name: LENOVO 20NKS01Y00/20NKS01Y00, BIOS R12ET61W(1.31 ) 07/28/2022 RIP: 0010:drm_dp_atomic_find_time_slots+0x5e/0x260 [drm_display_helper] Code: 01 00 00 48 8b 85 60 05 00 00 48 63 80 88 00 00 00 3b 43 28 0f 8d 2e 01 00 00 48 8b 53 30 48 8d 04 80 48 8d 04 c2 48 8b 40 18 <48> 8> RSP: 0018:ffff960cc2df77d8 EFLAGS: 00010293 RAX: 0000000000000000 RBX: ffff8afb87e81280 RCX: 0000000000000224 RDX: ffff8afb9ee37c00 RSI: ffff8afb8da1a578 RDI: ffff8afb87e81280 RBP: ffff8afb83d67000 R08: 0000000000000001 R09: ffff8afb9652f850 R10: ffff960cc2df7908 R11: 0000000000000002 R12: 0000000000000000 R13: ffff8afb8d7688a0 R14: ffff8afb8da1a578 R15: 0000000000000224 FS: 00007f4dac35ce00(0000) GS:ffff8afe30b00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000008 CR3: 000000010ddc6000 CR4: 00000000003506e0 Call Trace: <TASK> ? __die+0x23/0x70 ? page_fault_oops+0x171/0x4e0 ? plist_add+0xbe/0x100 ? exc_page_fault+0x7c/0x180 ? asm_exc_page_fault+0x26/0x30 ? drm_dp_atomic_find_time_slots+0x5e/0x260 [drm_display_helper 0e67723696438d8e02b741593dd50d80b44c2026] ? drm_dp_atomic_find_time_slots+0x28/0x260 [drm_display_helper 0e67723696438d8e02b741593dd50d80b44c2026] compute_mst_dsc_configs_for_link+0x2ff/0xa40 [amdgpu 62e600d2a75e9158e1cd0a243bdc8e6da040c054] ? fill_plane_buffer_attributes+0x419/0x510 [amdgpu 62e600d2a75e9158e1cd0a243bdc8e6da040c054] compute_mst_dsc_configs_for_state+0x1e1/0x250 [amdgpu 62e600d2a75e9158e1cd0a243bdc8e6da040c054] amdgpu_dm_atomic_check+0xecd/0x1190 [amdgpu 62e600d2a75e9158e1cd0a243bdc8e6da040c054] drm_atomic_check_only+0x5c5/0xa40 drm_mode_atomic_ioctl+0x76e/0xbc0 [how] dsc recompute should be skipped if no mode change detected on the new request. If detected, keep checking whether the stream is already on current state or not.(CVE-2024-47683)
In the Linux kernel, the following vulnerability has been resolved: tcp: check skb is non-NULL in tcp_rto_delta_us() We have some machines running stock Ubuntu 20.04.6 which is their 5.4.0-174-generic kernel that are running ceph and recently hit a null ptr dereference in tcp_rearm_rto(). Initially hitting it from the TLP path, but then later we also saw it getting hit from the RACK case as well. Here are examples of the oops messages we saw in each of those cases: Jul 26 15:05:02 rx [11061395.780353] BUG: kernel NULL pointer dereference, address: 0000000000000020 Jul 26 15:05:02 rx [11061395.787572] #PF: supervisor read access in kernel mode Jul 26 15:05:02 rx [11061395.792971] #PF: error_code(0x0000) - not-present page Jul 26 15:05:02 rx [11061395.798362] PGD 0 P4D 0 Jul 26 15:05:02 rx [11061395.801164] Oops: 0000 [#1] SMP NOPTI Jul 26 15:05:02 rx [11061395.805091] CPU: 0 PID: 9180 Comm: msgr-worker-1 Tainted: G W 5.4.0-174-generic #193-Ubuntu Jul 26 15:05:02 rx [11061395.814996] Hardware name: Supermicro SMC 2x26 os-gen8 64C NVME-Y 256G/H12SSW-NTR, BIOS 2.5.V1.2U.NVMe.UEFI 05/09/2023 Jul 26 15:05:02 rx [11061395.825952] RIP: 0010:tcp_rearm_rto+0xe4/0x160 Jul 26 15:05:02 rx [11061395.830656] Code: 87 ca 04 00 00 00 5b 41 5c 41 5d 5d c3 c3 49 8b bc 24 40 06 00 00 eb 8d 48 bb cf f7 53 e3 a5 9b c4 20 4c 89 ef e8 0c fe 0e 00 <48> 8b 78 20 48 c1 ef 03 48 89 f8 41 8b bc 24 80 04 00 00 48 f7 e3 Jul 26 15:05:02 rx [11061395.849665] RSP: 0018:ffffb75d40003e08 EFLAGS: 00010246 Jul 26 15:05:02 rx [11061395.855149] RAX: 0000000000000000 RBX: 20c49ba5e353f7cf RCX: 0000000000000000 Jul 26 15:05:02 rx [11061395.862542] RDX: 0000000062177c30 RSI: 000000000000231c RDI: ffff9874ad283a60 Jul 26 15:05:02 rx [11061395.869933] RBP: ffffb75d40003e20 R08: 0000000000000000 R09: ffff987605e20aa8 Jul 26 15:05:02 rx [11061395.877318] R10: ffffb75d40003f00 R11: ffffb75d4460f740 R12: ffff9874ad283900 Jul 26 15:05:02 rx [11061395.884710] R13: ffff9874ad283a60 R14: ffff9874ad283980 R15: ffff9874ad283d30 Jul 26 15:05:02 rx [11061395.892095] FS: 00007f1ef4a2e700(0000) GS:ffff987605e00000(0000) knlGS:0000000000000000 Jul 26 15:05:02 rx [11061395.900438] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 26 15:05:02 rx [11061395.906435] CR2: 0000000000000020 CR3: 0000003e450ba003 CR4: 0000000000760ef0 Jul 26 15:05:02 rx [11061395.913822] PKRU: 55555554 Jul 26 15:05:02 rx [11061395.916786] Call Trace: Jul 26 15:05:02 rx [11061395.919488] Jul 26 15:05:02 rx [11061395.921765] ? show_regs.cold+0x1a/0x1f Jul 26 15:05:02 rx [11061395.925859] ? __die+0x90/0xd9 Jul 26 15:05:02 rx [11061395.929169] ? no_context+0x196/0x380 Jul 26 15:05:02 rx [11061395.933088] ? ip6_protocol_deliver_rcu+0x4e0/0x4e0 Jul 26 15:05:02 rx [11061395.938216] ? ip6_sublist_rcv_finish+0x3d/0x50 Jul 26 15:05:02 rx [11061395.943000] ? __bad_area_nosemaphore+0x50/0x1a0 Jul 26 15:05:02 rx [11061395.947873] ? bad_area_nosemaphore+0x16/0x20 Jul 26 15:05:02 rx [11061395.952486] ? do_user_addr_fault+0x267/0x450 Jul 26 15:05:02 rx [11061395.957104] ? ipv6_list_rcv+0x112/0x140 Jul 26 15:05:02 rx [11061395.961279] ? __do_page_fault+0x58/0x90 Jul 26 15:05:02 rx [11061395.965458] ? do_page_fault+0x2c/0xe0 Jul 26 15:05:02 rx [11061395.969465] ? page_fault+0x34/0x40 Jul 26 15:05:02 rx [11061395.973217] ? tcp_rearm_rto+0xe4/0x160 Jul 26 15:05:02 rx [11061395.977313] ? tcp_rearm_rto+0xe4/0x160 Jul 26 15:05:02 rx [11061395.981408] tcp_send_loss_probe+0x10b/0x220 Jul 26 15:05:02 rx [11061395.985937] tcp_write_timer_handler+0x1b4/0x240 Jul 26 15:05:02 rx [11061395.990809] tcp_write_timer+0x9e/0xe0 Jul 26 15:05:02 rx [11061395.994814] ? tcp_write_timer_handler+0x240/0x240 Jul 26 15:05:02 rx [11061395.999866] call_timer_fn+0x32/0x130 Jul 26 15:05:02 rx [11061396.003782] __run_timers.part.0+0x180/0x280 Jul 26 15:05:02 rx [11061396.008309] ? recalibrate_cpu_khz+0x10/0x10 Jul 26 15:05:02 rx [11061396.012841] ? native_x2apic_icr_write+0x30/0x30 Jul 26 15:05:02 rx [11061396.017718] ? lapic_next_even ---truncated---(CVE-2024-47684)
In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put() syzbot reported that nf_reject_ip6_tcphdr_put() was possibly sending garbage on the four reserved tcp bits (th->res1) Use skb_put_zero() to clear the whole TCP header, as done in nf_reject_ip_tcphdr_put() BUG: KMSAN: uninit-value in nf_reject_ip6_tcphdr_put+0x688/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:255 nf_reject_ip6_tcphdr_put+0x688/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:255 nf_send_reset6+0xd84/0x15b0 net/ipv6/netfilter/nf_reject_ipv6.c:344 nft_reject_inet_eval+0x3c1/0x880 net/netfilter/nft_reject_inet.c:48 expr_call_ops_eval net/netfilter/nf_tables_core.c:240 [inline] nft_do_chain+0x438/0x22a0 net/netfilter/nf_tables_core.c:288 nft_do_chain_inet+0x41a/0x4f0 net/netfilter/nft_chain_filter.c:161 nf_hook_entry_hookfn include/linux/netfilter.h:154 [inline] nf_hook_slow+0xf4/0x400 net/netfilter/core.c:626 nf_hook include/linux/netfilter.h:269 [inline] NF_HOOK include/linux/netfilter.h:312 [inline] ipv6_rcv+0x29b/0x390 net/ipv6/ip6_input.c:310 __netif_receive_skb_one_core net/core/dev.c:5661 [inline] __netif_receive_skb+0x1da/0xa00 net/core/dev.c:5775 process_backlog+0x4ad/0xa50 net/core/dev.c:6108 __napi_poll+0xe7/0x980 net/core/dev.c:6772 napi_poll net/core/dev.c:6841 [inline] net_rx_action+0xa5a/0x19b0 net/core/dev.c:6963 handle_softirqs+0x1ce/0x800 kernel/softirq.c:554 __do_softirq+0x14/0x1a kernel/softirq.c:588 do_softirq+0x9a/0x100 kernel/softirq.c:455 __local_bh_enable_ip+0x9f/0xb0 kernel/softirq.c:382 local_bh_enable include/linux/bottom_half.h:33 [inline] rcu_read_unlock_bh include/linux/rcupdate.h:908 [inline] __dev_queue_xmit+0x2692/0x5610 net/core/dev.c:4450 dev_queue_xmit include/linux/netdevice.h:3105 [inline] neigh_resolve_output+0x9ca/0xae0 net/core/neighbour.c:1565 neigh_output include/net/neighbour.h:542 [inline] ip6_finish_output2+0x2347/0x2ba0 net/ipv6/ip6_output.c:141 __ip6_finish_output net/ipv6/ip6_output.c:215 [inline] ip6_finish_output+0xbb8/0x14b0 net/ipv6/ip6_output.c:226 NF_HOOK_COND include/linux/netfilter.h:303 [inline] ip6_output+0x356/0x620 net/ipv6/ip6_output.c:247 dst_output include/net/dst.h:450 [inline] NF_HOOK include/linux/netfilter.h:314 [inline] ip6_xmit+0x1ba6/0x25d0 net/ipv6/ip6_output.c:366 inet6_csk_xmit+0x442/0x530 net/ipv6/inet6_connection_sock.c:135 __tcp_transmit_skb+0x3b07/0x4880 net/ipv4/tcp_output.c:1466 tcp_transmit_skb net/ipv4/tcp_output.c:1484 [inline] tcp_connect+0x35b6/0x7130 net/ipv4/tcp_output.c:4143 tcp_v6_connect+0x1bcc/0x1e40 net/ipv6/tcp_ipv6.c:333 __inet_stream_connect+0x2ef/0x1730 net/ipv4/af_inet.c:679 inet_stream_connect+0x6a/0xd0 net/ipv4/af_inet.c:750 __sys_connect_file net/socket.c:2061 [inline] __sys_connect+0x606/0x690 net/socket.c:2078 __do_sys_connect net/socket.c:2088 [inline] __se_sys_connect net/socket.c:2085 [inline] __x64_sys_connect+0x91/0xe0 net/socket.c:2085 x64_sys_call+0x27a5/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:43 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was stored to memory at: nf_reject_ip6_tcphdr_put+0x60c/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:249 nf_send_reset6+0xd84/0x15b0 net/ipv6/netfilter/nf_reject_ipv6.c:344 nft_reject_inet_eval+0x3c1/0x880 net/netfilter/nft_reject_inet.c:48 expr_call_ops_eval net/netfilter/nf_tables_core.c:240 [inline] nft_do_chain+0x438/0x22a0 net/netfilter/nf_tables_core.c:288 nft_do_chain_inet+0x41a/0x4f0 net/netfilter/nft_chain_filter.c:161 nf_hook_entry_hookfn include/linux/netfilter.h:154 [inline] nf_hook_slow+0xf4/0x400 net/netfilter/core.c:626 nf_hook include/linux/netfilter.h:269 [inline] NF_HOOK include/linux/netfilter.h:312 [inline] ipv6_rcv+0x29b/0x390 net/ipv6/ip6_input.c:310 __netif_receive_skb_one_core ---truncated---(CVE-2024-47685)
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to don't set SB_RDONLY in f2fs_handle_critical_error() syzbot reports a f2fs bug as below: ------------[ cut here ]------------ WARNING: CPU: 1 PID: 58 at kernel/rcu/sync.c:177 rcu_sync_dtor+0xcd/0x180 kernel/rcu/sync.c:177 CPU: 1 UID: 0 PID: 58 Comm: kworker/1:2 Not tainted 6.10.0-syzkaller-12562-g1722389b0d86 #0 Workqueue: events destroy_super_work RIP: 0010:rcu_sync_dtor+0xcd/0x180 kernel/rcu/sync.c:177 Call Trace: percpu_free_rwsem+0x41/0x80 kernel/locking/percpu-rwsem.c:42 destroy_super_work+0xec/0x130 fs/super.c:282 process_one_work kernel/workqueue.c:3231 [inline] process_scheduled_works+0xa2c/0x1830 kernel/workqueue.c:3312 worker_thread+0x86d/0xd40 kernel/workqueue.c:3390 kthread+0x2f0/0x390 kernel/kthread.c:389 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 As Christian Brauner pointed out [1]: the root cause is f2fs sets SB_RDONLY flag in internal function, rather than setting the flag covered w/ sb->s_umount semaphore via remount procedure, then below race condition causes this bug: - freeze_super() - sb_wait_write(sb, SB_FREEZE_WRITE) - sb_wait_write(sb, SB_FREEZE_PAGEFAULT) - sb_wait_write(sb, SB_FREEZE_FS) - f2fs_handle_critical_error - sb->s_flags |= SB_RDONLY - thaw_super - thaw_super_locked - sb_rdonly() is true, so it skips sb_freeze_unlock(sb, SB_FREEZE_FS) - deactivate_locked_super Since f2fs has almost the same logic as ext4 [2] when handling critical error in filesystem if it mounts w/ errors=remount-ro option: - set CP_ERROR_FLAG flag which indicates filesystem is stopped - record errors to superblock - set SB_RDONLY falg Once we set CP_ERROR_FLAG flag, all writable interfaces can detect the flag and stop any further updates on filesystem. So, it is safe to not set SB_RDONLY flag, let's remove the logic and keep in line w/ ext4 [3]. [1] https://lore.kernel.org/all/20240729-himbeeren-funknetz-96e62f9c7aee@brauner [2] https://lore.kernel.org/all/20240729132721.hxih6ehigadqf7wx@quack3 [3] https://lore.kernel.org/linux-ext4/20240805201241.27286-1-jack@suse.cz(CVE-2024-47689)
In the Linux kernel, the following vulnerability has been resolved: nfsd: return -EINVAL when namelen is 0 When we have a corrupted main.sqlite in /var/lib/nfs/nfsdcld/, it may result in namelen being 0, which will cause memdup_user() to return ZERO_SIZE_PTR. When we access the name.data that has been assigned the value of ZERO_SIZE_PTR in nfs4_client_to_reclaim(), null pointer dereference is triggered. [ T1205] ================================================================== [ T1205] BUG: KASAN: null-ptr-deref in nfs4_client_to_reclaim+0xe9/0x260 [ T1205] Read of size 1 at addr 0000000000000010 by task nfsdcld/1205 [ T1205] [ T1205] CPU: 11 PID: 1205 Comm: nfsdcld Not tainted 5.10.0-00003-g2c1423731b8d #406 [ T1205] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS ?-20190727_073836-buildvm-ppc64le-16.ppc.fedoraproject.org-3.fc31 04/01/2014 [ T1205] Call Trace: [ T1205] dump_stack+0x9a/0xd0 [ T1205] ? nfs4_client_to_reclaim+0xe9/0x260 [ T1205] __kasan_report.cold+0x34/0x84 [ T1205] ? nfs4_client_to_reclaim+0xe9/0x260 [ T1205] kasan_report+0x3a/0x50 [ T1205] nfs4_client_to_reclaim+0xe9/0x260 [ T1205] ? nfsd4_release_lockowner+0x410/0x410 [ T1205] cld_pipe_downcall+0x5ca/0x760 [ T1205] ? nfsd4_cld_tracking_exit+0x1d0/0x1d0 [ T1205] ? down_write_killable_nested+0x170/0x170 [ T1205] ? avc_policy_seqno+0x28/0x40 [ T1205] ? selinux_file_permission+0x1b4/0x1e0 [ T1205] rpc_pipe_write+0x84/0xb0 [ T1205] vfs_write+0x143/0x520 [ T1205] ksys_write+0xc9/0x170 [ T1205] ? __ia32_sys_read+0x50/0x50 [ T1205] ? ktime_get_coarse_real_ts64+0xfe/0x110 [ T1205] ? ktime_get_coarse_real_ts64+0xa2/0x110 [ T1205] do_syscall_64+0x33/0x40 [ T1205] entry_SYSCALL_64_after_hwframe+0x67/0xd1 [ T1205] RIP: 0033:0x7fdbdb761bc7 [ T1205] Code: 0f 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 0f 1f 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 514 [ T1205] RSP: 002b:00007fff8c4b7248 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 [ T1205] RAX: ffffffffffffffda RBX: 000000000000042b RCX: 00007fdbdb761bc7 [ T1205] RDX: 000000000000042b RSI: 00007fff8c4b75f0 RDI: 0000000000000008 [ T1205] RBP: 00007fdbdb761bb0 R08: 0000000000000000 R09: 0000000000000001 [ T1205] R10: 0000000000000000 R11: 0000000000000246 R12: 000000000000042b [ T1205] R13: 0000000000000008 R14: 00007fff8c4b75f0 R15: 0000000000000000 [ T1205] ================================================================== Fix it by checking namelen.(CVE-2024-47692)
In the Linux kernel, the following vulnerability has been resolved: RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds In the function init_conns(), after the create_con() and create_cm() for loop if something fails. In the cleanup for loop after the destroy tag, we access out of bound memory because cid is set to clt_path->s.con_num. This commits resets the cid to clt_path->s.con_num - 1, to stay in bounds in the cleanup loop later.(CVE-2024-47695)
In the Linux kernel, the following vulnerability has been resolved: drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error Ensure index in rtl2832_pid_filter does not exceed 31 to prevent out-of-bounds access. dev->filters is a 32-bit value, so set_bit and clear_bit functions should only operate on indices from 0 to 31. If index is 32, it will attempt to access a non-existent 33rd bit, leading to out-of-bounds access. Change the boundary check from index > 32 to index >= 32 to resolve this issue. hverkuil: added fixes tag, rtl2830_pid_filter -> rtl2832_pid_filter in logmsg
In the Linux kernel, the following vulnerability has been resolved: can: bcm: Clear bo->bcm_proc_read after remove_proc_entry(). syzbot reported a warning in bcm_release(). [0] The blamed change fixed another warning that is triggered when connect() is issued again for a socket whose connect()ed device has been unregistered. However, if the socket is just close()d without the 2nd connect(), the remaining bo->bcm_proc_read triggers unnecessary remove_proc_entry() in bcm_release(). Let's clear bo->bcm_proc_read after remove_proc_entry() in bcm_notify(). [0] name '4986' WARNING: CPU: 0 PID: 5234 at fs/proc/generic.c:711 remove_proc_entry+0x2e7/0x5d0 fs/proc/generic.c:711 Modules linked in: CPU: 0 UID: 0 PID: 5234 Comm: syz-executor606 Not tainted 6.11.0-rc5-syzkaller-00178-g5517ae241919 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 RIP: 0010:remove_proc_entry+0x2e7/0x5d0 fs/proc/generic.c:711 Code: ff eb 05 e8 cb 1e 5e ff 48 8b 5c 24 10 48 c7 c7 e0 f7 aa 8e e8 2a 38 8e 09 90 48 c7 c7 60 3a 1b 8c 48 89 de e8 da 42 20 ff 90 <0f> 0b 90 90 48 8b 44 24 18 48 c7 44 24 40 0e 36 e0 45 49 c7 04 07 RSP: 0018:ffffc9000345fa20 EFLAGS: 00010246 RAX: 2a2d0aee2eb64600 RBX: ffff888032f1f548 RCX: ffff888029431e00 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffc9000345fb08 R08: ffffffff8155b2f2 R09: 1ffff1101710519a R10: dffffc0000000000 R11: ffffed101710519b R12: ffff888011d38640 R13: 0000000000000004 R14: 0000000000000000 R15: dffffc0000000000 FS: 0000000000000000(0000) GS:ffff8880b8800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fcfb52722f0 CR3: 000000000e734000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> bcm_release+0x250/0x880 net/can/bcm.c:1578 __sock_release net/socket.c:659 [inline] sock_close+0xbc/0x240 net/socket.c:1421 __fput+0x24a/0x8a0 fs/file_table.c:422 task_work_run+0x24f/0x310 kernel/task_work.c:228 exit_task_work include/linux/task_work.h:40 [inline] do_exit+0xa2f/0x27f0 kernel/exit.c:882 do_group_exit+0x207/0x2c0 kernel/exit.c:1031 __do_sys_exit_group kernel/exit.c:1042 [inline] __se_sys_exit_group kernel/exit.c:1040 [inline] __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1040 x64_sys_call+0x2634/0x2640 arch/x86/include/generated/asm/syscalls_64.h:232 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fcfb51ee969 Code: Unable to access opcode bytes at 0x7fcfb51ee93f. RSP: 002b:00007ffce0109ca8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007fcfb51ee969 RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001 RBP: 00007fcfb526f3b0 R08: ffffffffffffffb8 R09: 0000555500000000 R10: 0000555500000000 R11: 0000000000000246 R12: 00007fcfb526f3b0 R13: 0000000000000000 R14: 00007fcfb5271ee0 R15: 00007fcfb51bf160 </TASK>(CVE-2024-47709)
In the Linux kernel, the following vulnerability has been resolved: sock_map: Add a cond_resched() in sock_hash_free() Several syzbot soft lockup reports all have in common sock_hash_free() If a map with a large number of buckets is destroyed, we need to yield the cpu when needed.(CVE-2024-47710)
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add null check for set_output_gamma in dcn30_set_output_transfer_func This commit adds a null check for the set_output_gamma function pointer in the dcn30_set_output_transfer_func function. Previously, set_output_gamma was being checked for nullity at line 386, but then it was being dereferenced without any nullity check at line 401. This could potentially lead to a null pointer dereference error if set_output_gamma is indeed null. To fix this, we now ensure that set_output_gamma is not null before dereferencing it. We do this by adding a nullity check for set_output_gamma before the call to set_output_gamma at line 401. If set_output_gamma is null, we log an error message and do not call the function. This fix prevents a potential null pointer dereference error. drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c:401 dcn30_set_output_transfer_func() error: we previously assumed 'mpc->funcs->set_output_gamma' could be null (see line 386) drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c 373 bool dcn30_set_output_transfer_func(struct dc dc, 374 struct pipe_ctx pipe_ctx, 375 const struct dc_stream_state stream) 376 { 377 int mpcc_id = pipe_ctx->plane_res.hubp->inst; 378 struct mpc mpc = pipe_ctx->stream_res.opp->ctx->dc->res_pool->mpc; 379 const struct pwl_params params = NULL; 380 bool ret = false; 381 382 / program OGAM or 3DLUT only for the top pipe/ 383 if (pipe_ctx->top_pipe == NULL) { 384 /program rmu shaper and 3dlut in MPC/ 385 ret = dcn30_set_mpc_shaper_3dlut(pipe_ctx, stream); 386 if (ret == false && mpc->funcs->set_output_gamma) { ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ If this is NULL 387 if (stream->out_transfer_func.type == TF_TYPE_HWPWL) 388 params = &stream->out_transfer_func.pwl; 389 else if (pipe_ctx->stream->out_transfer_func.type == 390 TF_TYPE_DISTRIBUTED_POINTS && 391 cm3_helper_translate_curve_to_hw_format( 392 &stream->out_transfer_func, 393 &mpc->blender_params, false)) 394 params = &mpc->blender_params; 395 / there are no ROM LUTs in OUTGAM */ 396 if (stream->out_transfer_func.type == TF_TYPE_PREDEFINED) 397 BREAK_TO_DEBUGGER(); 398 } 399 } 400 --> 401 mpc->funcs->set_output_gamma(mpc, mpcc_id, params); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Then it will crash 402 return ret; 403 }(CVE-2024-47720)
In the Linux kernel, the following vulnerability has been resolved: nfsd: call cache_put if xdr_reserve_space returns NULL If not enough buffer space available, but idmap_lookup has triggered lookup_fn which calls cache_get and returns successfully. Then we missed to call cache_put here which pairs with cache_get. Reviwed-by: Jeff Layton <jlayton@kernel.org>(CVE-2024-47737)
In the Linux kernel, the following vulnerability has been resolved: KEYS: prevent NULL pointer dereference in find_asymmetric_key() In find_asymmetric_key(), if all NULLs are passed in the id_{0,1,2} arguments, the kernel will first emit WARN but then have an oops because id_2 gets dereferenced anyway. Add the missing id_2 check and move WARN_ON() to the final else branch to avoid duplicate NULL checks. Found by Linux Verification Center (linuxtesting.org) with Svace static analysis tool.(CVE-2024-47743)
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential oob read in nilfs_btree_check_delete() The function nilfs_btree_check_delete(), which checks whether degeneration to direct mapping occurs before deleting a b-tree entry, causes memory access outside the block buffer when retrieving the maximum key if the root node has no entries. This does not usually happen because b-tree mappings with 0 child nodes are never created by mkfs.nilfs2 or nilfs2 itself. However, it can happen if the b-tree root node read from a device is configured that way, so fix this potential issue by adding a check for that case.(CVE-2024-47757)
In the Linux kernel, the following vulnerability has been resolved: nbd: fix race between timeout and normal completion If request timetout is handled by nbd_requeue_cmd(), normal completion has to be stopped for avoiding to complete this requeued request, other use-after-free can be triggered. Fix the race by clearing NBD_CMD_INFLIGHT in nbd_requeue_cmd(), meantime make sure that cmd->lock is grabbed for clearing the flag and the requeue.(CVE-2024-49855)
In the Linux kernel, the following vulnerability has been resolved: tracing/timerlat: Fix a race during cpuhp processing There is another found exception that the "timerlat/1" thread was scheduled on CPU0, and lead to timer corruption finally: ODEBUG: init active (active state 0) object: ffff888237c2e108 object type: hrtimer hint: timerlat_irq+0x0/0x220 WARNING: CPU: 0 PID: 426 at lib/debugobjects.c:518 debug_print_object+0x7d/0xb0 Modules linked in: CPU: 0 UID: 0 PID: 426 Comm: timerlat/1 Not tainted 6.11.0-rc7+ #45 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: 0010:debug_print_object+0x7d/0xb0 ... Call Trace: <TASK> ? __warn+0x7c/0x110 ? debug_print_object+0x7d/0xb0 ? report_bug+0xf1/0x1d0 ? prb_read_valid+0x17/0x20 ? handle_bug+0x3f/0x70 ? exc_invalid_op+0x13/0x60 ? asm_exc_invalid_op+0x16/0x20 ? debug_print_object+0x7d/0xb0 ? debug_print_object+0x7d/0xb0 ? __pfx_timerlat_irq+0x10/0x10 __debug_object_init+0x110/0x150 hrtimer_init+0x1d/0x60 timerlat_main+0xab/0x2d0 ? __pfx_timerlat_main+0x10/0x10 kthread+0xb7/0xe0 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x2d/0x40 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> After tracing the scheduling event, it was discovered that the migration of the "timerlat/1" thread was performed during thread creation. Further analysis confirmed that it is because the CPU online processing for osnoise is implemented through workers, which is asynchronous with the offline processing. When the worker was scheduled to create a thread, the CPU may has already been removed from the cpu_online_mask during the offline process, resulting in the inability to select the right CPU: T1 | T2 [CPUHP_ONLINE] | cpu_device_down() osnoise_hotplug_workfn() | | cpus_write_lock() | takedown_cpu(1) | cpus_write_unlock() [CPUHP_OFFLINE] | cpus_read_lock() | start_kthread(1) | cpus_read_unlock() | To fix this, skip online processing if the CPU is already offline.(CVE-2024-49866)
In the Linux kernel, the following vulnerability has been resolved: btrfs: wait for fixup workers before stopping cleaner kthread during umount During unmount, at close_ctree(), we have the following steps in this order: 1) Park the cleaner kthread - this doesn't destroy the kthread, it basically halts its execution (wake ups against it work but do nothing); 2) We stop the cleaner kthread - this results in freeing the respective struct task_struct; 3) We call btrfs_stop_all_workers() which waits for any jobs running in all the work queues and then free the work queues. Syzbot reported a case where a fixup worker resulted in a crash when doing a delayed iput on its inode while attempting to wake up the cleaner at btrfs_add_delayed_iput(), because the task_struct of the cleaner kthread was already freed. This can happen during unmount because we don't wait for any fixup workers still running before we call kthread_stop() against the cleaner kthread, which stops and free all its resources. Fix this by waiting for any fixup workers at close_ctree() before we call kthread_stop() against the cleaner and run pending delayed iputs. The stack traces reported by syzbot were the following: BUG: KASAN: slab-use-after-free in __lock_acquire+0x77/0x2050 kernel/locking/lockdep.c:5065 Read of size 8 at addr ffff8880272a8a18 by task kworker/u8:3/52 CPU: 1 UID: 0 PID: 52 Comm: kworker/u8:3 Not tainted 6.12.0-rc1-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Workqueue: btrfs-fixup btrfs_work_helper Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:377 [inline] print_report+0x169/0x550 mm/kasan/report.c:488 kasan_report+0x143/0x180 mm/kasan/report.c:601 __lock_acquire+0x77/0x2050 kernel/locking/lockdep.c:5065 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0xd5/0x120 kernel/locking/spinlock.c:162 class_raw_spinlock_irqsave_constructor include/linux/spinlock.h:551 [inline] try_to_wake_up+0xb0/0x1480 kernel/sched/core.c:4154 btrfs_writepage_fixup_worker+0xc16/0xdf0 fs/btrfs/inode.c:2842 btrfs_work_helper+0x390/0xc50 fs/btrfs/async-thread.c:314 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xa63/0x1850 kernel/workqueue.c:3310 worker_thread+0x870/0xd30 kernel/workqueue.c:3391 kthread+0x2f0/0x390 kernel/kthread.c:389 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 </TASK> Allocated by task 2: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3f/0x80 mm/kasan/common.c:68 unpoison_slab_object mm/kasan/common.c:319 [inline] __kasan_slab_alloc+0x66/0x80 mm/kasan/common.c:345 kasan_slab_alloc include/linux/kasan.h:247 [inline] slab_post_alloc_hook mm/slub.c:4086 [inline] slab_alloc_node mm/slub.c:4135 [inline] kmem_cache_alloc_node_noprof+0x16b/0x320 mm/slub.c:4187 alloc_task_struct_node kernel/fork.c:180 [inline] dup_task_struct+0x57/0x8c0 kernel/fork.c:1107 copy_process+0x5d1/0x3d50 kernel/fork.c:2206 kernel_clone+0x223/0x880 kernel/fork.c:2787 kernel_thread+0x1bc/0x240 kernel/fork.c:2849 create_kthread kernel/kthread.c:412 [inline] kthreadd+0x60d/0x810 kernel/kthread.c:765 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 Freed by task 61: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3f/0x80 mm/kasan/common.c:68 kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:579 poison_slab_object mm/kasan/common.c:247 [inline] __kasan_slab_free+0x59/0x70 mm/kasan/common.c:264 kasan_slab_free include/linux/kasan.h:230 [inline] slab_free_h ---truncated---(CVE-2024-49867)
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix a NULL pointer dereference when failed to start a new trasacntion [BUG] Syzbot reported a NULL pointer dereference with the following crash: FAULT_INJECTION: forcing a failure. start_transaction+0x830/0x1670 fs/btrfs/transaction.c:676 prepare_to_relocate+0x31f/0x4c0 fs/btrfs/relocation.c:3642 relocate_block_group+0x169/0xd20 fs/btrfs/relocation.c:3678 ... BTRFS info (device loop0): balance: ended with status: -12 Oops: general protection fault, probably for non-canonical address 0xdffffc00000000cc: 0000 [#1] PREEMPT SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000660-0x0000000000000667] RIP: 0010:btrfs_update_reloc_root+0x362/0xa80 fs/btrfs/relocation.c:926 Call Trace: <TASK> commit_fs_roots+0x2ee/0x720 fs/btrfs/transaction.c:1496 btrfs_commit_transaction+0xfaf/0x3740 fs/btrfs/transaction.c:2430 del_balance_item fs/btrfs/volumes.c:3678 [inline] reset_balance_state+0x25e/0x3c0 fs/btrfs/volumes.c:3742 btrfs_balance+0xead/0x10c0 fs/btrfs/volumes.c:4574 btrfs_ioctl_balance+0x493/0x7c0 fs/btrfs/ioctl.c:3673 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl+0xf9/0x170 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f [CAUSE] The allocation failure happens at the start_transaction() inside prepare_to_relocate(), and during the error handling we call unset_reloc_control(), which makes fs_info->balance_ctl to be NULL. Then we continue the error path cleanup in btrfs_balance() by calling reset_balance_state() which will call del_balance_item() to fully delete the balance item in the root tree. However during the small window between set_reloc_contrl() and unset_reloc_control(), we can have a subvolume tree update and created a reloc_root for that subvolume. Then we go into the final btrfs_commit_transaction() of del_balance_item(), and into btrfs_update_reloc_root() inside commit_fs_roots(). That function checks if fs_info->reloc_ctl is in the merge_reloc_tree stage, but since fs_info->reloc_ctl is NULL, it results a NULL pointer dereference. [FIX] Just add extra check on fs_info->reloc_ctl inside btrfs_update_reloc_root(), before checking fs_info->reloc_ctl->merge_reloc_tree. That DEAD_RELOC_TREE handling is to prevent further modification to the reloc tree during merge stage, but since there is no reloc_ctl at all, we do not need to bother that.(CVE-2024-49868)
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix index out of bounds in DCN30 degamma hardware format translation This commit addresses a potential index out of bounds issue in the cm3_helper_translate_curve_to_degamma_hw_format function in the DCN30 color management module. The issue could occur when the index 'i' exceeds the number of transfer function points (TRANSFER_FUNC_POINTS). The fix adds a check to ensure 'i' is within bounds before accessing the transfer function points. If 'i' is out of bounds, the function returns false to indicate an error. Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:338 cm3_helper_translate_curve_to_degamma_hw_format() error: buffer overflow 'output_tf->tf_pts.red' 1025 <= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:339 cm3_helper_translate_curve_to_degamma_hw_format() error: buffer overflow 'output_tf->tf_pts.green' 1025 <= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:340 cm3_helper_translate_curve_to_degamma_hw_format() error: buffer overflow 'output_tf->tf_pts.blue' 1025 <= s32max(CVE-2024-49895)
In the Linux kernel, the following vulnerability has been resolved: jfs: Fix uninit-value access of new_ea in ea_buffer syzbot reports that lzo1x_1_do_compress is using uninit-value: ===================================================== BUG: KMSAN: uninit-value in lzo1x_1_do_compress+0x19f9/0x2510 lib/lzo/lzo1x_compress.c:178 ... Uninit was stored to memory at: ea_put fs/jfs/xattr.c:639 [inline] ... Local variable ea_buf created at: __jfs_setxattr+0x5d/0x1ae0 fs/jfs/xattr.c:662 __jfs_xattr_set+0xe6/0x1f0 fs/jfs/xattr.c:934 ===================================================== The reason is ea_buf->new_ea is not initialized properly. Fix this by using memset to empty its content at the beginning in ea_get().(CVE-2024-49900)
In the Linux kernel, the following vulnerability has been resolved: jfs: check if leafidx greater than num leaves per dmap tree syzbot report a out of bounds in dbSplit, it because dmt_leafidx greater than num leaves per dmap tree, add a checking for dmt_leafidx in dbFindLeaf. Shaggy: Modified sanity check to apply to control pages as well as leaf pages.(CVE-2024-49902)
In the Linux kernel, the following vulnerability has been resolved: jfs: Fix uaf in dbFreeBits [syzbot reported] ================================================================== BUG: KASAN: slab-use-after-free in __mutex_lock_common kernel/locking/mutex.c:587 [inline] BUG: KASAN: slab-use-after-free in __mutex_lock+0xfe/0xd70 kernel/locking/mutex.c:752 Read of size 8 at addr ffff8880229254b0 by task syz-executor357/5216 CPU: 0 UID: 0 PID: 5216 Comm: syz-executor357 Not tainted 6.11.0-rc3-syzkaller-00156-gd7a5aa4b3c00 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024 Call Trace: <TASK> __dump_stack lib/dump_stack.c:93 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119 print_address_description mm/kasan/report.c:377 [inline] print_report+0x169/0x550 mm/kasan/report.c:488 kasan_report+0x143/0x180 mm/kasan/report.c:601 __mutex_lock_common kernel/locking/mutex.c:587 [inline] __mutex_lock+0xfe/0xd70 kernel/locking/mutex.c:752 dbFreeBits+0x7ea/0xd90 fs/jfs/jfs_dmap.c:2390 dbFreeDmap fs/jfs/jfs_dmap.c:2089 [inline] dbFree+0x35b/0x680 fs/jfs/jfs_dmap.c:409 dbDiscardAG+0x8a9/0xa20 fs/jfs/jfs_dmap.c:1650 jfs_ioc_trim+0x433/0x670 fs/jfs/jfs_discard.c:100 jfs_ioctl+0x2d0/0x3e0 fs/jfs/ioctl.c:131 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 Freed by task 5218: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3f/0x80 mm/kasan/common.c:68 kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:579 poison_slab_object+0xe0/0x150 mm/kasan/common.c:240 __kasan_slab_free+0x37/0x60 mm/kasan/common.c:256 kasan_slab_free include/linux/kasan.h:184 [inline] slab_free_hook mm/slub.c:2252 [inline] slab_free mm/slub.c:4473 [inline] kfree+0x149/0x360 mm/slub.c:4594 dbUnmount+0x11d/0x190 fs/jfs/jfs_dmap.c:278 jfs_mount_rw+0x4ac/0x6a0 fs/jfs/jfs_mount.c:247 jfs_remount+0x3d1/0x6b0 fs/jfs/super.c:454 reconfigure_super+0x445/0x880 fs/super.c:1083 vfs_cmd_reconfigure fs/fsopen.c:263 [inline] vfs_fsconfig_locked fs/fsopen.c:292 [inline] __do_sys_fsconfig fs/fsopen.c:473 [inline] __se_sys_fsconfig+0xb6e/0xf80 fs/fsopen.c:345 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f [Analysis] There are two paths (dbUnmount and jfs_ioc_trim) that generate race condition when accessing bmap, which leads to the occurrence of uaf. Use the lock s_umount to synchronize them, in order to avoid uaf caused by race condition.(CVE-2024-49903)
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add NULL check for function pointer in dcn20_set_output_transfer_func This commit adds a null check for the set_output_gamma function pointer in the dcn20_set_output_transfer_func function. Previously, set_output_gamma was being checked for null at line 1030, but then it was being dereferenced without any null check at line 1048. This could potentially lead to a null pointer dereference error if set_output_gamma is null. To fix this, we now ensure that set_output_gamma is not null before dereferencing it. We do this by adding a null check for set_output_gamma before the call to set_output_gamma at line 1048.(CVE-2024-49911)
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add null check for head_pipe in dcn32_acquire_idle_pipe_for_head_pipe_in_layer This commit addresses a potential null pointer dereference issue in the dcn32_acquire_idle_pipe_for_head_pipe_in_layer function. The issue could occur when head_pipe is null. The fix adds a check to ensure head_pipe is not null before asserting it. If head_pipe is null, the function returns NULL to prevent a potential null pointer dereference. Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/resource/dcn32/dcn32_resource.c:2690 dcn32_acquire_idle_pipe_for_head_pipe_in_layer() error: we previously assumed 'head_pipe' could be null (see line 2681)(CVE-2024-49918)
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add null check for head_pipe in dcn201_acquire_free_pipe_for_layer This commit addresses a potential null pointer dereference issue in the dcn201_acquire_free_pipe_for_layer function. The issue could occur when head_pipe is null. The fix adds a check to ensure head_pipe is not null before asserting it. If head_pipe is null, the function returns NULL to prevent a potential null pointer dereference. Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/resource/dcn201/dcn201_resource.c:1016 dcn201_acquire_free_pipe_for_layer() error: we previously assumed 'head_pipe' could be null (see line 1010)(CVE-2024-49919)
In the Linux kernel, the following vulnerability has been resolved: x86/ioapic: Handle allocation failures gracefully Breno observed panics when using failslab under certain conditions during runtime: can not alloc irq_pin_list (-1,0,20) Kernel panic - not syncing: IO-APIC: failed to add irq-pin. Can not proceed panic+0x4e9/0x590 mp_irqdomain_alloc+0x9ab/0xa80 irq_domain_alloc_irqs_locked+0x25d/0x8d0 __irq_domain_alloc_irqs+0x80/0x110 mp_map_pin_to_irq+0x645/0x890 acpi_register_gsi_ioapic+0xe6/0x150 hpet_open+0x313/0x480 That's a pointless panic which is a leftover of the historic IO/APIC code which panic'ed during early boot when the interrupt allocation failed. The only place which might justify panic is the PIT/HPET timer_check() code which tries to figure out whether the timer interrupt is delivered through the IO/APIC. But that code does not require to handle interrupt allocation failures. If the interrupt cannot be allocated then timer delivery fails and it either panics due to that or falls back to legacy mode. Cure this by removing the panic wrapper around __add_pin_to_irq_node() and making mp_irqdomain_alloc() aware of the failure condition and handle it as any other failure in this function gracefully.(CVE-2024-49927)
In the Linux kernel, the following vulnerability has been resolved: ocfs2: remove unreasonable unlock in ocfs2_read_blocks Patch series "Misc fixes for ocfs2_read_blocks", v5. This series contains 2 fixes for ocfs2_read_blocks(). The first patch fix the issue reported by syzbot, which detects bad unlock balance in ocfs2_read_blocks(). The second patch fixes an issue reported by Heming Zhao when reviewing above fix. This patch (of 2): There was a lock release before exiting, so remove the unreasonable unlock.(CVE-2024-49965)
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix index out of bounds in DCN30 color transformation This commit addresses a potential index out of bounds issue in the cm3_helper_translate_curve_to_hw_format function in the DCN30 color management module. The issue could occur when the index 'i' exceeds the number of transfer function points (TRANSFER_FUNC_POINTS). The fix adds a check to ensure 'i' is within bounds before accessing the transfer function points. If 'i' is out of bounds, the function returns false to indicate an error. drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:180 cm3_helper_translate_curve_to_hw_format() error: buffer overflow 'output_tf->tf_pts.red' 1025 <= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:181 cm3_helper_translate_curve_to_hw_format() error: buffer overflow 'output_tf->tf_pts.green' 1025 <= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:182 cm3_helper_translate_curve_to_hw_format() error: buffer overflow 'output_tf->tf_pts.blue' 1025 <= s32max(CVE-2024-49969)
In the Linux kernel, the following vulnerability has been resolved: NFSD: Limit the number of concurrent async COPY operations Nothing appears to limit the number of concurrent async COPY operations that clients can start. In addition, AFAICT each async COPY can copy an unlimited number of 4MB chunks, so can run for a long time. Thus IMO async COPY can become a DoS vector. Add a restriction mechanism that bounds the number of concurrent background COPY operations. Start simple and try to be fair -- this patch implements a per-namespace limit. An async COPY request that occurs while this limit is exceeded gets NFS4ERR_DELAY. The requesting client can choose to send the request again after a delay or fall back to a traditional read/write style copy. If there is need to make the mechanism more sophisticated, we can visit that in future patches.(CVE-2024-49974)
In the Linux kernel, the following vulnerability has been resolved: tracing/timerlat: Drop interface_lock in stop_kthread() stop_kthread() is the offline callback for "trace/osnoise:online", since commit 5bfbcd1ee57b ("tracing/timerlat: Add interface_lock around clearing of kthread in stop_kthread()"), the following ABBA deadlock scenario is introduced: T1 | T2 [BP] | T3 [AP] osnoise_hotplug_workfn() | work_for_cpu_fn() | cpuhp_thread_fun() | _cpu_down() | osnoise_cpu_die() mutex_lock(&interface_lock) | | stop_kthread() | cpus_write_lock() | mutex_lock(&interface_lock) cpus_read_lock() | cpuhp_kick_ap() | As the interface_lock here in just for protecting the "kthread" field of the osn_var, use xchg() instead to fix this issue. Also use for_each_online_cpu() back in stop_per_cpu_kthreads() as it can take cpu_read_lock() again.(CVE-2024-49976)
In the Linux kernel, the following vulnerability has been resolved: i2c: stm32f7: Do not prepare/unprepare clock during runtime suspend/resume In case there is any sort of clock controller attached to this I2C bus controller, for example Versaclock or even an AIC32x4 I2C codec, then an I2C transfer triggered from the clock controller clk_ops .prepare callback may trigger a deadlock on drivers/clk/clk.c prepare_lock mutex. This is because the clock controller first grabs the prepare_lock mutex and then performs the prepare operation, including its I2C access. The I2C access resumes this I2C bus controller via .runtime_resume callback, which calls clk_prepare_enable(), which attempts to grab the prepare_lock mutex again and deadlocks. Since the clock are already prepared since probe() and unprepared in remove(), use simple clk_enable()/clk_disable() calls to enable and disable the clock on runtime suspend and resume, to avoid hitting the prepare_lock mutex.(CVE-2024-49985)
In the Linux kernel, the following vulnerability has been resolved: ALSA: asihpi: Fix potential OOB array access ASIHPI driver stores some values in the static array upon a response from the driver, and its index depends on the firmware. We shouldn't trust it blindly. This patch adds a sanity check of the array index to fit in the array size.(CVE-2024-50007)
In the Linux kernel, the following vulnerability has been resolved: cpufreq: Avoid a bad reference count on CPU node In the parse_perf_domain function, if the call to of_parse_phandle_with_args returns an error, then the reference to the CPU device node that was acquired at the start of the function would not be properly decremented. Address this by declaring the variable with the __free(device_node) cleanup attribute.(CVE-2024-50012)
In the Linux kernel, the following vulnerability has been resolved: NFSv4: Prevent NULL-pointer dereference in nfs42_complete_copies() On the node of an NFS client, some files saved in the mountpoint of the NFS server were copied to another location of the same NFS server. Accidentally, the nfs42_complete_copies() got a NULL-pointer dereference crash with the following syslog: [232064.838881] NFSv4: state recovery failed for open file nfs/pvc-12b5200d-cd0f-46a3-b9f0-af8f4fe0ef64.qcow2, error = -116 [232064.839360] NFSv4: state recovery failed for open file nfs/pvc-12b5200d-cd0f-46a3-b9f0-af8f4fe0ef64.qcow2, error = -116 [232066.588183] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000058 [232066.588586] Mem abort info: [232066.588701] ESR = 0x0000000096000007 [232066.588862] EC = 0x25: DABT (current EL), IL = 32 bits [232066.589084] SET = 0, FnV = 0 [232066.589216] EA = 0, S1PTW = 0 [232066.589340] FSC = 0x07: level 3 translation fault [232066.589559] Data abort info: [232066.589683] ISV = 0, ISS = 0x00000007 [232066.589842] CM = 0, WnR = 0 [232066.589967] user pgtable: 64k pages, 48-bit VAs, pgdp=00002000956ff400 [232066.590231] [0000000000000058] pgd=08001100ae100003, p4d=08001100ae100003, pud=08001100ae100003, pmd=08001100b3c00003, pte=0000000000000000 [232066.590757] Internal error: Oops: 96000007 [#1] SMP [232066.590958] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace fscache netfs ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm vhost_net vhost vhost_iotlb tap tun ipt_rpfilter xt_multiport ip_set_hash_ip ip_set_hash_net xfrm_interface xfrm6_tunnel tunnel4 tunnel6 esp4 ah4 wireguard libcurve25519_generic veth xt_addrtype xt_set nf_conntrack_netlink ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_bitmap_port ip_set_hash_ipport dummy ip_set ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs iptable_filter sch_ingress nfnetlink_cttimeout vport_gre ip_gre ip_tunnel gre vport_geneve geneve vport_vxlan vxlan ip6_udp_tunnel udp_tunnel openvswitch nf_conncount dm_round_robin dm_service_time dm_multipath xt_nat xt_MASQUERADE nft_chain_nat nf_nat xt_mark xt_conntrack xt_comment nft_compat nft_counter nf_tables nfnetlink ocfs2 ocfs2_nodemanager ocfs2_stackglue iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ipmi_ssif nbd overlay 8021q garp mrp bonding tls rfkill sunrpc ext4 mbcache jbd2 [232066.591052] vfat fat cas_cache cas_disk ses enclosure scsi_transport_sas sg acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler ip_tables vfio_pci vfio_pci_core vfio_virqfd vfio_iommu_type1 vfio dm_mirror dm_region_hash dm_log dm_mod nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter bridge stp llc fuse xfs libcrc32c ast drm_vram_helper qla2xxx drm_kms_helper syscopyarea crct10dif_ce sysfillrect ghash_ce sysimgblt sha2_ce fb_sys_fops cec sha256_arm64 sha1_ce drm_ttm_helper ttm nvme_fc igb sbsa_gwdt nvme_fabrics drm nvme_core i2c_algo_bit i40e scsi_transport_fc megaraid_sas aes_neon_bs [232066.596953] CPU: 6 PID: 4124696 Comm: 10.253.166.125- Kdump: loaded Not tainted 5.15.131-9.cl9_ocfs2.aarch64 #1 [232066.597356] Hardware name: Great Wall .\x93\x8e...RF6260 V5/GWMSSE2GL1T, BIOS T656FBE_V3.0.18 2024-01-06 [232066.597721] pstate: 20400009 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [232066.598034] pc : nfs4_reclaim_open_state+0x220/0x800 [nfsv4] [232066.598327] lr : nfs4_reclaim_open_state+0x12c/0x800 [nfsv4] [232066.598595] sp : ffff8000f568fc70 [232066.598731] x29: ffff8000f568fc70 x28: 0000000000001000 x27: ffff21003db33000 [232066.599030] x26: ffff800005521ae0 x25: ffff0100f98fa3f0 x24: 0000000000000001 [232066.599319] x23: ffff800009920008 x22: ffff21003db33040 x21: ffff21003db33050 [232066.599628] x20: ffff410172fe9e40 x19: ffff410172fe9e00 x18: 0000000000000000 [232066.599914] x17: 0000000000000000 x16: 0000000000000004 x15: 0000000000000000 [232066.600195] x14: 0000000000000000 x13: ffff800008e685a8 x12: 00000000eac0c6e6 [232066.600498] x11: 00000000000000 ---truncated---(CVE-2024-50046)
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check null pointer before dereferencing se [WHAT & HOW] se is null checked previously in the same function, indicating it might be null; therefore, it must be checked when used again. This fixes 1 FORWARD_NULL issue reported by Coverity.(CVE-2024-50049)
In the Linux kernel, the following vulnerability has been resolved: usb: typec: tipd: Free IRQ only if it was requested before In polling mode, if no IRQ was requested there is no need to free it. Call devm_free_irq() only if client->irq is set. This fixes the warning caused by the tps6598x module removal: WARNING: CPU: 2 PID: 333 at kernel/irq/devres.c:144 devm_free_irq+0x80/0x8c ... ... Call trace: devm_free_irq+0x80/0x8c tps6598x_remove+0x28/0x88 [tps6598x] i2c_device_remove+0x2c/0x9c device_remove+0x4c/0x80 device_release_driver_internal+0x1cc/0x228 driver_detach+0x50/0x98 bus_remove_driver+0x6c/0xbc driver_unregister+0x30/0x60 i2c_del_driver+0x54/0x64 tps6598x_i2c_driver_exit+0x18/0xc3c [tps6598x] __arm64_sys_delete_module+0x184/0x264 invoke_syscall+0x48/0x110 el0_svc_common.constprop.0+0xc8/0xe8 do_el0_svc+0x20/0x2c el0_svc+0x28/0x98 el0t_64_sync_handler+0x13c/0x158 el0t_64_sync+0x190/0x194(CVE-2024-50057)
In the Linux kernel, the following vulnerability has been resolved: ntfs3: Change to non-blocking allocation in ntfs_d_hash d_hash is done while under "rcu-walk" and should not sleep. __get_name() allocates using GFP_KERNEL, having the possibility to sleep when under memory pressure. Change the allocation to GFP_NOWAIT.(CVE-2024-50065)
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"bpftool-6.6.0-48.0.0.53.oe2403.aarch64.rpm",
"bpftool-debuginfo-6.6.0-48.0.0.53.oe2403.aarch64.rpm",
"kernel-6.6.0-48.0.0.53.oe2403.aarch64.rpm",
"kernel-debuginfo-6.6.0-48.0.0.53.oe2403.aarch64.rpm",
"kernel-debugsource-6.6.0-48.0.0.53.oe2403.aarch64.rpm",
"kernel-devel-6.6.0-48.0.0.53.oe2403.aarch64.rpm",
"kernel-headers-6.6.0-48.0.0.53.oe2403.aarch64.rpm",
"kernel-source-6.6.0-48.0.0.53.oe2403.aarch64.rpm",
"kernel-tools-6.6.0-48.0.0.53.oe2403.aarch64.rpm",
"kernel-tools-debuginfo-6.6.0-48.0.0.53.oe2403.aarch64.rpm",
"kernel-tools-devel-6.6.0-48.0.0.53.oe2403.aarch64.rpm",
"perf-6.6.0-48.0.0.53.oe2403.aarch64.rpm",
"perf-debuginfo-6.6.0-48.0.0.53.oe2403.aarch64.rpm",
"python3-perf-6.6.0-48.0.0.53.oe2403.aarch64.rpm",
"python3-perf-debuginfo-6.6.0-48.0.0.53.oe2403.aarch64.rpm"
],
"src": [
"kernel-6.6.0-48.0.0.53.oe2403.src.rpm"
],
"x86_64": [
"bpftool-6.6.0-48.0.0.53.oe2403.x86_64.rpm",
"bpftool-debuginfo-6.6.0-48.0.0.53.oe2403.x86_64.rpm",
"kernel-6.6.0-48.0.0.53.oe2403.x86_64.rpm",
"kernel-debuginfo-6.6.0-48.0.0.53.oe2403.x86_64.rpm",
"kernel-debugsource-6.6.0-48.0.0.53.oe2403.x86_64.rpm",
"kernel-devel-6.6.0-48.0.0.53.oe2403.x86_64.rpm",
"kernel-headers-6.6.0-48.0.0.53.oe2403.x86_64.rpm",
"kernel-source-6.6.0-48.0.0.53.oe2403.x86_64.rpm",
"kernel-tools-6.6.0-48.0.0.53.oe2403.x86_64.rpm",
"kernel-tools-debuginfo-6.6.0-48.0.0.53.oe2403.x86_64.rpm",
"kernel-tools-devel-6.6.0-48.0.0.53.oe2403.x86_64.rpm",
"perf-6.6.0-48.0.0.53.oe2403.x86_64.rpm",
"perf-debuginfo-6.6.0-48.0.0.53.oe2403.x86_64.rpm",
"python3-perf-6.6.0-48.0.0.53.oe2403.x86_64.rpm",
"python3-perf-debuginfo-6.6.0-48.0.0.53.oe2403.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:24.03-LTS",
"name": "kernel",
"purl": "pkg:rpm/openEuler/kernel\u0026distro=openEuler-24.03-LTS"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.6.0-48.0.0.53.oe2403"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "Critical"
},
"details": "The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir() The debugfs_create_dir() function returns error pointers. It never returns NULL. So use IS_ERR() to check it.(CVE-2023-52917)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: media: pci: cx23885: check cx23885_vdev_init() return cx23885_vdev_init() can return a NULL pointer, but that pointer is used in the next line without a check. Add a NULL pointer check and go to the error unwind if it is NULL.(CVE-2023-52918)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbtrfs: make sure that WRITTEN is set on all metadata blocks\r\n\r\nWe previously would call btrfs_check_leaf() if we had the check\nintegrity code enabled, which meant that we could only run the extended\nleaf checks if we had WRITTEN set on the header flags.\r\n\r\nThis leaves a gap in our checking, because we could end up with\ncorruption on disk where WRITTEN isn\u0026apos;t set on the leaf, and then the\nextended leaf checks don\u0026apos;t get run which we rely on to validate all of\nthe item pointers to make sure we don\u0026apos;t access memory outside of the\nextent buffer.\r\n\r\nHowever, since 732fab95abe2 (\u0026quot;btrfs: check-integrity: remove\nCONFIG_BTRFS_FS_CHECK_INTEGRITY option\u0026quot;) we no longer call\nbtrfs_check_leaf() from btrfs_mark_buffer_dirty(), which means we only\never call it on blocks that are being written out, and thus have WRITTEN\nset, or that are being read in, which should have WRITTEN set.\r\n\r\nAdd checks to make sure we have WRITTEN set appropriately, and then make\nsure __btrfs_check_leaf() always does the item checking. This will\nprotect us from file systems that have been corrupted and no longer have\nWRITTEN set on some of the blocks.\r\n\r\nThis was hit on a crafted image tweaking the WRITTEN bit and reported by\nKASAN as out-of-bound access in the eb accessors. The example is a dir\nitem at the end of an eb.\r\n\r\n [2.042] BTRFS warning (device loop1): bad eb member start: ptr 0x3fff start 30572544 member offset 16410 size 2\n [2.040] general protection fault, probably for non-canonical address 0xe0009d1000000003: 0000 [#1] PREEMPT SMP KASAN NOPTI\n [2.537] KASAN: maybe wild-memory-access in range [0x0005088000000018-0x000508800000001f]\n [2.729] CPU: 0 PID: 2587 Comm: mount Not tainted 6.8.2 #1\n [2.729] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014\n [2.621] RIP: 0010:btrfs_get_16+0x34b/0x6d0\n [2.621] RSP: 0018:ffff88810871fab8 EFLAGS: 00000206\n [2.621] RAX: 0000a11000000003 RBX: ffff888104ff8720 RCX: ffff88811b2288c0\n [2.621] RDX: dffffc0000000000 RSI: ffffffff81dd8aca RDI: ffff88810871f748\n [2.621] RBP: 000000000000401a R08: 0000000000000001 R09: ffffed10210e3ee9\n [2.621] R10: ffff88810871f74f R11: 205d323430333737 R12: 000000000000001a\n [2.621] R13: 000508800000001a R14: 1ffff110210e3f5d R15: ffffffff850011e8\n [2.621] FS: 00007f56ea275840(0000) GS:ffff88811b200000(0000) knlGS:0000000000000000\n [2.621] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n [2.621] CR2: 00007febd13b75c0 CR3: 000000010bb50000 CR4: 00000000000006f0\n [2.621] Call Trace:\n [2.621] \u0026lt;TASK\u0026gt;\n [2.621] ? show_regs+0x74/0x80\n [2.621] ? die_addr+0x46/0xc0\n [2.621] ? exc_general_protection+0x161/0x2a0\n [2.621] ? asm_exc_general_protection+0x26/0x30\n [2.621] ? btrfs_get_16+0x33a/0x6d0\n [2.621] ? btrfs_get_16+0x34b/0x6d0\n [2.621] ? btrfs_get_16+0x33a/0x6d0\n [2.621] ? __pfx_btrfs_get_16+0x10/0x10\n [2.621] ? __pfx_mutex_unlock+0x10/0x10\n [2.621] btrfs_match_dir_item_name+0x101/0x1a0\n [2.621] btrfs_lookup_dir_item+0x1f3/0x280\n [2.621] ? __pfx_btrfs_lookup_dir_item+0x10/0x10\n [2.621] btrfs_get_tree+0xd25/0x1910\r\n\r\n[ copy more details from report ](CVE-2024-35949)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nBluetooth: ISO: Fix not validating setsockopt user input\r\n\r\nCheck user input length before copying data.(CVE-2024-35964)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\niommu/arm-smmu: Use the correct type in nvidia_smmu_context_fault()\r\n\r\nThis was missed because of the function pointer indirection.\r\n\r\nnvidia_smmu_context_fault() is also installed as a irq function, and the\n\u0026apos;void *\u0026apos; was changed to a struct arm_smmu_domain. Since the iommu_domain\nis embedded at a non-zero offset this causes nvidia_smmu_context_fault()\nto miscompute the offset. Fixup the types.\r\n\r\n Unable to handle kernel NULL pointer dereference at virtual address 0000000000000120\n Mem abort info:\n ESR = 0x0000000096000004\n EC = 0x25: DABT (current EL), IL = 32 bits\n SET = 0, FnV = 0\n EA = 0, S1PTW = 0\n FSC = 0x04: level 0 translation fault\n Data abort info:\n ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000\n CM = 0, WnR = 0, TnD = 0, TagAccess = 0\n GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0\n user pgtable: 4k pages, 48-bit VAs, pgdp=0000000107c9f000\n [0000000000000120] pgd=0000000000000000, p4d=0000000000000000\n Internal error: Oops: 0000000096000004 [#1] SMP\n Modules linked in:\n CPU: 1 PID: 47 Comm: kworker/u25:0 Not tainted 6.9.0-0.rc7.58.eln136.aarch64 #1\n Hardware name: Unknown NVIDIA Jetson Orin NX/NVIDIA Jetson Orin NX, BIOS 3.1-32827747 03/19/2023\n Workqueue: events_unbound deferred_probe_work_func\n pstate: 604000c9 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n pc : nvidia_smmu_context_fault+0x1c/0x158\n lr : __free_irq+0x1d4/0x2e8\n sp : ffff80008044b6f0\n x29: ffff80008044b6f0 x28: ffff000080a60b18 x27: ffffd32b5172e970\n x26: 0000000000000000 x25: ffff0000802f5aac x24: ffff0000802f5a30\n x23: ffff0000802f5b60 x22: 0000000000000057 x21: 0000000000000000\n x20: ffff0000802f5a00 x19: ffff000087d4cd80 x18: ffffffffffffffff\n x17: 6234362066666666 x16: 6630303078302d30 x15: ffff00008156d888\n x14: 0000000000000000 x13: ffff0000801db910 x12: ffff00008156d6d0\n x11: 0000000000000003 x10: ffff0000801db918 x9 : ffffd32b50f94d9c\n x8 : 1fffe0001032fda1 x7 : ffff00008197ed00 x6 : 000000000000000f\n x5 : 000000000000010e x4 : 000000000000010e x3 : 0000000000000000\n x2 : ffffd32b51720cd8 x1 : ffff000087e6f700 x0 : 0000000000000057\n Call trace:\n nvidia_smmu_context_fault+0x1c/0x158\n __free_irq+0x1d4/0x2e8\n free_irq+0x3c/0x80\n devm_free_irq+0x64/0xa8\n arm_smmu_domain_free+0xc4/0x158\n iommu_domain_free+0x44/0xa0\n iommu_deinit_device+0xd0/0xf8\n __iommu_group_remove_device+0xcc/0xe0\n iommu_bus_notifier+0x64/0xa8\n notifier_call_chain+0x78/0x148\n blocking_notifier_call_chain+0x4c/0x90\n bus_notify+0x44/0x70\n device_del+0x264/0x3e8\n pci_remove_bus_device+0x84/0x120\n pci_remove_root_bus+0x5c/0xc0\n dw_pcie_host_deinit+0x38/0xe0\n tegra_pcie_config_rp+0xc0/0x1f0\n tegra_pcie_dw_probe+0x34c/0x700\n platform_probe+0x70/0xe8\n really_probe+0xc8/0x3a0\n __driver_probe_device+0x84/0x160\n driver_probe_device+0x44/0x130\n __device_attach_driver+0xc4/0x170\n bus_for_each_drv+0x90/0x100\n __device_attach+0xa8/0x1c8\n device_initial_probe+0x1c/0x30\n bus_probe_device+0xb0/0xc0\n deferred_probe_work_func+0xbc/0x120\n process_one_work+0x194/0x490\n worker_thread+0x284/0x3b0\n kthread+0xf4/0x108\n ret_from_fork+0x10/0x20\n Code: a9b97bfd 910003fd a9025bf5 f85a0035 (b94122a1)(CVE-2024-36884)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndev/parport: fix the array out-of-bounds risk\r\n\r\nFixed array out-of-bounds issues caused by sprintf\nby replacing it with snprintf for safer data copying,\nensuring the destination buffer is not overflowed.\r\n\r\nBelow is the stack trace I encountered during the actual issue:\r\n\r\n[ 66.575408s] [pid:5118,cpu4,QThread,4]Kernel panic - not syncing: stack-protector:\nKernel stack is corrupted in: do_hardware_base_addr+0xcc/0xd0 [parport]\n[ 66.575408s] [pid:5118,cpu4,QThread,5]CPU: 4 PID: 5118 Comm:\nQThread Tainted: G S W O 5.10.97-arm64-desktop #7100.57021.2\n[ 66.575439s] [pid:5118,cpu4,QThread,6]TGID: 5087 Comm: EFileApp\n[ 66.575439s] [pid:5118,cpu4,QThread,7]Hardware name: HUAWEI HUAWEI QingYun\nPGUX-W515x-B081/SP1PANGUXM, BIOS 1.00.07 04/29/2024\n[ 66.575439s] [pid:5118,cpu4,QThread,8]Call trace:\n[ 66.575469s] [pid:5118,cpu4,QThread,9] dump_backtrace+0x0/0x1c0\n[ 66.575469s] [pid:5118,cpu4,QThread,0] show_stack+0x14/0x20\n[ 66.575469s] [pid:5118,cpu4,QThread,1] dump_stack+0xd4/0x10c\n[ 66.575500s] [pid:5118,cpu4,QThread,2] panic+0x1d8/0x3bc\n[ 66.575500s] [pid:5118,cpu4,QThread,3] __stack_chk_fail+0x2c/0x38\n[ 66.575500s] [pid:5118,cpu4,QThread,4] do_hardware_base_addr+0xcc/0xd0 [parport](CVE-2024-42301)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\njfs: Fix array-index-out-of-bounds in diFree(CVE-2024-43858)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/nouveau: prime: fix refcount underflow\r\n\r\nCalling nouveau_bo_ref() on a nouveau_bo without initializing it (and\nhence the backing ttm_bo) leads to a refcount underflow.\r\n\r\nInstead of calling nouveau_bo_ref() in the unwind path of\ndrm_gem_object_init(), clean things up manually.\r\n\r\n(cherry picked from commit 1b93f3e89d03cfc576636e195466a0d728ad8de5)(CVE-2024-43867)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndevres: Fix memory leakage caused by driver API devm_free_percpu()\r\n\r\nIt will cause memory leakage when use driver API devm_free_percpu()\nto free memory allocated by devm_alloc_percpu(), fixed by using\ndevres_release() instead of devres_destroy() within devm_free_percpu().(CVE-2024-43871)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/msm/dpu: cleanup FB if dpu_format_populate_layout fails\r\n\r\nIf the dpu_format_populate_layout() fails, then FB is prepared, but not\ncleaned up. This ends up leaking the pin_count on the GEM object and\ncauses a splat during DRM file closure:\r\n\r\nmsm_obj-\u0026gt;pin_count\nWARNING: CPU: 2 PID: 569 at drivers/gpu/drm/msm/msm_gem.c:121 update_lru_locked+0xc4/0xcc\n[...]\nCall trace:\n update_lru_locked+0xc4/0xcc\n put_pages+0xac/0x100\n msm_gem_free_object+0x138/0x180\n drm_gem_object_free+0x1c/0x30\n drm_gem_object_handle_put_unlocked+0x108/0x10c\n drm_gem_object_release_handle+0x58/0x70\n idr_for_each+0x68/0xec\n drm_gem_release+0x28/0x40\n drm_file_free+0x174/0x234\n drm_release+0xb0/0x160\n __fput+0xc0/0x2c8\n __fput_sync+0x50/0x5c\n __arm64_sys_close+0x38/0x7c\n invoke_syscall+0x48/0x118\n el0_svc_common.constprop.0+0x40/0xe0\n do_el0_svc+0x1c/0x28\n el0_svc+0x4c/0x120\n el0t_64_sync_handler+0x100/0x12c\n el0t_64_sync+0x190/0x194\nirq event stamp: 129818\nhardirqs last enabled at (129817): [\u0026lt;ffffa5f6d953fcc0\u0026gt;] console_unlock+0x118/0x124\nhardirqs last disabled at (129818): [\u0026lt;ffffa5f6da7dcf04\u0026gt;] el1_dbg+0x24/0x8c\nsoftirqs last enabled at (129808): [\u0026lt;ffffa5f6d94afc18\u0026gt;] handle_softirqs+0x4c8/0x4e8\nsoftirqs last disabled at (129785): [\u0026lt;ffffa5f6d94105e4\u0026gt;] __do_softirq+0x14/0x20\r\n\r\nPatchwork: https://patchwork.freedesktop.org/patch/600714/(CVE-2024-44982)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: ethernet: mtk_wed: fix use-after-free panic in mtk_wed_setup_tc_block_cb()\r\n\r\nWhen there are multiple ap interfaces on one band and with WED on,\nturning the interface down will cause a kernel panic on MT798X.\r\n\r\nPreviously, cb_priv was freed in mtk_wed_setup_tc_block() without\nmarking NULL,and mtk_wed_setup_tc_block_cb() didn\u0026apos;t check the value, too.\r\n\r\nAssign NULL after free cb_priv in mtk_wed_setup_tc_block() and check NULL\nin mtk_wed_setup_tc_block_cb().\r\n\r\n----------\nUnable to handle kernel paging request at virtual address 0072460bca32b4f5\nCall trace:\n mtk_wed_setup_tc_block_cb+0x4/0x38\n 0xffffffc0794084bc\n tcf_block_playback_offloads+0x70/0x1e8\n tcf_block_unbind+0x6c/0xc8\n...\n---------(CVE-2024-44997)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nusb: dwc3: core: Prevent USB core invalid event buffer address access\r\n\r\nThis commit addresses an issue where the USB core could access an\ninvalid event buffer address during runtime suspend, potentially causing\nSMMU faults and other memory issues in Exynos platforms. The problem\narises from the following sequence.\n 1. In dwc3_gadget_suspend, there is a chance of a timeout when\n moving the USB core to the halt state after clearing the\n run/stop bit by software.\n 2. In dwc3_core_exit, the event buffer is cleared regardless of\n the USB core\u0026apos;s status, which may lead to an SMMU faults and\n other memory issues. if the USB core tries to access the event\n buffer address.\r\n\r\nTo prevent this hardware quirk on Exynos platforms, this commit ensures\nthat the event buffer address is not cleared by software when the USB\ncore is active during runtime suspend by checking its status before\nclearing the buffer address.(CVE-2024-46675)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ngtp: fix a potential NULL pointer dereference\r\n\r\nWhen sockfd_lookup() fails, gtp_encap_enable_socket() returns a\nNULL pointer, but its callers only check for error pointers thus miss\nthe NULL pointer case.\r\n\r\nFix it by returning an error pointer with the error code carried from\nsockfd_lookup().\r\n\r\n(I found this bug during code inspection.)(CVE-2024-46677)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: Fix out-of-bounds read of df_v1_7_channel_number\r\n\r\nCheck the fb_channel_number range to avoid the array out-of-bounds\nread error(CVE-2024-46724)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nBluetooth: btnxpuart: Fix Null pointer dereference in btnxpuart_flush()\r\n\r\nThis adds a check before freeing the rx-\u0026gt;skb in flush and close\nfunctions to handle the kernel crash seen while removing driver after FW\ndownload fails or before FW download completes.\r\n\r\ndmesg log:\n[ 54.634586] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000080\n[ 54.643398] Mem abort info:\n[ 54.646204] ESR = 0x0000000096000004\n[ 54.649964] EC = 0x25: DABT (current EL), IL = 32 bits\n[ 54.655286] SET = 0, FnV = 0\n[ 54.658348] EA = 0, S1PTW = 0\n[ 54.661498] FSC = 0x04: level 0 translation fault\n[ 54.666391] Data abort info:\n[ 54.669273] ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000\n[ 54.674768] CM = 0, WnR = 0, TnD = 0, TagAccess = 0\n[ 54.674771] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0\n[ 54.674775] user pgtable: 4k pages, 48-bit VAs, pgdp=0000000048860000\n[ 54.674780] [0000000000000080] pgd=0000000000000000, p4d=0000000000000000\n[ 54.703880] Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP\n[ 54.710152] Modules linked in: btnxpuart(-) overlay fsl_jr_uio caam_jr caamkeyblob_desc caamhash_desc caamalg_desc crypto_engine authenc libdes crct10dif_ce polyval_ce polyval_generic snd_soc_imx_spdif snd_soc_imx_card snd_soc_ak5558 snd_soc_ak4458 caam secvio error snd_soc_fsl_micfil snd_soc_fsl_spdif snd_soc_fsl_sai snd_soc_fsl_utils imx_pcm_dma gpio_ir_recv rc_core sch_fq_codel fuse\n[ 54.744357] CPU: 3 PID: 72 Comm: kworker/u9:0 Not tainted 6.6.3-otbr-g128004619037 #2\n[ 54.744364] Hardware name: FSL i.MX8MM EVK board (DT)\n[ 54.744368] Workqueue: hci0 hci_power_on\n[ 54.757244] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[ 54.757249] pc : kfree_skb_reason+0x18/0xb0\n[ 54.772299] lr : btnxpuart_flush+0x40/0x58 [btnxpuart]\n[ 54.782921] sp : ffff8000805ebca0\n[ 54.782923] x29: ffff8000805ebca0 x28: ffffa5c6cf1869c0 x27: ffffa5c6cf186000\n[ 54.782931] x26: ffff377b84852400 x25: ffff377b848523c0 x24: ffff377b845e7230\n[ 54.782938] x23: ffffa5c6ce8dbe08 x22: ffffa5c6ceb65410 x21: 00000000ffffff92\n[ 54.782945] x20: ffffa5c6ce8dbe98 x19: ffffffffffffffac x18: ffffffffffffffff\n[ 54.807651] x17: 0000000000000000 x16: ffffa5c6ce2824ec x15: ffff8001005eb857\n[ 54.821917] x14: 0000000000000000 x13: ffffa5c6cf1a02e0 x12: 0000000000000642\n[ 54.821924] x11: 0000000000000040 x10: ffffa5c6cf19d690 x9 : ffffa5c6cf19d688\n[ 54.821931] x8 : ffff377b86000028 x7 : 0000000000000000 x6 : 0000000000000000\n[ 54.821938] x5 : ffff377b86000000 x4 : 0000000000000000 x3 : 0000000000000000\n[ 54.843331] x2 : 0000000000000000 x1 : 0000000000000002 x0 : ffffffffffffffac\n[ 54.857599] Call trace:\n[ 54.857601] kfree_skb_reason+0x18/0xb0\n[ 54.863878] btnxpuart_flush+0x40/0x58 [btnxpuart]\n[ 54.863888] hci_dev_open_sync+0x3a8/0xa04\n[ 54.872773] hci_power_on+0x54/0x2e4\n[ 54.881832] process_one_work+0x138/0x260\n[ 54.881842] worker_thread+0x32c/0x438\n[ 54.881847] kthread+0x118/0x11c\n[ 54.881853] ret_from_fork+0x10/0x20\n[ 54.896406] Code: a9be7bfd 910003fd f9000bf3 aa0003f3 (b940d400)\n[ 54.896410] ---[ end trace 0000000000000000 ]---(CVE-2024-46749)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nhwmon: (nct6775-core) Fix underflows seen when writing limit attributes\r\n\r\nDIV_ROUND_CLOSEST() after kstrtol() results in an underflow if a large\nnegative number such as -9223372036854775808 is provided by the user.\nFix it by reordering clamp_val() and DIV_ROUND_CLOSEST() operations.(CVE-2024-46757)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Validate function returns\r\n\r\n[WHAT \u0026amp; HOW]\nFunction return values must be checked before data can be used\nin subsequent functions.\r\n\r\nThis fixes 4 CHECKED_RETURN issues reported by Coverity.(CVE-2024-46775)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nila: call nf_unregister_net_hooks() sooner\r\n\r\nsyzbot found an use-after-free Read in ila_nf_input [1]\r\n\r\nIssue here is that ila_xlat_exit_net() frees the rhashtable,\nthen call nf_unregister_net_hooks().\r\n\r\nIt should be done in the reverse way, with a synchronize_rcu().\r\n\r\nThis is a good match for a pre_exit() method.\r\n\r\n[1]\n BUG: KASAN: use-after-free in rht_key_hashfn include/linux/rhashtable.h:159 [inline]\n BUG: KASAN: use-after-free in __rhashtable_lookup include/linux/rhashtable.h:604 [inline]\n BUG: KASAN: use-after-free in rhashtable_lookup include/linux/rhashtable.h:646 [inline]\n BUG: KASAN: use-after-free in rhashtable_lookup_fast+0x77a/0x9b0 include/linux/rhashtable.h:672\nRead of size 4 at addr ffff888064620008 by task ksoftirqd/0/16\r\n\r\nCPU: 0 UID: 0 PID: 16 Comm: ksoftirqd/0 Not tainted 6.11.0-rc4-syzkaller-00238-g2ad6d23f465a #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __dump_stack lib/dump_stack.c:93 [inline]\n dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119\n print_address_description mm/kasan/report.c:377 [inline]\n print_report+0x169/0x550 mm/kasan/report.c:488\n kasan_report+0x143/0x180 mm/kasan/report.c:601\n rht_key_hashfn include/linux/rhashtable.h:159 [inline]\n __rhashtable_lookup include/linux/rhashtable.h:604 [inline]\n rhashtable_lookup include/linux/rhashtable.h:646 [inline]\n rhashtable_lookup_fast+0x77a/0x9b0 include/linux/rhashtable.h:672\n ila_lookup_wildcards net/ipv6/ila/ila_xlat.c:132 [inline]\n ila_xlat_addr net/ipv6/ila/ila_xlat.c:652 [inline]\n ila_nf_input+0x1fe/0x3c0 net/ipv6/ila/ila_xlat.c:190\n nf_hook_entry_hookfn include/linux/netfilter.h:154 [inline]\n nf_hook_slow+0xc3/0x220 net/netfilter/core.c:626\n nf_hook include/linux/netfilter.h:269 [inline]\n NF_HOOK+0x29e/0x450 include/linux/netfilter.h:312\n __netif_receive_skb_one_core net/core/dev.c:5661 [inline]\n __netif_receive_skb+0x1ea/0x650 net/core/dev.c:5775\n process_backlog+0x662/0x15b0 net/core/dev.c:6108\n __napi_poll+0xcb/0x490 net/core/dev.c:6772\n napi_poll net/core/dev.c:6841 [inline]\n net_rx_action+0x89b/0x1240 net/core/dev.c:6963\n handle_softirqs+0x2c4/0x970 kernel/softirq.c:554\n run_ksoftirqd+0xca/0x130 kernel/softirq.c:928\n smpboot_thread_fn+0x544/0xa30 kernel/smpboot.c:164\n kthread+0x2f0/0x390 kernel/kthread.c:389\n ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244\n \u0026lt;/TASK\u0026gt;\r\n\r\nThe buggy address belongs to the physical page:\npage: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x64620\nflags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff)\npage_type: 0xbfffffff(buddy)\nraw: 00fff00000000000 ffffea0000959608 ffffea00019d9408 0000000000000000\nraw: 0000000000000000 0000000000000003 00000000bfffffff 0000000000000000\npage dumped because: kasan: bad access detected\npage_owner tracks the page as freed\npage last allocated via order 3, migratetype Unmovable, gfp_mask 0x52dc0(GFP_KERNEL|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_ZERO), pid 5242, tgid 5242 (syz-executor), ts 73611328570, free_ts 618981657187\n set_page_owner include/linux/page_owner.h:32 [inline]\n post_alloc_hook+0x1f3/0x230 mm/page_alloc.c:1493\n prep_new_page mm/page_alloc.c:1501 [inline]\n get_page_from_freelist+0x2e4c/0x2f10 mm/page_alloc.c:3439\n __alloc_pages_noprof+0x256/0x6c0 mm/page_alloc.c:4695\n __alloc_pages_node_noprof include/linux/gfp.h:269 [inline]\n alloc_pages_node_noprof include/linux/gfp.h:296 [inline]\n ___kmalloc_large_node+0x8b/0x1d0 mm/slub.c:4103\n __kmalloc_large_node_noprof+0x1a/0x80 mm/slub.c:4130\n __do_kmalloc_node mm/slub.c:4146 [inline]\n __kmalloc_node_noprof+0x2d2/0x440 mm/slub.c:4164\n __kvmalloc_node_noprof+0x72/0x190 mm/util.c:650\n bucket_table_alloc lib/rhashtable.c:186 [inline]\n rhashtable_init_noprof+0x534/0xa60 lib/rhashtable.c:1071\n ila_xlat_init_net+0xa0/0x110 net/ipv6/ila/ila_xlat.c:613\n ops_ini\n---truncated---(CVE-2024-46782)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: added NULL check at start of dc_validate_stream\r\n\r\n[Why]\nprevent invalid memory access\r\n\r\n[How]\ncheck if dc and stream are NULL(CVE-2024-46802)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nspi: nxp-fspi: fix the KASAN report out-of-bounds bug\r\n\r\nChange the memcpy length to fix the out-of-bounds issue when writing the\ndata that is not 4 byte aligned to TX FIFO.\r\n\r\nTo reproduce the issue, write 3 bytes data to NOR chip.\r\n\r\ndd if=3b of=/dev/mtd0\n[ 36.926103] ==================================================================\n[ 36.933409] BUG: KASAN: slab-out-of-bounds in nxp_fspi_exec_op+0x26ec/0x2838\n[ 36.940514] Read of size 4 at addr ffff00081037c2a0 by task dd/455\n[ 36.946721]\n[ 36.948235] CPU: 3 UID: 0 PID: 455 Comm: dd Not tainted 6.11.0-rc5-gc7b0e37c8434 #1070\n[ 36.956185] Hardware name: Freescale i.MX8QM MEK (DT)\n[ 36.961260] Call trace:\n[ 36.963723] dump_backtrace+0x90/0xe8\n[ 36.967414] show_stack+0x18/0x24\n[ 36.970749] dump_stack_lvl+0x78/0x90\n[ 36.974451] print_report+0x114/0x5cc\n[ 36.978151] kasan_report+0xa4/0xf0\n[ 36.981670] __asan_report_load_n_noabort+0x1c/0x28\n[ 36.986587] nxp_fspi_exec_op+0x26ec/0x2838\n[ 36.990800] spi_mem_exec_op+0x8ec/0xd30\n[ 36.994762] spi_mem_no_dirmap_read+0x190/0x1e0\n[ 36.999323] spi_mem_dirmap_write+0x238/0x32c\n[ 37.003710] spi_nor_write_data+0x220/0x374\n[ 37.007932] spi_nor_write+0x110/0x2e8\n[ 37.011711] mtd_write_oob_std+0x154/0x1f0\n[ 37.015838] mtd_write_oob+0x104/0x1d0\n[ 37.019617] mtd_write+0xb8/0x12c\n[ 37.022953] mtdchar_write+0x224/0x47c\n[ 37.026732] vfs_write+0x1e4/0x8c8\n[ 37.030163] ksys_write+0xec/0x1d0\n[ 37.033586] __arm64_sys_write+0x6c/0x9c\n[ 37.037539] invoke_syscall+0x6c/0x258\n[ 37.041327] el0_svc_common.constprop.0+0x160/0x22c\n[ 37.046244] do_el0_svc+0x44/0x5c\n[ 37.049589] el0_svc+0x38/0x78\n[ 37.052681] el0t_64_sync_handler+0x13c/0x158\n[ 37.057077] el0t_64_sync+0x190/0x194\n[ 37.060775]\n[ 37.062274] Allocated by task 455:\n[ 37.065701] kasan_save_stack+0x2c/0x54\n[ 37.069570] kasan_save_track+0x20/0x3c\n[ 37.073438] kasan_save_alloc_info+0x40/0x54\n[ 37.077736] __kasan_kmalloc+0xa0/0xb8\n[ 37.081515] __kmalloc_noprof+0x158/0x2f8\n[ 37.085563] mtd_kmalloc_up_to+0x120/0x154\n[ 37.089690] mtdchar_write+0x130/0x47c\n[ 37.093469] vfs_write+0x1e4/0x8c8\n[ 37.096901] ksys_write+0xec/0x1d0\n[ 37.100332] __arm64_sys_write+0x6c/0x9c\n[ 37.104287] invoke_syscall+0x6c/0x258\n[ 37.108064] el0_svc_common.constprop.0+0x160/0x22c\n[ 37.112972] do_el0_svc+0x44/0x5c\n[ 37.116319] el0_svc+0x38/0x78\n[ 37.119401] el0t_64_sync_handler+0x13c/0x158\n[ 37.123788] el0t_64_sync+0x190/0x194\n[ 37.127474]\n[ 37.128977] The buggy address belongs to the object at ffff00081037c2a0\n[ 37.128977] which belongs to the cache kmalloc-8 of size 8\n[ 37.141177] The buggy address is located 0 bytes inside of\n[ 37.141177] allocated 3-byte region [ffff00081037c2a0, ffff00081037c2a3)\n[ 37.153465]\n[ 37.154971] The buggy address belongs to the physical page:\n[ 37.160559] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x89037c\n[ 37.168596] flags: 0xbfffe0000000000(node=0|zone=2|lastcpupid=0x1ffff)\n[ 37.175149] page_type: 0xfdffffff(slab)\n[ 37.179021] raw: 0bfffe0000000000 ffff000800002500 dead000000000122 0000000000000000\n[ 37.186788] raw: 0000000000000000 0000000080800080 00000001fdffffff 0000000000000000\n[ 37.194553] page dumped because: kasan: bad access detected\n[ 37.200144]\n[ 37.201647] Memory state around the buggy address:\n[ 37.206460] ffff00081037c180: fa fc fc fc fa fc fc fc fa fc fc fc fa fc fc fc\n[ 37.213701] ffff00081037c200: fa fc fc fc 05 fc fc fc 03 fc fc fc 02 fc fc fc\n[ 37.220946] \u0026gt;ffff00081037c280: 06 fc fc fc 03 fc fc fc fc fc fc fc fc fc fc fc\n[ 37.228186] ^\n[ 37.232473] ffff00081037c300: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n[ 37.239718] ffff00081037c380: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc\n[ 37.246962] ==============================================================\n---truncated---(CVE-2024-46853)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Correct the defined value for AMDGPU_DMUB_NOTIFICATION_MAX\r\n\r\n[Why \u0026amp; How]\nIt actually exposes \u0026apos;6\u0026apos; types in enum dmub_notification_type. Not 5. Using smaller\nnumber to create array dmub_callback \u0026amp; dmub_thread_offload has potential to access\nitem out of array bound. Fix it.(CVE-2024-46871)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsmack: tcp: ipv4, fix incorrect labeling\r\n\r\nCurrently, Smack mirrors the label of incoming tcp/ipv4 connections:\nwhen a label \u0026apos;foo\u0026apos; connects to a label \u0026apos;bar\u0026apos; with tcp/ipv4,\n\u0026apos;foo\u0026apos; always gets \u0026apos;foo\u0026apos; in returned ipv4 packets. So,\n1) returned packets are incorrectly labeled (\u0026apos;foo\u0026apos; instead of \u0026apos;bar\u0026apos;)\n2) \u0026apos;bar\u0026apos; can write to \u0026apos;foo\u0026apos; without being authorized to write.\r\n\r\nHere is a scenario how to see this:\r\n\r\n* Take two machines, let\u0026apos;s call them C and S,\n with active Smack in the default state\n (no settings, no rules, no labeled hosts, only builtin labels)\r\n\r\n* At S, add Smack rule \u0026apos;foo bar w\u0026apos;\n (labels \u0026apos;foo\u0026apos; and \u0026apos;bar\u0026apos; are instantiated at S at this moment)\r\n\r\n* At S, at label \u0026apos;bar\u0026apos;, launch a program\n that listens for incoming tcp/ipv4 connections\r\n\r\n* From C, at label \u0026apos;foo\u0026apos;, connect to the listener at S.\n (label \u0026apos;foo\u0026apos; is instantiated at C at this moment)\n Connection succeedes and works.\r\n\r\n* Send some data in both directions.\n* Collect network traffic of this connection.\r\n\r\nAll packets in both directions are labeled with the CIPSO\nof the label \u0026apos;foo\u0026apos;. Hence, label \u0026apos;bar\u0026apos; writes to \u0026apos;foo\u0026apos; without\nbeing authorized, and even without ever being known at C.\r\n\r\nIf anybody cares: exactly the same happens with DCCP.\r\n\r\nThis behavior 1st manifested in release 2.6.29.4 (see Fixes below)\nand it looks unintentional. At least, no explanation was provided.\r\n\r\nI changed returned packes label into the \u0026apos;bar\u0026apos;,\nto bring it into line with the Smack documentation claims.(CVE-2024-47659)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfsnotify: clear PARENT_WATCHED flags lazily\r\n\r\nIn some setups directories can have many (usually negative) dentries.\nHence __fsnotify_update_child_dentry_flags() function can take a\nsignificant amount of time. Since the bulk of this function happens\nunder inode-\u0026gt;i_lock this causes a significant contention on the lock\nwhen we remove the watch from the directory as the\n__fsnotify_update_child_dentry_flags() call from fsnotify_recalc_mask()\nraces with __fsnotify_update_child_dentry_flags() calls from\n__fsnotify_parent() happening on children. This can lead upto softlockup\nreports reported by users.\r\n\r\nFix the problem by calling fsnotify_update_children_dentry_flags() to\nset PARENT_WATCHED flags only when parent starts watching children.\r\n\r\nWhen parent stops watching children, clear false positive PARENT_WATCHED\nflags lazily in __fsnotify_parent() for each accessed child.(CVE-2024-47660)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Avoid overflow from uint32_t to uint8_t\r\n\r\n[WHAT \u0026amp; HOW]\ndmub_rb_cmd\u0026apos;s ramping_boundary has size of uint8_t and it is assigned\n0xFFFF. Fix it by changing it to uint8_t with value of 0xFF.\r\n\r\nThis fixes 2 INTEGER_OVERFLOW issues reported by Coverity.(CVE-2024-47661)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nPCI: keystone: Add workaround for Errata #i2037 (AM65x SR 1.0)\r\n\r\nErrata #i2037 in AM65x/DRA80xM Processors Silicon Revision 1.0\n(SPRZ452D_July 2018_Revised December 2019 [1]) mentions when an\ninbound PCIe TLP spans more than two internal AXI 128-byte bursts,\nthe bus may corrupt the packet payload and the corrupt data may\ncause associated applications or the processor to hang.\r\n\r\nThe workaround for Errata #i2037 is to limit the maximum read\nrequest size and maximum payload size to 128 bytes. Add workaround\nfor Errata #i2037 here.\r\n\r\nThe errata and workaround is applicable only to AM65x SR 1.0 and\nlater versions of the silicon will have this fixed.\r\n\r\n[1] -\u0026gt; https://www.ti.com/lit/er/sprz452i/sprz452i.pdf(CVE-2024-47667)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7996: fix NULL pointer dereference in mt7996_mcu_sta_bfer_he Fix the NULL pointer dereference in mt7996_mcu_sta_bfer_he routine adding an sta interface to the mt7996 driver. Found by code review.(CVE-2024-47681)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Skip Recompute DSC Params if no Stream on Link [why] Encounter NULL pointer dereference uner mst + dsc setup. BUG: kernel NULL pointer dereference, address: 0000000000000008 PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP NOPTI CPU: 4 PID: 917 Comm: sway Not tainted 6.3.9-arch1-1 #1 124dc55df4f5272ccb409f39ef4872fc2b3376a2 Hardware name: LENOVO 20NKS01Y00/20NKS01Y00, BIOS R12ET61W(1.31 ) 07/28/2022 RIP: 0010:drm_dp_atomic_find_time_slots+0x5e/0x260 [drm_display_helper] Code: 01 00 00 48 8b 85 60 05 00 00 48 63 80 88 00 00 00 3b 43 28 0f 8d 2e 01 00 00 48 8b 53 30 48 8d 04 80 48 8d 04 c2 48 8b 40 18 \u0026lt;48\u0026gt; 8\u0026gt; RSP: 0018:ffff960cc2df77d8 EFLAGS: 00010293 RAX: 0000000000000000 RBX: ffff8afb87e81280 RCX: 0000000000000224 RDX: ffff8afb9ee37c00 RSI: ffff8afb8da1a578 RDI: ffff8afb87e81280 RBP: ffff8afb83d67000 R08: 0000000000000001 R09: ffff8afb9652f850 R10: ffff960cc2df7908 R11: 0000000000000002 R12: 0000000000000000 R13: ffff8afb8d7688a0 R14: ffff8afb8da1a578 R15: 0000000000000224 FS: 00007f4dac35ce00(0000) GS:ffff8afe30b00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000008 CR3: 000000010ddc6000 CR4: 00000000003506e0 Call Trace: \u0026lt;TASK\u0026gt; ? __die+0x23/0x70 ? page_fault_oops+0x171/0x4e0 ? plist_add+0xbe/0x100 ? exc_page_fault+0x7c/0x180 ? asm_exc_page_fault+0x26/0x30 ? drm_dp_atomic_find_time_slots+0x5e/0x260 [drm_display_helper 0e67723696438d8e02b741593dd50d80b44c2026] ? drm_dp_atomic_find_time_slots+0x28/0x260 [drm_display_helper 0e67723696438d8e02b741593dd50d80b44c2026] compute_mst_dsc_configs_for_link+0x2ff/0xa40 [amdgpu 62e600d2a75e9158e1cd0a243bdc8e6da040c054] ? fill_plane_buffer_attributes+0x419/0x510 [amdgpu 62e600d2a75e9158e1cd0a243bdc8e6da040c054] compute_mst_dsc_configs_for_state+0x1e1/0x250 [amdgpu 62e600d2a75e9158e1cd0a243bdc8e6da040c054] amdgpu_dm_atomic_check+0xecd/0x1190 [amdgpu 62e600d2a75e9158e1cd0a243bdc8e6da040c054] drm_atomic_check_only+0x5c5/0xa40 drm_mode_atomic_ioctl+0x76e/0xbc0 [how] dsc recompute should be skipped if no mode change detected on the new request. If detected, keep checking whether the stream is already on current state or not.(CVE-2024-47683)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: tcp: check skb is non-NULL in tcp_rto_delta_us() We have some machines running stock Ubuntu 20.04.6 which is their 5.4.0-174-generic kernel that are running ceph and recently hit a null ptr dereference in tcp_rearm_rto(). Initially hitting it from the TLP path, but then later we also saw it getting hit from the RACK case as well. Here are examples of the oops messages we saw in each of those cases: Jul 26 15:05:02 rx [11061395.780353] BUG: kernel NULL pointer dereference, address: 0000000000000020 Jul 26 15:05:02 rx [11061395.787572] #PF: supervisor read access in kernel mode Jul 26 15:05:02 rx [11061395.792971] #PF: error_code(0x0000) - not-present page Jul 26 15:05:02 rx [11061395.798362] PGD 0 P4D 0 Jul 26 15:05:02 rx [11061395.801164] Oops: 0000 [#1] SMP NOPTI Jul 26 15:05:02 rx [11061395.805091] CPU: 0 PID: 9180 Comm: msgr-worker-1 Tainted: G W 5.4.0-174-generic #193-Ubuntu Jul 26 15:05:02 rx [11061395.814996] Hardware name: Supermicro SMC 2x26 os-gen8 64C NVME-Y 256G/H12SSW-NTR, BIOS 2.5.V1.2U.NVMe.UEFI 05/09/2023 Jul 26 15:05:02 rx [11061395.825952] RIP: 0010:tcp_rearm_rto+0xe4/0x160 Jul 26 15:05:02 rx [11061395.830656] Code: 87 ca 04 00 00 00 5b 41 5c 41 5d 5d c3 c3 49 8b bc 24 40 06 00 00 eb 8d 48 bb cf f7 53 e3 a5 9b c4 20 4c 89 ef e8 0c fe 0e 00 \u0026lt;48\u0026gt; 8b 78 20 48 c1 ef 03 48 89 f8 41 8b bc 24 80 04 00 00 48 f7 e3 Jul 26 15:05:02 rx [11061395.849665] RSP: 0018:ffffb75d40003e08 EFLAGS: 00010246 Jul 26 15:05:02 rx [11061395.855149] RAX: 0000000000000000 RBX: 20c49ba5e353f7cf RCX: 0000000000000000 Jul 26 15:05:02 rx [11061395.862542] RDX: 0000000062177c30 RSI: 000000000000231c RDI: ffff9874ad283a60 Jul 26 15:05:02 rx [11061395.869933] RBP: ffffb75d40003e20 R08: 0000000000000000 R09: ffff987605e20aa8 Jul 26 15:05:02 rx [11061395.877318] R10: ffffb75d40003f00 R11: ffffb75d4460f740 R12: ffff9874ad283900 Jul 26 15:05:02 rx [11061395.884710] R13: ffff9874ad283a60 R14: ffff9874ad283980 R15: ffff9874ad283d30 Jul 26 15:05:02 rx [11061395.892095] FS: 00007f1ef4a2e700(0000) GS:ffff987605e00000(0000) knlGS:0000000000000000 Jul 26 15:05:02 rx [11061395.900438] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 26 15:05:02 rx [11061395.906435] CR2: 0000000000000020 CR3: 0000003e450ba003 CR4: 0000000000760ef0 Jul 26 15:05:02 rx [11061395.913822] PKRU: 55555554 Jul 26 15:05:02 rx [11061395.916786] Call Trace: Jul 26 15:05:02 rx [11061395.919488] Jul 26 15:05:02 rx [11061395.921765] ? show_regs.cold+0x1a/0x1f Jul 26 15:05:02 rx [11061395.925859] ? __die+0x90/0xd9 Jul 26 15:05:02 rx [11061395.929169] ? no_context+0x196/0x380 Jul 26 15:05:02 rx [11061395.933088] ? ip6_protocol_deliver_rcu+0x4e0/0x4e0 Jul 26 15:05:02 rx [11061395.938216] ? ip6_sublist_rcv_finish+0x3d/0x50 Jul 26 15:05:02 rx [11061395.943000] ? __bad_area_nosemaphore+0x50/0x1a0 Jul 26 15:05:02 rx [11061395.947873] ? bad_area_nosemaphore+0x16/0x20 Jul 26 15:05:02 rx [11061395.952486] ? do_user_addr_fault+0x267/0x450 Jul 26 15:05:02 rx [11061395.957104] ? ipv6_list_rcv+0x112/0x140 Jul 26 15:05:02 rx [11061395.961279] ? __do_page_fault+0x58/0x90 Jul 26 15:05:02 rx [11061395.965458] ? do_page_fault+0x2c/0xe0 Jul 26 15:05:02 rx [11061395.969465] ? page_fault+0x34/0x40 Jul 26 15:05:02 rx [11061395.973217] ? tcp_rearm_rto+0xe4/0x160 Jul 26 15:05:02 rx [11061395.977313] ? tcp_rearm_rto+0xe4/0x160 Jul 26 15:05:02 rx [11061395.981408] tcp_send_loss_probe+0x10b/0x220 Jul 26 15:05:02 rx [11061395.985937] tcp_write_timer_handler+0x1b4/0x240 Jul 26 15:05:02 rx [11061395.990809] tcp_write_timer+0x9e/0xe0 Jul 26 15:05:02 rx [11061395.994814] ? tcp_write_timer_handler+0x240/0x240 Jul 26 15:05:02 rx [11061395.999866] call_timer_fn+0x32/0x130 Jul 26 15:05:02 rx [11061396.003782] __run_timers.part.0+0x180/0x280 Jul 26 15:05:02 rx [11061396.008309] ? recalibrate_cpu_khz+0x10/0x10 Jul 26 15:05:02 rx [11061396.012841] ? native_x2apic_icr_write+0x30/0x30 Jul 26 15:05:02 rx [11061396.017718] ? lapic_next_even ---truncated---(CVE-2024-47684)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: netfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put() syzbot reported that nf_reject_ip6_tcphdr_put() was possibly sending garbage on the four reserved tcp bits (th-\u0026gt;res1) Use skb_put_zero() to clear the whole TCP header, as done in nf_reject_ip_tcphdr_put() BUG: KMSAN: uninit-value in nf_reject_ip6_tcphdr_put+0x688/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:255 nf_reject_ip6_tcphdr_put+0x688/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:255 nf_send_reset6+0xd84/0x15b0 net/ipv6/netfilter/nf_reject_ipv6.c:344 nft_reject_inet_eval+0x3c1/0x880 net/netfilter/nft_reject_inet.c:48 expr_call_ops_eval net/netfilter/nf_tables_core.c:240 [inline] nft_do_chain+0x438/0x22a0 net/netfilter/nf_tables_core.c:288 nft_do_chain_inet+0x41a/0x4f0 net/netfilter/nft_chain_filter.c:161 nf_hook_entry_hookfn include/linux/netfilter.h:154 [inline] nf_hook_slow+0xf4/0x400 net/netfilter/core.c:626 nf_hook include/linux/netfilter.h:269 [inline] NF_HOOK include/linux/netfilter.h:312 [inline] ipv6_rcv+0x29b/0x390 net/ipv6/ip6_input.c:310 __netif_receive_skb_one_core net/core/dev.c:5661 [inline] __netif_receive_skb+0x1da/0xa00 net/core/dev.c:5775 process_backlog+0x4ad/0xa50 net/core/dev.c:6108 __napi_poll+0xe7/0x980 net/core/dev.c:6772 napi_poll net/core/dev.c:6841 [inline] net_rx_action+0xa5a/0x19b0 net/core/dev.c:6963 handle_softirqs+0x1ce/0x800 kernel/softirq.c:554 __do_softirq+0x14/0x1a kernel/softirq.c:588 do_softirq+0x9a/0x100 kernel/softirq.c:455 __local_bh_enable_ip+0x9f/0xb0 kernel/softirq.c:382 local_bh_enable include/linux/bottom_half.h:33 [inline] rcu_read_unlock_bh include/linux/rcupdate.h:908 [inline] __dev_queue_xmit+0x2692/0x5610 net/core/dev.c:4450 dev_queue_xmit include/linux/netdevice.h:3105 [inline] neigh_resolve_output+0x9ca/0xae0 net/core/neighbour.c:1565 neigh_output include/net/neighbour.h:542 [inline] ip6_finish_output2+0x2347/0x2ba0 net/ipv6/ip6_output.c:141 __ip6_finish_output net/ipv6/ip6_output.c:215 [inline] ip6_finish_output+0xbb8/0x14b0 net/ipv6/ip6_output.c:226 NF_HOOK_COND include/linux/netfilter.h:303 [inline] ip6_output+0x356/0x620 net/ipv6/ip6_output.c:247 dst_output include/net/dst.h:450 [inline] NF_HOOK include/linux/netfilter.h:314 [inline] ip6_xmit+0x1ba6/0x25d0 net/ipv6/ip6_output.c:366 inet6_csk_xmit+0x442/0x530 net/ipv6/inet6_connection_sock.c:135 __tcp_transmit_skb+0x3b07/0x4880 net/ipv4/tcp_output.c:1466 tcp_transmit_skb net/ipv4/tcp_output.c:1484 [inline] tcp_connect+0x35b6/0x7130 net/ipv4/tcp_output.c:4143 tcp_v6_connect+0x1bcc/0x1e40 net/ipv6/tcp_ipv6.c:333 __inet_stream_connect+0x2ef/0x1730 net/ipv4/af_inet.c:679 inet_stream_connect+0x6a/0xd0 net/ipv4/af_inet.c:750 __sys_connect_file net/socket.c:2061 [inline] __sys_connect+0x606/0x690 net/socket.c:2078 __do_sys_connect net/socket.c:2088 [inline] __se_sys_connect net/socket.c:2085 [inline] __x64_sys_connect+0x91/0xe0 net/socket.c:2085 x64_sys_call+0x27a5/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:43 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was stored to memory at: nf_reject_ip6_tcphdr_put+0x60c/0x6c0 net/ipv6/netfilter/nf_reject_ipv6.c:249 nf_send_reset6+0xd84/0x15b0 net/ipv6/netfilter/nf_reject_ipv6.c:344 nft_reject_inet_eval+0x3c1/0x880 net/netfilter/nft_reject_inet.c:48 expr_call_ops_eval net/netfilter/nf_tables_core.c:240 [inline] nft_do_chain+0x438/0x22a0 net/netfilter/nf_tables_core.c:288 nft_do_chain_inet+0x41a/0x4f0 net/netfilter/nft_chain_filter.c:161 nf_hook_entry_hookfn include/linux/netfilter.h:154 [inline] nf_hook_slow+0xf4/0x400 net/netfilter/core.c:626 nf_hook include/linux/netfilter.h:269 [inline] NF_HOOK include/linux/netfilter.h:312 [inline] ipv6_rcv+0x29b/0x390 net/ipv6/ip6_input.c:310 __netif_receive_skb_one_core ---truncated---(CVE-2024-47685)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: f2fs: fix to don\u0026apos;t set SB_RDONLY in f2fs_handle_critical_error() syzbot reports a f2fs bug as below: ------------[ cut here ]------------ WARNING: CPU: 1 PID: 58 at kernel/rcu/sync.c:177 rcu_sync_dtor+0xcd/0x180 kernel/rcu/sync.c:177 CPU: 1 UID: 0 PID: 58 Comm: kworker/1:2 Not tainted 6.10.0-syzkaller-12562-g1722389b0d86 #0 Workqueue: events destroy_super_work RIP: 0010:rcu_sync_dtor+0xcd/0x180 kernel/rcu/sync.c:177 Call Trace: percpu_free_rwsem+0x41/0x80 kernel/locking/percpu-rwsem.c:42 destroy_super_work+0xec/0x130 fs/super.c:282 process_one_work kernel/workqueue.c:3231 [inline] process_scheduled_works+0xa2c/0x1830 kernel/workqueue.c:3312 worker_thread+0x86d/0xd40 kernel/workqueue.c:3390 kthread+0x2f0/0x390 kernel/kthread.c:389 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 As Christian Brauner pointed out [1]: the root cause is f2fs sets SB_RDONLY flag in internal function, rather than setting the flag covered w/ sb-\u0026gt;s_umount semaphore via remount procedure, then below race condition causes this bug: - freeze_super() - sb_wait_write(sb, SB_FREEZE_WRITE) - sb_wait_write(sb, SB_FREEZE_PAGEFAULT) - sb_wait_write(sb, SB_FREEZE_FS) - f2fs_handle_critical_error - sb-\u0026gt;s_flags |= SB_RDONLY - thaw_super - thaw_super_locked - sb_rdonly() is true, so it skips sb_freeze_unlock(sb, SB_FREEZE_FS) - deactivate_locked_super Since f2fs has almost the same logic as ext4 [2] when handling critical error in filesystem if it mounts w/ errors=remount-ro option: - set CP_ERROR_FLAG flag which indicates filesystem is stopped - record errors to superblock - set SB_RDONLY falg Once we set CP_ERROR_FLAG flag, all writable interfaces can detect the flag and stop any further updates on filesystem. So, it is safe to not set SB_RDONLY flag, let\u0026apos;s remove the logic and keep in line w/ ext4 [3]. [1] https://lore.kernel.org/all/20240729-himbeeren-funknetz-96e62f9c7aee@brauner [2] https://lore.kernel.org/all/20240729132721.hxih6ehigadqf7wx@quack3 [3] https://lore.kernel.org/linux-ext4/20240805201241.27286-1-jack@suse.cz(CVE-2024-47689)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: nfsd: return -EINVAL when namelen is 0 When we have a corrupted main.sqlite in /var/lib/nfs/nfsdcld/, it may result in namelen being 0, which will cause memdup_user() to return ZERO_SIZE_PTR. When we access the name.data that has been assigned the value of ZERO_SIZE_PTR in nfs4_client_to_reclaim(), null pointer dereference is triggered. [ T1205] ================================================================== [ T1205] BUG: KASAN: null-ptr-deref in nfs4_client_to_reclaim+0xe9/0x260 [ T1205] Read of size 1 at addr 0000000000000010 by task nfsdcld/1205 [ T1205] [ T1205] CPU: 11 PID: 1205 Comm: nfsdcld Not tainted 5.10.0-00003-g2c1423731b8d #406 [ T1205] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS ?-20190727_073836-buildvm-ppc64le-16.ppc.fedoraproject.org-3.fc31 04/01/2014 [ T1205] Call Trace: [ T1205] dump_stack+0x9a/0xd0 [ T1205] ? nfs4_client_to_reclaim+0xe9/0x260 [ T1205] __kasan_report.cold+0x34/0x84 [ T1205] ? nfs4_client_to_reclaim+0xe9/0x260 [ T1205] kasan_report+0x3a/0x50 [ T1205] nfs4_client_to_reclaim+0xe9/0x260 [ T1205] ? nfsd4_release_lockowner+0x410/0x410 [ T1205] cld_pipe_downcall+0x5ca/0x760 [ T1205] ? nfsd4_cld_tracking_exit+0x1d0/0x1d0 [ T1205] ? down_write_killable_nested+0x170/0x170 [ T1205] ? avc_policy_seqno+0x28/0x40 [ T1205] ? selinux_file_permission+0x1b4/0x1e0 [ T1205] rpc_pipe_write+0x84/0xb0 [ T1205] vfs_write+0x143/0x520 [ T1205] ksys_write+0xc9/0x170 [ T1205] ? __ia32_sys_read+0x50/0x50 [ T1205] ? ktime_get_coarse_real_ts64+0xfe/0x110 [ T1205] ? ktime_get_coarse_real_ts64+0xa2/0x110 [ T1205] do_syscall_64+0x33/0x40 [ T1205] entry_SYSCALL_64_after_hwframe+0x67/0xd1 [ T1205] RIP: 0033:0x7fdbdb761bc7 [ T1205] Code: 0f 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 0f 1f 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 514 [ T1205] RSP: 002b:00007fff8c4b7248 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 [ T1205] RAX: ffffffffffffffda RBX: 000000000000042b RCX: 00007fdbdb761bc7 [ T1205] RDX: 000000000000042b RSI: 00007fff8c4b75f0 RDI: 0000000000000008 [ T1205] RBP: 00007fdbdb761bb0 R08: 0000000000000000 R09: 0000000000000001 [ T1205] R10: 0000000000000000 R11: 0000000000000246 R12: 000000000000042b [ T1205] R13: 0000000000000008 R14: 00007fff8c4b75f0 R15: 0000000000000000 [ T1205] ================================================================== Fix it by checking namelen.(CVE-2024-47692)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds In the function init_conns(), after the create_con() and create_cm() for loop if something fails. In the cleanup for loop after the destroy tag, we access out of bound memory because cid is set to clt_path-\u0026gt;s.con_num. This commits resets the cid to clt_path-\u0026gt;s.con_num - 1, to stay in bounds in the cleanup loop later.(CVE-2024-47695)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error Ensure index in rtl2832_pid_filter does not exceed 31 to prevent out-of-bounds access. dev-\u0026gt;filters is a 32-bit value, so set_bit and clear_bit functions should only operate on indices from 0 to 31. If index is 32, it will attempt to access a non-existent 33rd bit, leading to out-of-bounds access. Change the boundary check from index \u0026gt; 32 to index \u0026gt;= 32 to resolve this issue. [hverkuil: added fixes tag, rtl2830_pid_filter -\u0026gt; rtl2832_pid_filter in logmsg](CVE-2024-47698)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: can: bcm: Clear bo-\u0026gt;bcm_proc_read after remove_proc_entry(). syzbot reported a warning in bcm_release(). [0] The blamed change fixed another warning that is triggered when connect() is issued again for a socket whose connect()ed device has been unregistered. However, if the socket is just close()d without the 2nd connect(), the remaining bo-\u0026gt;bcm_proc_read triggers unnecessary remove_proc_entry() in bcm_release(). Let\u0026apos;s clear bo-\u0026gt;bcm_proc_read after remove_proc_entry() in bcm_notify(). [0] name \u0026apos;4986\u0026apos; WARNING: CPU: 0 PID: 5234 at fs/proc/generic.c:711 remove_proc_entry+0x2e7/0x5d0 fs/proc/generic.c:711 Modules linked in: CPU: 0 UID: 0 PID: 5234 Comm: syz-executor606 Not tainted 6.11.0-rc5-syzkaller-00178-g5517ae241919 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 RIP: 0010:remove_proc_entry+0x2e7/0x5d0 fs/proc/generic.c:711 Code: ff eb 05 e8 cb 1e 5e ff 48 8b 5c 24 10 48 c7 c7 e0 f7 aa 8e e8 2a 38 8e 09 90 48 c7 c7 60 3a 1b 8c 48 89 de e8 da 42 20 ff 90 \u0026lt;0f\u0026gt; 0b 90 90 48 8b 44 24 18 48 c7 44 24 40 0e 36 e0 45 49 c7 04 07 RSP: 0018:ffffc9000345fa20 EFLAGS: 00010246 RAX: 2a2d0aee2eb64600 RBX: ffff888032f1f548 RCX: ffff888029431e00 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffc9000345fb08 R08: ffffffff8155b2f2 R09: 1ffff1101710519a R10: dffffc0000000000 R11: ffffed101710519b R12: ffff888011d38640 R13: 0000000000000004 R14: 0000000000000000 R15: dffffc0000000000 FS: 0000000000000000(0000) GS:ffff8880b8800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fcfb52722f0 CR3: 000000000e734000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: \u0026lt;TASK\u0026gt; bcm_release+0x250/0x880 net/can/bcm.c:1578 __sock_release net/socket.c:659 [inline] sock_close+0xbc/0x240 net/socket.c:1421 __fput+0x24a/0x8a0 fs/file_table.c:422 task_work_run+0x24f/0x310 kernel/task_work.c:228 exit_task_work include/linux/task_work.h:40 [inline] do_exit+0xa2f/0x27f0 kernel/exit.c:882 do_group_exit+0x207/0x2c0 kernel/exit.c:1031 __do_sys_exit_group kernel/exit.c:1042 [inline] __se_sys_exit_group kernel/exit.c:1040 [inline] __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1040 x64_sys_call+0x2634/0x2640 arch/x86/include/generated/asm/syscalls_64.h:232 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fcfb51ee969 Code: Unable to access opcode bytes at 0x7fcfb51ee93f. RSP: 002b:00007ffce0109ca8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007fcfb51ee969 RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001 RBP: 00007fcfb526f3b0 R08: ffffffffffffffb8 R09: 0000555500000000 R10: 0000555500000000 R11: 0000000000000246 R12: 00007fcfb526f3b0 R13: 0000000000000000 R14: 00007fcfb5271ee0 R15: 00007fcfb51bf160 \u0026lt;/TASK\u0026gt;(CVE-2024-47709)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: sock_map: Add a cond_resched() in sock_hash_free() Several syzbot soft lockup reports all have in common sock_hash_free() If a map with a large number of buckets is destroyed, we need to yield the cpu when needed.(CVE-2024-47710)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add null check for set_output_gamma in dcn30_set_output_transfer_func This commit adds a null check for the set_output_gamma function pointer in the dcn30_set_output_transfer_func function. Previously, set_output_gamma was being checked for nullity at line 386, but then it was being dereferenced without any nullity check at line 401. This could potentially lead to a null pointer dereference error if set_output_gamma is indeed null. To fix this, we now ensure that set_output_gamma is not null before dereferencing it. We do this by adding a nullity check for set_output_gamma before the call to set_output_gamma at line 401. If set_output_gamma is null, we log an error message and do not call the function. This fix prevents a potential null pointer dereference error. drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c:401 dcn30_set_output_transfer_func() error: we previously assumed \u0026apos;mpc-\u0026gt;funcs-\u0026gt;set_output_gamma\u0026apos; could be null (see line 386) drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c 373 bool dcn30_set_output_transfer_func(struct dc *dc, 374 struct pipe_ctx *pipe_ctx, 375 const struct dc_stream_state *stream) 376 { 377 int mpcc_id = pipe_ctx-\u0026gt;plane_res.hubp-\u0026gt;inst; 378 struct mpc *mpc = pipe_ctx-\u0026gt;stream_res.opp-\u0026gt;ctx-\u0026gt;dc-\u0026gt;res_pool-\u0026gt;mpc; 379 const struct pwl_params *params = NULL; 380 bool ret = false; 381 382 /* program OGAM or 3DLUT only for the top pipe*/ 383 if (pipe_ctx-\u0026gt;top_pipe == NULL) { 384 /*program rmu shaper and 3dlut in MPC*/ 385 ret = dcn30_set_mpc_shaper_3dlut(pipe_ctx, stream); 386 if (ret == false \u0026amp;\u0026amp; mpc-\u0026gt;funcs-\u0026gt;set_output_gamma) { ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ If this is NULL 387 if (stream-\u0026gt;out_transfer_func.type == TF_TYPE_HWPWL) 388 params = \u0026amp;stream-\u0026gt;out_transfer_func.pwl; 389 else if (pipe_ctx-\u0026gt;stream-\u0026gt;out_transfer_func.type == 390 TF_TYPE_DISTRIBUTED_POINTS \u0026amp;\u0026amp; 391 cm3_helper_translate_curve_to_hw_format( 392 \u0026amp;stream-\u0026gt;out_transfer_func, 393 \u0026amp;mpc-\u0026gt;blender_params, false)) 394 params = \u0026amp;mpc-\u0026gt;blender_params; 395 /* there are no ROM LUTs in OUTGAM */ 396 if (stream-\u0026gt;out_transfer_func.type == TF_TYPE_PREDEFINED) 397 BREAK_TO_DEBUGGER(); 398 } 399 } 400 --\u0026gt; 401 mpc-\u0026gt;funcs-\u0026gt;set_output_gamma(mpc, mpcc_id, params); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Then it will crash 402 return ret; 403 }(CVE-2024-47720)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: nfsd: call cache_put if xdr_reserve_space returns NULL If not enough buffer space available, but idmap_lookup has triggered lookup_fn which calls cache_get and returns successfully. Then we missed to call cache_put here which pairs with cache_get. Reviwed-by: Jeff Layton \u0026lt;jlayton@kernel.org\u0026gt;(CVE-2024-47737)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: KEYS: prevent NULL pointer dereference in find_asymmetric_key() In find_asymmetric_key(), if all NULLs are passed in the id_{0,1,2} arguments, the kernel will first emit WARN but then have an oops because id_2 gets dereferenced anyway. Add the missing id_2 check and move WARN_ON() to the final else branch to avoid duplicate NULL checks. Found by Linux Verification Center (linuxtesting.org) with Svace static analysis tool.(CVE-2024-47743)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential oob read in nilfs_btree_check_delete() The function nilfs_btree_check_delete(), which checks whether degeneration to direct mapping occurs before deleting a b-tree entry, causes memory access outside the block buffer when retrieving the maximum key if the root node has no entries. This does not usually happen because b-tree mappings with 0 child nodes are never created by mkfs.nilfs2 or nilfs2 itself. However, it can happen if the b-tree root node read from a device is configured that way, so fix this potential issue by adding a check for that case.(CVE-2024-47757)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: nbd: fix race between timeout and normal completion If request timetout is handled by nbd_requeue_cmd(), normal completion has to be stopped for avoiding to complete this requeued request, other use-after-free can be triggered. Fix the race by clearing NBD_CMD_INFLIGHT in nbd_requeue_cmd(), meantime make sure that cmd-\u0026gt;lock is grabbed for clearing the flag and the requeue.(CVE-2024-49855)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: tracing/timerlat: Fix a race during cpuhp processing There is another found exception that the \u0026quot;timerlat/1\u0026quot; thread was scheduled on CPU0, and lead to timer corruption finally: ``` ODEBUG: init active (active state 0) object: ffff888237c2e108 object type: hrtimer hint: timerlat_irq+0x0/0x220 WARNING: CPU: 0 PID: 426 at lib/debugobjects.c:518 debug_print_object+0x7d/0xb0 Modules linked in: CPU: 0 UID: 0 PID: 426 Comm: timerlat/1 Not tainted 6.11.0-rc7+ #45 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: 0010:debug_print_object+0x7d/0xb0 ... Call Trace: \u0026lt;TASK\u0026gt; ? __warn+0x7c/0x110 ? debug_print_object+0x7d/0xb0 ? report_bug+0xf1/0x1d0 ? prb_read_valid+0x17/0x20 ? handle_bug+0x3f/0x70 ? exc_invalid_op+0x13/0x60 ? asm_exc_invalid_op+0x16/0x20 ? debug_print_object+0x7d/0xb0 ? debug_print_object+0x7d/0xb0 ? __pfx_timerlat_irq+0x10/0x10 __debug_object_init+0x110/0x150 hrtimer_init+0x1d/0x60 timerlat_main+0xab/0x2d0 ? __pfx_timerlat_main+0x10/0x10 kthread+0xb7/0xe0 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x2d/0x40 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 \u0026lt;/TASK\u0026gt; ``` After tracing the scheduling event, it was discovered that the migration of the \u0026quot;timerlat/1\u0026quot; thread was performed during thread creation. Further analysis confirmed that it is because the CPU online processing for osnoise is implemented through workers, which is asynchronous with the offline processing. When the worker was scheduled to create a thread, the CPU may has already been removed from the cpu_online_mask during the offline process, resulting in the inability to select the right CPU: T1 | T2 [CPUHP_ONLINE] | cpu_device_down() osnoise_hotplug_workfn() | | cpus_write_lock() | takedown_cpu(1) | cpus_write_unlock() [CPUHP_OFFLINE] | cpus_read_lock() | start_kthread(1) | cpus_read_unlock() | To fix this, skip online processing if the CPU is already offline.(CVE-2024-49866)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: btrfs: wait for fixup workers before stopping cleaner kthread during umount During unmount, at close_ctree(), we have the following steps in this order: 1) Park the cleaner kthread - this doesn\u0026apos;t destroy the kthread, it basically halts its execution (wake ups against it work but do nothing); 2) We stop the cleaner kthread - this results in freeing the respective struct task_struct; 3) We call btrfs_stop_all_workers() which waits for any jobs running in all the work queues and then free the work queues. Syzbot reported a case where a fixup worker resulted in a crash when doing a delayed iput on its inode while attempting to wake up the cleaner at btrfs_add_delayed_iput(), because the task_struct of the cleaner kthread was already freed. This can happen during unmount because we don\u0026apos;t wait for any fixup workers still running before we call kthread_stop() against the cleaner kthread, which stops and free all its resources. Fix this by waiting for any fixup workers at close_ctree() before we call kthread_stop() against the cleaner and run pending delayed iputs. The stack traces reported by syzbot were the following: BUG: KASAN: slab-use-after-free in __lock_acquire+0x77/0x2050 kernel/locking/lockdep.c:5065 Read of size 8 at addr ffff8880272a8a18 by task kworker/u8:3/52 CPU: 1 UID: 0 PID: 52 Comm: kworker/u8:3 Not tainted 6.12.0-rc1-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Workqueue: btrfs-fixup btrfs_work_helper Call Trace: \u0026lt;TASK\u0026gt; __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:377 [inline] print_report+0x169/0x550 mm/kasan/report.c:488 kasan_report+0x143/0x180 mm/kasan/report.c:601 __lock_acquire+0x77/0x2050 kernel/locking/lockdep.c:5065 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0xd5/0x120 kernel/locking/spinlock.c:162 class_raw_spinlock_irqsave_constructor include/linux/spinlock.h:551 [inline] try_to_wake_up+0xb0/0x1480 kernel/sched/core.c:4154 btrfs_writepage_fixup_worker+0xc16/0xdf0 fs/btrfs/inode.c:2842 btrfs_work_helper+0x390/0xc50 fs/btrfs/async-thread.c:314 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xa63/0x1850 kernel/workqueue.c:3310 worker_thread+0x870/0xd30 kernel/workqueue.c:3391 kthread+0x2f0/0x390 kernel/kthread.c:389 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 \u0026lt;/TASK\u0026gt; Allocated by task 2: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3f/0x80 mm/kasan/common.c:68 unpoison_slab_object mm/kasan/common.c:319 [inline] __kasan_slab_alloc+0x66/0x80 mm/kasan/common.c:345 kasan_slab_alloc include/linux/kasan.h:247 [inline] slab_post_alloc_hook mm/slub.c:4086 [inline] slab_alloc_node mm/slub.c:4135 [inline] kmem_cache_alloc_node_noprof+0x16b/0x320 mm/slub.c:4187 alloc_task_struct_node kernel/fork.c:180 [inline] dup_task_struct+0x57/0x8c0 kernel/fork.c:1107 copy_process+0x5d1/0x3d50 kernel/fork.c:2206 kernel_clone+0x223/0x880 kernel/fork.c:2787 kernel_thread+0x1bc/0x240 kernel/fork.c:2849 create_kthread kernel/kthread.c:412 [inline] kthreadd+0x60d/0x810 kernel/kthread.c:765 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 Freed by task 61: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3f/0x80 mm/kasan/common.c:68 kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:579 poison_slab_object mm/kasan/common.c:247 [inline] __kasan_slab_free+0x59/0x70 mm/kasan/common.c:264 kasan_slab_free include/linux/kasan.h:230 [inline] slab_free_h ---truncated---(CVE-2024-49867)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: btrfs: fix a NULL pointer dereference when failed to start a new trasacntion [BUG] Syzbot reported a NULL pointer dereference with the following crash: FAULT_INJECTION: forcing a failure. start_transaction+0x830/0x1670 fs/btrfs/transaction.c:676 prepare_to_relocate+0x31f/0x4c0 fs/btrfs/relocation.c:3642 relocate_block_group+0x169/0xd20 fs/btrfs/relocation.c:3678 ... BTRFS info (device loop0): balance: ended with status: -12 Oops: general protection fault, probably for non-canonical address 0xdffffc00000000cc: 0000 [#1] PREEMPT SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000660-0x0000000000000667] RIP: 0010:btrfs_update_reloc_root+0x362/0xa80 fs/btrfs/relocation.c:926 Call Trace: \u0026lt;TASK\u0026gt; commit_fs_roots+0x2ee/0x720 fs/btrfs/transaction.c:1496 btrfs_commit_transaction+0xfaf/0x3740 fs/btrfs/transaction.c:2430 del_balance_item fs/btrfs/volumes.c:3678 [inline] reset_balance_state+0x25e/0x3c0 fs/btrfs/volumes.c:3742 btrfs_balance+0xead/0x10c0 fs/btrfs/volumes.c:4574 btrfs_ioctl_balance+0x493/0x7c0 fs/btrfs/ioctl.c:3673 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl+0xf9/0x170 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f [CAUSE] The allocation failure happens at the start_transaction() inside prepare_to_relocate(), and during the error handling we call unset_reloc_control(), which makes fs_info-\u0026gt;balance_ctl to be NULL. Then we continue the error path cleanup in btrfs_balance() by calling reset_balance_state() which will call del_balance_item() to fully delete the balance item in the root tree. However during the small window between set_reloc_contrl() and unset_reloc_control(), we can have a subvolume tree update and created a reloc_root for that subvolume. Then we go into the final btrfs_commit_transaction() of del_balance_item(), and into btrfs_update_reloc_root() inside commit_fs_roots(). That function checks if fs_info-\u0026gt;reloc_ctl is in the merge_reloc_tree stage, but since fs_info-\u0026gt;reloc_ctl is NULL, it results a NULL pointer dereference. [FIX] Just add extra check on fs_info-\u0026gt;reloc_ctl inside btrfs_update_reloc_root(), before checking fs_info-\u0026gt;reloc_ctl-\u0026gt;merge_reloc_tree. That DEAD_RELOC_TREE handling is to prevent further modification to the reloc tree during merge stage, but since there is no reloc_ctl at all, we do not need to bother that.(CVE-2024-49868)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix index out of bounds in DCN30 degamma hardware format translation This commit addresses a potential index out of bounds issue in the `cm3_helper_translate_curve_to_degamma_hw_format` function in the DCN30 color management module. The issue could occur when the index \u0026apos;i\u0026apos; exceeds the number of transfer function points (TRANSFER_FUNC_POINTS). The fix adds a check to ensure \u0026apos;i\u0026apos; is within bounds before accessing the transfer function points. If \u0026apos;i\u0026apos; is out of bounds, the function returns false to indicate an error. Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:338 cm3_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.red\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:339 cm3_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.green\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:340 cm3_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.blue\u0026apos; 1025 \u0026lt;= s32max(CVE-2024-49895)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: jfs: Fix uninit-value access of new_ea in ea_buffer syzbot reports that lzo1x_1_do_compress is using uninit-value: ===================================================== BUG: KMSAN: uninit-value in lzo1x_1_do_compress+0x19f9/0x2510 lib/lzo/lzo1x_compress.c:178 ... Uninit was stored to memory at: ea_put fs/jfs/xattr.c:639 [inline] ... Local variable ea_buf created at: __jfs_setxattr+0x5d/0x1ae0 fs/jfs/xattr.c:662 __jfs_xattr_set+0xe6/0x1f0 fs/jfs/xattr.c:934 ===================================================== The reason is ea_buf-\u0026gt;new_ea is not initialized properly. Fix this by using memset to empty its content at the beginning in ea_get().(CVE-2024-49900)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: jfs: check if leafidx greater than num leaves per dmap tree syzbot report a out of bounds in dbSplit, it because dmt_leafidx greater than num leaves per dmap tree, add a checking for dmt_leafidx in dbFindLeaf. Shaggy: Modified sanity check to apply to control pages as well as leaf pages.(CVE-2024-49902)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: jfs: Fix uaf in dbFreeBits [syzbot reported] ================================================================== BUG: KASAN: slab-use-after-free in __mutex_lock_common kernel/locking/mutex.c:587 [inline] BUG: KASAN: slab-use-after-free in __mutex_lock+0xfe/0xd70 kernel/locking/mutex.c:752 Read of size 8 at addr ffff8880229254b0 by task syz-executor357/5216 CPU: 0 UID: 0 PID: 5216 Comm: syz-executor357 Not tainted 6.11.0-rc3-syzkaller-00156-gd7a5aa4b3c00 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024 Call Trace: \u0026lt;TASK\u0026gt; __dump_stack lib/dump_stack.c:93 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119 print_address_description mm/kasan/report.c:377 [inline] print_report+0x169/0x550 mm/kasan/report.c:488 kasan_report+0x143/0x180 mm/kasan/report.c:601 __mutex_lock_common kernel/locking/mutex.c:587 [inline] __mutex_lock+0xfe/0xd70 kernel/locking/mutex.c:752 dbFreeBits+0x7ea/0xd90 fs/jfs/jfs_dmap.c:2390 dbFreeDmap fs/jfs/jfs_dmap.c:2089 [inline] dbFree+0x35b/0x680 fs/jfs/jfs_dmap.c:409 dbDiscardAG+0x8a9/0xa20 fs/jfs/jfs_dmap.c:1650 jfs_ioc_trim+0x433/0x670 fs/jfs/jfs_discard.c:100 jfs_ioctl+0x2d0/0x3e0 fs/jfs/ioctl.c:131 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 Freed by task 5218: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3f/0x80 mm/kasan/common.c:68 kasan_save_free_info+0x40/0x50 mm/kasan/generic.c:579 poison_slab_object+0xe0/0x150 mm/kasan/common.c:240 __kasan_slab_free+0x37/0x60 mm/kasan/common.c:256 kasan_slab_free include/linux/kasan.h:184 [inline] slab_free_hook mm/slub.c:2252 [inline] slab_free mm/slub.c:4473 [inline] kfree+0x149/0x360 mm/slub.c:4594 dbUnmount+0x11d/0x190 fs/jfs/jfs_dmap.c:278 jfs_mount_rw+0x4ac/0x6a0 fs/jfs/jfs_mount.c:247 jfs_remount+0x3d1/0x6b0 fs/jfs/super.c:454 reconfigure_super+0x445/0x880 fs/super.c:1083 vfs_cmd_reconfigure fs/fsopen.c:263 [inline] vfs_fsconfig_locked fs/fsopen.c:292 [inline] __do_sys_fsconfig fs/fsopen.c:473 [inline] __se_sys_fsconfig+0xb6e/0xf80 fs/fsopen.c:345 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f [Analysis] There are two paths (dbUnmount and jfs_ioc_trim) that generate race condition when accessing bmap, which leads to the occurrence of uaf. Use the lock s_umount to synchronize them, in order to avoid uaf caused by race condition.(CVE-2024-49903)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add NULL check for function pointer in dcn20_set_output_transfer_func This commit adds a null check for the set_output_gamma function pointer in the dcn20_set_output_transfer_func function. Previously, set_output_gamma was being checked for null at line 1030, but then it was being dereferenced without any null check at line 1048. This could potentially lead to a null pointer dereference error if set_output_gamma is null. To fix this, we now ensure that set_output_gamma is not null before dereferencing it. We do this by adding a null check for set_output_gamma before the call to set_output_gamma at line 1048.(CVE-2024-49911)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add null check for head_pipe in dcn32_acquire_idle_pipe_for_head_pipe_in_layer This commit addresses a potential null pointer dereference issue in the `dcn32_acquire_idle_pipe_for_head_pipe_in_layer` function. The issue could occur when `head_pipe` is null. The fix adds a check to ensure `head_pipe` is not null before asserting it. If `head_pipe` is null, the function returns NULL to prevent a potential null pointer dereference. Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/resource/dcn32/dcn32_resource.c:2690 dcn32_acquire_idle_pipe_for_head_pipe_in_layer() error: we previously assumed \u0026apos;head_pipe\u0026apos; could be null (see line 2681)(CVE-2024-49918)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add null check for head_pipe in dcn201_acquire_free_pipe_for_layer This commit addresses a potential null pointer dereference issue in the `dcn201_acquire_free_pipe_for_layer` function. The issue could occur when `head_pipe` is null. The fix adds a check to ensure `head_pipe` is not null before asserting it. If `head_pipe` is null, the function returns NULL to prevent a potential null pointer dereference. Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/resource/dcn201/dcn201_resource.c:1016 dcn201_acquire_free_pipe_for_layer() error: we previously assumed \u0026apos;head_pipe\u0026apos; could be null (see line 1010)(CVE-2024-49919)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: x86/ioapic: Handle allocation failures gracefully Breno observed panics when using failslab under certain conditions during runtime: can not alloc irq_pin_list (-1,0,20) Kernel panic - not syncing: IO-APIC: failed to add irq-pin. Can not proceed panic+0x4e9/0x590 mp_irqdomain_alloc+0x9ab/0xa80 irq_domain_alloc_irqs_locked+0x25d/0x8d0 __irq_domain_alloc_irqs+0x80/0x110 mp_map_pin_to_irq+0x645/0x890 acpi_register_gsi_ioapic+0xe6/0x150 hpet_open+0x313/0x480 That\u0026apos;s a pointless panic which is a leftover of the historic IO/APIC code which panic\u0026apos;ed during early boot when the interrupt allocation failed. The only place which might justify panic is the PIT/HPET timer_check() code which tries to figure out whether the timer interrupt is delivered through the IO/APIC. But that code does not require to handle interrupt allocation failures. If the interrupt cannot be allocated then timer delivery fails and it either panics due to that or falls back to legacy mode. Cure this by removing the panic wrapper around __add_pin_to_irq_node() and making mp_irqdomain_alloc() aware of the failure condition and handle it as any other failure in this function gracefully.(CVE-2024-49927)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ocfs2: remove unreasonable unlock in ocfs2_read_blocks Patch series \u0026quot;Misc fixes for ocfs2_read_blocks\u0026quot;, v5. This series contains 2 fixes for ocfs2_read_blocks(). The first patch fix the issue reported by syzbot, which detects bad unlock balance in ocfs2_read_blocks(). The second patch fixes an issue reported by Heming Zhao when reviewing above fix. This patch (of 2): There was a lock release before exiting, so remove the unreasonable unlock.(CVE-2024-49965)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix index out of bounds in DCN30 color transformation This commit addresses a potential index out of bounds issue in the `cm3_helper_translate_curve_to_hw_format` function in the DCN30 color management module. The issue could occur when the index \u0026apos;i\u0026apos; exceeds the number of transfer function points (TRANSFER_FUNC_POINTS). The fix adds a check to ensure \u0026apos;i\u0026apos; is within bounds before accessing the transfer function points. If \u0026apos;i\u0026apos; is out of bounds, the function returns false to indicate an error. drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:180 cm3_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.red\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:181 cm3_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.green\u0026apos; 1025 \u0026lt;= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn30/dcn30_cm_common.c:182 cm3_helper_translate_curve_to_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.blue\u0026apos; 1025 \u0026lt;= s32max(CVE-2024-49969)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: NFSD: Limit the number of concurrent async COPY operations Nothing appears to limit the number of concurrent async COPY operations that clients can start. In addition, AFAICT each async COPY can copy an unlimited number of 4MB chunks, so can run for a long time. Thus IMO async COPY can become a DoS vector. Add a restriction mechanism that bounds the number of concurrent background COPY operations. Start simple and try to be fair -- this patch implements a per-namespace limit. An async COPY request that occurs while this limit is exceeded gets NFS4ERR_DELAY. The requesting client can choose to send the request again after a delay or fall back to a traditional read/write style copy. If there is need to make the mechanism more sophisticated, we can visit that in future patches.(CVE-2024-49974)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: tracing/timerlat: Drop interface_lock in stop_kthread() stop_kthread() is the offline callback for \u0026quot;trace/osnoise:online\u0026quot;, since commit 5bfbcd1ee57b (\u0026quot;tracing/timerlat: Add interface_lock around clearing of kthread in stop_kthread()\u0026quot;), the following ABBA deadlock scenario is introduced: T1 | T2 [BP] | T3 [AP] osnoise_hotplug_workfn() | work_for_cpu_fn() | cpuhp_thread_fun() | _cpu_down() | osnoise_cpu_die() mutex_lock(\u0026amp;interface_lock) | | stop_kthread() | cpus_write_lock() | mutex_lock(\u0026amp;interface_lock) cpus_read_lock() | cpuhp_kick_ap() | As the interface_lock here in just for protecting the \u0026quot;kthread\u0026quot; field of the osn_var, use xchg() instead to fix this issue. Also use for_each_online_cpu() back in stop_per_cpu_kthreads() as it can take cpu_read_lock() again.(CVE-2024-49976)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: i2c: stm32f7: Do not prepare/unprepare clock during runtime suspend/resume In case there is any sort of clock controller attached to this I2C bus controller, for example Versaclock or even an AIC32x4 I2C codec, then an I2C transfer triggered from the clock controller clk_ops .prepare callback may trigger a deadlock on drivers/clk/clk.c prepare_lock mutex. This is because the clock controller first grabs the prepare_lock mutex and then performs the prepare operation, including its I2C access. The I2C access resumes this I2C bus controller via .runtime_resume callback, which calls clk_prepare_enable(), which attempts to grab the prepare_lock mutex again and deadlocks. Since the clock are already prepared since probe() and unprepared in remove(), use simple clk_enable()/clk_disable() calls to enable and disable the clock on runtime suspend and resume, to avoid hitting the prepare_lock mutex.(CVE-2024-49985)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ALSA: asihpi: Fix potential OOB array access ASIHPI driver stores some values in the static array upon a response from the driver, and its index depends on the firmware. We shouldn\u0026apos;t trust it blindly. This patch adds a sanity check of the array index to fit in the array size.(CVE-2024-50007)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: cpufreq: Avoid a bad reference count on CPU node In the parse_perf_domain function, if the call to of_parse_phandle_with_args returns an error, then the reference to the CPU device node that was acquired at the start of the function would not be properly decremented. Address this by declaring the variable with the __free(device_node) cleanup attribute.(CVE-2024-50012)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: NFSv4: Prevent NULL-pointer dereference in nfs42_complete_copies() On the node of an NFS client, some files saved in the mountpoint of the NFS server were copied to another location of the same NFS server. Accidentally, the nfs42_complete_copies() got a NULL-pointer dereference crash with the following syslog: [232064.838881] NFSv4: state recovery failed for open file nfs/pvc-12b5200d-cd0f-46a3-b9f0-af8f4fe0ef64.qcow2, error = -116 [232064.839360] NFSv4: state recovery failed for open file nfs/pvc-12b5200d-cd0f-46a3-b9f0-af8f4fe0ef64.qcow2, error = -116 [232066.588183] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000058 [232066.588586] Mem abort info: [232066.588701] ESR = 0x0000000096000007 [232066.588862] EC = 0x25: DABT (current EL), IL = 32 bits [232066.589084] SET = 0, FnV = 0 [232066.589216] EA = 0, S1PTW = 0 [232066.589340] FSC = 0x07: level 3 translation fault [232066.589559] Data abort info: [232066.589683] ISV = 0, ISS = 0x00000007 [232066.589842] CM = 0, WnR = 0 [232066.589967] user pgtable: 64k pages, 48-bit VAs, pgdp=00002000956ff400 [232066.590231] [0000000000000058] pgd=08001100ae100003, p4d=08001100ae100003, pud=08001100ae100003, pmd=08001100b3c00003, pte=0000000000000000 [232066.590757] Internal error: Oops: 96000007 [#1] SMP [232066.590958] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace fscache netfs ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm vhost_net vhost vhost_iotlb tap tun ipt_rpfilter xt_multiport ip_set_hash_ip ip_set_hash_net xfrm_interface xfrm6_tunnel tunnel4 tunnel6 esp4 ah4 wireguard libcurve25519_generic veth xt_addrtype xt_set nf_conntrack_netlink ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_bitmap_port ip_set_hash_ipport dummy ip_set ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs iptable_filter sch_ingress nfnetlink_cttimeout vport_gre ip_gre ip_tunnel gre vport_geneve geneve vport_vxlan vxlan ip6_udp_tunnel udp_tunnel openvswitch nf_conncount dm_round_robin dm_service_time dm_multipath xt_nat xt_MASQUERADE nft_chain_nat nf_nat xt_mark xt_conntrack xt_comment nft_compat nft_counter nf_tables nfnetlink ocfs2 ocfs2_nodemanager ocfs2_stackglue iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ipmi_ssif nbd overlay 8021q garp mrp bonding tls rfkill sunrpc ext4 mbcache jbd2 [232066.591052] vfat fat cas_cache cas_disk ses enclosure scsi_transport_sas sg acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler ip_tables vfio_pci vfio_pci_core vfio_virqfd vfio_iommu_type1 vfio dm_mirror dm_region_hash dm_log dm_mod nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter bridge stp llc fuse xfs libcrc32c ast drm_vram_helper qla2xxx drm_kms_helper syscopyarea crct10dif_ce sysfillrect ghash_ce sysimgblt sha2_ce fb_sys_fops cec sha256_arm64 sha1_ce drm_ttm_helper ttm nvme_fc igb sbsa_gwdt nvme_fabrics drm nvme_core i2c_algo_bit i40e scsi_transport_fc megaraid_sas aes_neon_bs [232066.596953] CPU: 6 PID: 4124696 Comm: 10.253.166.125- Kdump: loaded Not tainted 5.15.131-9.cl9_ocfs2.aarch64 #1 [232066.597356] Hardware name: Great Wall .\\x93\\x8e...RF6260 V5/GWMSSE2GL1T, BIOS T656FBE_V3.0.18 2024-01-06 [232066.597721] pstate: 20400009 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [232066.598034] pc : nfs4_reclaim_open_state+0x220/0x800 [nfsv4] [232066.598327] lr : nfs4_reclaim_open_state+0x12c/0x800 [nfsv4] [232066.598595] sp : ffff8000f568fc70 [232066.598731] x29: ffff8000f568fc70 x28: 0000000000001000 x27: ffff21003db33000 [232066.599030] x26: ffff800005521ae0 x25: ffff0100f98fa3f0 x24: 0000000000000001 [232066.599319] x23: ffff800009920008 x22: ffff21003db33040 x21: ffff21003db33050 [232066.599628] x20: ffff410172fe9e40 x19: ffff410172fe9e00 x18: 0000000000000000 [232066.599914] x17: 0000000000000000 x16: 0000000000000004 x15: 0000000000000000 [232066.600195] x14: 0000000000000000 x13: ffff800008e685a8 x12: 00000000eac0c6e6 [232066.600498] x11: 00000000000000 ---truncated---(CVE-2024-50046)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check null pointer before dereferencing se [WHAT \u0026amp; HOW] se is null checked previously in the same function, indicating it might be null; therefore, it must be checked when used again. This fixes 1 FORWARD_NULL issue reported by Coverity.(CVE-2024-50049)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: usb: typec: tipd: Free IRQ only if it was requested before In polling mode, if no IRQ was requested there is no need to free it. Call devm_free_irq() only if client-\u0026gt;irq is set. This fixes the warning caused by the tps6598x module removal: WARNING: CPU: 2 PID: 333 at kernel/irq/devres.c:144 devm_free_irq+0x80/0x8c ... ... Call trace: devm_free_irq+0x80/0x8c tps6598x_remove+0x28/0x88 [tps6598x] i2c_device_remove+0x2c/0x9c device_remove+0x4c/0x80 device_release_driver_internal+0x1cc/0x228 driver_detach+0x50/0x98 bus_remove_driver+0x6c/0xbc driver_unregister+0x30/0x60 i2c_del_driver+0x54/0x64 tps6598x_i2c_driver_exit+0x18/0xc3c [tps6598x] __arm64_sys_delete_module+0x184/0x264 invoke_syscall+0x48/0x110 el0_svc_common.constprop.0+0xc8/0xe8 do_el0_svc+0x20/0x2c el0_svc+0x28/0x98 el0t_64_sync_handler+0x13c/0x158 el0t_64_sync+0x190/0x194(CVE-2024-50057)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ntfs3: Change to non-blocking allocation in ntfs_d_hash d_hash is done while under \u0026quot;rcu-walk\u0026quot; and should not sleep. __get_name() allocates using GFP_KERNEL, having the possibility to sleep when under memory pressure. Change the allocation to GFP_NOWAIT.(CVE-2024-50065)",
"id": "OESA-2024-2325",
"modified": "2026-08-06T11:07:48Z",
"published": "2024-11-01T11:07:48Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2325"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-52917"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-52918"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-35949"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-35964"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-36884"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42301"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43858"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43867"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43871"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-44982"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-44997"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-46675"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-46677"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-46724"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-46749"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-46757"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-46775"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-46782"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-46802"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-46853"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-46871"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47659"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47660"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47661"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47667"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47681"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47683"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47684"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47685"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47689"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47692"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47695"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47698"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47709"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47710"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47720"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47737"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47743"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47757"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49855"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49866"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49867"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49868"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49895"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49900"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49902"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49903"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49911"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49918"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49919"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49927"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49965"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49969"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49974"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49976"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49985"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50007"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50012"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50046"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50049"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50057"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50065"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "kernel security update",
"upstream": [
"CVE-2023-52917",
"CVE-2023-52918",
"CVE-2024-35949",
"CVE-2024-35964",
"CVE-2024-36884",
"CVE-2024-42301",
"CVE-2024-43858",
"CVE-2024-43867",
"CVE-2024-43871",
"CVE-2024-44982",
"CVE-2024-44997",
"CVE-2024-46675",
"CVE-2024-46677",
"CVE-2024-46724",
"CVE-2024-46749",
"CVE-2024-46757",
"CVE-2024-46775",
"CVE-2024-46782",
"CVE-2024-46802",
"CVE-2024-46853",
"CVE-2024-46871",
"CVE-2024-47659",
"CVE-2024-47660",
"CVE-2024-47661",
"CVE-2024-47667",
"CVE-2024-47681",
"CVE-2024-47683",
"CVE-2024-47684",
"CVE-2024-47685",
"CVE-2024-47689",
"CVE-2024-47692",
"CVE-2024-47695",
"CVE-2024-47698",
"CVE-2024-47709",
"CVE-2024-47710",
"CVE-2024-47720",
"CVE-2024-47737",
"CVE-2024-47743",
"CVE-2024-47757",
"CVE-2024-49855",
"CVE-2024-49866",
"CVE-2024-49867",
"CVE-2024-49868",
"CVE-2024-49895",
"CVE-2024-49900",
"CVE-2024-49902",
"CVE-2024-49903",
"CVE-2024-49911",
"CVE-2024-49918",
"CVE-2024-49919",
"CVE-2024-49927",
"CVE-2024-49965",
"CVE-2024-49969",
"CVE-2024-49974",
"CVE-2024-49976",
"CVE-2024-49985",
"CVE-2024-50007",
"CVE-2024-50012",
"CVE-2024-50046",
"CVE-2024-50049",
"CVE-2024-50057",
"CVE-2024-50065"
]
}
OESA-2024-2368 (CVE-2022-48961)
Vulnerability from osv_openeuler – Published: 2024-11-08 11:07 – Updated: 2026-08-06 11:07 – Source websiteThe Linux Kernel, the operating system core itself.
Security Fix(es):
In the Linux kernel, the following vulnerability has been resolved: net: mdio: fix unbalanced fwnode reference count in mdio_device_release() There is warning report about of_node refcount leak while probing mdio device: OF: ERROR: memory leak, expected refcount 1 instead of 2, of_node_get()/of_node_put() unbalanced - destroy cset entry: attach overlay node /spi/soc@0/mdio@710700c0/ethernet@4 In of_mdiobus_register_device(), we increase fwnode refcount by fwnode_handle_get() before associating the of_node with mdio device, but it has never been decreased in normal path. Since that, in mdio_device_release(), it needs to call fwnode_handle_put() in addition instead of calling kfree() directly. After above, just calling mdio_device_free() in the error handle path of of_mdiobus_register_device() is enough to keep the refcount balanced.(CVE-2022-48961)
In the Linux kernel, the following vulnerability has been resolved: gpiolib: fix memory leak in gpiochip_setup_dev() Here is a backtrace report about memory leak detected in gpiochip_setup_dev(): unreferenced object 0xffff88810b406400 (size 512): comm "python3", pid 1682, jiffies 4295346908 (age 24.090s) backtrace: kmalloc_trace device_add device_private_init at drivers/base/core.c:3361 (inlined by) device_add at drivers/base/core.c:3411 cdev_device_add gpiolib_cdev_register gpiochip_setup_dev gpiochip_add_data_with_key gcdev_register() & gcdev_unregister() would call device_add() & device_del() (no matter CONFIG_GPIO_CDEV is enabled or not) to register/unregister device. However, if device_add() succeeds, some resource (like struct device_private allocated by device_private_init()) is not released by device_del(). Therefore, after device_add() succeeds by gcdev_register(), it needs to call put_device() to release resource in the error handle path. Here we move forward the register of release function, and let it release every piece of resource by put_device() instead of kfree(). While at it, fix another subtle issue, i.e. when gc->ngpio is equal to 0, we still call kcalloc() and, in case of further error, kfree() on the ZERO_PTR pointer, which is not NULL. It's not a bug per se, but rather waste of the resources and potentially wrong expectation about contents of the gdev->descs variable.(CVE-2022-48975)
In the Linux kernel, the following vulnerability has been resolved: riscv: Sync efi page table's kernel mappings before switching The EFI page table is initially created as a copy of the kernel page table. With VMAP_STACK enabled, kernel stacks are allocated in the vmalloc area: if the stack is allocated in a new PGD (one that was not present at the moment of the efi page table creation or not synced in a previous vmalloc fault), the kernel will take a trap when switching to the efi page table when the vmalloc kernel stack is accessed, resulting in a kernel panic. Fix that by updating the efi kernel mappings before switching to the efi page table.(CVE-2022-49004)
In the Linux kernel, the following vulnerability has been resolved:
memcg_write_event_control(): fix a user-triggerable oops
we are not guaranteed that anything past the terminating NUL is mapped (let alone initialized with anything sane).(CVE-2024-45021)
In the Linux kernel, the following vulnerability has been resolved:
gtp: fix a potential NULL pointer dereference
When sockfd_lookup() fails, gtp_encap_enable_socket() returns a NULL pointer, but its callers only check for error pointers thus miss the NULL pointer case.
Fix it by returning an error pointer with the error code carried from sockfd_lookup().
(I found this bug during code inspection.)(CVE-2024-46677)
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Check BIOS images before it is used
BIOS images may fail to load and null checks are added before they are used.
This fixes 6 NULL_RETURNS issues reported by Coverity.(CVE-2024-46809)
In the Linux kernel, the following vulnerability has been resolved:
smack: tcp: ipv4, fix incorrect labeling
Currently, Smack mirrors the label of incoming tcp/ipv4 connections: when a label 'foo' connects to a label 'bar' with tcp/ipv4, 'foo' always gets 'foo' in returned ipv4 packets. So, 1) returned packets are incorrectly labeled ('foo' instead of 'bar') 2) 'bar' can write to 'foo' without being authorized to write.
Here is a scenario how to see this:
-
Take two machines, let's call them C and S, with active Smack in the default state (no settings, no rules, no labeled hosts, only builtin labels)
-
At S, add Smack rule 'foo bar w' (labels 'foo' and 'bar' are instantiated at S at this moment)
-
At S, at label 'bar', launch a program that listens for incoming tcp/ipv4 connections
-
From C, at label 'foo', connect to the listener at S. (label 'foo' is instantiated at C at this moment) Connection succeedes and works.
-
Send some data in both directions.
- Collect network traffic of this connection.
All packets in both directions are labeled with the CIPSO of the label 'foo'. Hence, label 'bar' writes to 'foo' without being authorized, and even without ever being known at C.
If anybody cares: exactly the same happens with DCCP.
This behavior 1st manifested in release 2.6.29.4 (see Fixes below) and it looks unintentional. At least, no explanation was provided.
I changed returned packes label into the 'bar', to bring it into line with the Smack documentation claims.(CVE-2024-47659)
In the Linux kernel, the following vulnerability has been resolved:
fsnotify: clear PARENT_WATCHED flags lazily
In some setups directories can have many (usually negative) dentries. Hence __fsnotify_update_child_dentry_flags() function can take a significant amount of time. Since the bulk of this function happens under inode->i_lock this causes a significant contention on the lock when we remove the watch from the directory as the __fsnotify_update_child_dentry_flags() call from fsnotify_recalc_mask() races with __fsnotify_update_child_dentry_flags() calls from __fsnotify_parent() happening on children. This can lead upto softlockup reports reported by users.
Fix the problem by calling fsnotify_update_children_dentry_flags() to set PARENT_WATCHED flags only when parent starts watching children.
When parent stops watching children, clear false positive PARENT_WATCHED flags lazily in __fsnotify_parent() for each accessed child.(CVE-2024-47660)
In the Linux kernel, the following vulnerability has been resolved:
lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc()
If we need to increase the tree depth, allocate a new node, and then race with another thread that increased the tree depth before us, we'll still have a preallocated node that might be used later.
If we then use that node for a new non-root node, it'll still have a pointer to the old root instead of being zeroed - fix this by zeroing it in the cmpxchg failure path.(CVE-2024-47668)
In the Linux kernel, the following vulnerability has been resolved:
wifi: iwlwifi: mvm: pause TCM when the firmware is stopped
Not doing so will make us send a host command to the transport while the firmware is not alive, which will trigger a WARNING.
bad state = 0 WARNING: CPU: 2 PID: 17434 at drivers/net/wireless/intel/iwlwifi/iwl-trans.c:115 iwl_trans_send_cmd+0x1cb/0x1e0 [iwlwifi] RIP: 0010:iwl_trans_send_cmd+0x1cb/0x1e0 [iwlwifi] Call Trace: <TASK> iwl_mvm_send_cmd+0x40/0xc0 [iwlmvm] iwl_mvm_config_scan+0x198/0x260 [iwlmvm] iwl_mvm_recalc_tcm+0x730/0x11d0 [iwlmvm] iwl_mvm_tcm_work+0x1d/0x30 [iwlmvm] process_one_work+0x29e/0x640 worker_thread+0x2df/0x690 ? rescuer_thread+0x540/0x540 kthread+0x192/0x1e0 ? set_kthread_struct+0x90/0x90 ret_from_fork+0x22/0x30(CVE-2024-47673)
In the Linux kernel, the following vulnerability has been resolved: f2fs: get rid of online repaire on corrupted directory syzbot reports a f2fs bug as below: kernel BUG at fs/f2fs/inode.c:896! RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896 Call Trace: evict+0x532/0x950 fs/inode.c:704 dispose_list fs/inode.c:747 [inline] evict_inodes+0x5f9/0x690 fs/inode.c:797 generic_shutdown_super+0x9d/0x2d0 fs/super.c:627 kill_block_super+0x44/0x90 fs/super.c:1696 kill_f2fs_super+0x344/0x690 fs/f2fs/super.c:4898 deactivate_locked_super+0xc4/0x130 fs/super.c:473 cleanup_mnt+0x41f/0x4b0 fs/namespace.c:1373 task_work_run+0x24f/0x310 kernel/task_work.c:228 ptrace_notify+0x2d2/0x380 kernel/signal.c:2402 ptrace_report_syscall include/linux/ptrace.h:415 [inline] ptrace_report_syscall_exit include/linux/ptrace.h:477 [inline] syscall_exit_work+0xc6/0x190 kernel/entry/common.c:173 syscall_exit_to_user_mode_prepare kernel/entry/common.c:200 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:205 [inline] syscall_exit_to_user_mode+0x279/0x370 kernel/entry/common.c:218 do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896 Online repaire on corrupted directory in f2fs_lookup() can generate dirty data/meta while racing w/ readonly remount, it may leave dirty inode after filesystem becomes readonly, however, checkpoint() will skips flushing dirty inode in a state of readonly mode, result in above panic. Let's get rid of online repaire in f2fs_lookup(), and leave the work to fsck.f2fs.(CVE-2024-47690)
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid use-after-free in f2fs_stop_gc_thread() syzbot reports a f2fs bug as below: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114 print_report+0xe8/0x550 mm/kasan/report.c:491 kasan_report+0x143/0x180 mm/kasan/report.c:601 kasan_check_range+0x282/0x290 mm/kasan/generic.c:189 instrument_atomic_read_write include/linux/instrumented.h:96 [inline] atomic_fetch_add_relaxed include/linux/atomic/atomic-instrumented.h:252 [inline] __refcount_add include/linux/refcount.h:184 [inline] __refcount_inc include/linux/refcount.h:241 [inline] refcount_inc include/linux/refcount.h:258 [inline] get_task_struct include/linux/sched/task.h:118 [inline] kthread_stop+0xca/0x630 kernel/kthread.c:704 f2fs_stop_gc_thread+0x65/0xb0 fs/f2fs/gc.c:210 f2fs_do_shutdown+0x192/0x540 fs/f2fs/file.c:2283 f2fs_ioc_shutdown fs/f2fs/file.c:2325 [inline] __f2fs_ioctl+0x443a/0xbe60 fs/f2fs/file.c:4325 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f The root cause is below race condition, it may cause use-after-free issue in sbi->gc_th pointer. - remount - f2fs_remount - f2fs_stop_gc_thread - kfree(gc_th) - f2fs_ioc_shutdown - f2fs_do_shutdown - f2fs_stop_gc_thread - kthread_stop(gc_th->f2fs_gc_task) : sbi->gc_thread = NULL; We will call f2fs_do_shutdown() in two paths: - for f2fs_ioc_shutdown() path, we should grab sb->s_umount semaphore for fixing. - for f2fs_shutdown() path, it's safe since caller has already grabbed sb->s_umount semaphore.(CVE-2024-47691)
In the Linux kernel, the following vulnerability has been resolved: IB/core: Fix ib_cache_setup_one error flow cleanup When ib_cache_update return an error, we exit ib_cache_setup_one instantly with no proper cleanup, even though before this we had already successfully done gid_table_setup_one, that results in the kernel WARN below. Do proper cleanup using gid_table_cleanup_one before returning the err in order to fix the issue. WARNING: CPU: 4 PID: 922 at drivers/infiniband/core/cache.c:806 gid_table_release_one+0x181/0x1a0 Modules linked in: CPU: 4 UID: 0 PID: 922 Comm: c_repro Not tainted 6.11.0-rc1+ #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:gid_table_release_one+0x181/0x1a0 Code: 44 8b 38 75 0c e8 2f cb 34 ff 4d 8b b5 28 05 00 00 e8 23 cb 34 ff 44 89 f9 89 da 4c 89 f6 48 c7 c7 d0 58 14 83 e8 4f de 21 ff <0f> 0b 4c 8b 75 30 e9 54 ff ff ff 48 8 3 c4 10 5b 5d 41 5c 41 5d 41 RSP: 0018:ffffc90002b835b0 EFLAGS: 00010286 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff811c8527 RDX: 0000000000000000 RSI: ffffffff811c8534 RDI: 0000000000000001 RBP: ffff8881011b3d00 R08: ffff88810b3abe00 R09: 205d303839303631 R10: 666572207972746e R11: 72746e6520444947 R12: 0000000000000001 R13: ffff888106390000 R14: ffff8881011f2110 R15: 0000000000000001 FS: 00007fecc3b70800(0000) GS:ffff88813bd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020000340 CR3: 000000010435a001 CR4: 00000000003706b0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ? show_regs+0x94/0xa0 ? __warn+0x9e/0x1c0 ? gid_table_release_one+0x181/0x1a0 ? report_bug+0x1f9/0x340 ? gid_table_release_one+0x181/0x1a0 ? handle_bug+0xa2/0x110 ? exc_invalid_op+0x31/0xa0 ? asm_exc_invalid_op+0x16/0x20 ? __warn_printk+0xc7/0x180 ? __warn_printk+0xd4/0x180 ? gid_table_release_one+0x181/0x1a0 ib_device_release+0x71/0xe0 ? __pfx_ib_device_release+0x10/0x10 device_release+0x44/0xd0 kobject_put+0x135/0x3d0 put_device+0x20/0x30 rxe_net_add+0x7d/0xa0 rxe_newlink+0xd7/0x190 nldev_newlink+0x1b0/0x2a0 ? __pfx_nldev_newlink+0x10/0x10 rdma_nl_rcv_msg+0x1ad/0x2e0 rdma_nl_rcv_skb.constprop.0+0x176/0x210 netlink_unicast+0x2de/0x400 netlink_sendmsg+0x306/0x660 __sock_sendmsg+0x110/0x120 _syssendmsg+0x30e/0x390 _sys_sendmsg+0x9b/0xf0 ? kstrtouint+0x6e/0xa0 ? kstrtouint_from_user+0x7c/0xb0 ? get_pid_task+0xb0/0xd0 ? proc_fail_nth_write+0x5b/0x140 ? __fget_light+0x9a/0x200 ? preempt_count_add+0x47/0xa0 __sys_sendmsg+0x61/0xd0 do_syscall_64+0x50/0x110 entry_SYSCALL_64_after_hwframe+0x76/0x7e(CVE-2024-47693)
In the Linux kernel, the following vulnerability has been resolved: RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency In the commit aee2424246f9 ("RDMA/iwcm: Fix a use-after-free related to destroying CM IDs"), the function flush_workqueue is invoked to flush the work queue iwcm_wq. But at that time, the work queue iwcm_wq was created via the function alloc_ordered_workqueue without the flag WQ_MEM_RECLAIM. Because the current process is trying to flush the whole iwcm_wq, if iwcm_wq doesn't have the flag WQ_MEM_RECLAIM, verify that the current process is not reclaiming memory or running on a workqueue which doesn't have the flag WQ_MEM_RECLAIM as that can break forward-progress guarantee leading to a deadlock. The call trace is as below: [ 125.350876][ T1430] Call Trace: [ 125.356281][ T1430] <TASK> [ 125.361285][ T1430] ? __warn (kernel/panic.c:693) [ 125.367640][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.375689][ T1430] ? report_bug (lib/bug.c:180 lib/bug.c:219) [ 125.382505][ T1430] ? handle_bug (arch/x86/kernel/traps.c:239) [ 125.388987][ T1430] ? exc_invalid_op (arch/x86/kernel/traps.c:260 (discriminator 1)) [ 125.395831][ T1430] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:621) [ 125.403125][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.410984][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.418764][ T1430] __flush_workqueue (kernel/workqueue.c:3970) [ 125.426021][ T1430] ? __pfxmightresched (kernel/sched/core.c:10151) [ 125.433431][ T1430] ? destroy_cm_id (drivers/infiniband/core/iwcm.c:375) iw_cm [ 125.441209][ T1430] ? pfxflushworkqueue (kernel/workqueue.c:3910) [ 125.473900][ T1430] ? _raw_spin_lock_irqsave (arch/x86/include/asm/atomic.h:107 include/linux/atomic/atomic-arch-fallback.h:2170 include/linux/atomic/atomic-instrumented.h:1302 include/asm-generic/qspinlock.h:111 include/linux/spinlock.h:187 include/linux/spinlock_api_smp.h:111 kernel/locking/spinlock.c:162) [ 125.473909][ T1430] ? pfx__raw_spin_lock_irqsave (kernel/locking/spinlock.c:161) [ 125.482537][ T1430] _destroy_id (drivers/infiniband/core/cma.c:2044) rdma_cm [ 125.495072][ T1430] nvme_rdma_free_queue (drivers/nvme/host/rdma.c:656 drivers/nvme/host/rdma.c:650) nvme_rdma [ 125.505827][ T1430] nvme_rdma_reset_ctrl_work (drivers/nvme/host/rdma.c:2180) nvme_rdma [ 125.505831][ T1430] process_one_work (kernel/workqueue.c:3231) [ 125.515122][ T1430] worker_thread (kernel/workqueue.c:3306 kernel/workqueue.c:3393) [ 125.515127][ T1430] ? __pfx_worker_thread (kernel/workqueue.c:3339) [ 125.531837][ T1430] kthread (kernel/kthread.c:389) [ 125.539864][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.550628][ T1430] ret_from_fork (arch/x86/kernel/process.c:147) [ 125.558840][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.558844][ T1430] ret_from_fork_asm (arch/x86/entry/entry_64.S:257) [ 125.566487][ T1430] </TASK> [ 125.566488][ T1430] ---[ end trace 0000000000000000 ]---(CVE-2024-47696)
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential null-ptr-deref in nilfs_btree_insert() Patch series "nilfs2: fix potential issues with empty b-tree nodes". This series addresses three potential issues with empty b-tree nodes that can occur with corrupted filesystem images, including one recently discovered by syzbot. This patch (of 3): If a b-tree is broken on the device, and the b-tree height is greater than 2 (the level of the root node is greater than 1) even if the number of child nodes of the b-tree root is 0, a NULL pointer dereference occurs in nilfs_btree_prepare_insert(), which is called from nilfs_btree_insert(). This is because, when the number of child nodes of the b-tree root is 0, nilfs_btree_do_lookup() does not set the block buffer head in any of path[x].bp_bh, leaving it as the initial value of NULL, but if the level of the b-tree root node is greater than 1, nilfs_btree_get_nonroot_node(), which accesses the buffer memory of path[x].bp_bh, is called. Fix this issue by adding a check to nilfs_btree_root_broken(), which performs sanity checks when reading the root node from the device, to detect this inconsistency. Thanks to Lizhi Xu for trying to solve the bug and clarifying the cause early on.(CVE-2024-47699)
In the Linux kernel, the following vulnerability has been resolved: ext4: avoid OOB when system.data xattr changes underneath the filesystem When looking up for an entry in an inlined directory, if e_value_offs is changed underneath the filesystem by some change in the block device, it will lead to an out-of-bounds access that KASAN detects as an UAF. EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none. loop0: detected capacity change from 2048 to 2047 ================================================================== BUG: KASAN: use-after-free in ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500 Read of size 1 at addr ffff88803e91130f by task syz-executor269/5103 CPU: 0 UID: 0 PID: 5103 Comm: syz-executor269 Not tainted 6.11.0-rc4-syzkaller #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Call Trace: <TASK> __dump_stack lib/dump_stack.c:93 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119 print_address_description mm/kasan/report.c:377 [inline] print_report+0x169/0x550 mm/kasan/report.c:488 kasan_report+0x143/0x180 mm/kasan/report.c:601 ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500 ext4_find_inline_entry+0x4be/0x5e0 fs/ext4/inline.c:1697 __ext4_find_entry+0x2b4/0x1b30 fs/ext4/namei.c:1573 ext4_lookup_entry fs/ext4/namei.c:1727 [inline] ext4_lookup+0x15f/0x750 fs/ext4/namei.c:1795 lookup_one_qstr_excl+0x11f/0x260 fs/namei.c:1633 filename_create+0x297/0x540 fs/namei.c:3980 do_symlinkat+0xf9/0x3a0 fs/namei.c:4587 __do_sys_symlinkat fs/namei.c:4610 [inline] __se_sys_symlinkat fs/namei.c:4607 [inline] __x64_sys_symlinkat+0x95/0xb0 fs/namei.c:4607 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f3e73ced469 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 21 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fff4d40c258 EFLAGS: 00000246 ORIG_RAX: 000000000000010a RAX: ffffffffffffffda RBX: 0032656c69662f2e RCX: 00007f3e73ced469 RDX: 0000000020000200 RSI: 00000000ffffff9c RDI: 00000000200001c0 RBP: 0000000000000000 R08: 00007fff4d40c290 R09: 00007fff4d40c290 R10: 0023706f6f6c2f76 R11: 0000000000000246 R12: 00007fff4d40c27c R13: 0000000000000003 R14: 431bde82d7b634db R15: 00007fff4d40c2b0 </TASK> Calling ext4_xattr_ibody_find right after reading the inode with ext4_get_inode_loc will lead to a check of the validity of the xattrs, avoiding this problem.(CVE-2024-47701)
In the Linux kernel, the following vulnerability has been resolved: bpf, lsm: Add check for BPF LSM return value A bpf prog returning a positive number attached to file_alloc_security hook makes kernel panic. This happens because file system can not filter out the positive number returned by the LSM prog using IS_ERR, and misinterprets this positive number as a file pointer. Given that hook file_alloc_security never returned positive number before the introduction of BPF LSM, and other BPF LSM hooks may encounter similar issues, this patch adds LSM return value check in verifier, to ensure no unexpected value is returned.(CVE-2024-47703)
In the Linux kernel, the following vulnerability has been resolved: block: fix potential invalid pointer dereference in blk_add_partition The blk_add_partition() function initially used a single if-condition (IS_ERR(part)) to check for errors when adding a partition. This was modified to handle the specific case of -ENXIO separately, allowing the function to proceed without logging the error in this case. However, this change unintentionally left a path where md_autodetect_dev() could be called without confirming that part is a valid pointer. This commit separates the error handling logic by splitting the initial if-condition, improving code readability and handling specific error scenarios explicitly. The function now distinguishes the general error case from -ENXIO without altering the existing behavior of md_autodetect_dev() calls.(CVE-2024-47705)
In the Linux kernel, the following vulnerability has been resolved: jfs: fix out-of-bounds in dbNextAG() and diAlloc() In dbNextAG() , there is no check for the case where bmp->db_numag is greater or same than MAXAG due to a polluted image, which causes an out-of-bounds. Therefore, a bounds check should be added in dbMount(). And in dbNextAG(), a check for the case where agpref is greater than bmp->db_numag should be added, so an out-of-bounds exception should be prevented. Additionally, a check for the case where agno is greater or same than MAXAG should be added in diAlloc() to prevent out-of-bounds.(CVE-2024-47723)
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to wait dio completion It should wait all existing dio write IOs before block removal, otherwise, previous direct write IO may overwrite data in the block which may be reused by other inode.(CVE-2024-47726)
In the Linux kernel, the following vulnerability has been resolved: padata: use integer wrap around to prevent deadlock on seq_nr overflow When submitting more than 2^32 padata objects to padata_do_serial, the current sorting implementation incorrectly sorts padata objects with overflowed seq_nr, causing them to be placed before existing objects in the reorder list. This leads to a deadlock in the serialization process as padata_find_next cannot match padata->seq_nr and pd->processed because the padata instance with overflowed seq_nr will be selected next. To fix this, we use an unsigned integer wrap around to correctly sort padata objects in scenarios with integer overflow.(CVE-2024-47739)
In the Linux kernel, the following vulnerability has been resolved: firmware_loader: Block path traversal Most firmware names are hardcoded strings, or are constructed from fairly constrained format strings where the dynamic parts are just some hex numbers or such. However, there are a couple codepaths in the kernel where firmware file names contain string components that are passed through from a device or semi-privileged userspace; the ones I could find (not counting interfaces that require root privileges) are: - lpfc_sli4_request_firmware_update() seems to construct the firmware filename from "ModelName", a string that was previously parsed out of some descriptor ("Vital Product Data") in lpfc_fill_vpd() - nfp_net_fw_find() seems to construct a firmware filename from a model name coming from nfp_hwinfo_lookup(pf->hwinfo, "nffw.partno"), which I think parses some descriptor that was read from the device. (But this case likely isn't exploitable because the format string looks like "netronome/nic_%s", and there shouldn't be any folders starting with "netronome/nic_". The previous case was different because there, the "%s" is at the start of the format string.) - module_flash_fw_schedule() is reachable from the ETHTOOL_MSG_MODULE_FW_FLASH_ACT netlink command, which is marked as GENL_UNS_ADMIN_PERM (meaning CAP_NET_ADMIN inside a user namespace is enough to pass the privilege check), and takes a userspace-provided firmware name. (But I think to reach this case, you need to have CAP_NET_ADMIN over a network namespace that a special kind of ethernet device is mapped into, so I think this is not a viable attack path in practice.) Fix it by rejecting any firmware names containing ".." path components. For what it's worth, I went looking and haven't found any USB device drivers that use the firmware loader dangerously.(CVE-2024-47742)
In the Linux kernel, the following vulnerability has been resolved: vhost_vdpa: assign irq bypass producer token correctly We used to call irq_bypass_unregister_producer() in vhost_vdpa_setup_vq_irq() which is problematic as we don't know if the token pointer is still valid or not. Actually, we use the eventfd_ctx as the token so the life cycle of the token should be bound to the VHOST_SET_VRING_CALL instead of vhost_vdpa_setup_vq_irq() which could be called by set_status(). Fixing this by setting up irq bypass producer's token when handling VHOST_SET_VRING_CALL and un-registering the producer before calling vhost_vring_ioctl() to prevent a possible use after free as eventfd could have been released in vhost_vring_ioctl(). And such registering and unregistering will only be done if DRIVER_OK is set.(CVE-2024-47748)
In the Linux kernel, the following vulnerability has been resolved: PCI: keystone: Fix if-statement expression in ks_pcie_quirk() This code accidentally uses && where || was intended. It potentially results in a NULL dereference. Thus, fix the if-statement expression to use the correct condition. kwilczynski: commit log
In the Linux kernel, the following vulnerability has been resolved: nbd: fix race between timeout and normal completion If request timetout is handled by nbd_requeue_cmd(), normal completion has to be stopped for avoiding to complete this requeued request, other use-after-free can be triggered. Fix the race by clearing NBD_CMD_INFLIGHT in nbd_requeue_cmd(), meantime make sure that cmd->lock is grabbed for clearing the flag and the requeue.(CVE-2024-49855)
In the Linux kernel, the following vulnerability has been resolved: efistub/tpm: Use ACPI reclaim memory for event log to avoid corruption The TPM event log table is a Linux specific construct, where the data produced by the GetEventLog() boot service is cached in memory, and passed on to the OS using an EFI configuration table. The use of EFI_LOADER_DATA here results in the region being left unreserved in the E820 memory map constructed by the EFI stub, and this is the memory description that is passed on to the incoming kernel by kexec, which is therefore unaware that the region should be reserved. Even though the utility of the TPM2 event log after a kexec is questionable, any corruption might send the parsing code off into the weeds and crash the kernel. So let's use EFI_ACPI_RECLAIM_MEMORY instead, which is always treated as reserved by the E820 conversion logic.(CVE-2024-49858)
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to check atomic_file in f2fs ioctl interfaces Some f2fs ioctl interfaces like f2fs_ioc_set_pin_file(), f2fs_move_file_range(), and f2fs_defragment_range() missed to check atomic_write status, which may cause potential race issue, fix it.(CVE-2024-49859)
In the Linux kernel, the following vulnerability has been resolved: ACPI: sysfs: validate return type of _STR method Only buffer objects are valid return values of _STR. If something else is returned description_show() will access invalid memory.(CVE-2024-49860)
In the Linux kernel, the following vulnerability has been resolved: powercap: intel_rapl: Fix off by one in get_rpi() The rp->priv->rpi array is either rpi_msr or rpi_tpmi which have NR_RAPL_PRIMITIVES number of elements. Thus the > needs to be >= to prevent an off by one access.(CVE-2024-49862)
In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate When doing cleanup, if flags without OCFS2_BH_READAHEAD, it may trigger NULL pointer dereference in the following ocfs2_set_buffer_uptodate() if bh is NULL.(CVE-2024-49877)
In the Linux kernel, the following vulnerability has been resolved: drm: omapdrm: Add missing check for alloc_ordered_workqueue As it may return NULL pointer and cause NULL pointer dereference. Add check for the return value of alloc_ordered_workqueue.(CVE-2024-49879)
In the Linux kernel, the following vulnerability has been resolved: ext4: update orig_path in ext4_find_extent() In ext4_find_extent(), if the path is not big enough, we free it and set orig_path to NULL. But after reallocating and successfully initializing the path, we don't update orig_path, in which case the caller gets a valid path but a NULL ppath, and this may cause a NULL pointer dereference or a path memory leak. For example: ext4_split_extent path = ppath = 2000 ext4_find_extent if (depth > path[0].p_maxdepth) kfree(path = 2000); orig_path = path = NULL; path = kcalloc() = 3000 ext4_split_extent_at(ppath = NULL) path = ppath; ex = path[depth].p_ext; // NULL pointer dereference! ================================================================== BUG: kernel NULL pointer dereference, address: 0000000000000010 CPU: 6 UID: 0 PID: 576 Comm: fsstress Not tainted 6.11.0-rc2-dirty #847 RIP: 0010:ext4_split_extent_at+0x6d/0x560 Call Trace: <TASK> ext4_split_extent.isra.0+0xcb/0x1b0 ext4_ext_convert_to_initialized+0x168/0x6c0 ext4_ext_handle_unwritten_extents+0x325/0x4d0 ext4_ext_map_blocks+0x520/0xdb0 ext4_map_blocks+0x2b0/0x690 ext4_iomap_begin+0x20e/0x2c0 [...] ================================================================== Therefore, orig_path is updated when the extent lookup succeeds, so that the caller can safely use path or ppath.(CVE-2024-49881)
In the Linux kernel, the following vulnerability has been resolved: ext4: fix double brelse() the buffer of the extents path In ext4_ext_try_to_merge_up(), set path[1].p_bh to NULL after it has been released, otherwise it may be released twice. An example of what triggers this is as follows: split2 map split1 |--------|-------|--------| ext4_ext_map_blocks ext4_ext_handle_unwritten_extents ext4_split_convert_extents // path->p_depth == 0 ext4_split_extent // 1. do split1 ext4_split_extent_at |ext4_ext_insert_extent | ext4_ext_create_new_leaf | ext4_ext_grow_indepth | le16_add_cpu(&neh->eh_depth, 1) | ext4_find_extent | // return -ENOMEM |// get error and try zeroout |path = ext4_find_extent | path->p_depth = 1 |ext4_ext_try_to_merge | ext4_ext_try_to_merge_up | path->p_depth = 0 | brelse(path[1].p_bh) ---> not set to NULL here |// zeroout success // 2. update path ext4_find_extent // 3. do split2 ext4_split_extent_at ext4_ext_insert_extent ext4_ext_create_new_leaf ext4_ext_grow_indepth le16_add_cpu(&neh->eh_depth, 1) ext4_find_extent path[0].p_bh = NULL; path->p_depth = 1 read_extent_tree_block ---> return err // path[1].p_bh is still the old value ext4_free_ext_path ext4_ext_drop_refs // path->p_depth == 1 brelse(path[1].p_bh) ---> brelse a buffer twice Finally got the following WARRNING when removing the buffer from lru: ============================================ VFS: brelse: Trying to free free buffer WARNING: CPU: 2 PID: 72 at fs/buffer.c:1241 __brelse+0x58/0x90 CPU: 2 PID: 72 Comm: kworker/u19:1 Not tainted 6.9.0-dirty #716 RIP: 0010:__brelse+0x58/0x90 Call Trace: <TASK> __find_get_block+0x6e7/0x810 bdev_getblk+0x2b/0x480 __ext4_get_inode_loc+0x48a/0x1240 ext4_get_inode_loc+0xb2/0x150 ext4_reserve_inode_write+0xb7/0x230 __ext4_mark_inode_dirty+0x144/0x6a0 ext4_ext_insert_extent+0x9c8/0x3230 ext4_ext_map_blocks+0xf45/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] ============================================(CVE-2024-49882)
In the Linux kernel, the following vulnerability has been resolved: ext4: aovid use-after-free in ext4_ext_insert_extent() As Ojaswin mentioned in Link, in ext4_ext_insert_extent(), if the path is reallocated in ext4_ext_create_new_leaf(), we'll use the stale path and cause UAF. Below is a sample trace with dummy values: ext4_ext_insert_extent path = ppath = 2000 ext4_ext_create_new_leaf(ppath) ext4_find_extent(ppath) path = ppath = 2000 if (depth > path[0].p_maxdepth) kfree(path = 2000); ppath = path = NULL; path = kcalloc() = 3000 ppath = 3000; return path; / here path is still 2000, UAF! / eh = path[depth].p_hdr ================================================================== BUG: KASAN: slab-use-after-free in ext4_ext_insert_extent+0x26d4/0x3330 Read of size 8 at addr ffff8881027bf7d0 by task kworker/u36:1/179 CPU: 3 UID: 0 PID: 179 Comm: kworker/u6:1 Not tainted 6.11.0-rc2-dirty #866 Call Trace: <TASK> ext4_ext_insert_extent+0x26d4/0x3330 ext4_ext_map_blocks+0xe22/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 [...] Allocated by task 179: ext4_find_extent+0x81c/0x1f70 ext4_ext_map_blocks+0x146/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 ext4_writepages+0x26d/0x4e0 do_writepages+0x175/0x700 [...] Freed by task 179: kfree+0xcb/0x240 ext4_find_extent+0x7c0/0x1f70 ext4_ext_insert_extent+0xa26/0x3330 ext4_ext_map_blocks+0xe22/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 ext4_writepages+0x26d/0x4e0 do_writepages+0x175/0x700 [...] ================================================================== So use *ppath to update the path to avoid the above problem.(CVE-2024-49883)
In the Linux kernel, the following vulnerability has been resolved: ext4: fix slab-use-after-free in ext4_split_extent_at() We hit the following use-after-free: ================================================================== BUG: KASAN: slab-use-after-free in ext4_split_extent_at+0xba8/0xcc0 Read of size 2 at addr ffff88810548ed08 by task kworker/u20:0/40 CPU: 0 PID: 40 Comm: kworker/u20:0 Not tainted 6.9.0-dirty #724 Call Trace: <TASK> kasan_report+0x93/0xc0 ext4_split_extent_at+0xba8/0xcc0 ext4_split_extent.isra.0+0x18f/0x500 ext4_split_convert_extents+0x275/0x750 ext4_ext_handle_unwritten_extents+0x73e/0x1580 ext4_ext_map_blocks+0xe20/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] Allocated by task 40: __kmalloc_noprof+0x1ac/0x480 ext4_find_extent+0xf3b/0x1e70 ext4_ext_map_blocks+0x188/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] Freed by task 40: kfree+0xf1/0x2b0 ext4_find_extent+0xa71/0x1e70 ext4_ext_insert_extent+0xa22/0x3260 ext4_split_extent_at+0x3ef/0xcc0 ext4_split_extent.isra.0+0x18f/0x500 ext4_split_convert_extents+0x275/0x750 ext4_ext_handle_unwritten_extents+0x73e/0x1580 ext4_ext_map_blocks+0xe20/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] ================================================================== The flow of issue triggering is as follows: ext4_split_extent_at path = ppath ext4_ext_insert_extent(ppath) ext4_ext_create_new_leaf(ppath) ext4_find_extent(orig_path) path = orig_path read_extent_tree_block // return -ENOMEM or -EIO ext4_free_ext_path(path) kfree(path) orig_path = NULL a. If err is -ENOMEM: ext4_ext_dirty(path + path->p_depth) // path use-after-free !!! b. If err is -EIO and we have EXT_DEBUG defined: ext4_ext_show_leaf(path) eh = path[depth].p_hdr // path also use-after-free !!! So when trying to zeroout or fix the extent length, call ext4_find_extent() to update the path. In addition we use ppath directly as an ext4_ext_show_leaf() input to avoid possible use-after-free when EXT_DEBUG is defined, and to avoid unnecessary path updates.(CVE-2024-49884)
In the Linux kernel, the following vulnerability has been resolved: platform/x86: ISST: Fix the KASAN report slab-out-of-bounds bug Attaching SST PCI device to VM causes "BUG: KASAN: slab-out-of-bounds". kasan report: [ 19.411889] ================================================================== [ 19.413702] BUG: KASAN: slab-out-of-bounds in _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.415634] Read of size 8 at addr ffff888829e65200 by task cpuhp/16/113 [ 19.417368] [ 19.418627] CPU: 16 PID: 113 Comm: cpuhp/16 Tainted: G E 6.9.0 #10 [ 19.420435] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference Platform, BIOS VMW201.00V.20192059.B64.2207280713 07/28/2022 [ 19.422687] Call Trace: [ 19.424091] <TASK> [ 19.425448] dump_stack_lvl+0x5d/0x80 [ 19.426963] ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.428694] print_report+0x19d/0x52e [ 19.430206] ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [ 19.431837] ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.433539] kasan_report+0xf0/0x170 [ 19.435019] ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.436709] _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.438379] ? __pfx_sched_clock_cpu+0x10/0x10 [ 19.439910] isst_if_cpu_online+0x406/0x58f [isst_if_common] [ 19.441573] ? __pfx_isst_if_cpu_online+0x10/0x10 [isst_if_common] [ 19.443263] ? ttwu_queue_wakelist+0x2c1/0x360 [ 19.444797] cpuhp_invoke_callback+0x221/0xec0 [ 19.446337] cpuhp_thread_fun+0x21b/0x610 [ 19.447814] ? __pfx_cpuhp_thread_fun+0x10/0x10 [ 19.449354] smpboot_thread_fn+0x2e7/0x6e0 [ 19.450859] ? __pfx_smpboot_thread_fn+0x10/0x10 [ 19.452405] kthread+0x29c/0x350 [ 19.453817] ? __pfx_kthread+0x10/0x10 [ 19.455253] ret_from_fork+0x31/0x70 [ 19.456685] ? __pfx_kthread+0x10/0x10 [ 19.458114] ret_from_fork_asm+0x1a/0x30 [ 19.459573] </TASK> [ 19.460853] [ 19.462055] Allocated by task 1198: [ 19.463410] kasan_save_stack+0x30/0x50 [ 19.464788] kasan_save_track+0x14/0x30 [ 19.466139] __kasan_kmalloc+0xaa/0xb0 [ 19.467465] __kmalloc+0x1cd/0x470 [ 19.468748] isst_if_cdev_register+0x1da/0x350 [isst_if_common] [ 19.470233] isst_if_mbox_init+0x108/0xff0 [isst_if_mbox_msr] [ 19.471670] do_one_initcall+0xa4/0x380 [ 19.472903] do_init_module+0x238/0x760 [ 19.474105] load_module+0x5239/0x6f00 [ 19.475285] init_module_from_file+0xd1/0x130 [ 19.476506] idempotent_init_module+0x23b/0x650 [ 19.477725] __x64_sys_finit_module+0xbe/0x130 [ 19.476506] idempotent_init_module+0x23b/0x650 [ 19.477725] __x64_sys_finit_module+0xbe/0x130 [ 19.478920] do_syscall_64+0x82/0x160 [ 19.480036] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 19.481292] [ 19.482205] The buggy address belongs to the object at ffff888829e65000 which belongs to the cache kmalloc-512 of size 512 [ 19.484818] The buggy address is located 0 bytes to the right of allocated 512-byte region [ffff888829e65000, ffff888829e65200) [ 19.487447] [ 19.488328] The buggy address belongs to the physical page: [ 19.489569] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff888829e60c00 pfn:0x829e60 [ 19.491140] head: order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0 [ 19.492466] anon flags: 0x57ffffc0000840(slab|head|node=1|zone=2|lastcpupid=0x1fffff) [ 19.493914] page_type: 0xffffffff() [ 19.494988] raw: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [ 19.496451] raw: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [ 19.497906] head: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [ 19.499379] head: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [ 19.500844] head: 0057ffffc0000003 ffffea0020a79801 ffffea0020a79848 00000000ffffffff [ 19.502316] head: 0000000800000000 0000000000000000 00000000ffffffff 0000000000000000 [ 19.503784] page dumped because: k ---truncated---(CVE-2024-49886)
In the Linux kernel, the following vulnerability has been resolved: ext4: avoid use-after-free in ext4_ext_show_leaf() In ext4_find_extent(), path may be freed by error or be reallocated, so using a previously saved ppath may have been freed and thus may trigger use-after-free, as follows: ext4_split_extent path = ppath; ext4_split_extent_at(ppath) path = ext4_find_extent(ppath) ext4_split_extent_at(ppath) // ext4_find_extent fails to free path // but zeroout succeeds ext4_ext_show_leaf(inode, path) eh = path[depth].p_hdr // path use-after-free !!! Similar to ext4_split_extent_at(), we use ppath directly as an input to ext4_ext_show_leaf(). Fix a spelling error by the way. Same problem in ext4_ext_handle_unwritten_extents(). Since 'path' is only used in ext4_ext_show_leaf(), remove 'path' and use ppath directly. This issue is triggered only when EXT_DEBUG is defined and therefore does not affect functionality.(CVE-2024-49889)
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check stream before comparing them [WHAT & HOW] amdgpu_dm can pass a null stream to dc_is_stream_unchanged. It is necessary to check for null before dereferencing them. This fixes 1 FORWARD_NULL issue reported by Coverity.(CVE-2024-49896)
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add null check for top_pipe_to_program in commit_planes_for_stream This commit addresses a null pointer dereference issue in the commit_planes_for_stream function at line 4140. The issue could occur when top_pipe_to_program is null. The fix adds a check to ensure top_pipe_to_program is not null before accessing its stream_res. This prevents a null pointer dereference. Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.c:4140 commit_planes_for_stream() error: we previously assumed 'top_pipe_to_program' could be null (see line 3906)(CVE-2024-49913)
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add NULL check for clk_mgr and clk_mgr->funcs in dcn30_init_hw This commit addresses a potential null pointer dereference issue in the dcn30_init_hw function. The issue could occur when dc->clk_mgr or dc->clk_mgr->funcs is null. The fix adds a check to ensure dc->clk_mgr and dc->clk_mgr->funcs is not null before accessing its functions. This prevents a potential null pointer dereference. Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c:789 dcn30_init_hw() error: we previously assumed 'dc->clk_mgr' could be null (see line 628)(CVE-2024-49917)
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check null pointers before using them [WHAT & HOW] These pointers are null checked previously in the same function, indicating they might be null as reported by Coverity. As a result, they need to be checked when used again. This fixes 3 FORWARD_NULL issue reported by Coverity.(CVE-2024-49922)
In the Linux kernel, the following vulnerability has been resolved: fbdev: pxafb: Fix possible use after free in pxafb_task() In the pxafb_probe function, it calls the pxafb_init_fbinfo function, after which &fbi->task is associated with pxafb_task. Moreover, within this pxafb_init_fbinfo function, the pxafb_blank function within the &pxafb_ops struct is capable of scheduling work. If we remove the module which will call pxafb_remove to make cleanup, it will call unregister_framebuffer function which can call do_unregister_framebuffer to free fbi->fb through put_fb_info(fb_info), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows: CPU0 CPU1 | pxafb_task pxafb_remove | unregister_framebuffer(info) | do_unregister_framebuffer(fb_info) | put_fb_info(fb_info) | // free fbi->fb | set_ctrlr_state(fbi, state) | __pxafb_lcd_power(fbi, 0) | fbi->lcd_power(on, &fbi->fb.var) | //use fbi->fb Fix it by ensuring that the work is canceled before proceeding with the cleanup in pxafb_remove. Note that only root user can remove the driver at runtime.(CVE-2024-49924)
In the Linux kernel, the following vulnerability has been resolved: blk_iocost: fix more out of bound shifts Recently running UBSAN caught few out of bound shifts in the ioc_forgive_debts() function: UBSAN: shift-out-of-bounds in block/blk-iocost.c:2142:38 shift exponent 80 is too large for 64-bit type 'u64' (aka 'unsigned long long') ... UBSAN: shift-out-of-bounds in block/blk-iocost.c:2144:30 shift exponent 80 is too large for 64-bit type 'u64' (aka 'unsigned long long') ... Call Trace: <IRQ> dump_stack_lvl+0xca/0x130 __ubsan_handle_shift_out_of_bounds+0x22c/0x280 ? __lock_acquire+0x6441/0x7c10 ioc_timer_fn+0x6cec/0x7750 ? blk_iocost_init+0x720/0x720 ? call_timer_fn+0x5d/0x470 call_timer_fn+0xfa/0x470 ? blk_iocost_init+0x720/0x720 __run_timer_base+0x519/0x700 ... Actual impact of this issue was not identified but I propose to fix the undefined behaviour. The proposed fix to prevent those out of bound shifts consist of precalculating exponent before using it the shift operations by taking min value from the actual exponent and maximum possible number of bits.(CVE-2024-49933)
In the Linux kernel, the following vulnerability has been resolved: fs/inode: Prevent dump_mapping() accessing invalid dentry.d_name.name It's observed that a crash occurs during hot-remove a memory device, in which user is accessing the hugetlb. See calltrace as following: ------------[ cut here ]------------ WARNING: CPU: 1 PID: 14045 at arch/x86/mm/fault.c:1278 do_user_addr_fault+0x2a0/0x790 Modules linked in: kmem device_dax cxl_mem cxl_pmem cxl_port cxl_pci dax_hmem dax_pmem nd_pmem cxl_acpi nd_btt cxl_core crc32c_intel nvme virtiofs fuse nvme_core nfit libnvdimm dm_multipath scsi_dh_rdac scsi_dh_emc s mirror dm_region_hash dm_log dm_mod CPU: 1 PID: 14045 Comm: daxctl Not tainted 6.10.0-rc2-lizhijian+ #492 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:do_user_addr_fault+0x2a0/0x790 Code: 48 8b 00 a8 04 0f 84 b5 fe ff ff e9 1c ff ff ff 4c 89 e9 4c 89 e2 be 01 00 00 00 bf 02 00 00 00 e8 b5 ef 24 00 e9 42 fe ff ff <0f> 0b 48 83 c4 08 4c 89 ea 48 89 ee 4c 89 e7 5b 5d 41 5c 41 5d 41 RSP: 0000:ffffc90000a575f0 EFLAGS: 00010046 RAX: ffff88800c303600 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000001000 RSI: ffffffff82504162 RDI: ffffffff824b2c36 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffffc90000a57658 R13: 0000000000001000 R14: ffff88800bc2e040 R15: 0000000000000000 FS: 00007f51cb57d880(0000) GS:ffff88807fd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000001000 CR3: 00000000072e2004 CR4: 00000000001706f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ? __warn+0x8d/0x190 ? do_user_addr_fault+0x2a0/0x790 ? report_bug+0x1c3/0x1d0 ? handle_bug+0x3c/0x70 ? exc_invalid_op+0x14/0x70 ? asm_exc_invalid_op+0x16/0x20 ? do_user_addr_fault+0x2a0/0x790 ? exc_page_fault+0x31/0x200 exc_page_fault+0x68/0x200 <...snip...> BUG: unable to handle page fault for address: 0000000000001000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0 Oops: Oops: 0000 [#1] PREEMPT SMP PTI ---[ end trace 0000000000000000 ]--- BUG: unable to handle page fault for address: 0000000000001000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0 Oops: Oops: 0000 [#1] PREEMPT SMP PTI CPU: 1 PID: 14045 Comm: daxctl Kdump: loaded Tainted: G W 6.10.0-rc2-lizhijian+ #492 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:dentry_name+0x1f4/0x440 <...snip...> ? dentry_name+0x2fa/0x440 vsnprintf+0x1f3/0x4f0 vprintk_store+0x23a/0x540 vprintk_emit+0x6d/0x330 _printk+0x58/0x80 dump_mapping+0x10b/0x1a0 ? __pfx_free_object_rcu+0x10/0x10 __dump_page+0x26b/0x3e0 ? vprintk_emit+0xe0/0x330 ? _printk+0x58/0x80 ? dump_page+0x17/0x50 dump_page+0x17/0x50 do_migrate_range+0x2f7/0x7f0 ? do_migrate_range+0x42/0x7f0 ? offline_pages+0x2f4/0x8c0 offline_pages+0x60a/0x8c0 memory_subsys_offline+0x9f/0x1c0 ? lockdep_hardirqs_on+0x77/0x100 ? _raw_spin_unlock_irqrestore+0x38/0x60 device_offline+0xe3/0x110 state_store+0x6e/0xc0 kernfs_fop_write_iter+0x143/0x200 vfs_write+0x39f/0x560 ksys_write+0x65/0xf0 do_syscall_64+0x62/0x130 Previously, some sanity check have been done in dump_mapping() before the print facility parsing '%pd' though, it's still possible to run into an invalid dentry.d_name.name. Since dump_mapping() only needs to dump the filename only, retrieve it by itself in a safer way to prevent an unnecessary crash. Note that either retrieving the filename with '%pd' or strncpy_from_kernel_nofault(), the filename could be unreliable.(CVE-2024-49934)
In the Linux kernel, the following vulnerability has been resolved: net/xen-netback: prevent UAF in xenvif_flush_hash() During the list_for_each_entry_rcu iteration call of xenvif_flush_hash, kfree_rcu does not exist inside the rcu read critical section, so if kfree_rcu is called when the rcu grace period ends during the iteration, UAF occurs when accessing head->next after the entry becomes free. Therefore, to solve this, you need to change it to list_for_each_entry_safe.(CVE-2024-49936)
In the Linux kernel, the following vulnerability has been resolved: l2tp: prevent possible tunnel refcount underflow When a session is created, it sets a backpointer to its tunnel. When the session refcount drops to 0, l2tp_session_free drops the tunnel refcount if session->tunnel is non-NULL. However, session->tunnel is set in l2tp_session_create, before the tunnel refcount is incremented by l2tp_session_register, which leaves a small window where session->tunnel is non-NULL when the tunnel refcount hasn't been bumped. Moving the assignment to l2tp_session_register is trivial but l2tp_session_create calls l2tp_session_set_header_len which uses session->tunnel to get the tunnel's encap. Add an encap arg to l2tp_session_set_header_len to avoid using session->tunnel. If l2tpv3 sessions have colliding IDs, it is possible for l2tp_v3_session_get to race with l2tp_session_register and fetch a session which doesn't yet have session->tunnel set. Add a check for this case.(CVE-2024-49940)
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix uaf in l2cap_connect [Syzbot reported] BUG: KASAN: slab-use-after-free in l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949 Read of size 8 at addr ffff8880241e9800 by task kworker/u9:0/54 CPU: 0 UID: 0 PID: 54 Comm: kworker/u9:0 Not tainted 6.11.0-rc6-syzkaller-00268-g788220eee30d #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 Workqueue: hci2 hci_rx_work Call Trace: <TASK> __dump_stack lib/dump_stack.c:93 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:119 print_address_description mm/kasan/report.c:377 [inline] print_report+0xc3/0x620 mm/kasan/report.c:488 kasan_report+0xd9/0x110 mm/kasan/report.c:601 l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949 l2cap_connect_req net/bluetooth/l2cap_core.c:4080 [inline] l2cap_bredr_sig_cmd net/bluetooth/l2cap_core.c:4772 [inline] l2cap_sig_channel net/bluetooth/l2cap_core.c:5543 [inline] l2cap_recv_frame+0xf0b/0x8eb0 net/bluetooth/l2cap_core.c:6825 l2cap_recv_acldata+0x9b4/0xb70 net/bluetooth/l2cap_core.c:7514 hci_acldata_packet net/bluetooth/hci_core.c:3791 [inline] hci_rx_work+0xaab/0x1610 net/bluetooth/hci_core.c:4028 process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231 process_scheduled_works kernel/workqueue.c:3312 [inline] worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389 kthread+0x2c1/0x3a0 kernel/kthread.c:389 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 ... Freed by task 5245: kasan_save_stack+0x33/0x60 mm/kasan/common.c:47 kasan_save_track+0x14/0x30 mm/kasan/common.c:68 kasan_save_free_info+0x3b/0x60 mm/kasan/generic.c:579 poison_slab_object+0xf7/0x160 mm/kasan/common.c:240 __kasan_slab_free+0x32/0x50 mm/kasan/common.c:256 kasan_slab_free include/linux/kasan.h:184 [inline] slab_free_hook mm/slub.c:2256 [inline] slab_free mm/slub.c:4477 [inline] kfree+0x12a/0x3b0 mm/slub.c:4598 l2cap_conn_free net/bluetooth/l2cap_core.c:1810 [inline] kref_put include/linux/kref.h:65 [inline] l2cap_conn_put net/bluetooth/l2cap_core.c:1822 [inline] l2cap_conn_del+0x59d/0x730 net/bluetooth/l2cap_core.c:1802 l2cap_connect_cfm+0x9e6/0xf80 net/bluetooth/l2cap_core.c:7241 hci_connect_cfm include/net/bluetooth/hci_core.h:1960 [inline] hci_conn_failed+0x1c3/0x370 net/bluetooth/hci_conn.c:1265 hci_abort_conn_sync+0x75a/0xb50 net/bluetooth/hci_sync.c:5583 abort_conn_sync+0x197/0x360 net/bluetooth/hci_conn.c:2917 hci_cmd_sync_work+0x1a4/0x410 net/bluetooth/hci_sync.c:328 process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231 process_scheduled_works kernel/workqueue.c:3312 [inline] worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389 kthread+0x2c1/0x3a0 kernel/kthread.c:389 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244(CVE-2024-49950)
In the Linux kernel, the following vulnerability has been resolved: static_call: Replace pointless WARN_ON() in static_call_module_notify() static_call_module_notify() triggers a WARN_ON(), when memory allocation fails in __static_call_add_module(). That's not really justified, because the failure case must be correctly handled by the well known call chain and the error code is passed through to the initiating userspace application. A memory allocation fail is not a fatal problem, but the WARN_ON() takes the machine out when panic_on_warn is set. Replace it with a pr_warn().(CVE-2024-49954)
In the Linux kernel, the following vulnerability has been resolved: ACPI: battery: Fix possible crash when unregistering a battery hook When a battery hook returns an error when adding a new battery, then the battery hook is automatically unregistered. However the battery hook provider cannot know that, so it will later call battery_hook_unregister() on the already unregistered battery hook, resulting in a crash. Fix this by using the list head to mark already unregistered battery hooks as already being unregistered so that they can be ignored by battery_hook_unregister().(CVE-2024-49955)
In the Linux kernel, the following vulnerability has been resolved: ocfs2: reserve space for inline xattr before attaching reflink tree One of our customers reported a crash and a corrupted ocfs2 filesystem. The crash was due to the detection of corruption. Upon troubleshooting, the fsck -fn output showed the below corruption [EXTENT_LIST_FREE] Extent list in owner 33080590 claims 230 as the next free chain record, but fsck believes the largest valid value is 227. Clamp the next record value? n The stat output from the debugfs.ocfs2 showed the following corruption where the "Next Free Rec:" had overshot the "Count:" in the root metadata block. Inode: 33080590 Mode: 0640 Generation: 2619713622 (0x9c25a856) FS Generation: 904309833 (0x35e6ac49) CRC32: 00000000 ECC: 0000 Type: Regular Attr: 0x0 Flags: Valid Dynamic Features: (0x16) HasXattr InlineXattr Refcounted Extended Attributes Block: 0 Extended Attributes Inline Size: 256 User: 0 (root) Group: 0 (root) Size: 281320357888 Links: 1 Clusters: 141738 ctime: 0x66911b56 0x316edcb8 -- Fri Jul 12 06:02:30.829349048 2024 atime: 0x66911d6b 0x7f7a28d -- Fri Jul 12 06:11:23.133669517 2024 mtime: 0x66911b56 0x12ed75d7 -- Fri Jul 12 06:02:30.317552087 2024 dtime: 0x0 -- Wed Dec 31 17:00:00 1969 Refcount Block: 2777346 Last Extblk: 2886943 Orphan Slot: 0 Sub Alloc Slot: 0 Sub Alloc Bit: 14 Tree Depth: 1 Count: 227 Next Free Rec: 230 ## Offset Clusters Block# 0 0 2310 2776351 1 2310 2139 2777375 2 4449 1221 2778399 3 5670 731 2779423 4 6401 566 2780447 ....... .... ....... ....... .... ....... The issue was in the reflink workfow while reserving space for inline xattr. The problematic function is ocfs2_reflink_xattr_inline(). By the time this function is called the reflink tree is already recreated at the destination inode from the source inode. At this point, this function reserves space for inline xattrs at the destination inode without even checking if there is space at the root metadata block. It simply reduces the l_count from 243 to 227 thereby making space of 256 bytes for inline xattr whereas the inode already has extents beyond this index (in this case up to 230), thereby causing corruption. The fix for this is to reserve space for inline metadata at the destination inode before the reflink tree gets recreated. The customer has verified the fix.(CVE-2024-49958)
In the Linux kernel, the following vulnerability has been resolved: r8169: add tally counter fields added with RTL8125 RTL8125 added fields to the tally counter, what may result in the chip dma'ing these new fields to unallocated memory. Therefore make sure that the allocated memory area is big enough to hold all of the tally counter values, even if we use only parts of it.(CVE-2024-49973)
In the Linux kernel, the following vulnerability has been resolved: uprobes: fix kernel info leak via "[uprobes]" vma xol_add_vma() maps the uninitialized page allocated by __create_xol_area() into userspace. On some architectures (x86) this memory is readable even without VM_READ, VM_EXEC results in the same pgprot_t as VM_EXEC|VM_READ, although this doesn't really matter, debugger can read this memory anyway.(CVE-2024-49975)
In the Linux kernel, the following vulnerability has been resolved: gso: fix udp gso fraglist segmentation after pull from frag_list Detect gso fraglist skbs with corrupted geometry (see below) and pass these to skb_segment instead of skb_segment_list, as the first can segment them correctly. Valid SKB_GSO_FRAGLIST skbs - consist of two or more segments - the head_skb holds the protocol headers plus first gso_size - one or more frag_list skbs hold exactly one segment - all but the last must be gso_size Optional datapath hooks such as NAT and BPF (bpf_skb_pull_data) can modify these skbs, breaking these invariants. In extreme cases they pull all data into skb linear. For UDP, this causes a NULL ptr deref in __udpv4_gso_segment_list_csum at udp_hdr(seg->next)->dest. Detect invalid geometry due to pull, by checking head_skb size. Don't just drop, as this may blackhole a destination. Convert to be able to pass to regular skb_segment.(CVE-2024-49978)
In the Linux kernel, the following vulnerability has been resolved: media: venus: fix use after free bug in venus_remove due to race condition in venus_probe, core->work is bound with venus_sys_error_handler, which is used to handle error. The code use core->sys_err_done to make sync work. The core->work is started in venus_event_notify. If we call venus_remove, there might be an unfished work. The possible sequence is as follows: CPU0 CPU1 |venus_sys_error_handler venus_remove | hfi_destroy | venus_hfi_destroy | kfree(hdev); | |hfi_reinit |venus_hfi_queues_reinit |//use hdev Fix it by canceling the work in venus_remove.(CVE-2024-49981)
In the Linux kernel, the following vulnerability has been resolved: drm/stm: Avoid use-after-free issues with crtc and plane ltdc_load() calls functions drm_crtc_init_with_planes(), drm_universal_plane_init() and drm_encoder_init(). These functions should not be called with parameters allocated with devm_kzalloc() to avoid use-after-free issues [1]. Use allocations managed by the DRM framework. Found by Linux Verification Center (linuxtesting.org). [1] https://lore.kernel.org/lkml/u366i76e3qhh3ra5oxrtngjtm2u5lterkekcz6y2jkndhuxzli@diujon4h7qwb/(CVE-2024-49992)
In the Linux kernel, the following vulnerability has been resolved: tipc: guard against string buffer overrun Smatch reports that copying media_name and if_name to name_parts may overwrite the destination. .../bearer.c:166 bearer_name_validate() error: strcpy() 'media_name' too large for 'name_parts->media_name' (32 vs 16) .../bearer.c:167 bearer_name_validate() error: strcpy() 'if_name' too large for 'name_parts->if_name' (1010102 vs 16) This does seem to be the case so guard against this possibility by using strscpy() and failing if truncation occurs. Introduced by commit b97bf3fd8f6a ("[TIPC] Initial merge") Compile tested only.(CVE-2024-49995)
In the Linux kernel, the following vulnerability has been resolved: cifs: Fix buffer overflow when parsing NFS reparse points ReparseDataLength is sum of the InodeType size and DataBuffer size. So to get DataBuffer size it is needed to subtract InodeType's size from ReparseDataLength. Function cifs_strndup_from_utf16() is currentlly accessing buf->DataBuffer at position after the end of the buffer because it does not subtract InodeType size from the length. Fix this problem and correctly subtract variable len. Member InodeType is present only when reparse buffer is large enough. Check for ReparseDataLength before accessing InodeType to prevent another invalid memory access. Major and minor rdev values are present also only when reparse buffer is large enough. Check for reparse buffer size before calling reparse_mkdev().(CVE-2024-49996)
In the Linux kernel, the following vulnerability has been resolved: static_call: Handle module init failure correctly in static_call_del_module() Module insertion invokes static_call_add_module() to initialize the static calls in a module. static_call_add_module() invokes __static_call_init(), which allocates a struct static_call_mod to either encapsulate the built-in static call sites of the associated key into it so further modules can be added or to append the module to the module chain. If that allocation fails the function returns with an error code and the module core invokes static_call_del_module() to clean up eventually added static_call_mod entries. This works correctly, when all keys used by the module were converted over to a module chain before the failure. If not then static_call_del_module() causes a #GP as it blindly assumes that key::mods points to a valid struct static_call_mod. The problem is that key::mods is not a individual struct member of struct static_call_key, it's part of a union to save space: union { / bit 0: 0 = mods, 1 = sites / unsigned long type; struct static_call_mod mods; struct static_call_site sites; }; key::sites is a pointer to the list of built-in usage sites of the static call. The type of the pointer is differentiated by bit 0. A mods pointer has the bit clear, the sites pointer has the bit set. As static_call_del_module() blidly assumes that the pointer is a valid static_call_mod type, it fails to check for this failure case and dereferences the pointer to the list of built-in call sites, which is obviously bogus. Cure it by checking whether the key has a sites or a mods pointer. If it's a sites pointer then the key is not to be touched. As the sites are walked in the same order as in __static_call_init() the site walk can be terminated because all subsequent sites have not been touched by the init code due to the error exit. If it was converted before the allocation fail, then the inner loop which searches for a module match will find nothing. A fail in the second allocation in __static_call_init() is harmless and does not require special treatment. The first allocation succeeded and converted the key to a module chain. That first entry has mod::mod == NULL and mod::next == NULL, so the inner loop of static_call_del_module() will neither find a module match nor a module chain. The next site in the walk was either already converted, but can't match the module, or it will exit the outer loop because it has a static_call_site pointer and not a static_call_mod pointer.(CVE-2024-50002)
In the Linux kernel, the following vulnerability has been resolved: ALSA: asihpi: Fix potential OOB array access ASIHPI driver stores some values in the static array upon a response from the driver, and its index depends on the firmware. We shouldn't trust it blindly. This patch adds a sanity check of the array index to fit in the array size.(CVE-2024-50007)
In the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_cmd_802_11_scan_ext() Replace one-element array with a flexible-array member in struct host_cmd_ds_802_11_scan_ext. With this, fix the following warning: elo 16 17:51:58 surfacebook kernel: ------------[ cut here ]------------ elo 16 17:51:58 surfacebook kernel: memcpy: detected field-spanning write (size 243) of single field "ext_scan->tlv_buffer" at drivers/net/wireless/marvell/mwifiex/scan.c:2239 (size 1) elo 16 17:51:58 surfacebook kernel: WARNING: CPU: 0 PID: 498 at drivers/net/wireless/marvell/mwifiex/scan.c:2239 mwifiex_cmd_802_11_scan_ext+0x83/0x90 mwifiex
In the Linux kernel, the following vulnerability has been resolved: ext4: dax: fix overflowing extents beyond inode size when partially writing The dax_iomap_rw() does two things in each iteration: map written blocks and copy user data to blocks. If the process is killed by user(See signal handling in dax_iomap_iter()), the copied data will be returned and added on inode size, which means that the length of written extents may exceed the inode size, then fsck will fail. An example is given as: dd if=/dev/urandom of=file bs=4M count=1 dax_iomap_rw iomap_iter // round 1 ext4_iomap_begin ext4_iomap_alloc // allocate 0~2M extents(written flag) dax_iomap_iter // copy 2M data iomap_iter // round 2 iomap_iter_advance iter->pos += iter->processed // iter->pos = 2M ext4_iomap_begin ext4_iomap_alloc // allocate 2~4M extents(written flag) dax_iomap_iter fatal_signal_pending done = iter->pos - iocb->ki_pos // done = 2M ext4_handle_inode_extension ext4_update_inode_size // inode size = 2M fsck reports: Inode 13, i_size is 2097152, should be 4194304. Fix? Fix the problem by truncating extents if the written length is smaller than expected.(CVE-2024-50015)
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Avoid overflow assignment in link_dp_cts sampling_rate is an uint8_t but is assigned an unsigned int, and thus it can overflow. As a result, sampling_rate is changed to uint32_t. Similarly, LINK_QUAL_PATTERN_SET has a size of 2 bits, and it should only be assigned to a value less or equal than 4. This fixes 2 INTEGER_OVERFLOW issues reported by Coverity.(CVE-2024-50016)
In the Linux kernel, the following vulnerability has been resolved: thermal: core: Reference count the zone in thermal_zone_get_by_id() There are places in the thermal netlink code where nothing prevents the thermal zone object from going away while being accessed after it has been returned by thermal_zone_get_by_id(). To address this, make thermal_zone_get_by_id() get a reference on the thermal zone device object to be returned with the help of get_device(), under thermal_list_lock, and adjust all of its callers to this change with the help of the cleanup.h infrastructure.(CVE-2024-50028)
In the Linux kernel, the following vulnerability has been resolved: slip: make slhc_remember() more robust against malicious packets syzbot found that slhc_remember() was missing checks against malicious packets [1]. slhc_remember() only checked the size of the packet was at least 20, which is not good enough. We need to make sure the packet includes the IPv4 and TCP header that are supposed to be carried. Add iph and th pointers to make the code more readable. [1] BUG: KMSAN: uninit-value in slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666 slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666 ppp_receive_nonmp_frame+0xe45/0x35e0 drivers/net/ppp/ppp_generic.c:2455 ppp_receive_frame drivers/net/ppp/ppp_generic.c:2372 [inline] ppp_do_recv+0x65f/0x40d0 drivers/net/ppp/ppp_generic.c:2212 ppp_input+0x7dc/0xe60 drivers/net/ppp/ppp_generic.c:2327 pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379 sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113 __release_sock+0x1da/0x330 net/core/sock.c:3072 release_sock+0x6b/0x250 net/core/sock.c:3626 pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 _syssendmsg+0x903/0xb60 net/socket.c:2602 _sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was created at: slab_post_alloc_hook mm/slub.c:4091 [inline] slab_alloc_node mm/slub.c:4134 [inline] kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4186 kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587 __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678 alloc_skb include/linux/skbuff.h:1322 [inline] sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732 pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 _syssendmsg+0x903/0xb60 net/socket.c:2602 _sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f CPU: 0 UID: 0 PID: 5460 Comm: syz.2.33 Not tainted 6.12.0-rc2-syzkaller-00006-g87d6aab2389e #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50033)
In the Linux kernel, the following vulnerability has been resolved: ppp: fix ppp_async_encode() illegal access syzbot reported an issue in ppp_async_encode() [1] In this case, pppoe_sendmsg() is called with a zero size. Then ppp_async_encode() is called with an empty skb. BUG: KMSAN: uninit-value in ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline] BUG: KMSAN: uninit-value in ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675 ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline] ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675 ppp_async_send+0x130/0x1b0 drivers/net/ppp/ppp_async.c:634 ppp_channel_bridge_input drivers/net/ppp/ppp_generic.c:2280 [inline] ppp_input+0x1f1/0xe60 drivers/net/ppp/ppp_generic.c:2304 pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379 sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113 __release_sock+0x1da/0x330 net/core/sock.c:3072 release_sock+0x6b/0x250 net/core/sock.c:3626 pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 _syssendmsg+0x903/0xb60 net/socket.c:2602 _sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was created at: slab_post_alloc_hook mm/slub.c:4092 [inline] slab_alloc_node mm/slub.c:4135 [inline] kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4187 kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587 __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678 alloc_skb include/linux/skbuff.h:1322 [inline] sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732 pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 _syssendmsg+0x903/0xb60 net/socket.c:2602 _sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f CPU: 1 UID: 0 PID: 5411 Comm: syz.1.14 Not tainted 6.12.0-rc1-syzkaller-00165-g360c1f1f24c6 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50035)
In the Linux kernel, the following vulnerability has been resolved: igb: Do not bring the device up after non-fatal error Commit 004d25060c78 ("igb: Fix igb_down hung on surprise removal") changed igb_io_error_detected() to ignore non-fatal pcie errors in order to avoid hung task that can happen when igb_down() is called multiple times. This caused an issue when processing transient non-fatal errors. igb_io_resume(), which is called after igb_io_error_detected(), assumes that device is brought down by igb_io_error_detected() if the interface is up. This resulted in panic with stacktrace below. [ T3256] igb 0000:09:00.0 haeth0: igb: haeth0 NIC Link is Down [ T292] pcieport 0000:00:1c.5: AER: Uncorrected (Non-Fatal) error received: 0000:09:00.0 [ T292] igb 0000:09:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [ T292] igb 0000:09:00.0: device [8086:1537] error status/mask=00004000/00000000 [ T292] igb 0000:09:00.0: [14] CmpltTO [ 200.105524,009][ T292] igb 0000:09:00.0: AER: TLP Header: 00000000 00000000 00000000 00000000 [ T292] pcieport 0000:00:1c.5: AER: broadcast error_detected message [ T292] igb 0000:09:00.0: Non-correctable non-fatal error reported. [ T292] pcieport 0000:00:1c.5: AER: broadcast mmio_enabled message [ T292] pcieport 0000:00:1c.5: AER: broadcast resume message [ T292] ------------[ cut here ]------------ [ T292] kernel BUG at net/core/dev.c:6539! [ T292] invalid opcode: 0000 [#1] PREEMPT SMP [ T292] RIP: 0010:napi_enable+0x37/0x40 [ T292] Call Trace: [ T292] <TASK> [ T292] ? die+0x33/0x90 [ T292] ? do_trap+0xdc/0x110 [ T292] ? napi_enable+0x37/0x40 [ T292] ? do_error_trap+0x70/0xb0 [ T292] ? napi_enable+0x37/0x40 [ T292] ? napi_enable+0x37/0x40 [ T292] ? exc_invalid_op+0x4e/0x70 [ T292] ? napi_enable+0x37/0x40 [ T292] ? asm_exc_invalid_op+0x16/0x20 [ T292] ? napi_enable+0x37/0x40 [ T292] igb_up+0x41/0x150 [ T292] igb_io_resume+0x25/0x70 [ T292] report_resume+0x54/0x70 [ T292] ? report_frozen_detected+0x20/0x20 [ T292] pci_walk_bus+0x6c/0x90 [ T292] ? aer_print_port_info+0xa0/0xa0 [ T292] pcie_do_recovery+0x22f/0x380 [ T292] aer_process_err_devices+0x110/0x160 [ T292] aer_isr+0x1c1/0x1e0 [ T292] ? disable_irq_nosync+0x10/0x10 [ T292] irq_thread_fn+0x1a/0x60 [ T292] irq_thread+0xe3/0x1a0 [ T292] ? irq_set_affinity_notifier+0x120/0x120 [ T292] ? irq_affinity_notify+0x100/0x100 [ T292] kthread+0xe2/0x110 [ T292] ? kthread_complete_and_exit+0x20/0x20 [ T292] ret_from_fork+0x2d/0x50 [ T292] ? kthread_complete_and_exit+0x20/0x20 [ T292] ret_from_fork_asm+0x11/0x20 [ T292] </TASK> To fix this issue igb_io_resume() checks if the interface is running and the device is not down this means igb_io_error_detected() did not bring the device down and there is no need to bring it up.(CVE-2024-50040)
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix UAF in async decryption Doing an async decryption (large read) crashes with a slab-use-after-free way down in the crypto API. Reproducer: # mount.cifs -o ...,seal,esize=1 //srv/share /mnt # dd if=/mnt/largefile of=/dev/null ... [ 194.196391] ================================================================== [ 194.196844] BUG: KASAN: slab-use-after-free in gf128mul_4k_lle+0xc1/0x110 [ 194.197269] Read of size 8 at addr ffff888112bd0448 by task kworker/u77:2/899 [ 194.197707] [ 194.197818] CPU: 12 UID: 0 PID: 899 Comm: kworker/u77:2 Not tainted 6.11.0-lku-00028-gfca3ca14a17a-dirty #43 [ 194.198400] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.2-3-gd478f380-prebuilt.qemu.org 04/01/2014 [ 194.199046] Workqueue: smb3decryptd smb2_decrypt_offload [cifs] [ 194.200032] Call Trace: [ 194.200191] <TASK> [ 194.200327] dump_stack_lvl+0x4e/0x70 [ 194.200558] ? gf128mul_4k_lle+0xc1/0x110 [ 194.200809] print_report+0x174/0x505 [ 194.201040] ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [ 194.201352] ? srso_return_thunk+0x5/0x5f [ 194.201604] ? __virt_addr_valid+0xdf/0x1c0 [ 194.201868] ? gf128mul_4k_lle+0xc1/0x110 [ 194.202128] kasan_report+0xc8/0x150 [ 194.202361] ? gf128mul_4k_lle+0xc1/0x110 [ 194.202616] gf128mul_4k_lle+0xc1/0x110 [ 194.202863] ghash_update+0x184/0x210 [ 194.203103] shash_ahash_update+0x184/0x2a0 [ 194.203377] ? __pfx_shash_ahash_update+0x10/0x10 [ 194.203651] ? srso_return_thunk+0x5/0x5f [ 194.203877] ? crypto_gcm_init_common+0x1ba/0x340 [ 194.204142] gcm_hash_assoc_remain_continue+0x10a/0x140 [ 194.204434] crypt_message+0xec1/0x10a0 [cifs] [ 194.206489] ? __pfx_crypt_message+0x10/0x10 [cifs] [ 194.208507] ? srso_return_thunk+0x5/0x5f [ 194.209205] ? srso_return_thunk+0x5/0x5f [ 194.209925] ? srso_return_thunk+0x5/0x5f [ 194.210443] ? srso_return_thunk+0x5/0x5f [ 194.211037] decrypt_raw_data+0x15f/0x250 [cifs] [ 194.212906] ? __pfx_decrypt_raw_data+0x10/0x10 [cifs] [ 194.214670] ? srso_return_thunk+0x5/0x5f [ 194.215193] smb2_decrypt_offload+0x12a/0x6c0 [cifs] This is because TFM is being used in parallel. Fix this by allocating a new AEAD TFM for async decryption, but keep the existing one for synchronous READ cases (similar to what is done in smb3_calc_signature()). Also remove the calls to aead_request_set_callback() and crypto_wait_req() since it's always going to be a synchronous operation.(CVE-2024-50047)
In the Linux kernel, the following vulnerability has been resolved: serial: protect uart_port_dtr_rts() in uart_shutdown() too Commit af224ca2df29 (serial: core: Prevent unsafe uart port access, part 3) added few uport == NULL checks. It added one to uart_shutdown(), so the commit assumes, uport can be NULL in there. But right after that protection, there is an unprotected "uart_port_dtr_rts(uport, false);" call. That is invoked only if HUPCL is set, so I assume that is the reason why we do not see lots of these reports. Or it cannot be NULL at this point at all for some reason :P. Until the above is investigated, stay on the safe side and move this dereference to the if too. I got this inconsistency from Coverity under CID 1585130. Thanks.(CVE-2024-50058)
In the Linux kernel, the following vulnerability has been resolved: ntb: ntb_hw_switchtec: Fix use after free vulnerability in switchtec_ntb_remove due to race condition In the switchtec_ntb_add function, it can call switchtec_ntb_init_sndev function, then &sndev->check_link_status_work is bound with check_link_status_work. switchtec_ntb_link_notification may be called to start the work. If we remove the module which will call switchtec_ntb_remove to make cleanup, it will free sndev through kfree(sndev), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows: CPU0 CPU1 | check_link_status_work switchtec_ntb_remove | kfree(sndev); | | if (sndev->link_force_down) | // use sndev Fix it by ensuring that the work is canceled before proceeding with the cleanup in switchtec_ntb_remove.(CVE-2024-50059)
In the Linux kernel, the following vulnerability has been resolved: io_uring: check if we need to reschedule during overflow flush In terms of normal application usage, this list will always be empty. And if an application does overflow a bit, it'll have a few entries. However, nothing obviously prevents syzbot from running a test case that generates a ton of overflow entries, and then flushing them can take quite a while. Check for needing to reschedule while flushing, and drop our locks and do so if necessary. There's no state to maintain here as overflows always prune from head-of-list, hence it's fine to drop and reacquire the locks at the end of the loop.(CVE-2024-50060)
In the Linux kernel, the following vulnerability has been resolved: bpf: Prevent tail call between progs attached to different hooks bpf progs can be attached to kernel functions, and the attached functions can take different parameters or return different return values. If prog attached to one kernel function tail calls prog attached to another kernel function, the ctx access or return value verification could be bypassed. For example, if prog1 is attached to func1 which takes only 1 parameter and prog2 is attached to func2 which takes two parameters. Since verifier assumes the bpf ctx passed to prog2 is constructed based on func2's prototype, verifier allows prog2 to access the second parameter from the bpf ctx passed to it. The problem is that verifier does not prevent prog1 from passing its bpf ctx to prog2 via tail call. In this case, the bpf ctx passed to prog2 is constructed from func1 instead of func2, that is, the assumption for ctx access verification is bypassed. Another example, if BPF LSM prog1 is attached to hook file_alloc_security, and BPF LSM prog2 is attached to hook bpf_lsm_audit_rule_known. Verifier knows the return value rules for these two hooks, e.g. it is legal for bpf_lsm_audit_rule_known to return positive number 1, and it is illegal for file_alloc_security to return positive number. So verifier allows prog2 to return positive number 1, but does not allow prog1 to return positive number. The problem is that verifier does not prevent prog1 from calling prog2 via tail call. In this case, prog2's return value 1 will be used as the return value for prog1's hook file_alloc_security. That is, the return value rule is bypassed. This patch adds restriction for tail call to prevent such bypasses.(CVE-2024-50063)
In the Linux kernel, the following vulnerability has been resolved: zram: free secondary algorithms names We need to kfree() secondary algorithms names when reset zram device that had multi-streams, otherwise we leak memory. [senozhatsky@chromium.org: kfree(NULL) is legal] Link: https://lkml.kernel.org/r/20240917013021.868769-1-senozhatsky@chromium.org(CVE-2024-50064)
In the Linux kernel, the following vulnerability has been resolved: uprobe: avoid out-of-bounds memory access of fetching args Uprobe needs to fetch args into a percpu buffer, and then copy to ring buffer to avoid non-atomic context problem. Sometimes user-space strings, arrays can be very large, but the size of percpu buffer is only page size. And store_trace_args() won't check whether these data exceeds a single page or not, caused out-of-bounds memory access. It could be reproduced by following steps: 1. build kernel with CONFIG_KASAN enabled 2. save follow program as test.c \#include <stdio.h> \#include <stdlib.h> \#include <string.h> // If string length large than MAX_STRING_SIZE, the fetch_store_strlen() // will return 0, cause __get_data_size() return shorter size, and // store_trace_args() will not trigger out-of-bounds access. // So make string length less than 4096. \#define STRLEN 4093 void generate_string(char *str, int n) { int i; for (i = 0; i < n; ++i) { char c = i % 26 + 'a'; str[i] = c; } str[n-1] = '\0'; } void print_string(char *str) { printf("%s\n", str); } int main() { char tmp[STRLEN]; generate_string(tmp, STRLEN); print_string(tmp); return 0; } 3. compile program gcc -o test test.c 4. get the offset of print_string() objdump -t test | grep -w print_string 0000000000401199 g F .text 000000000000001b print_string 5. configure uprobe with offset 0x1199 off=0x1199 cd /sys/kernel/debug/tracing/ echo "p /root/test:${off} arg1=+0(%di):ustring arg2=\$comm arg3=+0(%di):ustring" > uprobe_events echo 1 > events/uprobes/enable echo 1 > tracing_on 6. run test, and kasan will report error. ================================================================== BUG: KASAN: use-after-free in strncpy_from_user+0x1d6/0x1f0 Write of size 8 at addr ffff88812311c004 by task test/499CPU: 0 UID: 0 PID: 499 Comm: test Not tainted 6.12.0-rc3+ #18 Hardware name: Red Hat KVM, BIOS 1.16.0-4.al8 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x55/0x70 print_address_description.constprop.0+0x27/0x310 kasan_report+0x10f/0x120 ? strncpy_from_user+0x1d6/0x1f0 strncpy_from_user+0x1d6/0x1f0 ? rmqueue.constprop.0+0x70d/0x2ad0 process_fetch_insn+0xb26/0x1470 ? __pfx_process_fetch_insn+0x10/0x10 ? _raw_spin_lock+0x85/0xe0 ? __pfx__raw_spin_lock+0x10/0x10 ? __pte_offset_map+0x1f/0x2d0 ? unwind_next_frame+0xc5f/0x1f80 ? arch_stack_walk+0x68/0xf0 ? is_bpf_text_address+0x23/0x30 ? kernel_text_address.part.0+0xbb/0xd0 ? __kernel_text_address+0x66/0xb0 ? unwind_get_return_address+0x5e/0xa0 ? __pfx_stack_trace_consume_entry+0x10/0x10 ? arch_stack_walk+0xa2/0xf0 ? _raw_spin_lock_irqsave+0x8b/0xf0 ? __pfx__raw_spin_lock_irqsave+0x10/0x10 ? depot_alloc_stack+0x4c/0x1f0 ? _raw_spin_unlock_irqrestore+0xe/0x30 ? stack_depot_save_flags+0x35d/0x4f0 ? kasan_save_stack+0x34/0x50 ? kasan_save_stack+0x24/0x50 ? mutex_lock+0x91/0xe0 ? __pfx_mutex_lock+0x10/0x10 prepare_uprobe_buffer.part.0+0x2cd/0x500 uprobe_dispatcher+0x2c3/0x6a0 ? __pfx_uprobe_dispatcher+0x10/0x10 ? __kasan_slab_alloc+0x4d/0x90 handler_chain+0xdd/0x3e0 handle_swbp+0x26e/0x3d0 ? __pfx_handle_swbp+0x10/0x10 ? uprobe_pre_sstep_notifier+0x151/0x1b0 irqentry_exit_to_user_mode+0xe2/0x1b0 asm_exc_int3+0x39/0x40 RIP: 0033:0x401199 Code: 01 c2 0f b6 45 fb 88 02 83 45 fc 01 8b 45 fc 3b 45 e4 7c b7 8b 45 e4 48 98 48 8d 50 ff 48 8b 45 e8 48 01 d0 ce RSP: 002b:00007ffdf00576a8 EFLAGS: 00000206 RAX: 00007ffdf00576b0 RBX: 0000000000000000 RCX: 0000000000000ff2 RDX: 0000000000000ffc RSI: 0000000000000ffd RDI: 00007ffdf00576b0 RBP: 00007ffdf00586b0 R08: 00007feb2f9c0d20 R09: 00007feb2f9c0d20 R10: 0000000000000001 R11: 0000000000000202 R12: 0000000000401040 R13: 00007ffdf0058780 R14: 0000000000000000 R15: 0000000000000000 </TASK> This commit enforces the buffer's maxlen less than a page-size to avoid store_trace_args() out-of-memory access.(CVE-2024-50067)
In the Linux kernel, the following vulnerability has been resolved: parport: Proper fix for array out-of-bounds access The recent fix for array out-of-bounds accesses replaced sprintf() calls blindly with snprintf(). However, since snprintf() returns the would-be-printed size, not the actually output size, the length calculation can still go over the given limit. Use scnprintf() instead of snprintf(), which returns the actually output letters, for addressing the potential out-of-bounds access properly.(CVE-2024-50074)
In the Linux kernel, the following vulnerability has been resolved: tcp: fix mptcp DSS corruption due to large pmtu xmit Syzkaller was able to trigger a DSS corruption: TCP: request_sock_subflow_v4: Possible SYN flooding on port [::]:20002. Sending cookies. ------------[ cut here ]------------ WARNING: CPU: 0 PID: 5227 at net/mptcp/protocol.c:695 __mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695 Modules linked in: CPU: 0 UID: 0 PID: 5227 Comm: syz-executor350 Not tainted 6.11.0-syzkaller-08829-gaf9c191ac2a0 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 RIP: 0010:__mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695 Code: 0f b6 dc 31 ff 89 de e8 b5 dd ea f5 89 d8 48 81 c4 50 01 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 98 da ea f5 90 <0f> 0b 90 e9 47 ff ff ff e8 8a da ea f5 90 0f 0b 90 e9 99 e0 ff ff RSP: 0018:ffffc90000006db8 EFLAGS: 00010246 RAX: ffffffff8ba9df18 RBX: 00000000000055f0 RCX: ffff888030023c00 RDX: 0000000000000100 RSI: 00000000000081e5 RDI: 00000000000055f0 RBP: 1ffff110062bf1ae R08: ffffffff8ba9cf12 R09: 1ffff110062bf1b8 R10: dffffc0000000000 R11: ffffed10062bf1b9 R12: 0000000000000000 R13: dffffc0000000000 R14: 00000000700cec61 R15: 00000000000081e5 FS: 000055556679c380(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020287000 CR3: 0000000077892000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <IRQ> move_skbs_to_msk net/mptcp/protocol.c:811 [inline] mptcp_data_ready+0x29c/0xa90 net/mptcp/protocol.c:854 subflow_data_ready+0x34a/0x920 net/mptcp/subflow.c:1490 tcp_data_queue+0x20fd/0x76c0 net/ipv4/tcp_input.c:5283 tcp_rcv_established+0xfba/0x2020 net/ipv4/tcp_input.c:6237 tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915 tcp_v4_rcv+0x2dc0/0x37f0 net/ipv4/tcp_ipv4.c:2350 ip_protocol_deliver_rcu+0x22e/0x440 net/ipv4/ip_input.c:205 ip_local_deliver_finish+0x341/0x5f0 net/ipv4/ip_input.c:233 NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314 NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314 __netif_receive_skb_one_core net/core/dev.c:5662 [inline] __netif_receive_skb+0x2bf/0x650 net/core/dev.c:5775 process_backlog+0x662/0x15b0 net/core/dev.c:6107 __napi_poll+0xcb/0x490 net/core/dev.c:6771 napi_poll net/core/dev.c:6840 [inline] net_rx_action+0x89b/0x1240 net/core/dev.c:6962 handle_softirqs+0x2c5/0x980 kernel/softirq.c:554 do_softirq+0x11b/0x1e0 kernel/softirq.c:455 </IRQ> <TASK> __local_bh_enable_ip+0x1bb/0x200 kernel/softirq.c:382 local_bh_enable include/linux/bottom_half.h:33 [inline] rcu_read_unlock_bh include/linux/rcupdate.h:919 [inline] __dev_queue_xmit+0x1764/0x3e80 net/core/dev.c:4451 dev_queue_xmit include/linux/netdevice.h:3094 [inline] neigh_hh_output include/net/neighbour.h:526 [inline] neigh_output include/net/neighbour.h:540 [inline] ip_finish_output2+0xd41/0x1390 net/ipv4/ip_output.c:236 ip_local_out net/ipv4/ip_output.c:130 [inline] __ip_queue_xmit+0x118c/0x1b80 net/ipv4/ip_output.c:536 __tcp_transmit_skb+0x2544/0x3b30 net/ipv4/tcp_output.c:1466 tcp_transmit_skb net/ipv4/tcp_output.c:1484 [inline] tcp_mtu_probe net/ipv4/tcp_output.c:2547 [inline] tcp_write_xmit+0x641d/0x6bf0 net/ipv4/tcp_output.c:2752 __tcp_push_pending_frames+0x9b/0x360 net/ipv4/tcp_output.c:3015 tcp_push_pending_frames include/net/tcp.h:2107 [inline] tcp_data_snd_check net/ipv4/tcp_input.c:5714 [inline] tcp_rcv_established+0x1026/0x2020 net/ipv4/tcp_input.c:6239 tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915 sk_backlog_rcv include/net/sock.h:1113 [inline] __release_sock+0x214/0x350 net/core/sock.c:3072 release_sock+0x61/0x1f0 net/core/sock.c:3626 mptcp_push_ ---truncated---(CVE-2024-50083)
| URL | Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"bpftool-5.10.0-235.0.0.134.oe2203sp4.aarch64.rpm",
"bpftool-debuginfo-5.10.0-235.0.0.134.oe2203sp4.aarch64.rpm",
"kernel-5.10.0-235.0.0.134.oe2203sp4.aarch64.rpm",
"kernel-debuginfo-5.10.0-235.0.0.134.oe2203sp4.aarch64.rpm",
"kernel-debugsource-5.10.0-235.0.0.134.oe2203sp4.aarch64.rpm",
"kernel-devel-5.10.0-235.0.0.134.oe2203sp4.aarch64.rpm",
"kernel-headers-5.10.0-235.0.0.134.oe2203sp4.aarch64.rpm",
"kernel-source-5.10.0-235.0.0.134.oe2203sp4.aarch64.rpm",
"kernel-tools-5.10.0-235.0.0.134.oe2203sp4.aarch64.rpm",
"kernel-tools-debuginfo-5.10.0-235.0.0.134.oe2203sp4.aarch64.rpm",
"kernel-tools-devel-5.10.0-235.0.0.134.oe2203sp4.aarch64.rpm",
"perf-5.10.0-235.0.0.134.oe2203sp4.aarch64.rpm",
"perf-debuginfo-5.10.0-235.0.0.134.oe2203sp4.aarch64.rpm",
"python3-perf-5.10.0-235.0.0.134.oe2203sp4.aarch64.rpm",
"python3-perf-debuginfo-5.10.0-235.0.0.134.oe2203sp4.aarch64.rpm"
],
"src": [
"kernel-5.10.0-235.0.0.134.oe2203sp4.src.rpm"
],
"x86_64": [
"bpftool-5.10.0-235.0.0.134.oe2203sp4.x86_64.rpm",
"bpftool-debuginfo-5.10.0-235.0.0.134.oe2203sp4.x86_64.rpm",
"kernel-5.10.0-235.0.0.134.oe2203sp4.x86_64.rpm",
"kernel-debuginfo-5.10.0-235.0.0.134.oe2203sp4.x86_64.rpm",
"kernel-debugsource-5.10.0-235.0.0.134.oe2203sp4.x86_64.rpm",
"kernel-devel-5.10.0-235.0.0.134.oe2203sp4.x86_64.rpm",
"kernel-headers-5.10.0-235.0.0.134.oe2203sp4.x86_64.rpm",
"kernel-source-5.10.0-235.0.0.134.oe2203sp4.x86_64.rpm",
"kernel-tools-5.10.0-235.0.0.134.oe2203sp4.x86_64.rpm",
"kernel-tools-debuginfo-5.10.0-235.0.0.134.oe2203sp4.x86_64.rpm",
"kernel-tools-devel-5.10.0-235.0.0.134.oe2203sp4.x86_64.rpm",
"perf-5.10.0-235.0.0.134.oe2203sp4.x86_64.rpm",
"perf-debuginfo-5.10.0-235.0.0.134.oe2203sp4.x86_64.rpm",
"python3-perf-5.10.0-235.0.0.134.oe2203sp4.x86_64.rpm",
"python3-perf-debuginfo-5.10.0-235.0.0.134.oe2203sp4.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:22.03-LTS-SP4",
"name": "kernel",
"purl": "pkg:rpm/openEuler/kernel\u0026distro=openEuler-22.03-LTS-SP4"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.10.0-235.0.0.134.oe2203sp4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: net: mdio: fix unbalanced fwnode reference count in mdio_device_release() There is warning report about of_node refcount leak while probing mdio device: OF: ERROR: memory leak, expected refcount 1 instead of 2, of_node_get()/of_node_put() unbalanced - destroy cset entry: attach overlay node /spi/soc@0/mdio@710700c0/ethernet@4 In of_mdiobus_register_device(), we increase fwnode refcount by fwnode_handle_get() before associating the of_node with mdio device, but it has never been decreased in normal path. Since that, in mdio_device_release(), it needs to call fwnode_handle_put() in addition instead of calling kfree() directly. After above, just calling mdio_device_free() in the error handle path of of_mdiobus_register_device() is enough to keep the refcount balanced.(CVE-2022-48961)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: gpiolib: fix memory leak in gpiochip_setup_dev() Here is a backtrace report about memory leak detected in gpiochip_setup_dev(): unreferenced object 0xffff88810b406400 (size 512): comm \u0026quot;python3\u0026quot;, pid 1682, jiffies 4295346908 (age 24.090s) backtrace: kmalloc_trace device_add device_private_init at drivers/base/core.c:3361 (inlined by) device_add at drivers/base/core.c:3411 cdev_device_add gpiolib_cdev_register gpiochip_setup_dev gpiochip_add_data_with_key gcdev_register() \u0026amp; gcdev_unregister() would call device_add() \u0026amp; device_del() (no matter CONFIG_GPIO_CDEV is enabled or not) to register/unregister device. However, if device_add() succeeds, some resource (like struct device_private allocated by device_private_init()) is not released by device_del(). Therefore, after device_add() succeeds by gcdev_register(), it needs to call put_device() to release resource in the error handle path. Here we move forward the register of release function, and let it release every piece of resource by put_device() instead of kfree(). While at it, fix another subtle issue, i.e. when gc-\u0026gt;ngpio is equal to 0, we still call kcalloc() and, in case of further error, kfree() on the ZERO_PTR pointer, which is not NULL. It\u0026apos;s not a bug per se, but rather waste of the resources and potentially wrong expectation about contents of the gdev-\u0026gt;descs variable.(CVE-2022-48975)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: riscv: Sync efi page table\u0026apos;s kernel mappings before switching The EFI page table is initially created as a copy of the kernel page table. With VMAP_STACK enabled, kernel stacks are allocated in the vmalloc area: if the stack is allocated in a new PGD (one that was not present at the moment of the efi page table creation or not synced in a previous vmalloc fault), the kernel will take a trap when switching to the efi page table when the vmalloc kernel stack is accessed, resulting in a kernel panic. Fix that by updating the efi kernel mappings before switching to the efi page table.(CVE-2022-49004)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmemcg_write_event_control(): fix a user-triggerable oops\r\n\r\nwe are *not* guaranteed that anything past the terminating NUL\nis mapped (let alone initialized with anything sane).(CVE-2024-45021)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ngtp: fix a potential NULL pointer dereference\r\n\r\nWhen sockfd_lookup() fails, gtp_encap_enable_socket() returns a\nNULL pointer, but its callers only check for error pointers thus miss\nthe NULL pointer case.\r\n\r\nFix it by returning an error pointer with the error code carried from\nsockfd_lookup().\r\n\r\n(I found this bug during code inspection.)(CVE-2024-46677)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Check BIOS images before it is used\r\n\r\nBIOS images may fail to load and null checks are added before they are\nused.\r\n\r\nThis fixes 6 NULL_RETURNS issues reported by Coverity.(CVE-2024-46809)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsmack: tcp: ipv4, fix incorrect labeling\r\n\r\nCurrently, Smack mirrors the label of incoming tcp/ipv4 connections:\nwhen a label \u0026apos;foo\u0026apos; connects to a label \u0026apos;bar\u0026apos; with tcp/ipv4,\n\u0026apos;foo\u0026apos; always gets \u0026apos;foo\u0026apos; in returned ipv4 packets. So,\n1) returned packets are incorrectly labeled (\u0026apos;foo\u0026apos; instead of \u0026apos;bar\u0026apos;)\n2) \u0026apos;bar\u0026apos; can write to \u0026apos;foo\u0026apos; without being authorized to write.\r\n\r\nHere is a scenario how to see this:\r\n\r\n* Take two machines, let\u0026apos;s call them C and S,\n with active Smack in the default state\n (no settings, no rules, no labeled hosts, only builtin labels)\r\n\r\n* At S, add Smack rule \u0026apos;foo bar w\u0026apos;\n (labels \u0026apos;foo\u0026apos; and \u0026apos;bar\u0026apos; are instantiated at S at this moment)\r\n\r\n* At S, at label \u0026apos;bar\u0026apos;, launch a program\n that listens for incoming tcp/ipv4 connections\r\n\r\n* From C, at label \u0026apos;foo\u0026apos;, connect to the listener at S.\n (label \u0026apos;foo\u0026apos; is instantiated at C at this moment)\n Connection succeedes and works.\r\n\r\n* Send some data in both directions.\n* Collect network traffic of this connection.\r\n\r\nAll packets in both directions are labeled with the CIPSO\nof the label \u0026apos;foo\u0026apos;. Hence, label \u0026apos;bar\u0026apos; writes to \u0026apos;foo\u0026apos; without\nbeing authorized, and even without ever being known at C.\r\n\r\nIf anybody cares: exactly the same happens with DCCP.\r\n\r\nThis behavior 1st manifested in release 2.6.29.4 (see Fixes below)\nand it looks unintentional. At least, no explanation was provided.\r\n\r\nI changed returned packes label into the \u0026apos;bar\u0026apos;,\nto bring it into line with the Smack documentation claims.(CVE-2024-47659)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfsnotify: clear PARENT_WATCHED flags lazily\r\n\r\nIn some setups directories can have many (usually negative) dentries.\nHence __fsnotify_update_child_dentry_flags() function can take a\nsignificant amount of time. Since the bulk of this function happens\nunder inode-\u0026gt;i_lock this causes a significant contention on the lock\nwhen we remove the watch from the directory as the\n__fsnotify_update_child_dentry_flags() call from fsnotify_recalc_mask()\nraces with __fsnotify_update_child_dentry_flags() calls from\n__fsnotify_parent() happening on children. This can lead upto softlockup\nreports reported by users.\r\n\r\nFix the problem by calling fsnotify_update_children_dentry_flags() to\nset PARENT_WATCHED flags only when parent starts watching children.\r\n\r\nWhen parent stops watching children, clear false positive PARENT_WATCHED\nflags lazily in __fsnotify_parent() for each accessed child.(CVE-2024-47660)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nlib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc()\r\n\r\nIf we need to increase the tree depth, allocate a new node, and then\nrace with another thread that increased the tree depth before us, we\u0026apos;ll\nstill have a preallocated node that might be used later.\r\n\r\nIf we then use that node for a new non-root node, it\u0026apos;ll still have a\npointer to the old root instead of being zeroed - fix this by zeroing it\nin the cmpxchg failure path.(CVE-2024-47668)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: iwlwifi: mvm: pause TCM when the firmware is stopped\r\n\r\nNot doing so will make us send a host command to the transport while the\nfirmware is not alive, which will trigger a WARNING.\r\n\r\nbad state = 0\nWARNING: CPU: 2 PID: 17434 at drivers/net/wireless/intel/iwlwifi/iwl-trans.c:115 iwl_trans_send_cmd+0x1cb/0x1e0 [iwlwifi]\nRIP: 0010:iwl_trans_send_cmd+0x1cb/0x1e0 [iwlwifi]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n iwl_mvm_send_cmd+0x40/0xc0 [iwlmvm]\n iwl_mvm_config_scan+0x198/0x260 [iwlmvm]\n iwl_mvm_recalc_tcm+0x730/0x11d0 [iwlmvm]\n iwl_mvm_tcm_work+0x1d/0x30 [iwlmvm]\n process_one_work+0x29e/0x640\n worker_thread+0x2df/0x690\n ? rescuer_thread+0x540/0x540\n kthread+0x192/0x1e0\n ? set_kthread_struct+0x90/0x90\n ret_from_fork+0x22/0x30(CVE-2024-47673)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: f2fs: get rid of online repaire on corrupted directory syzbot reports a f2fs bug as below: kernel BUG at fs/f2fs/inode.c:896! RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896 Call Trace: evict+0x532/0x950 fs/inode.c:704 dispose_list fs/inode.c:747 [inline] evict_inodes+0x5f9/0x690 fs/inode.c:797 generic_shutdown_super+0x9d/0x2d0 fs/super.c:627 kill_block_super+0x44/0x90 fs/super.c:1696 kill_f2fs_super+0x344/0x690 fs/f2fs/super.c:4898 deactivate_locked_super+0xc4/0x130 fs/super.c:473 cleanup_mnt+0x41f/0x4b0 fs/namespace.c:1373 task_work_run+0x24f/0x310 kernel/task_work.c:228 ptrace_notify+0x2d2/0x380 kernel/signal.c:2402 ptrace_report_syscall include/linux/ptrace.h:415 [inline] ptrace_report_syscall_exit include/linux/ptrace.h:477 [inline] syscall_exit_work+0xc6/0x190 kernel/entry/common.c:173 syscall_exit_to_user_mode_prepare kernel/entry/common.c:200 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:205 [inline] syscall_exit_to_user_mode+0x279/0x370 kernel/entry/common.c:218 do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896 Online repaire on corrupted directory in f2fs_lookup() can generate dirty data/meta while racing w/ readonly remount, it may leave dirty inode after filesystem becomes readonly, however, checkpoint() will skips flushing dirty inode in a state of readonly mode, result in above panic. Let\u0026apos;s get rid of online repaire in f2fs_lookup(), and leave the work to fsck.f2fs.(CVE-2024-47690)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid use-after-free in f2fs_stop_gc_thread() syzbot reports a f2fs bug as below: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114 print_report+0xe8/0x550 mm/kasan/report.c:491 kasan_report+0x143/0x180 mm/kasan/report.c:601 kasan_check_range+0x282/0x290 mm/kasan/generic.c:189 instrument_atomic_read_write include/linux/instrumented.h:96 [inline] atomic_fetch_add_relaxed include/linux/atomic/atomic-instrumented.h:252 [inline] __refcount_add include/linux/refcount.h:184 [inline] __refcount_inc include/linux/refcount.h:241 [inline] refcount_inc include/linux/refcount.h:258 [inline] get_task_struct include/linux/sched/task.h:118 [inline] kthread_stop+0xca/0x630 kernel/kthread.c:704 f2fs_stop_gc_thread+0x65/0xb0 fs/f2fs/gc.c:210 f2fs_do_shutdown+0x192/0x540 fs/f2fs/file.c:2283 f2fs_ioc_shutdown fs/f2fs/file.c:2325 [inline] __f2fs_ioctl+0x443a/0xbe60 fs/f2fs/file.c:4325 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f The root cause is below race condition, it may cause use-after-free issue in sbi-\u0026gt;gc_th pointer. - remount - f2fs_remount - f2fs_stop_gc_thread - kfree(gc_th) - f2fs_ioc_shutdown - f2fs_do_shutdown - f2fs_stop_gc_thread - kthread_stop(gc_th-\u0026gt;f2fs_gc_task) : sbi-\u0026gt;gc_thread = NULL; We will call f2fs_do_shutdown() in two paths: - for f2fs_ioc_shutdown() path, we should grab sb-\u0026gt;s_umount semaphore for fixing. - for f2fs_shutdown() path, it\u0026apos;s safe since caller has already grabbed sb-\u0026gt;s_umount semaphore.(CVE-2024-47691)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: IB/core: Fix ib_cache_setup_one error flow cleanup When ib_cache_update return an error, we exit ib_cache_setup_one instantly with no proper cleanup, even though before this we had already successfully done gid_table_setup_one, that results in the kernel WARN below. Do proper cleanup using gid_table_cleanup_one before returning the err in order to fix the issue. WARNING: CPU: 4 PID: 922 at drivers/infiniband/core/cache.c:806 gid_table_release_one+0x181/0x1a0 Modules linked in: CPU: 4 UID: 0 PID: 922 Comm: c_repro Not tainted 6.11.0-rc1+ #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:gid_table_release_one+0x181/0x1a0 Code: 44 8b 38 75 0c e8 2f cb 34 ff 4d 8b b5 28 05 00 00 e8 23 cb 34 ff 44 89 f9 89 da 4c 89 f6 48 c7 c7 d0 58 14 83 e8 4f de 21 ff \u0026lt;0f\u0026gt; 0b 4c 8b 75 30 e9 54 ff ff ff 48 8 3 c4 10 5b 5d 41 5c 41 5d 41 RSP: 0018:ffffc90002b835b0 EFLAGS: 00010286 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff811c8527 RDX: 0000000000000000 RSI: ffffffff811c8534 RDI: 0000000000000001 RBP: ffff8881011b3d00 R08: ffff88810b3abe00 R09: 205d303839303631 R10: 666572207972746e R11: 72746e6520444947 R12: 0000000000000001 R13: ffff888106390000 R14: ffff8881011f2110 R15: 0000000000000001 FS: 00007fecc3b70800(0000) GS:ffff88813bd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020000340 CR3: 000000010435a001 CR4: 00000000003706b0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: \u0026lt;TASK\u0026gt; ? show_regs+0x94/0xa0 ? __warn+0x9e/0x1c0 ? gid_table_release_one+0x181/0x1a0 ? report_bug+0x1f9/0x340 ? gid_table_release_one+0x181/0x1a0 ? handle_bug+0xa2/0x110 ? exc_invalid_op+0x31/0xa0 ? asm_exc_invalid_op+0x16/0x20 ? __warn_printk+0xc7/0x180 ? __warn_printk+0xd4/0x180 ? gid_table_release_one+0x181/0x1a0 ib_device_release+0x71/0xe0 ? __pfx_ib_device_release+0x10/0x10 device_release+0x44/0xd0 kobject_put+0x135/0x3d0 put_device+0x20/0x30 rxe_net_add+0x7d/0xa0 rxe_newlink+0xd7/0x190 nldev_newlink+0x1b0/0x2a0 ? __pfx_nldev_newlink+0x10/0x10 rdma_nl_rcv_msg+0x1ad/0x2e0 rdma_nl_rcv_skb.constprop.0+0x176/0x210 netlink_unicast+0x2de/0x400 netlink_sendmsg+0x306/0x660 __sock_sendmsg+0x110/0x120 ____sys_sendmsg+0x30e/0x390 ___sys_sendmsg+0x9b/0xf0 ? kstrtouint+0x6e/0xa0 ? kstrtouint_from_user+0x7c/0xb0 ? get_pid_task+0xb0/0xd0 ? proc_fail_nth_write+0x5b/0x140 ? __fget_light+0x9a/0x200 ? preempt_count_add+0x47/0xa0 __sys_sendmsg+0x61/0xd0 do_syscall_64+0x50/0x110 entry_SYSCALL_64_after_hwframe+0x76/0x7e(CVE-2024-47693)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency In the commit aee2424246f9 (\u0026quot;RDMA/iwcm: Fix a use-after-free related to destroying CM IDs\u0026quot;), the function flush_workqueue is invoked to flush the work queue iwcm_wq. But at that time, the work queue iwcm_wq was created via the function alloc_ordered_workqueue without the flag WQ_MEM_RECLAIM. Because the current process is trying to flush the whole iwcm_wq, if iwcm_wq doesn\u0026apos;t have the flag WQ_MEM_RECLAIM, verify that the current process is not reclaiming memory or running on a workqueue which doesn\u0026apos;t have the flag WQ_MEM_RECLAIM as that can break forward-progress guarantee leading to a deadlock. The call trace is as below: [ 125.350876][ T1430] Call Trace: [ 125.356281][ T1430] \u0026lt;TASK\u0026gt; [ 125.361285][ T1430] ? __warn (kernel/panic.c:693) [ 125.367640][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.375689][ T1430] ? report_bug (lib/bug.c:180 lib/bug.c:219) [ 125.382505][ T1430] ? handle_bug (arch/x86/kernel/traps.c:239) [ 125.388987][ T1430] ? exc_invalid_op (arch/x86/kernel/traps.c:260 (discriminator 1)) [ 125.395831][ T1430] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:621) [ 125.403125][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.410984][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.418764][ T1430] __flush_workqueue (kernel/workqueue.c:3970) [ 125.426021][ T1430] ? __pfx___might_resched (kernel/sched/core.c:10151) [ 125.433431][ T1430] ? destroy_cm_id (drivers/infiniband/core/iwcm.c:375) iw_cm [ 125.441209][ T1430] ? __pfx___flush_workqueue (kernel/workqueue.c:3910) [ 125.473900][ T1430] ? _raw_spin_lock_irqsave (arch/x86/include/asm/atomic.h:107 include/linux/atomic/atomic-arch-fallback.h:2170 include/linux/atomic/atomic-instrumented.h:1302 include/asm-generic/qspinlock.h:111 include/linux/spinlock.h:187 include/linux/spinlock_api_smp.h:111 kernel/locking/spinlock.c:162) [ 125.473909][ T1430] ? __pfx__raw_spin_lock_irqsave (kernel/locking/spinlock.c:161) [ 125.482537][ T1430] _destroy_id (drivers/infiniband/core/cma.c:2044) rdma_cm [ 125.495072][ T1430] nvme_rdma_free_queue (drivers/nvme/host/rdma.c:656 drivers/nvme/host/rdma.c:650) nvme_rdma [ 125.505827][ T1430] nvme_rdma_reset_ctrl_work (drivers/nvme/host/rdma.c:2180) nvme_rdma [ 125.505831][ T1430] process_one_work (kernel/workqueue.c:3231) [ 125.515122][ T1430] worker_thread (kernel/workqueue.c:3306 kernel/workqueue.c:3393) [ 125.515127][ T1430] ? __pfx_worker_thread (kernel/workqueue.c:3339) [ 125.531837][ T1430] kthread (kernel/kthread.c:389) [ 125.539864][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.550628][ T1430] ret_from_fork (arch/x86/kernel/process.c:147) [ 125.558840][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.558844][ T1430] ret_from_fork_asm (arch/x86/entry/entry_64.S:257) [ 125.566487][ T1430] \u0026lt;/TASK\u0026gt; [ 125.566488][ T1430] ---[ end trace 0000000000000000 ]---(CVE-2024-47696)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential null-ptr-deref in nilfs_btree_insert() Patch series \u0026quot;nilfs2: fix potential issues with empty b-tree nodes\u0026quot;. This series addresses three potential issues with empty b-tree nodes that can occur with corrupted filesystem images, including one recently discovered by syzbot. This patch (of 3): If a b-tree is broken on the device, and the b-tree height is greater than 2 (the level of the root node is greater than 1) even if the number of child nodes of the b-tree root is 0, a NULL pointer dereference occurs in nilfs_btree_prepare_insert(), which is called from nilfs_btree_insert(). This is because, when the number of child nodes of the b-tree root is 0, nilfs_btree_do_lookup() does not set the block buffer head in any of path[x].bp_bh, leaving it as the initial value of NULL, but if the level of the b-tree root node is greater than 1, nilfs_btree_get_nonroot_node(), which accesses the buffer memory of path[x].bp_bh, is called. Fix this issue by adding a check to nilfs_btree_root_broken(), which performs sanity checks when reading the root node from the device, to detect this inconsistency. Thanks to Lizhi Xu for trying to solve the bug and clarifying the cause early on.(CVE-2024-47699)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ext4: avoid OOB when system.data xattr changes underneath the filesystem When looking up for an entry in an inlined directory, if e_value_offs is changed underneath the filesystem by some change in the block device, it will lead to an out-of-bounds access that KASAN detects as an UAF. EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none. loop0: detected capacity change from 2048 to 2047 ================================================================== BUG: KASAN: use-after-free in ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500 Read of size 1 at addr ffff88803e91130f by task syz-executor269/5103 CPU: 0 UID: 0 PID: 5103 Comm: syz-executor269 Not tainted 6.11.0-rc4-syzkaller #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Call Trace: \u0026lt;TASK\u0026gt; __dump_stack lib/dump_stack.c:93 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119 print_address_description mm/kasan/report.c:377 [inline] print_report+0x169/0x550 mm/kasan/report.c:488 kasan_report+0x143/0x180 mm/kasan/report.c:601 ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500 ext4_find_inline_entry+0x4be/0x5e0 fs/ext4/inline.c:1697 __ext4_find_entry+0x2b4/0x1b30 fs/ext4/namei.c:1573 ext4_lookup_entry fs/ext4/namei.c:1727 [inline] ext4_lookup+0x15f/0x750 fs/ext4/namei.c:1795 lookup_one_qstr_excl+0x11f/0x260 fs/namei.c:1633 filename_create+0x297/0x540 fs/namei.c:3980 do_symlinkat+0xf9/0x3a0 fs/namei.c:4587 __do_sys_symlinkat fs/namei.c:4610 [inline] __se_sys_symlinkat fs/namei.c:4607 [inline] __x64_sys_symlinkat+0x95/0xb0 fs/namei.c:4607 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f3e73ced469 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 21 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fff4d40c258 EFLAGS: 00000246 ORIG_RAX: 000000000000010a RAX: ffffffffffffffda RBX: 0032656c69662f2e RCX: 00007f3e73ced469 RDX: 0000000020000200 RSI: 00000000ffffff9c RDI: 00000000200001c0 RBP: 0000000000000000 R08: 00007fff4d40c290 R09: 00007fff4d40c290 R10: 0023706f6f6c2f76 R11: 0000000000000246 R12: 00007fff4d40c27c R13: 0000000000000003 R14: 431bde82d7b634db R15: 00007fff4d40c2b0 \u0026lt;/TASK\u0026gt; Calling ext4_xattr_ibody_find right after reading the inode with ext4_get_inode_loc will lead to a check of the validity of the xattrs, avoiding this problem.(CVE-2024-47701)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: bpf, lsm: Add check for BPF LSM return value A bpf prog returning a positive number attached to file_alloc_security hook makes kernel panic. This happens because file system can not filter out the positive number returned by the LSM prog using IS_ERR, and misinterprets this positive number as a file pointer. Given that hook file_alloc_security never returned positive number before the introduction of BPF LSM, and other BPF LSM hooks may encounter similar issues, this patch adds LSM return value check in verifier, to ensure no unexpected value is returned.(CVE-2024-47703)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: block: fix potential invalid pointer dereference in blk_add_partition The blk_add_partition() function initially used a single if-condition (IS_ERR(part)) to check for errors when adding a partition. This was modified to handle the specific case of -ENXIO separately, allowing the function to proceed without logging the error in this case. However, this change unintentionally left a path where md_autodetect_dev() could be called without confirming that part is a valid pointer. This commit separates the error handling logic by splitting the initial if-condition, improving code readability and handling specific error scenarios explicitly. The function now distinguishes the general error case from -ENXIO without altering the existing behavior of md_autodetect_dev() calls.(CVE-2024-47705)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: jfs: fix out-of-bounds in dbNextAG() and diAlloc() In dbNextAG() , there is no check for the case where bmp-\u0026gt;db_numag is greater or same than MAXAG due to a polluted image, which causes an out-of-bounds. Therefore, a bounds check should be added in dbMount(). And in dbNextAG(), a check for the case where agpref is greater than bmp-\u0026gt;db_numag should be added, so an out-of-bounds exception should be prevented. Additionally, a check for the case where agno is greater or same than MAXAG should be added in diAlloc() to prevent out-of-bounds.(CVE-2024-47723)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: f2fs: fix to wait dio completion It should wait all existing dio write IOs before block removal, otherwise, previous direct write IO may overwrite data in the block which may be reused by other inode.(CVE-2024-47726)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: padata: use integer wrap around to prevent deadlock on seq_nr overflow When submitting more than 2^32 padata objects to padata_do_serial, the current sorting implementation incorrectly sorts padata objects with overflowed seq_nr, causing them to be placed before existing objects in the reorder list. This leads to a deadlock in the serialization process as padata_find_next cannot match padata-\u0026gt;seq_nr and pd-\u0026gt;processed because the padata instance with overflowed seq_nr will be selected next. To fix this, we use an unsigned integer wrap around to correctly sort padata objects in scenarios with integer overflow.(CVE-2024-47739)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: firmware_loader: Block path traversal Most firmware names are hardcoded strings, or are constructed from fairly constrained format strings where the dynamic parts are just some hex numbers or such. However, there are a couple codepaths in the kernel where firmware file names contain string components that are passed through from a device or semi-privileged userspace; the ones I could find (not counting interfaces that require root privileges) are: - lpfc_sli4_request_firmware_update() seems to construct the firmware filename from \u0026quot;ModelName\u0026quot;, a string that was previously parsed out of some descriptor (\u0026quot;Vital Product Data\u0026quot;) in lpfc_fill_vpd() - nfp_net_fw_find() seems to construct a firmware filename from a model name coming from nfp_hwinfo_lookup(pf-\u0026gt;hwinfo, \u0026quot;nffw.partno\u0026quot;), which I think parses some descriptor that was read from the device. (But this case likely isn\u0026apos;t exploitable because the format string looks like \u0026quot;netronome/nic_%s\u0026quot;, and there shouldn\u0026apos;t be any *folders* starting with \u0026quot;netronome/nic_\u0026quot;. The previous case was different because there, the \u0026quot;%s\u0026quot; is *at the start* of the format string.) - module_flash_fw_schedule() is reachable from the ETHTOOL_MSG_MODULE_FW_FLASH_ACT netlink command, which is marked as GENL_UNS_ADMIN_PERM (meaning CAP_NET_ADMIN inside a user namespace is enough to pass the privilege check), and takes a userspace-provided firmware name. (But I think to reach this case, you need to have CAP_NET_ADMIN over a network namespace that a special kind of ethernet device is mapped into, so I think this is not a viable attack path in practice.) Fix it by rejecting any firmware names containing \u0026quot;..\u0026quot; path components. For what it\u0026apos;s worth, I went looking and haven\u0026apos;t found any USB device drivers that use the firmware loader dangerously.(CVE-2024-47742)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: vhost_vdpa: assign irq bypass producer token correctly We used to call irq_bypass_unregister_producer() in vhost_vdpa_setup_vq_irq() which is problematic as we don\u0026apos;t know if the token pointer is still valid or not. Actually, we use the eventfd_ctx as the token so the life cycle of the token should be bound to the VHOST_SET_VRING_CALL instead of vhost_vdpa_setup_vq_irq() which could be called by set_status(). Fixing this by setting up irq bypass producer\u0026apos;s token when handling VHOST_SET_VRING_CALL and un-registering the producer before calling vhost_vring_ioctl() to prevent a possible use after free as eventfd could have been released in vhost_vring_ioctl(). And such registering and unregistering will only be done if DRIVER_OK is set.(CVE-2024-47748)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: PCI: keystone: Fix if-statement expression in ks_pcie_quirk() This code accidentally uses \u0026amp;\u0026amp; where || was intended. It potentially results in a NULL dereference. Thus, fix the if-statement expression to use the correct condition. [kwilczynski: commit log](CVE-2024-47756)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: nbd: fix race between timeout and normal completion If request timetout is handled by nbd_requeue_cmd(), normal completion has to be stopped for avoiding to complete this requeued request, other use-after-free can be triggered. Fix the race by clearing NBD_CMD_INFLIGHT in nbd_requeue_cmd(), meantime make sure that cmd-\u0026gt;lock is grabbed for clearing the flag and the requeue.(CVE-2024-49855)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: efistub/tpm: Use ACPI reclaim memory for event log to avoid corruption The TPM event log table is a Linux specific construct, where the data produced by the GetEventLog() boot service is cached in memory, and passed on to the OS using an EFI configuration table. The use of EFI_LOADER_DATA here results in the region being left unreserved in the E820 memory map constructed by the EFI stub, and this is the memory description that is passed on to the incoming kernel by kexec, which is therefore unaware that the region should be reserved. Even though the utility of the TPM2 event log after a kexec is questionable, any corruption might send the parsing code off into the weeds and crash the kernel. So let\u0026apos;s use EFI_ACPI_RECLAIM_MEMORY instead, which is always treated as reserved by the E820 conversion logic.(CVE-2024-49858)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: f2fs: fix to check atomic_file in f2fs ioctl interfaces Some f2fs ioctl interfaces like f2fs_ioc_set_pin_file(), f2fs_move_file_range(), and f2fs_defragment_range() missed to check atomic_write status, which may cause potential race issue, fix it.(CVE-2024-49859)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ACPI: sysfs: validate return type of _STR method Only buffer objects are valid return values of _STR. If something else is returned description_show() will access invalid memory.(CVE-2024-49860)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: powercap: intel_rapl: Fix off by one in get_rpi() The rp-\u0026gt;priv-\u0026gt;rpi array is either rpi_msr or rpi_tpmi which have NR_RAPL_PRIMITIVES number of elements. Thus the \u0026gt; needs to be \u0026gt;= to prevent an off by one access.(CVE-2024-49862)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate When doing cleanup, if flags without OCFS2_BH_READAHEAD, it may trigger NULL pointer dereference in the following ocfs2_set_buffer_uptodate() if bh is NULL.(CVE-2024-49877)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm: omapdrm: Add missing check for alloc_ordered_workqueue As it may return NULL pointer and cause NULL pointer dereference. Add check for the return value of alloc_ordered_workqueue.(CVE-2024-49879)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ext4: update orig_path in ext4_find_extent() In ext4_find_extent(), if the path is not big enough, we free it and set *orig_path to NULL. But after reallocating and successfully initializing the path, we don\u0026apos;t update *orig_path, in which case the caller gets a valid path but a NULL ppath, and this may cause a NULL pointer dereference or a path memory leak. For example: ext4_split_extent path = *ppath = 2000 ext4_find_extent if (depth \u0026gt; path[0].p_maxdepth) kfree(path = 2000); *orig_path = path = NULL; path = kcalloc() = 3000 ext4_split_extent_at(*ppath = NULL) path = *ppath; ex = path[depth].p_ext; // NULL pointer dereference! ================================================================== BUG: kernel NULL pointer dereference, address: 0000000000000010 CPU: 6 UID: 0 PID: 576 Comm: fsstress Not tainted 6.11.0-rc2-dirty #847 RIP: 0010:ext4_split_extent_at+0x6d/0x560 Call Trace: \u0026lt;TASK\u0026gt; ext4_split_extent.isra.0+0xcb/0x1b0 ext4_ext_convert_to_initialized+0x168/0x6c0 ext4_ext_handle_unwritten_extents+0x325/0x4d0 ext4_ext_map_blocks+0x520/0xdb0 ext4_map_blocks+0x2b0/0x690 ext4_iomap_begin+0x20e/0x2c0 [...] ================================================================== Therefore, *orig_path is updated when the extent lookup succeeds, so that the caller can safely use path or *ppath.(CVE-2024-49881)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ext4: fix double brelse() the buffer of the extents path In ext4_ext_try_to_merge_up(), set path[1].p_bh to NULL after it has been released, otherwise it may be released twice. An example of what triggers this is as follows: split2 map split1 |--------|-------|--------| ext4_ext_map_blocks ext4_ext_handle_unwritten_extents ext4_split_convert_extents // path-\u0026gt;p_depth == 0 ext4_split_extent // 1. do split1 ext4_split_extent_at |ext4_ext_insert_extent | ext4_ext_create_new_leaf | ext4_ext_grow_indepth | le16_add_cpu(\u0026amp;neh-\u0026gt;eh_depth, 1) | ext4_find_extent | // return -ENOMEM |// get error and try zeroout |path = ext4_find_extent | path-\u0026gt;p_depth = 1 |ext4_ext_try_to_merge | ext4_ext_try_to_merge_up | path-\u0026gt;p_depth = 0 | brelse(path[1].p_bh) ---\u0026gt; not set to NULL here |// zeroout success // 2. update path ext4_find_extent // 3. do split2 ext4_split_extent_at ext4_ext_insert_extent ext4_ext_create_new_leaf ext4_ext_grow_indepth le16_add_cpu(\u0026amp;neh-\u0026gt;eh_depth, 1) ext4_find_extent path[0].p_bh = NULL; path-\u0026gt;p_depth = 1 read_extent_tree_block ---\u0026gt; return err // path[1].p_bh is still the old value ext4_free_ext_path ext4_ext_drop_refs // path-\u0026gt;p_depth == 1 brelse(path[1].p_bh) ---\u0026gt; brelse a buffer twice Finally got the following WARRNING when removing the buffer from lru: ============================================ VFS: brelse: Trying to free free buffer WARNING: CPU: 2 PID: 72 at fs/buffer.c:1241 __brelse+0x58/0x90 CPU: 2 PID: 72 Comm: kworker/u19:1 Not tainted 6.9.0-dirty #716 RIP: 0010:__brelse+0x58/0x90 Call Trace: \u0026lt;TASK\u0026gt; __find_get_block+0x6e7/0x810 bdev_getblk+0x2b/0x480 __ext4_get_inode_loc+0x48a/0x1240 ext4_get_inode_loc+0xb2/0x150 ext4_reserve_inode_write+0xb7/0x230 __ext4_mark_inode_dirty+0x144/0x6a0 ext4_ext_insert_extent+0x9c8/0x3230 ext4_ext_map_blocks+0xf45/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] ============================================(CVE-2024-49882)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ext4: aovid use-after-free in ext4_ext_insert_extent() As Ojaswin mentioned in Link, in ext4_ext_insert_extent(), if the path is reallocated in ext4_ext_create_new_leaf(), we\u0026apos;ll use the stale path and cause UAF. Below is a sample trace with dummy values: ext4_ext_insert_extent path = *ppath = 2000 ext4_ext_create_new_leaf(ppath) ext4_find_extent(ppath) path = *ppath = 2000 if (depth \u0026gt; path[0].p_maxdepth) kfree(path = 2000); *ppath = path = NULL; path = kcalloc() = 3000 *ppath = 3000; return path; /* here path is still 2000, UAF! */ eh = path[depth].p_hdr ================================================================== BUG: KASAN: slab-use-after-free in ext4_ext_insert_extent+0x26d4/0x3330 Read of size 8 at addr ffff8881027bf7d0 by task kworker/u36:1/179 CPU: 3 UID: 0 PID: 179 Comm: kworker/u6:1 Not tainted 6.11.0-rc2-dirty #866 Call Trace: \u0026lt;TASK\u0026gt; ext4_ext_insert_extent+0x26d4/0x3330 ext4_ext_map_blocks+0xe22/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 [...] Allocated by task 179: ext4_find_extent+0x81c/0x1f70 ext4_ext_map_blocks+0x146/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 ext4_writepages+0x26d/0x4e0 do_writepages+0x175/0x700 [...] Freed by task 179: kfree+0xcb/0x240 ext4_find_extent+0x7c0/0x1f70 ext4_ext_insert_extent+0xa26/0x3330 ext4_ext_map_blocks+0xe22/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 ext4_writepages+0x26d/0x4e0 do_writepages+0x175/0x700 [...] ================================================================== So use *ppath to update the path to avoid the above problem.(CVE-2024-49883)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ext4: fix slab-use-after-free in ext4_split_extent_at() We hit the following use-after-free: ================================================================== BUG: KASAN: slab-use-after-free in ext4_split_extent_at+0xba8/0xcc0 Read of size 2 at addr ffff88810548ed08 by task kworker/u20:0/40 CPU: 0 PID: 40 Comm: kworker/u20:0 Not tainted 6.9.0-dirty #724 Call Trace: \u0026lt;TASK\u0026gt; kasan_report+0x93/0xc0 ext4_split_extent_at+0xba8/0xcc0 ext4_split_extent.isra.0+0x18f/0x500 ext4_split_convert_extents+0x275/0x750 ext4_ext_handle_unwritten_extents+0x73e/0x1580 ext4_ext_map_blocks+0xe20/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] Allocated by task 40: __kmalloc_noprof+0x1ac/0x480 ext4_find_extent+0xf3b/0x1e70 ext4_ext_map_blocks+0x188/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] Freed by task 40: kfree+0xf1/0x2b0 ext4_find_extent+0xa71/0x1e70 ext4_ext_insert_extent+0xa22/0x3260 ext4_split_extent_at+0x3ef/0xcc0 ext4_split_extent.isra.0+0x18f/0x500 ext4_split_convert_extents+0x275/0x750 ext4_ext_handle_unwritten_extents+0x73e/0x1580 ext4_ext_map_blocks+0xe20/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] ================================================================== The flow of issue triggering is as follows: ext4_split_extent_at path = *ppath ext4_ext_insert_extent(ppath) ext4_ext_create_new_leaf(ppath) ext4_find_extent(orig_path) path = *orig_path read_extent_tree_block // return -ENOMEM or -EIO ext4_free_ext_path(path) kfree(path) *orig_path = NULL a. If err is -ENOMEM: ext4_ext_dirty(path + path-\u0026gt;p_depth) // path use-after-free !!! b. If err is -EIO and we have EXT_DEBUG defined: ext4_ext_show_leaf(path) eh = path[depth].p_hdr // path also use-after-free !!! So when trying to zeroout or fix the extent length, call ext4_find_extent() to update the path. In addition we use *ppath directly as an ext4_ext_show_leaf() input to avoid possible use-after-free when EXT_DEBUG is defined, and to avoid unnecessary path updates.(CVE-2024-49884)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: platform/x86: ISST: Fix the KASAN report slab-out-of-bounds bug Attaching SST PCI device to VM causes \u0026quot;BUG: KASAN: slab-out-of-bounds\u0026quot;. kasan report: [ 19.411889] ================================================================== [ 19.413702] BUG: KASAN: slab-out-of-bounds in _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.415634] Read of size 8 at addr ffff888829e65200 by task cpuhp/16/113 [ 19.417368] [ 19.418627] CPU: 16 PID: 113 Comm: cpuhp/16 Tainted: G E 6.9.0 #10 [ 19.420435] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference Platform, BIOS VMW201.00V.20192059.B64.2207280713 07/28/2022 [ 19.422687] Call Trace: [ 19.424091] \u0026lt;TASK\u0026gt; [ 19.425448] dump_stack_lvl+0x5d/0x80 [ 19.426963] ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.428694] print_report+0x19d/0x52e [ 19.430206] ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [ 19.431837] ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.433539] kasan_report+0xf0/0x170 [ 19.435019] ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.436709] _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.438379] ? __pfx_sched_clock_cpu+0x10/0x10 [ 19.439910] isst_if_cpu_online+0x406/0x58f [isst_if_common] [ 19.441573] ? __pfx_isst_if_cpu_online+0x10/0x10 [isst_if_common] [ 19.443263] ? ttwu_queue_wakelist+0x2c1/0x360 [ 19.444797] cpuhp_invoke_callback+0x221/0xec0 [ 19.446337] cpuhp_thread_fun+0x21b/0x610 [ 19.447814] ? __pfx_cpuhp_thread_fun+0x10/0x10 [ 19.449354] smpboot_thread_fn+0x2e7/0x6e0 [ 19.450859] ? __pfx_smpboot_thread_fn+0x10/0x10 [ 19.452405] kthread+0x29c/0x350 [ 19.453817] ? __pfx_kthread+0x10/0x10 [ 19.455253] ret_from_fork+0x31/0x70 [ 19.456685] ? __pfx_kthread+0x10/0x10 [ 19.458114] ret_from_fork_asm+0x1a/0x30 [ 19.459573] \u0026lt;/TASK\u0026gt; [ 19.460853] [ 19.462055] Allocated by task 1198: [ 19.463410] kasan_save_stack+0x30/0x50 [ 19.464788] kasan_save_track+0x14/0x30 [ 19.466139] __kasan_kmalloc+0xaa/0xb0 [ 19.467465] __kmalloc+0x1cd/0x470 [ 19.468748] isst_if_cdev_register+0x1da/0x350 [isst_if_common] [ 19.470233] isst_if_mbox_init+0x108/0xff0 [isst_if_mbox_msr] [ 19.471670] do_one_initcall+0xa4/0x380 [ 19.472903] do_init_module+0x238/0x760 [ 19.474105] load_module+0x5239/0x6f00 [ 19.475285] init_module_from_file+0xd1/0x130 [ 19.476506] idempotent_init_module+0x23b/0x650 [ 19.477725] __x64_sys_finit_module+0xbe/0x130 [ 19.476506] idempotent_init_module+0x23b/0x650 [ 19.477725] __x64_sys_finit_module+0xbe/0x130 [ 19.478920] do_syscall_64+0x82/0x160 [ 19.480036] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 19.481292] [ 19.482205] The buggy address belongs to the object at ffff888829e65000 which belongs to the cache kmalloc-512 of size 512 [ 19.484818] The buggy address is located 0 bytes to the right of allocated 512-byte region [ffff888829e65000, ffff888829e65200) [ 19.487447] [ 19.488328] The buggy address belongs to the physical page: [ 19.489569] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff888829e60c00 pfn:0x829e60 [ 19.491140] head: order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0 [ 19.492466] anon flags: 0x57ffffc0000840(slab|head|node=1|zone=2|lastcpupid=0x1fffff) [ 19.493914] page_type: 0xffffffff() [ 19.494988] raw: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [ 19.496451] raw: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [ 19.497906] head: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [ 19.499379] head: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [ 19.500844] head: 0057ffffc0000003 ffffea0020a79801 ffffea0020a79848 00000000ffffffff [ 19.502316] head: 0000000800000000 0000000000000000 00000000ffffffff 0000000000000000 [ 19.503784] page dumped because: k ---truncated---(CVE-2024-49886)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ext4: avoid use-after-free in ext4_ext_show_leaf() In ext4_find_extent(), path may be freed by error or be reallocated, so using a previously saved *ppath may have been freed and thus may trigger use-after-free, as follows: ext4_split_extent path = *ppath; ext4_split_extent_at(ppath) path = ext4_find_extent(ppath) ext4_split_extent_at(ppath) // ext4_find_extent fails to free path // but zeroout succeeds ext4_ext_show_leaf(inode, path) eh = path[depth].p_hdr // path use-after-free !!! Similar to ext4_split_extent_at(), we use *ppath directly as an input to ext4_ext_show_leaf(). Fix a spelling error by the way. Same problem in ext4_ext_handle_unwritten_extents(). Since \u0026apos;path\u0026apos; is only used in ext4_ext_show_leaf(), remove \u0026apos;path\u0026apos; and use *ppath directly. This issue is triggered only when EXT_DEBUG is defined and therefore does not affect functionality.(CVE-2024-49889)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check stream before comparing them [WHAT \u0026amp; HOW] amdgpu_dm can pass a null stream to dc_is_stream_unchanged. It is necessary to check for null before dereferencing them. This fixes 1 FORWARD_NULL issue reported by Coverity.(CVE-2024-49896)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add null check for top_pipe_to_program in commit_planes_for_stream This commit addresses a null pointer dereference issue in the `commit_planes_for_stream` function at line 4140. The issue could occur when `top_pipe_to_program` is null. The fix adds a check to ensure `top_pipe_to_program` is not null before accessing its stream_res. This prevents a null pointer dereference. Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.c:4140 commit_planes_for_stream() error: we previously assumed \u0026apos;top_pipe_to_program\u0026apos; could be null (see line 3906)(CVE-2024-49913)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add NULL check for clk_mgr and clk_mgr-\u0026gt;funcs in dcn30_init_hw This commit addresses a potential null pointer dereference issue in the `dcn30_init_hw` function. The issue could occur when `dc-\u0026gt;clk_mgr` or `dc-\u0026gt;clk_mgr-\u0026gt;funcs` is null. The fix adds a check to ensure `dc-\u0026gt;clk_mgr` and `dc-\u0026gt;clk_mgr-\u0026gt;funcs` is not null before accessing its functions. This prevents a potential null pointer dereference. Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c:789 dcn30_init_hw() error: we previously assumed \u0026apos;dc-\u0026gt;clk_mgr\u0026apos; could be null (see line 628)(CVE-2024-49917)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check null pointers before using them [WHAT \u0026amp; HOW] These pointers are null checked previously in the same function, indicating they might be null as reported by Coverity. As a result, they need to be checked when used again. This fixes 3 FORWARD_NULL issue reported by Coverity.(CVE-2024-49922)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: fbdev: pxafb: Fix possible use after free in pxafb_task() In the pxafb_probe function, it calls the pxafb_init_fbinfo function, after which \u0026amp;fbi-\u0026gt;task is associated with pxafb_task. Moreover, within this pxafb_init_fbinfo function, the pxafb_blank function within the \u0026amp;pxafb_ops struct is capable of scheduling work. If we remove the module which will call pxafb_remove to make cleanup, it will call unregister_framebuffer function which can call do_unregister_framebuffer to free fbi-\u0026gt;fb through put_fb_info(fb_info), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows: CPU0 CPU1 | pxafb_task pxafb_remove | unregister_framebuffer(info) | do_unregister_framebuffer(fb_info) | put_fb_info(fb_info) | // free fbi-\u0026gt;fb | set_ctrlr_state(fbi, state) | __pxafb_lcd_power(fbi, 0) | fbi-\u0026gt;lcd_power(on, \u0026amp;fbi-\u0026gt;fb.var) | //use fbi-\u0026gt;fb Fix it by ensuring that the work is canceled before proceeding with the cleanup in pxafb_remove. Note that only root user can remove the driver at runtime.(CVE-2024-49924)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: blk_iocost: fix more out of bound shifts Recently running UBSAN caught few out of bound shifts in the ioc_forgive_debts() function: UBSAN: shift-out-of-bounds in block/blk-iocost.c:2142:38 shift exponent 80 is too large for 64-bit type \u0026apos;u64\u0026apos; (aka \u0026apos;unsigned long long\u0026apos;) ... UBSAN: shift-out-of-bounds in block/blk-iocost.c:2144:30 shift exponent 80 is too large for 64-bit type \u0026apos;u64\u0026apos; (aka \u0026apos;unsigned long long\u0026apos;) ... Call Trace: \u0026lt;IRQ\u0026gt; dump_stack_lvl+0xca/0x130 __ubsan_handle_shift_out_of_bounds+0x22c/0x280 ? __lock_acquire+0x6441/0x7c10 ioc_timer_fn+0x6cec/0x7750 ? blk_iocost_init+0x720/0x720 ? call_timer_fn+0x5d/0x470 call_timer_fn+0xfa/0x470 ? blk_iocost_init+0x720/0x720 __run_timer_base+0x519/0x700 ... Actual impact of this issue was not identified but I propose to fix the undefined behaviour. The proposed fix to prevent those out of bound shifts consist of precalculating exponent before using it the shift operations by taking min value from the actual exponent and maximum possible number of bits.(CVE-2024-49933)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: fs/inode: Prevent dump_mapping() accessing invalid dentry.d_name.name It\u0026apos;s observed that a crash occurs during hot-remove a memory device, in which user is accessing the hugetlb. See calltrace as following: ------------[ cut here ]------------ WARNING: CPU: 1 PID: 14045 at arch/x86/mm/fault.c:1278 do_user_addr_fault+0x2a0/0x790 Modules linked in: kmem device_dax cxl_mem cxl_pmem cxl_port cxl_pci dax_hmem dax_pmem nd_pmem cxl_acpi nd_btt cxl_core crc32c_intel nvme virtiofs fuse nvme_core nfit libnvdimm dm_multipath scsi_dh_rdac scsi_dh_emc s mirror dm_region_hash dm_log dm_mod CPU: 1 PID: 14045 Comm: daxctl Not tainted 6.10.0-rc2-lizhijian+ #492 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:do_user_addr_fault+0x2a0/0x790 Code: 48 8b 00 a8 04 0f 84 b5 fe ff ff e9 1c ff ff ff 4c 89 e9 4c 89 e2 be 01 00 00 00 bf 02 00 00 00 e8 b5 ef 24 00 e9 42 fe ff ff \u0026lt;0f\u0026gt; 0b 48 83 c4 08 4c 89 ea 48 89 ee 4c 89 e7 5b 5d 41 5c 41 5d 41 RSP: 0000:ffffc90000a575f0 EFLAGS: 00010046 RAX: ffff88800c303600 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000001000 RSI: ffffffff82504162 RDI: ffffffff824b2c36 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffffc90000a57658 R13: 0000000000001000 R14: ffff88800bc2e040 R15: 0000000000000000 FS: 00007f51cb57d880(0000) GS:ffff88807fd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000001000 CR3: 00000000072e2004 CR4: 00000000001706f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: \u0026lt;TASK\u0026gt; ? __warn+0x8d/0x190 ? do_user_addr_fault+0x2a0/0x790 ? report_bug+0x1c3/0x1d0 ? handle_bug+0x3c/0x70 ? exc_invalid_op+0x14/0x70 ? asm_exc_invalid_op+0x16/0x20 ? do_user_addr_fault+0x2a0/0x790 ? exc_page_fault+0x31/0x200 exc_page_fault+0x68/0x200 \u0026lt;...snip...\u0026gt; BUG: unable to handle page fault for address: 0000000000001000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0 Oops: Oops: 0000 [#1] PREEMPT SMP PTI ---[ end trace 0000000000000000 ]--- BUG: unable to handle page fault for address: 0000000000001000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0 Oops: Oops: 0000 [#1] PREEMPT SMP PTI CPU: 1 PID: 14045 Comm: daxctl Kdump: loaded Tainted: G W 6.10.0-rc2-lizhijian+ #492 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:dentry_name+0x1f4/0x440 \u0026lt;...snip...\u0026gt; ? dentry_name+0x2fa/0x440 vsnprintf+0x1f3/0x4f0 vprintk_store+0x23a/0x540 vprintk_emit+0x6d/0x330 _printk+0x58/0x80 dump_mapping+0x10b/0x1a0 ? __pfx_free_object_rcu+0x10/0x10 __dump_page+0x26b/0x3e0 ? vprintk_emit+0xe0/0x330 ? _printk+0x58/0x80 ? dump_page+0x17/0x50 dump_page+0x17/0x50 do_migrate_range+0x2f7/0x7f0 ? do_migrate_range+0x42/0x7f0 ? offline_pages+0x2f4/0x8c0 offline_pages+0x60a/0x8c0 memory_subsys_offline+0x9f/0x1c0 ? lockdep_hardirqs_on+0x77/0x100 ? _raw_spin_unlock_irqrestore+0x38/0x60 device_offline+0xe3/0x110 state_store+0x6e/0xc0 kernfs_fop_write_iter+0x143/0x200 vfs_write+0x39f/0x560 ksys_write+0x65/0xf0 do_syscall_64+0x62/0x130 Previously, some sanity check have been done in dump_mapping() before the print facility parsing \u0026apos;%pd\u0026apos; though, it\u0026apos;s still possible to run into an invalid dentry.d_name.name. Since dump_mapping() only needs to dump the filename only, retrieve it by itself in a safer way to prevent an unnecessary crash. Note that either retrieving the filename with \u0026apos;%pd\u0026apos; or strncpy_from_kernel_nofault(), the filename could be unreliable.(CVE-2024-49934)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: net/xen-netback: prevent UAF in xenvif_flush_hash() During the list_for_each_entry_rcu iteration call of xenvif_flush_hash, kfree_rcu does not exist inside the rcu read critical section, so if kfree_rcu is called when the rcu grace period ends during the iteration, UAF occurs when accessing head-\u0026gt;next after the entry becomes free. Therefore, to solve this, you need to change it to list_for_each_entry_safe.(CVE-2024-49936)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: l2tp: prevent possible tunnel refcount underflow When a session is created, it sets a backpointer to its tunnel. When the session refcount drops to 0, l2tp_session_free drops the tunnel refcount if session-\u0026gt;tunnel is non-NULL. However, session-\u0026gt;tunnel is set in l2tp_session_create, before the tunnel refcount is incremented by l2tp_session_register, which leaves a small window where session-\u0026gt;tunnel is non-NULL when the tunnel refcount hasn\u0026apos;t been bumped. Moving the assignment to l2tp_session_register is trivial but l2tp_session_create calls l2tp_session_set_header_len which uses session-\u0026gt;tunnel to get the tunnel\u0026apos;s encap. Add an encap arg to l2tp_session_set_header_len to avoid using session-\u0026gt;tunnel. If l2tpv3 sessions have colliding IDs, it is possible for l2tp_v3_session_get to race with l2tp_session_register and fetch a session which doesn\u0026apos;t yet have session-\u0026gt;tunnel set. Add a check for this case.(CVE-2024-49940)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix uaf in l2cap_connect [Syzbot reported] BUG: KASAN: slab-use-after-free in l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949 Read of size 8 at addr ffff8880241e9800 by task kworker/u9:0/54 CPU: 0 UID: 0 PID: 54 Comm: kworker/u9:0 Not tainted 6.11.0-rc6-syzkaller-00268-g788220eee30d #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 Workqueue: hci2 hci_rx_work Call Trace: \u0026lt;TASK\u0026gt; __dump_stack lib/dump_stack.c:93 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:119 print_address_description mm/kasan/report.c:377 [inline] print_report+0xc3/0x620 mm/kasan/report.c:488 kasan_report+0xd9/0x110 mm/kasan/report.c:601 l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949 l2cap_connect_req net/bluetooth/l2cap_core.c:4080 [inline] l2cap_bredr_sig_cmd net/bluetooth/l2cap_core.c:4772 [inline] l2cap_sig_channel net/bluetooth/l2cap_core.c:5543 [inline] l2cap_recv_frame+0xf0b/0x8eb0 net/bluetooth/l2cap_core.c:6825 l2cap_recv_acldata+0x9b4/0xb70 net/bluetooth/l2cap_core.c:7514 hci_acldata_packet net/bluetooth/hci_core.c:3791 [inline] hci_rx_work+0xaab/0x1610 net/bluetooth/hci_core.c:4028 process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231 process_scheduled_works kernel/workqueue.c:3312 [inline] worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389 kthread+0x2c1/0x3a0 kernel/kthread.c:389 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 ... Freed by task 5245: kasan_save_stack+0x33/0x60 mm/kasan/common.c:47 kasan_save_track+0x14/0x30 mm/kasan/common.c:68 kasan_save_free_info+0x3b/0x60 mm/kasan/generic.c:579 poison_slab_object+0xf7/0x160 mm/kasan/common.c:240 __kasan_slab_free+0x32/0x50 mm/kasan/common.c:256 kasan_slab_free include/linux/kasan.h:184 [inline] slab_free_hook mm/slub.c:2256 [inline] slab_free mm/slub.c:4477 [inline] kfree+0x12a/0x3b0 mm/slub.c:4598 l2cap_conn_free net/bluetooth/l2cap_core.c:1810 [inline] kref_put include/linux/kref.h:65 [inline] l2cap_conn_put net/bluetooth/l2cap_core.c:1822 [inline] l2cap_conn_del+0x59d/0x730 net/bluetooth/l2cap_core.c:1802 l2cap_connect_cfm+0x9e6/0xf80 net/bluetooth/l2cap_core.c:7241 hci_connect_cfm include/net/bluetooth/hci_core.h:1960 [inline] hci_conn_failed+0x1c3/0x370 net/bluetooth/hci_conn.c:1265 hci_abort_conn_sync+0x75a/0xb50 net/bluetooth/hci_sync.c:5583 abort_conn_sync+0x197/0x360 net/bluetooth/hci_conn.c:2917 hci_cmd_sync_work+0x1a4/0x410 net/bluetooth/hci_sync.c:328 process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231 process_scheduled_works kernel/workqueue.c:3312 [inline] worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389 kthread+0x2c1/0x3a0 kernel/kthread.c:389 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244(CVE-2024-49950)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: static_call: Replace pointless WARN_ON() in static_call_module_notify() static_call_module_notify() triggers a WARN_ON(), when memory allocation fails in __static_call_add_module(). That\u0026apos;s not really justified, because the failure case must be correctly handled by the well known call chain and the error code is passed through to the initiating userspace application. A memory allocation fail is not a fatal problem, but the WARN_ON() takes the machine out when panic_on_warn is set. Replace it with a pr_warn().(CVE-2024-49954)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ACPI: battery: Fix possible crash when unregistering a battery hook When a battery hook returns an error when adding a new battery, then the battery hook is automatically unregistered. However the battery hook provider cannot know that, so it will later call battery_hook_unregister() on the already unregistered battery hook, resulting in a crash. Fix this by using the list head to mark already unregistered battery hooks as already being unregistered so that they can be ignored by battery_hook_unregister().(CVE-2024-49955)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ocfs2: reserve space for inline xattr before attaching reflink tree One of our customers reported a crash and a corrupted ocfs2 filesystem. The crash was due to the detection of corruption. Upon troubleshooting, the fsck -fn output showed the below corruption [EXTENT_LIST_FREE] Extent list in owner 33080590 claims 230 as the next free chain record, but fsck believes the largest valid value is 227. Clamp the next record value? n The stat output from the debugfs.ocfs2 showed the following corruption where the \u0026quot;Next Free Rec:\u0026quot; had overshot the \u0026quot;Count:\u0026quot; in the root metadata block. Inode: 33080590 Mode: 0640 Generation: 2619713622 (0x9c25a856) FS Generation: 904309833 (0x35e6ac49) CRC32: 00000000 ECC: 0000 Type: Regular Attr: 0x0 Flags: Valid Dynamic Features: (0x16) HasXattr InlineXattr Refcounted Extended Attributes Block: 0 Extended Attributes Inline Size: 256 User: 0 (root) Group: 0 (root) Size: 281320357888 Links: 1 Clusters: 141738 ctime: 0x66911b56 0x316edcb8 -- Fri Jul 12 06:02:30.829349048 2024 atime: 0x66911d6b 0x7f7a28d -- Fri Jul 12 06:11:23.133669517 2024 mtime: 0x66911b56 0x12ed75d7 -- Fri Jul 12 06:02:30.317552087 2024 dtime: 0x0 -- Wed Dec 31 17:00:00 1969 Refcount Block: 2777346 Last Extblk: 2886943 Orphan Slot: 0 Sub Alloc Slot: 0 Sub Alloc Bit: 14 Tree Depth: 1 Count: 227 Next Free Rec: 230 ## Offset Clusters Block# 0 0 2310 2776351 1 2310 2139 2777375 2 4449 1221 2778399 3 5670 731 2779423 4 6401 566 2780447 ....... .... ....... ....... .... ....... The issue was in the reflink workfow while reserving space for inline xattr. The problematic function is ocfs2_reflink_xattr_inline(). By the time this function is called the reflink tree is already recreated at the destination inode from the source inode. At this point, this function reserves space for inline xattrs at the destination inode without even checking if there is space at the root metadata block. It simply reduces the l_count from 243 to 227 thereby making space of 256 bytes for inline xattr whereas the inode already has extents beyond this index (in this case up to 230), thereby causing corruption. The fix for this is to reserve space for inline metadata at the destination inode before the reflink tree gets recreated. The customer has verified the fix.(CVE-2024-49958)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: r8169: add tally counter fields added with RTL8125 RTL8125 added fields to the tally counter, what may result in the chip dma\u0026apos;ing these new fields to unallocated memory. Therefore make sure that the allocated memory area is big enough to hold all of the tally counter values, even if we use only parts of it.(CVE-2024-49973)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: uprobes: fix kernel info leak via \u0026quot;[uprobes]\u0026quot; vma xol_add_vma() maps the uninitialized page allocated by __create_xol_area() into userspace. On some architectures (x86) this memory is readable even without VM_READ, VM_EXEC results in the same pgprot_t as VM_EXEC|VM_READ, although this doesn\u0026apos;t really matter, debugger can read this memory anyway.(CVE-2024-49975)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: gso: fix udp gso fraglist segmentation after pull from frag_list Detect gso fraglist skbs with corrupted geometry (see below) and pass these to skb_segment instead of skb_segment_list, as the first can segment them correctly. Valid SKB_GSO_FRAGLIST skbs - consist of two or more segments - the head_skb holds the protocol headers plus first gso_size - one or more frag_list skbs hold exactly one segment - all but the last must be gso_size Optional datapath hooks such as NAT and BPF (bpf_skb_pull_data) can modify these skbs, breaking these invariants. In extreme cases they pull all data into skb linear. For UDP, this causes a NULL ptr deref in __udpv4_gso_segment_list_csum at udp_hdr(seg-\u0026gt;next)-\u0026gt;dest. Detect invalid geometry due to pull, by checking head_skb size. Don\u0026apos;t just drop, as this may blackhole a destination. Convert to be able to pass to regular skb_segment.(CVE-2024-49978)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: media: venus: fix use after free bug in venus_remove due to race condition in venus_probe, core-\u0026gt;work is bound with venus_sys_error_handler, which is used to handle error. The code use core-\u0026gt;sys_err_done to make sync work. The core-\u0026gt;work is started in venus_event_notify. If we call venus_remove, there might be an unfished work. The possible sequence is as follows: CPU0 CPU1 |venus_sys_error_handler venus_remove | hfi_destroy | venus_hfi_destroy | kfree(hdev); | |hfi_reinit |venus_hfi_queues_reinit |//use hdev Fix it by canceling the work in venus_remove.(CVE-2024-49981)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm/stm: Avoid use-after-free issues with crtc and plane ltdc_load() calls functions drm_crtc_init_with_planes(), drm_universal_plane_init() and drm_encoder_init(). These functions should not be called with parameters allocated with devm_kzalloc() to avoid use-after-free issues [1]. Use allocations managed by the DRM framework. Found by Linux Verification Center (linuxtesting.org). [1] https://lore.kernel.org/lkml/u366i76e3qhh3ra5oxrtngjtm2u5lterkekcz6y2jkndhuxzli@diujon4h7qwb/(CVE-2024-49992)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: tipc: guard against string buffer overrun Smatch reports that copying media_name and if_name to name_parts may overwrite the destination. .../bearer.c:166 bearer_name_validate() error: strcpy() \u0026apos;media_name\u0026apos; too large for \u0026apos;name_parts-\u0026gt;media_name\u0026apos; (32 vs 16) .../bearer.c:167 bearer_name_validate() error: strcpy() \u0026apos;if_name\u0026apos; too large for \u0026apos;name_parts-\u0026gt;if_name\u0026apos; (1010102 vs 16) This does seem to be the case so guard against this possibility by using strscpy() and failing if truncation occurs. Introduced by commit b97bf3fd8f6a (\u0026quot;[TIPC] Initial merge\u0026quot;) Compile tested only.(CVE-2024-49995)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: cifs: Fix buffer overflow when parsing NFS reparse points ReparseDataLength is sum of the InodeType size and DataBuffer size. So to get DataBuffer size it is needed to subtract InodeType\u0026apos;s size from ReparseDataLength. Function cifs_strndup_from_utf16() is currentlly accessing buf-\u0026gt;DataBuffer at position after the end of the buffer because it does not subtract InodeType size from the length. Fix this problem and correctly subtract variable len. Member InodeType is present only when reparse buffer is large enough. Check for ReparseDataLength before accessing InodeType to prevent another invalid memory access. Major and minor rdev values are present also only when reparse buffer is large enough. Check for reparse buffer size before calling reparse_mkdev().(CVE-2024-49996)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: static_call: Handle module init failure correctly in static_call_del_module() Module insertion invokes static_call_add_module() to initialize the static calls in a module. static_call_add_module() invokes __static_call_init(), which allocates a struct static_call_mod to either encapsulate the built-in static call sites of the associated key into it so further modules can be added or to append the module to the module chain. If that allocation fails the function returns with an error code and the module core invokes static_call_del_module() to clean up eventually added static_call_mod entries. This works correctly, when all keys used by the module were converted over to a module chain before the failure. If not then static_call_del_module() causes a #GP as it blindly assumes that key::mods points to a valid struct static_call_mod. The problem is that key::mods is not a individual struct member of struct static_call_key, it\u0026apos;s part of a union to save space: union { /* bit 0: 0 = mods, 1 = sites */ unsigned long type; struct static_call_mod *mods; struct static_call_site *sites; }; key::sites is a pointer to the list of built-in usage sites of the static call. The type of the pointer is differentiated by bit 0. A mods pointer has the bit clear, the sites pointer has the bit set. As static_call_del_module() blidly assumes that the pointer is a valid static_call_mod type, it fails to check for this failure case and dereferences the pointer to the list of built-in call sites, which is obviously bogus. Cure it by checking whether the key has a sites or a mods pointer. If it\u0026apos;s a sites pointer then the key is not to be touched. As the sites are walked in the same order as in __static_call_init() the site walk can be terminated because all subsequent sites have not been touched by the init code due to the error exit. If it was converted before the allocation fail, then the inner loop which searches for a module match will find nothing. A fail in the second allocation in __static_call_init() is harmless and does not require special treatment. The first allocation succeeded and converted the key to a module chain. That first entry has mod::mod == NULL and mod::next == NULL, so the inner loop of static_call_del_module() will neither find a module match nor a module chain. The next site in the walk was either already converted, but can\u0026apos;t match the module, or it will exit the outer loop because it has a static_call_site pointer and not a static_call_mod pointer.(CVE-2024-50002)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ALSA: asihpi: Fix potential OOB array access ASIHPI driver stores some values in the static array upon a response from the driver, and its index depends on the firmware. We shouldn\u0026apos;t trust it blindly. This patch adds a sanity check of the array index to fit in the array size.(CVE-2024-50007)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_cmd_802_11_scan_ext() Replace one-element array with a flexible-array member in `struct host_cmd_ds_802_11_scan_ext`. With this, fix the following warning: elo 16 17:51:58 surfacebook kernel: ------------[ cut here ]------------ elo 16 17:51:58 surfacebook kernel: memcpy: detected field-spanning write (size 243) of single field \u0026quot;ext_scan-\u0026gt;tlv_buffer\u0026quot; at drivers/net/wireless/marvell/mwifiex/scan.c:2239 (size 1) elo 16 17:51:58 surfacebook kernel: WARNING: CPU: 0 PID: 498 at drivers/net/wireless/marvell/mwifiex/scan.c:2239 mwifiex_cmd_802_11_scan_ext+0x83/0x90 [mwifiex](CVE-2024-50008)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ext4: dax: fix overflowing extents beyond inode size when partially writing The dax_iomap_rw() does two things in each iteration: map written blocks and copy user data to blocks. If the process is killed by user(See signal handling in dax_iomap_iter()), the copied data will be returned and added on inode size, which means that the length of written extents may exceed the inode size, then fsck will fail. An example is given as: dd if=/dev/urandom of=file bs=4M count=1 dax_iomap_rw iomap_iter // round 1 ext4_iomap_begin ext4_iomap_alloc // allocate 0~2M extents(written flag) dax_iomap_iter // copy 2M data iomap_iter // round 2 iomap_iter_advance iter-\u0026gt;pos += iter-\u0026gt;processed // iter-\u0026gt;pos = 2M ext4_iomap_begin ext4_iomap_alloc // allocate 2~4M extents(written flag) dax_iomap_iter fatal_signal_pending done = iter-\u0026gt;pos - iocb-\u0026gt;ki_pos // done = 2M ext4_handle_inode_extension ext4_update_inode_size // inode size = 2M fsck reports: Inode 13, i_size is 2097152, should be 4194304. Fix? Fix the problem by truncating extents if the written length is smaller than expected.(CVE-2024-50015)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Avoid overflow assignment in link_dp_cts sampling_rate is an uint8_t but is assigned an unsigned int, and thus it can overflow. As a result, sampling_rate is changed to uint32_t. Similarly, LINK_QUAL_PATTERN_SET has a size of 2 bits, and it should only be assigned to a value less or equal than 4. This fixes 2 INTEGER_OVERFLOW issues reported by Coverity.(CVE-2024-50016)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: thermal: core: Reference count the zone in thermal_zone_get_by_id() There are places in the thermal netlink code where nothing prevents the thermal zone object from going away while being accessed after it has been returned by thermal_zone_get_by_id(). To address this, make thermal_zone_get_by_id() get a reference on the thermal zone device object to be returned with the help of get_device(), under thermal_list_lock, and adjust all of its callers to this change with the help of the cleanup.h infrastructure.(CVE-2024-50028)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: slip: make slhc_remember() more robust against malicious packets syzbot found that slhc_remember() was missing checks against malicious packets [1]. slhc_remember() only checked the size of the packet was at least 20, which is not good enough. We need to make sure the packet includes the IPv4 and TCP header that are supposed to be carried. Add iph and th pointers to make the code more readable. [1] BUG: KMSAN: uninit-value in slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666 slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666 ppp_receive_nonmp_frame+0xe45/0x35e0 drivers/net/ppp/ppp_generic.c:2455 ppp_receive_frame drivers/net/ppp/ppp_generic.c:2372 [inline] ppp_do_recv+0x65f/0x40d0 drivers/net/ppp/ppp_generic.c:2212 ppp_input+0x7dc/0xe60 drivers/net/ppp/ppp_generic.c:2327 pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379 sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113 __release_sock+0x1da/0x330 net/core/sock.c:3072 release_sock+0x6b/0x250 net/core/sock.c:3626 pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 ____sys_sendmsg+0x903/0xb60 net/socket.c:2602 ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was created at: slab_post_alloc_hook mm/slub.c:4091 [inline] slab_alloc_node mm/slub.c:4134 [inline] kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4186 kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587 __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678 alloc_skb include/linux/skbuff.h:1322 [inline] sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732 pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 ____sys_sendmsg+0x903/0xb60 net/socket.c:2602 ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f CPU: 0 UID: 0 PID: 5460 Comm: syz.2.33 Not tainted 6.12.0-rc2-syzkaller-00006-g87d6aab2389e #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50033)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ppp: fix ppp_async_encode() illegal access syzbot reported an issue in ppp_async_encode() [1] In this case, pppoe_sendmsg() is called with a zero size. Then ppp_async_encode() is called with an empty skb. BUG: KMSAN: uninit-value in ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline] BUG: KMSAN: uninit-value in ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675 ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline] ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675 ppp_async_send+0x130/0x1b0 drivers/net/ppp/ppp_async.c:634 ppp_channel_bridge_input drivers/net/ppp/ppp_generic.c:2280 [inline] ppp_input+0x1f1/0xe60 drivers/net/ppp/ppp_generic.c:2304 pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379 sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113 __release_sock+0x1da/0x330 net/core/sock.c:3072 release_sock+0x6b/0x250 net/core/sock.c:3626 pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 ____sys_sendmsg+0x903/0xb60 net/socket.c:2602 ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was created at: slab_post_alloc_hook mm/slub.c:4092 [inline] slab_alloc_node mm/slub.c:4135 [inline] kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4187 kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587 __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678 alloc_skb include/linux/skbuff.h:1322 [inline] sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732 pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 ____sys_sendmsg+0x903/0xb60 net/socket.c:2602 ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f CPU: 1 UID: 0 PID: 5411 Comm: syz.1.14 Not tainted 6.12.0-rc1-syzkaller-00165-g360c1f1f24c6 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50035)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: igb: Do not bring the device up after non-fatal error Commit 004d25060c78 (\u0026quot;igb: Fix igb_down hung on surprise removal\u0026quot;) changed igb_io_error_detected() to ignore non-fatal pcie errors in order to avoid hung task that can happen when igb_down() is called multiple times. This caused an issue when processing transient non-fatal errors. igb_io_resume(), which is called after igb_io_error_detected(), assumes that device is brought down by igb_io_error_detected() if the interface is up. This resulted in panic with stacktrace below. [ T3256] igb 0000:09:00.0 haeth0: igb: haeth0 NIC Link is Down [ T292] pcieport 0000:00:1c.5: AER: Uncorrected (Non-Fatal) error received: 0000:09:00.0 [ T292] igb 0000:09:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [ T292] igb 0000:09:00.0: device [8086:1537] error status/mask=00004000/00000000 [ T292] igb 0000:09:00.0: [14] CmpltTO [ 200.105524,009][ T292] igb 0000:09:00.0: AER: TLP Header: 00000000 00000000 00000000 00000000 [ T292] pcieport 0000:00:1c.5: AER: broadcast error_detected message [ T292] igb 0000:09:00.0: Non-correctable non-fatal error reported. [ T292] pcieport 0000:00:1c.5: AER: broadcast mmio_enabled message [ T292] pcieport 0000:00:1c.5: AER: broadcast resume message [ T292] ------------[ cut here ]------------ [ T292] kernel BUG at net/core/dev.c:6539! [ T292] invalid opcode: 0000 [#1] PREEMPT SMP [ T292] RIP: 0010:napi_enable+0x37/0x40 [ T292] Call Trace: [ T292] \u0026lt;TASK\u0026gt; [ T292] ? die+0x33/0x90 [ T292] ? do_trap+0xdc/0x110 [ T292] ? napi_enable+0x37/0x40 [ T292] ? do_error_trap+0x70/0xb0 [ T292] ? napi_enable+0x37/0x40 [ T292] ? napi_enable+0x37/0x40 [ T292] ? exc_invalid_op+0x4e/0x70 [ T292] ? napi_enable+0x37/0x40 [ T292] ? asm_exc_invalid_op+0x16/0x20 [ T292] ? napi_enable+0x37/0x40 [ T292] igb_up+0x41/0x150 [ T292] igb_io_resume+0x25/0x70 [ T292] report_resume+0x54/0x70 [ T292] ? report_frozen_detected+0x20/0x20 [ T292] pci_walk_bus+0x6c/0x90 [ T292] ? aer_print_port_info+0xa0/0xa0 [ T292] pcie_do_recovery+0x22f/0x380 [ T292] aer_process_err_devices+0x110/0x160 [ T292] aer_isr+0x1c1/0x1e0 [ T292] ? disable_irq_nosync+0x10/0x10 [ T292] irq_thread_fn+0x1a/0x60 [ T292] irq_thread+0xe3/0x1a0 [ T292] ? irq_set_affinity_notifier+0x120/0x120 [ T292] ? irq_affinity_notify+0x100/0x100 [ T292] kthread+0xe2/0x110 [ T292] ? kthread_complete_and_exit+0x20/0x20 [ T292] ret_from_fork+0x2d/0x50 [ T292] ? kthread_complete_and_exit+0x20/0x20 [ T292] ret_from_fork_asm+0x11/0x20 [ T292] \u0026lt;/TASK\u0026gt; To fix this issue igb_io_resume() checks if the interface is running and the device is not down this means igb_io_error_detected() did not bring the device down and there is no need to bring it up.(CVE-2024-50040)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: smb: client: fix UAF in async decryption Doing an async decryption (large read) crashes with a slab-use-after-free way down in the crypto API. Reproducer: # mount.cifs -o ...,seal,esize=1 //srv/share /mnt # dd if=/mnt/largefile of=/dev/null ... [ 194.196391] ================================================================== [ 194.196844] BUG: KASAN: slab-use-after-free in gf128mul_4k_lle+0xc1/0x110 [ 194.197269] Read of size 8 at addr ffff888112bd0448 by task kworker/u77:2/899 [ 194.197707] [ 194.197818] CPU: 12 UID: 0 PID: 899 Comm: kworker/u77:2 Not tainted 6.11.0-lku-00028-gfca3ca14a17a-dirty #43 [ 194.198400] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.2-3-gd478f380-prebuilt.qemu.org 04/01/2014 [ 194.199046] Workqueue: smb3decryptd smb2_decrypt_offload [cifs] [ 194.200032] Call Trace: [ 194.200191] \u0026lt;TASK\u0026gt; [ 194.200327] dump_stack_lvl+0x4e/0x70 [ 194.200558] ? gf128mul_4k_lle+0xc1/0x110 [ 194.200809] print_report+0x174/0x505 [ 194.201040] ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [ 194.201352] ? srso_return_thunk+0x5/0x5f [ 194.201604] ? __virt_addr_valid+0xdf/0x1c0 [ 194.201868] ? gf128mul_4k_lle+0xc1/0x110 [ 194.202128] kasan_report+0xc8/0x150 [ 194.202361] ? gf128mul_4k_lle+0xc1/0x110 [ 194.202616] gf128mul_4k_lle+0xc1/0x110 [ 194.202863] ghash_update+0x184/0x210 [ 194.203103] shash_ahash_update+0x184/0x2a0 [ 194.203377] ? __pfx_shash_ahash_update+0x10/0x10 [ 194.203651] ? srso_return_thunk+0x5/0x5f [ 194.203877] ? crypto_gcm_init_common+0x1ba/0x340 [ 194.204142] gcm_hash_assoc_remain_continue+0x10a/0x140 [ 194.204434] crypt_message+0xec1/0x10a0 [cifs] [ 194.206489] ? __pfx_crypt_message+0x10/0x10 [cifs] [ 194.208507] ? srso_return_thunk+0x5/0x5f [ 194.209205] ? srso_return_thunk+0x5/0x5f [ 194.209925] ? srso_return_thunk+0x5/0x5f [ 194.210443] ? srso_return_thunk+0x5/0x5f [ 194.211037] decrypt_raw_data+0x15f/0x250 [cifs] [ 194.212906] ? __pfx_decrypt_raw_data+0x10/0x10 [cifs] [ 194.214670] ? srso_return_thunk+0x5/0x5f [ 194.215193] smb2_decrypt_offload+0x12a/0x6c0 [cifs] This is because TFM is being used in parallel. Fix this by allocating a new AEAD TFM for async decryption, but keep the existing one for synchronous READ cases (similar to what is done in smb3_calc_signature()). Also remove the calls to aead_request_set_callback() and crypto_wait_req() since it\u0026apos;s always going to be a synchronous operation.(CVE-2024-50047)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: serial: protect uart_port_dtr_rts() in uart_shutdown() too Commit af224ca2df29 (serial: core: Prevent unsafe uart port access, part 3) added few uport == NULL checks. It added one to uart_shutdown(), so the commit assumes, uport can be NULL in there. But right after that protection, there is an unprotected \u0026quot;uart_port_dtr_rts(uport, false);\u0026quot; call. That is invoked only if HUPCL is set, so I assume that is the reason why we do not see lots of these reports. Or it cannot be NULL at this point at all for some reason :P. Until the above is investigated, stay on the safe side and move this dereference to the if too. I got this inconsistency from Coverity under CID 1585130. Thanks.(CVE-2024-50058)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ntb: ntb_hw_switchtec: Fix use after free vulnerability in switchtec_ntb_remove due to race condition In the switchtec_ntb_add function, it can call switchtec_ntb_init_sndev function, then \u0026amp;sndev-\u0026gt;check_link_status_work is bound with check_link_status_work. switchtec_ntb_link_notification may be called to start the work. If we remove the module which will call switchtec_ntb_remove to make cleanup, it will free sndev through kfree(sndev), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows: CPU0 CPU1 | check_link_status_work switchtec_ntb_remove | kfree(sndev); | | if (sndev-\u0026gt;link_force_down) | // use sndev Fix it by ensuring that the work is canceled before proceeding with the cleanup in switchtec_ntb_remove.(CVE-2024-50059)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: io_uring: check if we need to reschedule during overflow flush In terms of normal application usage, this list will always be empty. And if an application does overflow a bit, it\u0026apos;ll have a few entries. However, nothing obviously prevents syzbot from running a test case that generates a ton of overflow entries, and then flushing them can take quite a while. Check for needing to reschedule while flushing, and drop our locks and do so if necessary. There\u0026apos;s no state to maintain here as overflows always prune from head-of-list, hence it\u0026apos;s fine to drop and reacquire the locks at the end of the loop.(CVE-2024-50060)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: bpf: Prevent tail call between progs attached to different hooks bpf progs can be attached to kernel functions, and the attached functions can take different parameters or return different return values. If prog attached to one kernel function tail calls prog attached to another kernel function, the ctx access or return value verification could be bypassed. For example, if prog1 is attached to func1 which takes only 1 parameter and prog2 is attached to func2 which takes two parameters. Since verifier assumes the bpf ctx passed to prog2 is constructed based on func2\u0026apos;s prototype, verifier allows prog2 to access the second parameter from the bpf ctx passed to it. The problem is that verifier does not prevent prog1 from passing its bpf ctx to prog2 via tail call. In this case, the bpf ctx passed to prog2 is constructed from func1 instead of func2, that is, the assumption for ctx access verification is bypassed. Another example, if BPF LSM prog1 is attached to hook file_alloc_security, and BPF LSM prog2 is attached to hook bpf_lsm_audit_rule_known. Verifier knows the return value rules for these two hooks, e.g. it is legal for bpf_lsm_audit_rule_known to return positive number 1, and it is illegal for file_alloc_security to return positive number. So verifier allows prog2 to return positive number 1, but does not allow prog1 to return positive number. The problem is that verifier does not prevent prog1 from calling prog2 via tail call. In this case, prog2\u0026apos;s return value 1 will be used as the return value for prog1\u0026apos;s hook file_alloc_security. That is, the return value rule is bypassed. This patch adds restriction for tail call to prevent such bypasses.(CVE-2024-50063)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: zram: free secondary algorithms names We need to kfree() secondary algorithms names when reset zram device that had multi-streams, otherwise we leak memory. [senozhatsky@chromium.org: kfree(NULL) is legal] Link: https://lkml.kernel.org/r/20240917013021.868769-1-senozhatsky@chromium.org(CVE-2024-50064)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: uprobe: avoid out-of-bounds memory access of fetching args Uprobe needs to fetch args into a percpu buffer, and then copy to ring buffer to avoid non-atomic context problem. Sometimes user-space strings, arrays can be very large, but the size of percpu buffer is only page size. And store_trace_args() won\u0026apos;t check whether these data exceeds a single page or not, caused out-of-bounds memory access. It could be reproduced by following steps: 1. build kernel with CONFIG_KASAN enabled 2. save follow program as test.c ``` \\#include \u0026lt;stdio.h\u0026gt; \\#include \u0026lt;stdlib.h\u0026gt; \\#include \u0026lt;string.h\u0026gt; // If string length large than MAX_STRING_SIZE, the fetch_store_strlen() // will return 0, cause __get_data_size() return shorter size, and // store_trace_args() will not trigger out-of-bounds access. // So make string length less than 4096. \\#define STRLEN 4093 void generate_string(char *str, int n) { int i; for (i = 0; i \u0026lt; n; ++i) { char c = i % 26 + \u0026apos;a\u0026apos;; str[i] = c; } str[n-1] = \u0026apos;\\0\u0026apos;; } void print_string(char *str) { printf(\u0026quot;%s\\n\u0026quot;, str); } int main() { char tmp[STRLEN]; generate_string(tmp, STRLEN); print_string(tmp); return 0; } ``` 3. compile program `gcc -o test test.c` 4. get the offset of `print_string()` ``` objdump -t test | grep -w print_string 0000000000401199 g F .text 000000000000001b print_string ``` 5. configure uprobe with offset 0x1199 ``` off=0x1199 cd /sys/kernel/debug/tracing/ echo \u0026quot;p /root/test:${off} arg1=+0(%di):ustring arg2=\\$comm arg3=+0(%di):ustring\u0026quot; \u0026gt; uprobe_events echo 1 \u0026gt; events/uprobes/enable echo 1 \u0026gt; tracing_on ``` 6. run `test`, and kasan will report error. ================================================================== BUG: KASAN: use-after-free in strncpy_from_user+0x1d6/0x1f0 Write of size 8 at addr ffff88812311c004 by task test/499CPU: 0 UID: 0 PID: 499 Comm: test Not tainted 6.12.0-rc3+ #18 Hardware name: Red Hat KVM, BIOS 1.16.0-4.al8 04/01/2014 Call Trace: \u0026lt;TASK\u0026gt; dump_stack_lvl+0x55/0x70 print_address_description.constprop.0+0x27/0x310 kasan_report+0x10f/0x120 ? strncpy_from_user+0x1d6/0x1f0 strncpy_from_user+0x1d6/0x1f0 ? rmqueue.constprop.0+0x70d/0x2ad0 process_fetch_insn+0xb26/0x1470 ? __pfx_process_fetch_insn+0x10/0x10 ? _raw_spin_lock+0x85/0xe0 ? __pfx__raw_spin_lock+0x10/0x10 ? __pte_offset_map+0x1f/0x2d0 ? unwind_next_frame+0xc5f/0x1f80 ? arch_stack_walk+0x68/0xf0 ? is_bpf_text_address+0x23/0x30 ? kernel_text_address.part.0+0xbb/0xd0 ? __kernel_text_address+0x66/0xb0 ? unwind_get_return_address+0x5e/0xa0 ? __pfx_stack_trace_consume_entry+0x10/0x10 ? arch_stack_walk+0xa2/0xf0 ? _raw_spin_lock_irqsave+0x8b/0xf0 ? __pfx__raw_spin_lock_irqsave+0x10/0x10 ? depot_alloc_stack+0x4c/0x1f0 ? _raw_spin_unlock_irqrestore+0xe/0x30 ? stack_depot_save_flags+0x35d/0x4f0 ? kasan_save_stack+0x34/0x50 ? kasan_save_stack+0x24/0x50 ? mutex_lock+0x91/0xe0 ? __pfx_mutex_lock+0x10/0x10 prepare_uprobe_buffer.part.0+0x2cd/0x500 uprobe_dispatcher+0x2c3/0x6a0 ? __pfx_uprobe_dispatcher+0x10/0x10 ? __kasan_slab_alloc+0x4d/0x90 handler_chain+0xdd/0x3e0 handle_swbp+0x26e/0x3d0 ? __pfx_handle_swbp+0x10/0x10 ? uprobe_pre_sstep_notifier+0x151/0x1b0 irqentry_exit_to_user_mode+0xe2/0x1b0 asm_exc_int3+0x39/0x40 RIP: 0033:0x401199 Code: 01 c2 0f b6 45 fb 88 02 83 45 fc 01 8b 45 fc 3b 45 e4 7c b7 8b 45 e4 48 98 48 8d 50 ff 48 8b 45 e8 48 01 d0 ce RSP: 002b:00007ffdf00576a8 EFLAGS: 00000206 RAX: 00007ffdf00576b0 RBX: 0000000000000000 RCX: 0000000000000ff2 RDX: 0000000000000ffc RSI: 0000000000000ffd RDI: 00007ffdf00576b0 RBP: 00007ffdf00586b0 R08: 00007feb2f9c0d20 R09: 00007feb2f9c0d20 R10: 0000000000000001 R11: 0000000000000202 R12: 0000000000401040 R13: 00007ffdf0058780 R14: 0000000000000000 R15: 0000000000000000 \u0026lt;/TASK\u0026gt; This commit enforces the buffer\u0026apos;s maxlen less than a page-size to avoid store_trace_args() out-of-memory access.(CVE-2024-50067)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: parport: Proper fix for array out-of-bounds access The recent fix for array out-of-bounds accesses replaced sprintf() calls blindly with snprintf(). However, since snprintf() returns the would-be-printed size, not the actually output size, the length calculation can still go over the given limit. Use scnprintf() instead of snprintf(), which returns the actually output letters, for addressing the potential out-of-bounds access properly.(CVE-2024-50074)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: tcp: fix mptcp DSS corruption due to large pmtu xmit Syzkaller was able to trigger a DSS corruption: TCP: request_sock_subflow_v4: Possible SYN flooding on port [::]:20002. Sending cookies. ------------[ cut here ]------------ WARNING: CPU: 0 PID: 5227 at net/mptcp/protocol.c:695 __mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695 Modules linked in: CPU: 0 UID: 0 PID: 5227 Comm: syz-executor350 Not tainted 6.11.0-syzkaller-08829-gaf9c191ac2a0 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 RIP: 0010:__mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695 Code: 0f b6 dc 31 ff 89 de e8 b5 dd ea f5 89 d8 48 81 c4 50 01 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 98 da ea f5 90 \u0026lt;0f\u0026gt; 0b 90 e9 47 ff ff ff e8 8a da ea f5 90 0f 0b 90 e9 99 e0 ff ff RSP: 0018:ffffc90000006db8 EFLAGS: 00010246 RAX: ffffffff8ba9df18 RBX: 00000000000055f0 RCX: ffff888030023c00 RDX: 0000000000000100 RSI: 00000000000081e5 RDI: 00000000000055f0 RBP: 1ffff110062bf1ae R08: ffffffff8ba9cf12 R09: 1ffff110062bf1b8 R10: dffffc0000000000 R11: ffffed10062bf1b9 R12: 0000000000000000 R13: dffffc0000000000 R14: 00000000700cec61 R15: 00000000000081e5 FS: 000055556679c380(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020287000 CR3: 0000000077892000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: \u0026lt;IRQ\u0026gt; move_skbs_to_msk net/mptcp/protocol.c:811 [inline] mptcp_data_ready+0x29c/0xa90 net/mptcp/protocol.c:854 subflow_data_ready+0x34a/0x920 net/mptcp/subflow.c:1490 tcp_data_queue+0x20fd/0x76c0 net/ipv4/tcp_input.c:5283 tcp_rcv_established+0xfba/0x2020 net/ipv4/tcp_input.c:6237 tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915 tcp_v4_rcv+0x2dc0/0x37f0 net/ipv4/tcp_ipv4.c:2350 ip_protocol_deliver_rcu+0x22e/0x440 net/ipv4/ip_input.c:205 ip_local_deliver_finish+0x341/0x5f0 net/ipv4/ip_input.c:233 NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314 NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314 __netif_receive_skb_one_core net/core/dev.c:5662 [inline] __netif_receive_skb+0x2bf/0x650 net/core/dev.c:5775 process_backlog+0x662/0x15b0 net/core/dev.c:6107 __napi_poll+0xcb/0x490 net/core/dev.c:6771 napi_poll net/core/dev.c:6840 [inline] net_rx_action+0x89b/0x1240 net/core/dev.c:6962 handle_softirqs+0x2c5/0x980 kernel/softirq.c:554 do_softirq+0x11b/0x1e0 kernel/softirq.c:455 \u0026lt;/IRQ\u0026gt; \u0026lt;TASK\u0026gt; __local_bh_enable_ip+0x1bb/0x200 kernel/softirq.c:382 local_bh_enable include/linux/bottom_half.h:33 [inline] rcu_read_unlock_bh include/linux/rcupdate.h:919 [inline] __dev_queue_xmit+0x1764/0x3e80 net/core/dev.c:4451 dev_queue_xmit include/linux/netdevice.h:3094 [inline] neigh_hh_output include/net/neighbour.h:526 [inline] neigh_output include/net/neighbour.h:540 [inline] ip_finish_output2+0xd41/0x1390 net/ipv4/ip_output.c:236 ip_local_out net/ipv4/ip_output.c:130 [inline] __ip_queue_xmit+0x118c/0x1b80 net/ipv4/ip_output.c:536 __tcp_transmit_skb+0x2544/0x3b30 net/ipv4/tcp_output.c:1466 tcp_transmit_skb net/ipv4/tcp_output.c:1484 [inline] tcp_mtu_probe net/ipv4/tcp_output.c:2547 [inline] tcp_write_xmit+0x641d/0x6bf0 net/ipv4/tcp_output.c:2752 __tcp_push_pending_frames+0x9b/0x360 net/ipv4/tcp_output.c:3015 tcp_push_pending_frames include/net/tcp.h:2107 [inline] tcp_data_snd_check net/ipv4/tcp_input.c:5714 [inline] tcp_rcv_established+0x1026/0x2020 net/ipv4/tcp_input.c:6239 tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915 sk_backlog_rcv include/net/sock.h:1113 [inline] __release_sock+0x214/0x350 net/core/sock.c:3072 release_sock+0x61/0x1f0 net/core/sock.c:3626 mptcp_push_ ---truncated---(CVE-2024-50083)",
"id": "OESA-2024-2368",
"modified": "2026-08-06T11:07:50Z",
"published": "2024-11-08T11:07:50Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2368"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48961"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48975"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-49004"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-45021"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-46677"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-46809"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47659"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47660"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47668"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47673"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47690"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47691"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47693"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47696"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47699"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47701"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47703"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47705"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47723"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47726"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47739"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47742"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47748"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47756"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49855"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49858"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49859"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49860"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49862"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49877"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49879"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49881"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49882"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49883"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49884"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49886"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49889"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49896"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49913"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49917"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49922"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49924"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49933"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49934"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49936"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49940"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49950"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49954"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49955"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49958"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49973"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49975"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49978"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49981"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49992"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49995"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49996"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50002"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50007"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50008"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50015"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50016"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50028"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50033"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50035"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50040"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50047"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50058"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50059"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50060"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50063"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50064"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50067"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50074"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50083"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "kernel security update",
"upstream": [
"CVE-2022-48961",
"CVE-2022-48975",
"CVE-2022-49004",
"CVE-2024-45021",
"CVE-2024-46677",
"CVE-2024-46809",
"CVE-2024-47659",
"CVE-2024-47660",
"CVE-2024-47668",
"CVE-2024-47673",
"CVE-2024-47690",
"CVE-2024-47691",
"CVE-2024-47693",
"CVE-2024-47696",
"CVE-2024-47699",
"CVE-2024-47701",
"CVE-2024-47703",
"CVE-2024-47705",
"CVE-2024-47723",
"CVE-2024-47726",
"CVE-2024-47739",
"CVE-2024-47742",
"CVE-2024-47748",
"CVE-2024-47756",
"CVE-2024-49855",
"CVE-2024-49858",
"CVE-2024-49859",
"CVE-2024-49860",
"CVE-2024-49862",
"CVE-2024-49877",
"CVE-2024-49879",
"CVE-2024-49881",
"CVE-2024-49882",
"CVE-2024-49883",
"CVE-2024-49884",
"CVE-2024-49886",
"CVE-2024-49889",
"CVE-2024-49896",
"CVE-2024-49913",
"CVE-2024-49917",
"CVE-2024-49922",
"CVE-2024-49924",
"CVE-2024-49933",
"CVE-2024-49934",
"CVE-2024-49936",
"CVE-2024-49940",
"CVE-2024-49950",
"CVE-2024-49954",
"CVE-2024-49955",
"CVE-2024-49958",
"CVE-2024-49973",
"CVE-2024-49975",
"CVE-2024-49978",
"CVE-2024-49981",
"CVE-2024-49992",
"CVE-2024-49995",
"CVE-2024-49996",
"CVE-2024-50002",
"CVE-2024-50007",
"CVE-2024-50008",
"CVE-2024-50015",
"CVE-2024-50016",
"CVE-2024-50028",
"CVE-2024-50033",
"CVE-2024-50035",
"CVE-2024-50040",
"CVE-2024-50047",
"CVE-2024-50058",
"CVE-2024-50059",
"CVE-2024-50060",
"CVE-2024-50063",
"CVE-2024-50064",
"CVE-2024-50067",
"CVE-2024-50074",
"CVE-2024-50083"
]
}
OESA-2024-2369 (CVE-2022-48961)
Vulnerability from osv_openeuler – Published: 2024-11-08 11:07 – Updated: 2026-08-06 11:07 – Source websiteThe Linux Kernel, the operating system core itself.
Security Fix(es):
In the Linux kernel, the following vulnerability has been resolved: net: mdio: fix unbalanced fwnode reference count in mdio_device_release() There is warning report about of_node refcount leak while probing mdio device: OF: ERROR: memory leak, expected refcount 1 instead of 2, of_node_get()/of_node_put() unbalanced - destroy cset entry: attach overlay node /spi/soc@0/mdio@710700c0/ethernet@4 In of_mdiobus_register_device(), we increase fwnode refcount by fwnode_handle_get() before associating the of_node with mdio device, but it has never been decreased in normal path. Since that, in mdio_device_release(), it needs to call fwnode_handle_put() in addition instead of calling kfree() directly. After above, just calling mdio_device_free() in the error handle path of of_mdiobus_register_device() is enough to keep the refcount balanced.(CVE-2022-48961)
In the Linux kernel, the following vulnerability has been resolved: gpiolib: fix memory leak in gpiochip_setup_dev() Here is a backtrace report about memory leak detected in gpiochip_setup_dev(): unreferenced object 0xffff88810b406400 (size 512): comm "python3", pid 1682, jiffies 4295346908 (age 24.090s) backtrace: kmalloc_trace device_add device_private_init at drivers/base/core.c:3361 (inlined by) device_add at drivers/base/core.c:3411 cdev_device_add gpiolib_cdev_register gpiochip_setup_dev gpiochip_add_data_with_key gcdev_register() & gcdev_unregister() would call device_add() & device_del() (no matter CONFIG_GPIO_CDEV is enabled or not) to register/unregister device. However, if device_add() succeeds, some resource (like struct device_private allocated by device_private_init()) is not released by device_del(). Therefore, after device_add() succeeds by gcdev_register(), it needs to call put_device() to release resource in the error handle path. Here we move forward the register of release function, and let it release every piece of resource by put_device() instead of kfree(). While at it, fix another subtle issue, i.e. when gc->ngpio is equal to 0, we still call kcalloc() and, in case of further error, kfree() on the ZERO_PTR pointer, which is not NULL. It's not a bug per se, but rather waste of the resources and potentially wrong expectation about contents of the gdev->descs variable.(CVE-2022-48975)
In the Linux kernel, the following vulnerability has been resolved: riscv: Sync efi page table's kernel mappings before switching The EFI page table is initially created as a copy of the kernel page table. With VMAP_STACK enabled, kernel stacks are allocated in the vmalloc area: if the stack is allocated in a new PGD (one that was not present at the moment of the efi page table creation or not synced in a previous vmalloc fault), the kernel will take a trap when switching to the efi page table when the vmalloc kernel stack is accessed, resulting in a kernel panic. Fix that by updating the efi kernel mappings before switching to the efi page table.(CVE-2022-49004)
In the Linux kernel, the following vulnerability has been resolved:
memcg_write_event_control(): fix a user-triggerable oops
we are not guaranteed that anything past the terminating NUL is mapped (let alone initialized with anything sane).(CVE-2024-45021)
In the Linux kernel, the following vulnerability has been resolved:
gtp: fix a potential NULL pointer dereference
When sockfd_lookup() fails, gtp_encap_enable_socket() returns a NULL pointer, but its callers only check for error pointers thus miss the NULL pointer case.
Fix it by returning an error pointer with the error code carried from sockfd_lookup().
(I found this bug during code inspection.)(CVE-2024-46677)
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Check BIOS images before it is used
BIOS images may fail to load and null checks are added before they are used.
This fixes 6 NULL_RETURNS issues reported by Coverity.(CVE-2024-46809)
In the Linux kernel, the following vulnerability has been resolved:
smack: tcp: ipv4, fix incorrect labeling
Currently, Smack mirrors the label of incoming tcp/ipv4 connections: when a label 'foo' connects to a label 'bar' with tcp/ipv4, 'foo' always gets 'foo' in returned ipv4 packets. So, 1) returned packets are incorrectly labeled ('foo' instead of 'bar') 2) 'bar' can write to 'foo' without being authorized to write.
Here is a scenario how to see this:
-
Take two machines, let's call them C and S, with active Smack in the default state (no settings, no rules, no labeled hosts, only builtin labels)
-
At S, add Smack rule 'foo bar w' (labels 'foo' and 'bar' are instantiated at S at this moment)
-
At S, at label 'bar', launch a program that listens for incoming tcp/ipv4 connections
-
From C, at label 'foo', connect to the listener at S. (label 'foo' is instantiated at C at this moment) Connection succeedes and works.
-
Send some data in both directions.
- Collect network traffic of this connection.
All packets in both directions are labeled with the CIPSO of the label 'foo'. Hence, label 'bar' writes to 'foo' without being authorized, and even without ever being known at C.
If anybody cares: exactly the same happens with DCCP.
This behavior 1st manifested in release 2.6.29.4 (see Fixes below) and it looks unintentional. At least, no explanation was provided.
I changed returned packes label into the 'bar', to bring it into line with the Smack documentation claims.(CVE-2024-47659)
In the Linux kernel, the following vulnerability has been resolved:
fsnotify: clear PARENT_WATCHED flags lazily
In some setups directories can have many (usually negative) dentries. Hence __fsnotify_update_child_dentry_flags() function can take a significant amount of time. Since the bulk of this function happens under inode->i_lock this causes a significant contention on the lock when we remove the watch from the directory as the __fsnotify_update_child_dentry_flags() call from fsnotify_recalc_mask() races with __fsnotify_update_child_dentry_flags() calls from __fsnotify_parent() happening on children. This can lead upto softlockup reports reported by users.
Fix the problem by calling fsnotify_update_children_dentry_flags() to set PARENT_WATCHED flags only when parent starts watching children.
When parent stops watching children, clear false positive PARENT_WATCHED flags lazily in __fsnotify_parent() for each accessed child.(CVE-2024-47660)
In the Linux kernel, the following vulnerability has been resolved:
lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc()
If we need to increase the tree depth, allocate a new node, and then race with another thread that increased the tree depth before us, we'll still have a preallocated node that might be used later.
If we then use that node for a new non-root node, it'll still have a pointer to the old root instead of being zeroed - fix this by zeroing it in the cmpxchg failure path.(CVE-2024-47668)
In the Linux kernel, the following vulnerability has been resolved:
wifi: iwlwifi: mvm: pause TCM when the firmware is stopped
Not doing so will make us send a host command to the transport while the firmware is not alive, which will trigger a WARNING.
bad state = 0 WARNING: CPU: 2 PID: 17434 at drivers/net/wireless/intel/iwlwifi/iwl-trans.c:115 iwl_trans_send_cmd+0x1cb/0x1e0 [iwlwifi] RIP: 0010:iwl_trans_send_cmd+0x1cb/0x1e0 [iwlwifi] Call Trace: <TASK> iwl_mvm_send_cmd+0x40/0xc0 [iwlmvm] iwl_mvm_config_scan+0x198/0x260 [iwlmvm] iwl_mvm_recalc_tcm+0x730/0x11d0 [iwlmvm] iwl_mvm_tcm_work+0x1d/0x30 [iwlmvm] process_one_work+0x29e/0x640 worker_thread+0x2df/0x690 ? rescuer_thread+0x540/0x540 kthread+0x192/0x1e0 ? set_kthread_struct+0x90/0x90 ret_from_fork+0x22/0x30(CVE-2024-47673)
In the Linux kernel, the following vulnerability has been resolved: f2fs: get rid of online repaire on corrupted directory syzbot reports a f2fs bug as below: kernel BUG at fs/f2fs/inode.c:896! RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896 Call Trace: evict+0x532/0x950 fs/inode.c:704 dispose_list fs/inode.c:747 [inline] evict_inodes+0x5f9/0x690 fs/inode.c:797 generic_shutdown_super+0x9d/0x2d0 fs/super.c:627 kill_block_super+0x44/0x90 fs/super.c:1696 kill_f2fs_super+0x344/0x690 fs/f2fs/super.c:4898 deactivate_locked_super+0xc4/0x130 fs/super.c:473 cleanup_mnt+0x41f/0x4b0 fs/namespace.c:1373 task_work_run+0x24f/0x310 kernel/task_work.c:228 ptrace_notify+0x2d2/0x380 kernel/signal.c:2402 ptrace_report_syscall include/linux/ptrace.h:415 [inline] ptrace_report_syscall_exit include/linux/ptrace.h:477 [inline] syscall_exit_work+0xc6/0x190 kernel/entry/common.c:173 syscall_exit_to_user_mode_prepare kernel/entry/common.c:200 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:205 [inline] syscall_exit_to_user_mode+0x279/0x370 kernel/entry/common.c:218 do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896 Online repaire on corrupted directory in f2fs_lookup() can generate dirty data/meta while racing w/ readonly remount, it may leave dirty inode after filesystem becomes readonly, however, checkpoint() will skips flushing dirty inode in a state of readonly mode, result in above panic. Let's get rid of online repaire in f2fs_lookup(), and leave the work to fsck.f2fs.(CVE-2024-47690)
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid use-after-free in f2fs_stop_gc_thread() syzbot reports a f2fs bug as below: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114 print_report+0xe8/0x550 mm/kasan/report.c:491 kasan_report+0x143/0x180 mm/kasan/report.c:601 kasan_check_range+0x282/0x290 mm/kasan/generic.c:189 instrument_atomic_read_write include/linux/instrumented.h:96 [inline] atomic_fetch_add_relaxed include/linux/atomic/atomic-instrumented.h:252 [inline] __refcount_add include/linux/refcount.h:184 [inline] __refcount_inc include/linux/refcount.h:241 [inline] refcount_inc include/linux/refcount.h:258 [inline] get_task_struct include/linux/sched/task.h:118 [inline] kthread_stop+0xca/0x630 kernel/kthread.c:704 f2fs_stop_gc_thread+0x65/0xb0 fs/f2fs/gc.c:210 f2fs_do_shutdown+0x192/0x540 fs/f2fs/file.c:2283 f2fs_ioc_shutdown fs/f2fs/file.c:2325 [inline] __f2fs_ioctl+0x443a/0xbe60 fs/f2fs/file.c:4325 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f The root cause is below race condition, it may cause use-after-free issue in sbi->gc_th pointer. - remount - f2fs_remount - f2fs_stop_gc_thread - kfree(gc_th) - f2fs_ioc_shutdown - f2fs_do_shutdown - f2fs_stop_gc_thread - kthread_stop(gc_th->f2fs_gc_task) : sbi->gc_thread = NULL; We will call f2fs_do_shutdown() in two paths: - for f2fs_ioc_shutdown() path, we should grab sb->s_umount semaphore for fixing. - for f2fs_shutdown() path, it's safe since caller has already grabbed sb->s_umount semaphore.(CVE-2024-47691)
In the Linux kernel, the following vulnerability has been resolved: IB/core: Fix ib_cache_setup_one error flow cleanup When ib_cache_update return an error, we exit ib_cache_setup_one instantly with no proper cleanup, even though before this we had already successfully done gid_table_setup_one, that results in the kernel WARN below. Do proper cleanup using gid_table_cleanup_one before returning the err in order to fix the issue. WARNING: CPU: 4 PID: 922 at drivers/infiniband/core/cache.c:806 gid_table_release_one+0x181/0x1a0 Modules linked in: CPU: 4 UID: 0 PID: 922 Comm: c_repro Not tainted 6.11.0-rc1+ #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:gid_table_release_one+0x181/0x1a0 Code: 44 8b 38 75 0c e8 2f cb 34 ff 4d 8b b5 28 05 00 00 e8 23 cb 34 ff 44 89 f9 89 da 4c 89 f6 48 c7 c7 d0 58 14 83 e8 4f de 21 ff <0f> 0b 4c 8b 75 30 e9 54 ff ff ff 48 8 3 c4 10 5b 5d 41 5c 41 5d 41 RSP: 0018:ffffc90002b835b0 EFLAGS: 00010286 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff811c8527 RDX: 0000000000000000 RSI: ffffffff811c8534 RDI: 0000000000000001 RBP: ffff8881011b3d00 R08: ffff88810b3abe00 R09: 205d303839303631 R10: 666572207972746e R11: 72746e6520444947 R12: 0000000000000001 R13: ffff888106390000 R14: ffff8881011f2110 R15: 0000000000000001 FS: 00007fecc3b70800(0000) GS:ffff88813bd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020000340 CR3: 000000010435a001 CR4: 00000000003706b0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ? show_regs+0x94/0xa0 ? __warn+0x9e/0x1c0 ? gid_table_release_one+0x181/0x1a0 ? report_bug+0x1f9/0x340 ? gid_table_release_one+0x181/0x1a0 ? handle_bug+0xa2/0x110 ? exc_invalid_op+0x31/0xa0 ? asm_exc_invalid_op+0x16/0x20 ? __warn_printk+0xc7/0x180 ? __warn_printk+0xd4/0x180 ? gid_table_release_one+0x181/0x1a0 ib_device_release+0x71/0xe0 ? __pfx_ib_device_release+0x10/0x10 device_release+0x44/0xd0 kobject_put+0x135/0x3d0 put_device+0x20/0x30 rxe_net_add+0x7d/0xa0 rxe_newlink+0xd7/0x190 nldev_newlink+0x1b0/0x2a0 ? __pfx_nldev_newlink+0x10/0x10 rdma_nl_rcv_msg+0x1ad/0x2e0 rdma_nl_rcv_skb.constprop.0+0x176/0x210 netlink_unicast+0x2de/0x400 netlink_sendmsg+0x306/0x660 __sock_sendmsg+0x110/0x120 _syssendmsg+0x30e/0x390 _sys_sendmsg+0x9b/0xf0 ? kstrtouint+0x6e/0xa0 ? kstrtouint_from_user+0x7c/0xb0 ? get_pid_task+0xb0/0xd0 ? proc_fail_nth_write+0x5b/0x140 ? __fget_light+0x9a/0x200 ? preempt_count_add+0x47/0xa0 __sys_sendmsg+0x61/0xd0 do_syscall_64+0x50/0x110 entry_SYSCALL_64_after_hwframe+0x76/0x7e(CVE-2024-47693)
In the Linux kernel, the following vulnerability has been resolved: RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency In the commit aee2424246f9 ("RDMA/iwcm: Fix a use-after-free related to destroying CM IDs"), the function flush_workqueue is invoked to flush the work queue iwcm_wq. But at that time, the work queue iwcm_wq was created via the function alloc_ordered_workqueue without the flag WQ_MEM_RECLAIM. Because the current process is trying to flush the whole iwcm_wq, if iwcm_wq doesn't have the flag WQ_MEM_RECLAIM, verify that the current process is not reclaiming memory or running on a workqueue which doesn't have the flag WQ_MEM_RECLAIM as that can break forward-progress guarantee leading to a deadlock. The call trace is as below: [ 125.350876][ T1430] Call Trace: [ 125.356281][ T1430] <TASK> [ 125.361285][ T1430] ? __warn (kernel/panic.c:693) [ 125.367640][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.375689][ T1430] ? report_bug (lib/bug.c:180 lib/bug.c:219) [ 125.382505][ T1430] ? handle_bug (arch/x86/kernel/traps.c:239) [ 125.388987][ T1430] ? exc_invalid_op (arch/x86/kernel/traps.c:260 (discriminator 1)) [ 125.395831][ T1430] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:621) [ 125.403125][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.410984][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.418764][ T1430] __flush_workqueue (kernel/workqueue.c:3970) [ 125.426021][ T1430] ? __pfxmightresched (kernel/sched/core.c:10151) [ 125.433431][ T1430] ? destroy_cm_id (drivers/infiniband/core/iwcm.c:375) iw_cm [ 125.441209][ T1430] ? pfxflushworkqueue (kernel/workqueue.c:3910) [ 125.473900][ T1430] ? _raw_spin_lock_irqsave (arch/x86/include/asm/atomic.h:107 include/linux/atomic/atomic-arch-fallback.h:2170 include/linux/atomic/atomic-instrumented.h:1302 include/asm-generic/qspinlock.h:111 include/linux/spinlock.h:187 include/linux/spinlock_api_smp.h:111 kernel/locking/spinlock.c:162) [ 125.473909][ T1430] ? pfx__raw_spin_lock_irqsave (kernel/locking/spinlock.c:161) [ 125.482537][ T1430] _destroy_id (drivers/infiniband/core/cma.c:2044) rdma_cm [ 125.495072][ T1430] nvme_rdma_free_queue (drivers/nvme/host/rdma.c:656 drivers/nvme/host/rdma.c:650) nvme_rdma [ 125.505827][ T1430] nvme_rdma_reset_ctrl_work (drivers/nvme/host/rdma.c:2180) nvme_rdma [ 125.505831][ T1430] process_one_work (kernel/workqueue.c:3231) [ 125.515122][ T1430] worker_thread (kernel/workqueue.c:3306 kernel/workqueue.c:3393) [ 125.515127][ T1430] ? __pfx_worker_thread (kernel/workqueue.c:3339) [ 125.531837][ T1430] kthread (kernel/kthread.c:389) [ 125.539864][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.550628][ T1430] ret_from_fork (arch/x86/kernel/process.c:147) [ 125.558840][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.558844][ T1430] ret_from_fork_asm (arch/x86/entry/entry_64.S:257) [ 125.566487][ T1430] </TASK> [ 125.566488][ T1430] ---[ end trace 0000000000000000 ]---(CVE-2024-47696)
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential null-ptr-deref in nilfs_btree_insert() Patch series "nilfs2: fix potential issues with empty b-tree nodes". This series addresses three potential issues with empty b-tree nodes that can occur with corrupted filesystem images, including one recently discovered by syzbot. This patch (of 3): If a b-tree is broken on the device, and the b-tree height is greater than 2 (the level of the root node is greater than 1) even if the number of child nodes of the b-tree root is 0, a NULL pointer dereference occurs in nilfs_btree_prepare_insert(), which is called from nilfs_btree_insert(). This is because, when the number of child nodes of the b-tree root is 0, nilfs_btree_do_lookup() does not set the block buffer head in any of path[x].bp_bh, leaving it as the initial value of NULL, but if the level of the b-tree root node is greater than 1, nilfs_btree_get_nonroot_node(), which accesses the buffer memory of path[x].bp_bh, is called. Fix this issue by adding a check to nilfs_btree_root_broken(), which performs sanity checks when reading the root node from the device, to detect this inconsistency. Thanks to Lizhi Xu for trying to solve the bug and clarifying the cause early on.(CVE-2024-47699)
In the Linux kernel, the following vulnerability has been resolved: ext4: avoid OOB when system.data xattr changes underneath the filesystem When looking up for an entry in an inlined directory, if e_value_offs is changed underneath the filesystem by some change in the block device, it will lead to an out-of-bounds access that KASAN detects as an UAF. EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none. loop0: detected capacity change from 2048 to 2047 ================================================================== BUG: KASAN: use-after-free in ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500 Read of size 1 at addr ffff88803e91130f by task syz-executor269/5103 CPU: 0 UID: 0 PID: 5103 Comm: syz-executor269 Not tainted 6.11.0-rc4-syzkaller #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Call Trace: <TASK> __dump_stack lib/dump_stack.c:93 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119 print_address_description mm/kasan/report.c:377 [inline] print_report+0x169/0x550 mm/kasan/report.c:488 kasan_report+0x143/0x180 mm/kasan/report.c:601 ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500 ext4_find_inline_entry+0x4be/0x5e0 fs/ext4/inline.c:1697 __ext4_find_entry+0x2b4/0x1b30 fs/ext4/namei.c:1573 ext4_lookup_entry fs/ext4/namei.c:1727 [inline] ext4_lookup+0x15f/0x750 fs/ext4/namei.c:1795 lookup_one_qstr_excl+0x11f/0x260 fs/namei.c:1633 filename_create+0x297/0x540 fs/namei.c:3980 do_symlinkat+0xf9/0x3a0 fs/namei.c:4587 __do_sys_symlinkat fs/namei.c:4610 [inline] __se_sys_symlinkat fs/namei.c:4607 [inline] __x64_sys_symlinkat+0x95/0xb0 fs/namei.c:4607 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f3e73ced469 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 21 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fff4d40c258 EFLAGS: 00000246 ORIG_RAX: 000000000000010a RAX: ffffffffffffffda RBX: 0032656c69662f2e RCX: 00007f3e73ced469 RDX: 0000000020000200 RSI: 00000000ffffff9c RDI: 00000000200001c0 RBP: 0000000000000000 R08: 00007fff4d40c290 R09: 00007fff4d40c290 R10: 0023706f6f6c2f76 R11: 0000000000000246 R12: 00007fff4d40c27c R13: 0000000000000003 R14: 431bde82d7b634db R15: 00007fff4d40c2b0 </TASK> Calling ext4_xattr_ibody_find right after reading the inode with ext4_get_inode_loc will lead to a check of the validity of the xattrs, avoiding this problem.(CVE-2024-47701)
In the Linux kernel, the following vulnerability has been resolved: bpf, lsm: Add check for BPF LSM return value A bpf prog returning a positive number attached to file_alloc_security hook makes kernel panic. This happens because file system can not filter out the positive number returned by the LSM prog using IS_ERR, and misinterprets this positive number as a file pointer. Given that hook file_alloc_security never returned positive number before the introduction of BPF LSM, and other BPF LSM hooks may encounter similar issues, this patch adds LSM return value check in verifier, to ensure no unexpected value is returned.(CVE-2024-47703)
In the Linux kernel, the following vulnerability has been resolved: block: fix potential invalid pointer dereference in blk_add_partition The blk_add_partition() function initially used a single if-condition (IS_ERR(part)) to check for errors when adding a partition. This was modified to handle the specific case of -ENXIO separately, allowing the function to proceed without logging the error in this case. However, this change unintentionally left a path where md_autodetect_dev() could be called without confirming that part is a valid pointer. This commit separates the error handling logic by splitting the initial if-condition, improving code readability and handling specific error scenarios explicitly. The function now distinguishes the general error case from -ENXIO without altering the existing behavior of md_autodetect_dev() calls.(CVE-2024-47705)
In the Linux kernel, the following vulnerability has been resolved: jfs: fix out-of-bounds in dbNextAG() and diAlloc() In dbNextAG() , there is no check for the case where bmp->db_numag is greater or same than MAXAG due to a polluted image, which causes an out-of-bounds. Therefore, a bounds check should be added in dbMount(). And in dbNextAG(), a check for the case where agpref is greater than bmp->db_numag should be added, so an out-of-bounds exception should be prevented. Additionally, a check for the case where agno is greater or same than MAXAG should be added in diAlloc() to prevent out-of-bounds.(CVE-2024-47723)
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to wait dio completion It should wait all existing dio write IOs before block removal, otherwise, previous direct write IO may overwrite data in the block which may be reused by other inode.(CVE-2024-47726)
In the Linux kernel, the following vulnerability has been resolved: padata: use integer wrap around to prevent deadlock on seq_nr overflow When submitting more than 2^32 padata objects to padata_do_serial, the current sorting implementation incorrectly sorts padata objects with overflowed seq_nr, causing them to be placed before existing objects in the reorder list. This leads to a deadlock in the serialization process as padata_find_next cannot match padata->seq_nr and pd->processed because the padata instance with overflowed seq_nr will be selected next. To fix this, we use an unsigned integer wrap around to correctly sort padata objects in scenarios with integer overflow.(CVE-2024-47739)
In the Linux kernel, the following vulnerability has been resolved: firmware_loader: Block path traversal Most firmware names are hardcoded strings, or are constructed from fairly constrained format strings where the dynamic parts are just some hex numbers or such. However, there are a couple codepaths in the kernel where firmware file names contain string components that are passed through from a device or semi-privileged userspace; the ones I could find (not counting interfaces that require root privileges) are: - lpfc_sli4_request_firmware_update() seems to construct the firmware filename from "ModelName", a string that was previously parsed out of some descriptor ("Vital Product Data") in lpfc_fill_vpd() - nfp_net_fw_find() seems to construct a firmware filename from a model name coming from nfp_hwinfo_lookup(pf->hwinfo, "nffw.partno"), which I think parses some descriptor that was read from the device. (But this case likely isn't exploitable because the format string looks like "netronome/nic_%s", and there shouldn't be any folders starting with "netronome/nic_". The previous case was different because there, the "%s" is at the start of the format string.) - module_flash_fw_schedule() is reachable from the ETHTOOL_MSG_MODULE_FW_FLASH_ACT netlink command, which is marked as GENL_UNS_ADMIN_PERM (meaning CAP_NET_ADMIN inside a user namespace is enough to pass the privilege check), and takes a userspace-provided firmware name. (But I think to reach this case, you need to have CAP_NET_ADMIN over a network namespace that a special kind of ethernet device is mapped into, so I think this is not a viable attack path in practice.) Fix it by rejecting any firmware names containing ".." path components. For what it's worth, I went looking and haven't found any USB device drivers that use the firmware loader dangerously.(CVE-2024-47742)
In the Linux kernel, the following vulnerability has been resolved: vhost_vdpa: assign irq bypass producer token correctly We used to call irq_bypass_unregister_producer() in vhost_vdpa_setup_vq_irq() which is problematic as we don't know if the token pointer is still valid or not. Actually, we use the eventfd_ctx as the token so the life cycle of the token should be bound to the VHOST_SET_VRING_CALL instead of vhost_vdpa_setup_vq_irq() which could be called by set_status(). Fixing this by setting up irq bypass producer's token when handling VHOST_SET_VRING_CALL and un-registering the producer before calling vhost_vring_ioctl() to prevent a possible use after free as eventfd could have been released in vhost_vring_ioctl(). And such registering and unregistering will only be done if DRIVER_OK is set.(CVE-2024-47748)
In the Linux kernel, the following vulnerability has been resolved: PCI: keystone: Fix if-statement expression in ks_pcie_quirk() This code accidentally uses && where || was intended. It potentially results in a NULL dereference. Thus, fix the if-statement expression to use the correct condition. kwilczynski: commit log
In the Linux kernel, the following vulnerability has been resolved: nbd: fix race between timeout and normal completion If request timetout is handled by nbd_requeue_cmd(), normal completion has to be stopped for avoiding to complete this requeued request, other use-after-free can be triggered. Fix the race by clearing NBD_CMD_INFLIGHT in nbd_requeue_cmd(), meantime make sure that cmd->lock is grabbed for clearing the flag and the requeue.(CVE-2024-49855)
In the Linux kernel, the following vulnerability has been resolved: efistub/tpm: Use ACPI reclaim memory for event log to avoid corruption The TPM event log table is a Linux specific construct, where the data produced by the GetEventLog() boot service is cached in memory, and passed on to the OS using an EFI configuration table. The use of EFI_LOADER_DATA here results in the region being left unreserved in the E820 memory map constructed by the EFI stub, and this is the memory description that is passed on to the incoming kernel by kexec, which is therefore unaware that the region should be reserved. Even though the utility of the TPM2 event log after a kexec is questionable, any corruption might send the parsing code off into the weeds and crash the kernel. So let's use EFI_ACPI_RECLAIM_MEMORY instead, which is always treated as reserved by the E820 conversion logic.(CVE-2024-49858)
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to check atomic_file in f2fs ioctl interfaces Some f2fs ioctl interfaces like f2fs_ioc_set_pin_file(), f2fs_move_file_range(), and f2fs_defragment_range() missed to check atomic_write status, which may cause potential race issue, fix it.(CVE-2024-49859)
In the Linux kernel, the following vulnerability has been resolved: ACPI: sysfs: validate return type of _STR method Only buffer objects are valid return values of _STR. If something else is returned description_show() will access invalid memory.(CVE-2024-49860)
In the Linux kernel, the following vulnerability has been resolved: powercap: intel_rapl: Fix off by one in get_rpi() The rp->priv->rpi array is either rpi_msr or rpi_tpmi which have NR_RAPL_PRIMITIVES number of elements. Thus the > needs to be >= to prevent an off by one access.(CVE-2024-49862)
In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate When doing cleanup, if flags without OCFS2_BH_READAHEAD, it may trigger NULL pointer dereference in the following ocfs2_set_buffer_uptodate() if bh is NULL.(CVE-2024-49877)
In the Linux kernel, the following vulnerability has been resolved: drm: omapdrm: Add missing check for alloc_ordered_workqueue As it may return NULL pointer and cause NULL pointer dereference. Add check for the return value of alloc_ordered_workqueue.(CVE-2024-49879)
In the Linux kernel, the following vulnerability has been resolved: ext4: update orig_path in ext4_find_extent() In ext4_find_extent(), if the path is not big enough, we free it and set orig_path to NULL. But after reallocating and successfully initializing the path, we don't update orig_path, in which case the caller gets a valid path but a NULL ppath, and this may cause a NULL pointer dereference or a path memory leak. For example: ext4_split_extent path = ppath = 2000 ext4_find_extent if (depth > path[0].p_maxdepth) kfree(path = 2000); orig_path = path = NULL; path = kcalloc() = 3000 ext4_split_extent_at(ppath = NULL) path = ppath; ex = path[depth].p_ext; // NULL pointer dereference! ================================================================== BUG: kernel NULL pointer dereference, address: 0000000000000010 CPU: 6 UID: 0 PID: 576 Comm: fsstress Not tainted 6.11.0-rc2-dirty #847 RIP: 0010:ext4_split_extent_at+0x6d/0x560 Call Trace: <TASK> ext4_split_extent.isra.0+0xcb/0x1b0 ext4_ext_convert_to_initialized+0x168/0x6c0 ext4_ext_handle_unwritten_extents+0x325/0x4d0 ext4_ext_map_blocks+0x520/0xdb0 ext4_map_blocks+0x2b0/0x690 ext4_iomap_begin+0x20e/0x2c0 [...] ================================================================== Therefore, orig_path is updated when the extent lookup succeeds, so that the caller can safely use path or ppath.(CVE-2024-49881)
In the Linux kernel, the following vulnerability has been resolved: ext4: fix double brelse() the buffer of the extents path In ext4_ext_try_to_merge_up(), set path[1].p_bh to NULL after it has been released, otherwise it may be released twice. An example of what triggers this is as follows: split2 map split1 |--------|-------|--------| ext4_ext_map_blocks ext4_ext_handle_unwritten_extents ext4_split_convert_extents // path->p_depth == 0 ext4_split_extent // 1. do split1 ext4_split_extent_at |ext4_ext_insert_extent | ext4_ext_create_new_leaf | ext4_ext_grow_indepth | le16_add_cpu(&neh->eh_depth, 1) | ext4_find_extent | // return -ENOMEM |// get error and try zeroout |path = ext4_find_extent | path->p_depth = 1 |ext4_ext_try_to_merge | ext4_ext_try_to_merge_up | path->p_depth = 0 | brelse(path[1].p_bh) ---> not set to NULL here |// zeroout success // 2. update path ext4_find_extent // 3. do split2 ext4_split_extent_at ext4_ext_insert_extent ext4_ext_create_new_leaf ext4_ext_grow_indepth le16_add_cpu(&neh->eh_depth, 1) ext4_find_extent path[0].p_bh = NULL; path->p_depth = 1 read_extent_tree_block ---> return err // path[1].p_bh is still the old value ext4_free_ext_path ext4_ext_drop_refs // path->p_depth == 1 brelse(path[1].p_bh) ---> brelse a buffer twice Finally got the following WARRNING when removing the buffer from lru: ============================================ VFS: brelse: Trying to free free buffer WARNING: CPU: 2 PID: 72 at fs/buffer.c:1241 __brelse+0x58/0x90 CPU: 2 PID: 72 Comm: kworker/u19:1 Not tainted 6.9.0-dirty #716 RIP: 0010:__brelse+0x58/0x90 Call Trace: <TASK> __find_get_block+0x6e7/0x810 bdev_getblk+0x2b/0x480 __ext4_get_inode_loc+0x48a/0x1240 ext4_get_inode_loc+0xb2/0x150 ext4_reserve_inode_write+0xb7/0x230 __ext4_mark_inode_dirty+0x144/0x6a0 ext4_ext_insert_extent+0x9c8/0x3230 ext4_ext_map_blocks+0xf45/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] ============================================(CVE-2024-49882)
In the Linux kernel, the following vulnerability has been resolved: ext4: aovid use-after-free in ext4_ext_insert_extent() As Ojaswin mentioned in Link, in ext4_ext_insert_extent(), if the path is reallocated in ext4_ext_create_new_leaf(), we'll use the stale path and cause UAF. Below is a sample trace with dummy values: ext4_ext_insert_extent path = ppath = 2000 ext4_ext_create_new_leaf(ppath) ext4_find_extent(ppath) path = ppath = 2000 if (depth > path[0].p_maxdepth) kfree(path = 2000); ppath = path = NULL; path = kcalloc() = 3000 ppath = 3000; return path; / here path is still 2000, UAF! / eh = path[depth].p_hdr ================================================================== BUG: KASAN: slab-use-after-free in ext4_ext_insert_extent+0x26d4/0x3330 Read of size 8 at addr ffff8881027bf7d0 by task kworker/u36:1/179 CPU: 3 UID: 0 PID: 179 Comm: kworker/u6:1 Not tainted 6.11.0-rc2-dirty #866 Call Trace: <TASK> ext4_ext_insert_extent+0x26d4/0x3330 ext4_ext_map_blocks+0xe22/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 [...] Allocated by task 179: ext4_find_extent+0x81c/0x1f70 ext4_ext_map_blocks+0x146/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 ext4_writepages+0x26d/0x4e0 do_writepages+0x175/0x700 [...] Freed by task 179: kfree+0xcb/0x240 ext4_find_extent+0x7c0/0x1f70 ext4_ext_insert_extent+0xa26/0x3330 ext4_ext_map_blocks+0xe22/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 ext4_writepages+0x26d/0x4e0 do_writepages+0x175/0x700 [...] ================================================================== So use *ppath to update the path to avoid the above problem.(CVE-2024-49883)
In the Linux kernel, the following vulnerability has been resolved: ext4: fix slab-use-after-free in ext4_split_extent_at() We hit the following use-after-free: ================================================================== BUG: KASAN: slab-use-after-free in ext4_split_extent_at+0xba8/0xcc0 Read of size 2 at addr ffff88810548ed08 by task kworker/u20:0/40 CPU: 0 PID: 40 Comm: kworker/u20:0 Not tainted 6.9.0-dirty #724 Call Trace: <TASK> kasan_report+0x93/0xc0 ext4_split_extent_at+0xba8/0xcc0 ext4_split_extent.isra.0+0x18f/0x500 ext4_split_convert_extents+0x275/0x750 ext4_ext_handle_unwritten_extents+0x73e/0x1580 ext4_ext_map_blocks+0xe20/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] Allocated by task 40: __kmalloc_noprof+0x1ac/0x480 ext4_find_extent+0xf3b/0x1e70 ext4_ext_map_blocks+0x188/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] Freed by task 40: kfree+0xf1/0x2b0 ext4_find_extent+0xa71/0x1e70 ext4_ext_insert_extent+0xa22/0x3260 ext4_split_extent_at+0x3ef/0xcc0 ext4_split_extent.isra.0+0x18f/0x500 ext4_split_convert_extents+0x275/0x750 ext4_ext_handle_unwritten_extents+0x73e/0x1580 ext4_ext_map_blocks+0xe20/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] ================================================================== The flow of issue triggering is as follows: ext4_split_extent_at path = ppath ext4_ext_insert_extent(ppath) ext4_ext_create_new_leaf(ppath) ext4_find_extent(orig_path) path = orig_path read_extent_tree_block // return -ENOMEM or -EIO ext4_free_ext_path(path) kfree(path) orig_path = NULL a. If err is -ENOMEM: ext4_ext_dirty(path + path->p_depth) // path use-after-free !!! b. If err is -EIO and we have EXT_DEBUG defined: ext4_ext_show_leaf(path) eh = path[depth].p_hdr // path also use-after-free !!! So when trying to zeroout or fix the extent length, call ext4_find_extent() to update the path. In addition we use ppath directly as an ext4_ext_show_leaf() input to avoid possible use-after-free when EXT_DEBUG is defined, and to avoid unnecessary path updates.(CVE-2024-49884)
In the Linux kernel, the following vulnerability has been resolved: platform/x86: ISST: Fix the KASAN report slab-out-of-bounds bug Attaching SST PCI device to VM causes "BUG: KASAN: slab-out-of-bounds". kasan report: [ 19.411889] ================================================================== [ 19.413702] BUG: KASAN: slab-out-of-bounds in _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.415634] Read of size 8 at addr ffff888829e65200 by task cpuhp/16/113 [ 19.417368] [ 19.418627] CPU: 16 PID: 113 Comm: cpuhp/16 Tainted: G E 6.9.0 #10 [ 19.420435] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference Platform, BIOS VMW201.00V.20192059.B64.2207280713 07/28/2022 [ 19.422687] Call Trace: [ 19.424091] <TASK> [ 19.425448] dump_stack_lvl+0x5d/0x80 [ 19.426963] ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.428694] print_report+0x19d/0x52e [ 19.430206] ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [ 19.431837] ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.433539] kasan_report+0xf0/0x170 [ 19.435019] ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.436709] _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.438379] ? __pfx_sched_clock_cpu+0x10/0x10 [ 19.439910] isst_if_cpu_online+0x406/0x58f [isst_if_common] [ 19.441573] ? __pfx_isst_if_cpu_online+0x10/0x10 [isst_if_common] [ 19.443263] ? ttwu_queue_wakelist+0x2c1/0x360 [ 19.444797] cpuhp_invoke_callback+0x221/0xec0 [ 19.446337] cpuhp_thread_fun+0x21b/0x610 [ 19.447814] ? __pfx_cpuhp_thread_fun+0x10/0x10 [ 19.449354] smpboot_thread_fn+0x2e7/0x6e0 [ 19.450859] ? __pfx_smpboot_thread_fn+0x10/0x10 [ 19.452405] kthread+0x29c/0x350 [ 19.453817] ? __pfx_kthread+0x10/0x10 [ 19.455253] ret_from_fork+0x31/0x70 [ 19.456685] ? __pfx_kthread+0x10/0x10 [ 19.458114] ret_from_fork_asm+0x1a/0x30 [ 19.459573] </TASK> [ 19.460853] [ 19.462055] Allocated by task 1198: [ 19.463410] kasan_save_stack+0x30/0x50 [ 19.464788] kasan_save_track+0x14/0x30 [ 19.466139] __kasan_kmalloc+0xaa/0xb0 [ 19.467465] __kmalloc+0x1cd/0x470 [ 19.468748] isst_if_cdev_register+0x1da/0x350 [isst_if_common] [ 19.470233] isst_if_mbox_init+0x108/0xff0 [isst_if_mbox_msr] [ 19.471670] do_one_initcall+0xa4/0x380 [ 19.472903] do_init_module+0x238/0x760 [ 19.474105] load_module+0x5239/0x6f00 [ 19.475285] init_module_from_file+0xd1/0x130 [ 19.476506] idempotent_init_module+0x23b/0x650 [ 19.477725] __x64_sys_finit_module+0xbe/0x130 [ 19.476506] idempotent_init_module+0x23b/0x650 [ 19.477725] __x64_sys_finit_module+0xbe/0x130 [ 19.478920] do_syscall_64+0x82/0x160 [ 19.480036] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 19.481292] [ 19.482205] The buggy address belongs to the object at ffff888829e65000 which belongs to the cache kmalloc-512 of size 512 [ 19.484818] The buggy address is located 0 bytes to the right of allocated 512-byte region [ffff888829e65000, ffff888829e65200) [ 19.487447] [ 19.488328] The buggy address belongs to the physical page: [ 19.489569] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff888829e60c00 pfn:0x829e60 [ 19.491140] head: order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0 [ 19.492466] anon flags: 0x57ffffc0000840(slab|head|node=1|zone=2|lastcpupid=0x1fffff) [ 19.493914] page_type: 0xffffffff() [ 19.494988] raw: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [ 19.496451] raw: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [ 19.497906] head: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [ 19.499379] head: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [ 19.500844] head: 0057ffffc0000003 ffffea0020a79801 ffffea0020a79848 00000000ffffffff [ 19.502316] head: 0000000800000000 0000000000000000 00000000ffffffff 0000000000000000 [ 19.503784] page dumped because: k ---truncated---(CVE-2024-49886)
In the Linux kernel, the following vulnerability has been resolved: ext4: avoid use-after-free in ext4_ext_show_leaf() In ext4_find_extent(), path may be freed by error or be reallocated, so using a previously saved ppath may have been freed and thus may trigger use-after-free, as follows: ext4_split_extent path = ppath; ext4_split_extent_at(ppath) path = ext4_find_extent(ppath) ext4_split_extent_at(ppath) // ext4_find_extent fails to free path // but zeroout succeeds ext4_ext_show_leaf(inode, path) eh = path[depth].p_hdr // path use-after-free !!! Similar to ext4_split_extent_at(), we use ppath directly as an input to ext4_ext_show_leaf(). Fix a spelling error by the way. Same problem in ext4_ext_handle_unwritten_extents(). Since 'path' is only used in ext4_ext_show_leaf(), remove 'path' and use ppath directly. This issue is triggered only when EXT_DEBUG is defined and therefore does not affect functionality.(CVE-2024-49889)
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check stream before comparing them [WHAT & HOW] amdgpu_dm can pass a null stream to dc_is_stream_unchanged. It is necessary to check for null before dereferencing them. This fixes 1 FORWARD_NULL issue reported by Coverity.(CVE-2024-49896)
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add null check for top_pipe_to_program in commit_planes_for_stream This commit addresses a null pointer dereference issue in the commit_planes_for_stream function at line 4140. The issue could occur when top_pipe_to_program is null. The fix adds a check to ensure top_pipe_to_program is not null before accessing its stream_res. This prevents a null pointer dereference. Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.c:4140 commit_planes_for_stream() error: we previously assumed 'top_pipe_to_program' could be null (see line 3906)(CVE-2024-49913)
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add NULL check for clk_mgr and clk_mgr->funcs in dcn30_init_hw This commit addresses a potential null pointer dereference issue in the dcn30_init_hw function. The issue could occur when dc->clk_mgr or dc->clk_mgr->funcs is null. The fix adds a check to ensure dc->clk_mgr and dc->clk_mgr->funcs is not null before accessing its functions. This prevents a potential null pointer dereference. Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c:789 dcn30_init_hw() error: we previously assumed 'dc->clk_mgr' could be null (see line 628)(CVE-2024-49917)
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check null pointers before using them [WHAT & HOW] These pointers are null checked previously in the same function, indicating they might be null as reported by Coverity. As a result, they need to be checked when used again. This fixes 3 FORWARD_NULL issue reported by Coverity.(CVE-2024-49922)
In the Linux kernel, the following vulnerability has been resolved: fbdev: pxafb: Fix possible use after free in pxafb_task() In the pxafb_probe function, it calls the pxafb_init_fbinfo function, after which &fbi->task is associated with pxafb_task. Moreover, within this pxafb_init_fbinfo function, the pxafb_blank function within the &pxafb_ops struct is capable of scheduling work. If we remove the module which will call pxafb_remove to make cleanup, it will call unregister_framebuffer function which can call do_unregister_framebuffer to free fbi->fb through put_fb_info(fb_info), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows: CPU0 CPU1 | pxafb_task pxafb_remove | unregister_framebuffer(info) | do_unregister_framebuffer(fb_info) | put_fb_info(fb_info) | // free fbi->fb | set_ctrlr_state(fbi, state) | __pxafb_lcd_power(fbi, 0) | fbi->lcd_power(on, &fbi->fb.var) | //use fbi->fb Fix it by ensuring that the work is canceled before proceeding with the cleanup in pxafb_remove. Note that only root user can remove the driver at runtime.(CVE-2024-49924)
In the Linux kernel, the following vulnerability has been resolved: blk_iocost: fix more out of bound shifts Recently running UBSAN caught few out of bound shifts in the ioc_forgive_debts() function: UBSAN: shift-out-of-bounds in block/blk-iocost.c:2142:38 shift exponent 80 is too large for 64-bit type 'u64' (aka 'unsigned long long') ... UBSAN: shift-out-of-bounds in block/blk-iocost.c:2144:30 shift exponent 80 is too large for 64-bit type 'u64' (aka 'unsigned long long') ... Call Trace: <IRQ> dump_stack_lvl+0xca/0x130 __ubsan_handle_shift_out_of_bounds+0x22c/0x280 ? __lock_acquire+0x6441/0x7c10 ioc_timer_fn+0x6cec/0x7750 ? blk_iocost_init+0x720/0x720 ? call_timer_fn+0x5d/0x470 call_timer_fn+0xfa/0x470 ? blk_iocost_init+0x720/0x720 __run_timer_base+0x519/0x700 ... Actual impact of this issue was not identified but I propose to fix the undefined behaviour. The proposed fix to prevent those out of bound shifts consist of precalculating exponent before using it the shift operations by taking min value from the actual exponent and maximum possible number of bits.(CVE-2024-49933)
In the Linux kernel, the following vulnerability has been resolved: fs/inode: Prevent dump_mapping() accessing invalid dentry.d_name.name It's observed that a crash occurs during hot-remove a memory device, in which user is accessing the hugetlb. See calltrace as following: ------------[ cut here ]------------ WARNING: CPU: 1 PID: 14045 at arch/x86/mm/fault.c:1278 do_user_addr_fault+0x2a0/0x790 Modules linked in: kmem device_dax cxl_mem cxl_pmem cxl_port cxl_pci dax_hmem dax_pmem nd_pmem cxl_acpi nd_btt cxl_core crc32c_intel nvme virtiofs fuse nvme_core nfit libnvdimm dm_multipath scsi_dh_rdac scsi_dh_emc s mirror dm_region_hash dm_log dm_mod CPU: 1 PID: 14045 Comm: daxctl Not tainted 6.10.0-rc2-lizhijian+ #492 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:do_user_addr_fault+0x2a0/0x790 Code: 48 8b 00 a8 04 0f 84 b5 fe ff ff e9 1c ff ff ff 4c 89 e9 4c 89 e2 be 01 00 00 00 bf 02 00 00 00 e8 b5 ef 24 00 e9 42 fe ff ff <0f> 0b 48 83 c4 08 4c 89 ea 48 89 ee 4c 89 e7 5b 5d 41 5c 41 5d 41 RSP: 0000:ffffc90000a575f0 EFLAGS: 00010046 RAX: ffff88800c303600 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000001000 RSI: ffffffff82504162 RDI: ffffffff824b2c36 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffffc90000a57658 R13: 0000000000001000 R14: ffff88800bc2e040 R15: 0000000000000000 FS: 00007f51cb57d880(0000) GS:ffff88807fd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000001000 CR3: 00000000072e2004 CR4: 00000000001706f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ? __warn+0x8d/0x190 ? do_user_addr_fault+0x2a0/0x790 ? report_bug+0x1c3/0x1d0 ? handle_bug+0x3c/0x70 ? exc_invalid_op+0x14/0x70 ? asm_exc_invalid_op+0x16/0x20 ? do_user_addr_fault+0x2a0/0x790 ? exc_page_fault+0x31/0x200 exc_page_fault+0x68/0x200 <...snip...> BUG: unable to handle page fault for address: 0000000000001000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0 Oops: Oops: 0000 [#1] PREEMPT SMP PTI ---[ end trace 0000000000000000 ]--- BUG: unable to handle page fault for address: 0000000000001000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0 Oops: Oops: 0000 [#1] PREEMPT SMP PTI CPU: 1 PID: 14045 Comm: daxctl Kdump: loaded Tainted: G W 6.10.0-rc2-lizhijian+ #492 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:dentry_name+0x1f4/0x440 <...snip...> ? dentry_name+0x2fa/0x440 vsnprintf+0x1f3/0x4f0 vprintk_store+0x23a/0x540 vprintk_emit+0x6d/0x330 _printk+0x58/0x80 dump_mapping+0x10b/0x1a0 ? __pfx_free_object_rcu+0x10/0x10 __dump_page+0x26b/0x3e0 ? vprintk_emit+0xe0/0x330 ? _printk+0x58/0x80 ? dump_page+0x17/0x50 dump_page+0x17/0x50 do_migrate_range+0x2f7/0x7f0 ? do_migrate_range+0x42/0x7f0 ? offline_pages+0x2f4/0x8c0 offline_pages+0x60a/0x8c0 memory_subsys_offline+0x9f/0x1c0 ? lockdep_hardirqs_on+0x77/0x100 ? _raw_spin_unlock_irqrestore+0x38/0x60 device_offline+0xe3/0x110 state_store+0x6e/0xc0 kernfs_fop_write_iter+0x143/0x200 vfs_write+0x39f/0x560 ksys_write+0x65/0xf0 do_syscall_64+0x62/0x130 Previously, some sanity check have been done in dump_mapping() before the print facility parsing '%pd' though, it's still possible to run into an invalid dentry.d_name.name. Since dump_mapping() only needs to dump the filename only, retrieve it by itself in a safer way to prevent an unnecessary crash. Note that either retrieving the filename with '%pd' or strncpy_from_kernel_nofault(), the filename could be unreliable.(CVE-2024-49934)
In the Linux kernel, the following vulnerability has been resolved: net/xen-netback: prevent UAF in xenvif_flush_hash() During the list_for_each_entry_rcu iteration call of xenvif_flush_hash, kfree_rcu does not exist inside the rcu read critical section, so if kfree_rcu is called when the rcu grace period ends during the iteration, UAF occurs when accessing head->next after the entry becomes free. Therefore, to solve this, you need to change it to list_for_each_entry_safe.(CVE-2024-49936)
In the Linux kernel, the following vulnerability has been resolved: l2tp: prevent possible tunnel refcount underflow When a session is created, it sets a backpointer to its tunnel. When the session refcount drops to 0, l2tp_session_free drops the tunnel refcount if session->tunnel is non-NULL. However, session->tunnel is set in l2tp_session_create, before the tunnel refcount is incremented by l2tp_session_register, which leaves a small window where session->tunnel is non-NULL when the tunnel refcount hasn't been bumped. Moving the assignment to l2tp_session_register is trivial but l2tp_session_create calls l2tp_session_set_header_len which uses session->tunnel to get the tunnel's encap. Add an encap arg to l2tp_session_set_header_len to avoid using session->tunnel. If l2tpv3 sessions have colliding IDs, it is possible for l2tp_v3_session_get to race with l2tp_session_register and fetch a session which doesn't yet have session->tunnel set. Add a check for this case.(CVE-2024-49940)
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix uaf in l2cap_connect [Syzbot reported] BUG: KASAN: slab-use-after-free in l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949 Read of size 8 at addr ffff8880241e9800 by task kworker/u9:0/54 CPU: 0 UID: 0 PID: 54 Comm: kworker/u9:0 Not tainted 6.11.0-rc6-syzkaller-00268-g788220eee30d #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 Workqueue: hci2 hci_rx_work Call Trace: <TASK> __dump_stack lib/dump_stack.c:93 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:119 print_address_description mm/kasan/report.c:377 [inline] print_report+0xc3/0x620 mm/kasan/report.c:488 kasan_report+0xd9/0x110 mm/kasan/report.c:601 l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949 l2cap_connect_req net/bluetooth/l2cap_core.c:4080 [inline] l2cap_bredr_sig_cmd net/bluetooth/l2cap_core.c:4772 [inline] l2cap_sig_channel net/bluetooth/l2cap_core.c:5543 [inline] l2cap_recv_frame+0xf0b/0x8eb0 net/bluetooth/l2cap_core.c:6825 l2cap_recv_acldata+0x9b4/0xb70 net/bluetooth/l2cap_core.c:7514 hci_acldata_packet net/bluetooth/hci_core.c:3791 [inline] hci_rx_work+0xaab/0x1610 net/bluetooth/hci_core.c:4028 process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231 process_scheduled_works kernel/workqueue.c:3312 [inline] worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389 kthread+0x2c1/0x3a0 kernel/kthread.c:389 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 ... Freed by task 5245: kasan_save_stack+0x33/0x60 mm/kasan/common.c:47 kasan_save_track+0x14/0x30 mm/kasan/common.c:68 kasan_save_free_info+0x3b/0x60 mm/kasan/generic.c:579 poison_slab_object+0xf7/0x160 mm/kasan/common.c:240 __kasan_slab_free+0x32/0x50 mm/kasan/common.c:256 kasan_slab_free include/linux/kasan.h:184 [inline] slab_free_hook mm/slub.c:2256 [inline] slab_free mm/slub.c:4477 [inline] kfree+0x12a/0x3b0 mm/slub.c:4598 l2cap_conn_free net/bluetooth/l2cap_core.c:1810 [inline] kref_put include/linux/kref.h:65 [inline] l2cap_conn_put net/bluetooth/l2cap_core.c:1822 [inline] l2cap_conn_del+0x59d/0x730 net/bluetooth/l2cap_core.c:1802 l2cap_connect_cfm+0x9e6/0xf80 net/bluetooth/l2cap_core.c:7241 hci_connect_cfm include/net/bluetooth/hci_core.h:1960 [inline] hci_conn_failed+0x1c3/0x370 net/bluetooth/hci_conn.c:1265 hci_abort_conn_sync+0x75a/0xb50 net/bluetooth/hci_sync.c:5583 abort_conn_sync+0x197/0x360 net/bluetooth/hci_conn.c:2917 hci_cmd_sync_work+0x1a4/0x410 net/bluetooth/hci_sync.c:328 process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231 process_scheduled_works kernel/workqueue.c:3312 [inline] worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389 kthread+0x2c1/0x3a0 kernel/kthread.c:389 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244(CVE-2024-49950)
In the Linux kernel, the following vulnerability has been resolved: static_call: Replace pointless WARN_ON() in static_call_module_notify() static_call_module_notify() triggers a WARN_ON(), when memory allocation fails in __static_call_add_module(). That's not really justified, because the failure case must be correctly handled by the well known call chain and the error code is passed through to the initiating userspace application. A memory allocation fail is not a fatal problem, but the WARN_ON() takes the machine out when panic_on_warn is set. Replace it with a pr_warn().(CVE-2024-49954)
In the Linux kernel, the following vulnerability has been resolved: ACPI: battery: Fix possible crash when unregistering a battery hook When a battery hook returns an error when adding a new battery, then the battery hook is automatically unregistered. However the battery hook provider cannot know that, so it will later call battery_hook_unregister() on the already unregistered battery hook, resulting in a crash. Fix this by using the list head to mark already unregistered battery hooks as already being unregistered so that they can be ignored by battery_hook_unregister().(CVE-2024-49955)
In the Linux kernel, the following vulnerability has been resolved: ocfs2: reserve space for inline xattr before attaching reflink tree One of our customers reported a crash and a corrupted ocfs2 filesystem. The crash was due to the detection of corruption. Upon troubleshooting, the fsck -fn output showed the below corruption [EXTENT_LIST_FREE] Extent list in owner 33080590 claims 230 as the next free chain record, but fsck believes the largest valid value is 227. Clamp the next record value? n The stat output from the debugfs.ocfs2 showed the following corruption where the "Next Free Rec:" had overshot the "Count:" in the root metadata block. Inode: 33080590 Mode: 0640 Generation: 2619713622 (0x9c25a856) FS Generation: 904309833 (0x35e6ac49) CRC32: 00000000 ECC: 0000 Type: Regular Attr: 0x0 Flags: Valid Dynamic Features: (0x16) HasXattr InlineXattr Refcounted Extended Attributes Block: 0 Extended Attributes Inline Size: 256 User: 0 (root) Group: 0 (root) Size: 281320357888 Links: 1 Clusters: 141738 ctime: 0x66911b56 0x316edcb8 -- Fri Jul 12 06:02:30.829349048 2024 atime: 0x66911d6b 0x7f7a28d -- Fri Jul 12 06:11:23.133669517 2024 mtime: 0x66911b56 0x12ed75d7 -- Fri Jul 12 06:02:30.317552087 2024 dtime: 0x0 -- Wed Dec 31 17:00:00 1969 Refcount Block: 2777346 Last Extblk: 2886943 Orphan Slot: 0 Sub Alloc Slot: 0 Sub Alloc Bit: 14 Tree Depth: 1 Count: 227 Next Free Rec: 230 ## Offset Clusters Block# 0 0 2310 2776351 1 2310 2139 2777375 2 4449 1221 2778399 3 5670 731 2779423 4 6401 566 2780447 ....... .... ....... ....... .... ....... The issue was in the reflink workfow while reserving space for inline xattr. The problematic function is ocfs2_reflink_xattr_inline(). By the time this function is called the reflink tree is already recreated at the destination inode from the source inode. At this point, this function reserves space for inline xattrs at the destination inode without even checking if there is space at the root metadata block. It simply reduces the l_count from 243 to 227 thereby making space of 256 bytes for inline xattr whereas the inode already has extents beyond this index (in this case up to 230), thereby causing corruption. The fix for this is to reserve space for inline metadata at the destination inode before the reflink tree gets recreated. The customer has verified the fix.(CVE-2024-49958)
In the Linux kernel, the following vulnerability has been resolved: r8169: add tally counter fields added with RTL8125 RTL8125 added fields to the tally counter, what may result in the chip dma'ing these new fields to unallocated memory. Therefore make sure that the allocated memory area is big enough to hold all of the tally counter values, even if we use only parts of it.(CVE-2024-49973)
In the Linux kernel, the following vulnerability has been resolved: uprobes: fix kernel info leak via "[uprobes]" vma xol_add_vma() maps the uninitialized page allocated by __create_xol_area() into userspace. On some architectures (x86) this memory is readable even without VM_READ, VM_EXEC results in the same pgprot_t as VM_EXEC|VM_READ, although this doesn't really matter, debugger can read this memory anyway.(CVE-2024-49975)
In the Linux kernel, the following vulnerability has been resolved: gso: fix udp gso fraglist segmentation after pull from frag_list Detect gso fraglist skbs with corrupted geometry (see below) and pass these to skb_segment instead of skb_segment_list, as the first can segment them correctly. Valid SKB_GSO_FRAGLIST skbs - consist of two or more segments - the head_skb holds the protocol headers plus first gso_size - one or more frag_list skbs hold exactly one segment - all but the last must be gso_size Optional datapath hooks such as NAT and BPF (bpf_skb_pull_data) can modify these skbs, breaking these invariants. In extreme cases they pull all data into skb linear. For UDP, this causes a NULL ptr deref in __udpv4_gso_segment_list_csum at udp_hdr(seg->next)->dest. Detect invalid geometry due to pull, by checking head_skb size. Don't just drop, as this may blackhole a destination. Convert to be able to pass to regular skb_segment.(CVE-2024-49978)
In the Linux kernel, the following vulnerability has been resolved: media: venus: fix use after free bug in venus_remove due to race condition in venus_probe, core->work is bound with venus_sys_error_handler, which is used to handle error. The code use core->sys_err_done to make sync work. The core->work is started in venus_event_notify. If we call venus_remove, there might be an unfished work. The possible sequence is as follows: CPU0 CPU1 |venus_sys_error_handler venus_remove | hfi_destroy | venus_hfi_destroy | kfree(hdev); | |hfi_reinit |venus_hfi_queues_reinit |//use hdev Fix it by canceling the work in venus_remove.(CVE-2024-49981)
In the Linux kernel, the following vulnerability has been resolved: drm/stm: Avoid use-after-free issues with crtc and plane ltdc_load() calls functions drm_crtc_init_with_planes(), drm_universal_plane_init() and drm_encoder_init(). These functions should not be called with parameters allocated with devm_kzalloc() to avoid use-after-free issues [1]. Use allocations managed by the DRM framework. Found by Linux Verification Center (linuxtesting.org). [1] https://lore.kernel.org/lkml/u366i76e3qhh3ra5oxrtngjtm2u5lterkekcz6y2jkndhuxzli@diujon4h7qwb/(CVE-2024-49992)
In the Linux kernel, the following vulnerability has been resolved: tipc: guard against string buffer overrun Smatch reports that copying media_name and if_name to name_parts may overwrite the destination. .../bearer.c:166 bearer_name_validate() error: strcpy() 'media_name' too large for 'name_parts->media_name' (32 vs 16) .../bearer.c:167 bearer_name_validate() error: strcpy() 'if_name' too large for 'name_parts->if_name' (1010102 vs 16) This does seem to be the case so guard against this possibility by using strscpy() and failing if truncation occurs. Introduced by commit b97bf3fd8f6a ("[TIPC] Initial merge") Compile tested only.(CVE-2024-49995)
In the Linux kernel, the following vulnerability has been resolved: cifs: Fix buffer overflow when parsing NFS reparse points ReparseDataLength is sum of the InodeType size and DataBuffer size. So to get DataBuffer size it is needed to subtract InodeType's size from ReparseDataLength. Function cifs_strndup_from_utf16() is currentlly accessing buf->DataBuffer at position after the end of the buffer because it does not subtract InodeType size from the length. Fix this problem and correctly subtract variable len. Member InodeType is present only when reparse buffer is large enough. Check for ReparseDataLength before accessing InodeType to prevent another invalid memory access. Major and minor rdev values are present also only when reparse buffer is large enough. Check for reparse buffer size before calling reparse_mkdev().(CVE-2024-49996)
In the Linux kernel, the following vulnerability has been resolved: static_call: Handle module init failure correctly in static_call_del_module() Module insertion invokes static_call_add_module() to initialize the static calls in a module. static_call_add_module() invokes __static_call_init(), which allocates a struct static_call_mod to either encapsulate the built-in static call sites of the associated key into it so further modules can be added or to append the module to the module chain. If that allocation fails the function returns with an error code and the module core invokes static_call_del_module() to clean up eventually added static_call_mod entries. This works correctly, when all keys used by the module were converted over to a module chain before the failure. If not then static_call_del_module() causes a #GP as it blindly assumes that key::mods points to a valid struct static_call_mod. The problem is that key::mods is not a individual struct member of struct static_call_key, it's part of a union to save space: union { / bit 0: 0 = mods, 1 = sites / unsigned long type; struct static_call_mod mods; struct static_call_site sites; }; key::sites is a pointer to the list of built-in usage sites of the static call. The type of the pointer is differentiated by bit 0. A mods pointer has the bit clear, the sites pointer has the bit set. As static_call_del_module() blidly assumes that the pointer is a valid static_call_mod type, it fails to check for this failure case and dereferences the pointer to the list of built-in call sites, which is obviously bogus. Cure it by checking whether the key has a sites or a mods pointer. If it's a sites pointer then the key is not to be touched. As the sites are walked in the same order as in __static_call_init() the site walk can be terminated because all subsequent sites have not been touched by the init code due to the error exit. If it was converted before the allocation fail, then the inner loop which searches for a module match will find nothing. A fail in the second allocation in __static_call_init() is harmless and does not require special treatment. The first allocation succeeded and converted the key to a module chain. That first entry has mod::mod == NULL and mod::next == NULL, so the inner loop of static_call_del_module() will neither find a module match nor a module chain. The next site in the walk was either already converted, but can't match the module, or it will exit the outer loop because it has a static_call_site pointer and not a static_call_mod pointer.(CVE-2024-50002)
In the Linux kernel, the following vulnerability has been resolved: ALSA: asihpi: Fix potential OOB array access ASIHPI driver stores some values in the static array upon a response from the driver, and its index depends on the firmware. We shouldn't trust it blindly. This patch adds a sanity check of the array index to fit in the array size.(CVE-2024-50007)
In the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_cmd_802_11_scan_ext() Replace one-element array with a flexible-array member in struct host_cmd_ds_802_11_scan_ext. With this, fix the following warning: elo 16 17:51:58 surfacebook kernel: ------------[ cut here ]------------ elo 16 17:51:58 surfacebook kernel: memcpy: detected field-spanning write (size 243) of single field "ext_scan->tlv_buffer" at drivers/net/wireless/marvell/mwifiex/scan.c:2239 (size 1) elo 16 17:51:58 surfacebook kernel: WARNING: CPU: 0 PID: 498 at drivers/net/wireless/marvell/mwifiex/scan.c:2239 mwifiex_cmd_802_11_scan_ext+0x83/0x90 mwifiex
In the Linux kernel, the following vulnerability has been resolved: ext4: dax: fix overflowing extents beyond inode size when partially writing The dax_iomap_rw() does two things in each iteration: map written blocks and copy user data to blocks. If the process is killed by user(See signal handling in dax_iomap_iter()), the copied data will be returned and added on inode size, which means that the length of written extents may exceed the inode size, then fsck will fail. An example is given as: dd if=/dev/urandom of=file bs=4M count=1 dax_iomap_rw iomap_iter // round 1 ext4_iomap_begin ext4_iomap_alloc // allocate 0~2M extents(written flag) dax_iomap_iter // copy 2M data iomap_iter // round 2 iomap_iter_advance iter->pos += iter->processed // iter->pos = 2M ext4_iomap_begin ext4_iomap_alloc // allocate 2~4M extents(written flag) dax_iomap_iter fatal_signal_pending done = iter->pos - iocb->ki_pos // done = 2M ext4_handle_inode_extension ext4_update_inode_size // inode size = 2M fsck reports: Inode 13, i_size is 2097152, should be 4194304. Fix? Fix the problem by truncating extents if the written length is smaller than expected.(CVE-2024-50015)
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Avoid overflow assignment in link_dp_cts sampling_rate is an uint8_t but is assigned an unsigned int, and thus it can overflow. As a result, sampling_rate is changed to uint32_t. Similarly, LINK_QUAL_PATTERN_SET has a size of 2 bits, and it should only be assigned to a value less or equal than 4. This fixes 2 INTEGER_OVERFLOW issues reported by Coverity.(CVE-2024-50016)
In the Linux kernel, the following vulnerability has been resolved: thermal: core: Reference count the zone in thermal_zone_get_by_id() There are places in the thermal netlink code where nothing prevents the thermal zone object from going away while being accessed after it has been returned by thermal_zone_get_by_id(). To address this, make thermal_zone_get_by_id() get a reference on the thermal zone device object to be returned with the help of get_device(), under thermal_list_lock, and adjust all of its callers to this change with the help of the cleanup.h infrastructure.(CVE-2024-50028)
In the Linux kernel, the following vulnerability has been resolved: slip: make slhc_remember() more robust against malicious packets syzbot found that slhc_remember() was missing checks against malicious packets [1]. slhc_remember() only checked the size of the packet was at least 20, which is not good enough. We need to make sure the packet includes the IPv4 and TCP header that are supposed to be carried. Add iph and th pointers to make the code more readable. [1] BUG: KMSAN: uninit-value in slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666 slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666 ppp_receive_nonmp_frame+0xe45/0x35e0 drivers/net/ppp/ppp_generic.c:2455 ppp_receive_frame drivers/net/ppp/ppp_generic.c:2372 [inline] ppp_do_recv+0x65f/0x40d0 drivers/net/ppp/ppp_generic.c:2212 ppp_input+0x7dc/0xe60 drivers/net/ppp/ppp_generic.c:2327 pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379 sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113 __release_sock+0x1da/0x330 net/core/sock.c:3072 release_sock+0x6b/0x250 net/core/sock.c:3626 pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 _syssendmsg+0x903/0xb60 net/socket.c:2602 _sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was created at: slab_post_alloc_hook mm/slub.c:4091 [inline] slab_alloc_node mm/slub.c:4134 [inline] kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4186 kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587 __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678 alloc_skb include/linux/skbuff.h:1322 [inline] sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732 pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 _syssendmsg+0x903/0xb60 net/socket.c:2602 _sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f CPU: 0 UID: 0 PID: 5460 Comm: syz.2.33 Not tainted 6.12.0-rc2-syzkaller-00006-g87d6aab2389e #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50033)
In the Linux kernel, the following vulnerability has been resolved: ppp: fix ppp_async_encode() illegal access syzbot reported an issue in ppp_async_encode() [1] In this case, pppoe_sendmsg() is called with a zero size. Then ppp_async_encode() is called with an empty skb. BUG: KMSAN: uninit-value in ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline] BUG: KMSAN: uninit-value in ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675 ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline] ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675 ppp_async_send+0x130/0x1b0 drivers/net/ppp/ppp_async.c:634 ppp_channel_bridge_input drivers/net/ppp/ppp_generic.c:2280 [inline] ppp_input+0x1f1/0xe60 drivers/net/ppp/ppp_generic.c:2304 pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379 sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113 __release_sock+0x1da/0x330 net/core/sock.c:3072 release_sock+0x6b/0x250 net/core/sock.c:3626 pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 _syssendmsg+0x903/0xb60 net/socket.c:2602 _sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was created at: slab_post_alloc_hook mm/slub.c:4092 [inline] slab_alloc_node mm/slub.c:4135 [inline] kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4187 kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587 __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678 alloc_skb include/linux/skbuff.h:1322 [inline] sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732 pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 _syssendmsg+0x903/0xb60 net/socket.c:2602 _sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f CPU: 1 UID: 0 PID: 5411 Comm: syz.1.14 Not tainted 6.12.0-rc1-syzkaller-00165-g360c1f1f24c6 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50035)
In the Linux kernel, the following vulnerability has been resolved: igb: Do not bring the device up after non-fatal error Commit 004d25060c78 ("igb: Fix igb_down hung on surprise removal") changed igb_io_error_detected() to ignore non-fatal pcie errors in order to avoid hung task that can happen when igb_down() is called multiple times. This caused an issue when processing transient non-fatal errors. igb_io_resume(), which is called after igb_io_error_detected(), assumes that device is brought down by igb_io_error_detected() if the interface is up. This resulted in panic with stacktrace below. [ T3256] igb 0000:09:00.0 haeth0: igb: haeth0 NIC Link is Down [ T292] pcieport 0000:00:1c.5: AER: Uncorrected (Non-Fatal) error received: 0000:09:00.0 [ T292] igb 0000:09:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [ T292] igb 0000:09:00.0: device [8086:1537] error status/mask=00004000/00000000 [ T292] igb 0000:09:00.0: [14] CmpltTO [ 200.105524,009][ T292] igb 0000:09:00.0: AER: TLP Header: 00000000 00000000 00000000 00000000 [ T292] pcieport 0000:00:1c.5: AER: broadcast error_detected message [ T292] igb 0000:09:00.0: Non-correctable non-fatal error reported. [ T292] pcieport 0000:00:1c.5: AER: broadcast mmio_enabled message [ T292] pcieport 0000:00:1c.5: AER: broadcast resume message [ T292] ------------[ cut here ]------------ [ T292] kernel BUG at net/core/dev.c:6539! [ T292] invalid opcode: 0000 [#1] PREEMPT SMP [ T292] RIP: 0010:napi_enable+0x37/0x40 [ T292] Call Trace: [ T292] <TASK> [ T292] ? die+0x33/0x90 [ T292] ? do_trap+0xdc/0x110 [ T292] ? napi_enable+0x37/0x40 [ T292] ? do_error_trap+0x70/0xb0 [ T292] ? napi_enable+0x37/0x40 [ T292] ? napi_enable+0x37/0x40 [ T292] ? exc_invalid_op+0x4e/0x70 [ T292] ? napi_enable+0x37/0x40 [ T292] ? asm_exc_invalid_op+0x16/0x20 [ T292] ? napi_enable+0x37/0x40 [ T292] igb_up+0x41/0x150 [ T292] igb_io_resume+0x25/0x70 [ T292] report_resume+0x54/0x70 [ T292] ? report_frozen_detected+0x20/0x20 [ T292] pci_walk_bus+0x6c/0x90 [ T292] ? aer_print_port_info+0xa0/0xa0 [ T292] pcie_do_recovery+0x22f/0x380 [ T292] aer_process_err_devices+0x110/0x160 [ T292] aer_isr+0x1c1/0x1e0 [ T292] ? disable_irq_nosync+0x10/0x10 [ T292] irq_thread_fn+0x1a/0x60 [ T292] irq_thread+0xe3/0x1a0 [ T292] ? irq_set_affinity_notifier+0x120/0x120 [ T292] ? irq_affinity_notify+0x100/0x100 [ T292] kthread+0xe2/0x110 [ T292] ? kthread_complete_and_exit+0x20/0x20 [ T292] ret_from_fork+0x2d/0x50 [ T292] ? kthread_complete_and_exit+0x20/0x20 [ T292] ret_from_fork_asm+0x11/0x20 [ T292] </TASK> To fix this issue igb_io_resume() checks if the interface is running and the device is not down this means igb_io_error_detected() did not bring the device down and there is no need to bring it up.(CVE-2024-50040)
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix UAF in async decryption Doing an async decryption (large read) crashes with a slab-use-after-free way down in the crypto API. Reproducer: # mount.cifs -o ...,seal,esize=1 //srv/share /mnt # dd if=/mnt/largefile of=/dev/null ... [ 194.196391] ================================================================== [ 194.196844] BUG: KASAN: slab-use-after-free in gf128mul_4k_lle+0xc1/0x110 [ 194.197269] Read of size 8 at addr ffff888112bd0448 by task kworker/u77:2/899 [ 194.197707] [ 194.197818] CPU: 12 UID: 0 PID: 899 Comm: kworker/u77:2 Not tainted 6.11.0-lku-00028-gfca3ca14a17a-dirty #43 [ 194.198400] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.2-3-gd478f380-prebuilt.qemu.org 04/01/2014 [ 194.199046] Workqueue: smb3decryptd smb2_decrypt_offload [cifs] [ 194.200032] Call Trace: [ 194.200191] <TASK> [ 194.200327] dump_stack_lvl+0x4e/0x70 [ 194.200558] ? gf128mul_4k_lle+0xc1/0x110 [ 194.200809] print_report+0x174/0x505 [ 194.201040] ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [ 194.201352] ? srso_return_thunk+0x5/0x5f [ 194.201604] ? __virt_addr_valid+0xdf/0x1c0 [ 194.201868] ? gf128mul_4k_lle+0xc1/0x110 [ 194.202128] kasan_report+0xc8/0x150 [ 194.202361] ? gf128mul_4k_lle+0xc1/0x110 [ 194.202616] gf128mul_4k_lle+0xc1/0x110 [ 194.202863] ghash_update+0x184/0x210 [ 194.203103] shash_ahash_update+0x184/0x2a0 [ 194.203377] ? __pfx_shash_ahash_update+0x10/0x10 [ 194.203651] ? srso_return_thunk+0x5/0x5f [ 194.203877] ? crypto_gcm_init_common+0x1ba/0x340 [ 194.204142] gcm_hash_assoc_remain_continue+0x10a/0x140 [ 194.204434] crypt_message+0xec1/0x10a0 [cifs] [ 194.206489] ? __pfx_crypt_message+0x10/0x10 [cifs] [ 194.208507] ? srso_return_thunk+0x5/0x5f [ 194.209205] ? srso_return_thunk+0x5/0x5f [ 194.209925] ? srso_return_thunk+0x5/0x5f [ 194.210443] ? srso_return_thunk+0x5/0x5f [ 194.211037] decrypt_raw_data+0x15f/0x250 [cifs] [ 194.212906] ? __pfx_decrypt_raw_data+0x10/0x10 [cifs] [ 194.214670] ? srso_return_thunk+0x5/0x5f [ 194.215193] smb2_decrypt_offload+0x12a/0x6c0 [cifs] This is because TFM is being used in parallel. Fix this by allocating a new AEAD TFM for async decryption, but keep the existing one for synchronous READ cases (similar to what is done in smb3_calc_signature()). Also remove the calls to aead_request_set_callback() and crypto_wait_req() since it's always going to be a synchronous operation.(CVE-2024-50047)
In the Linux kernel, the following vulnerability has been resolved: serial: protect uart_port_dtr_rts() in uart_shutdown() too Commit af224ca2df29 (serial: core: Prevent unsafe uart port access, part 3) added few uport == NULL checks. It added one to uart_shutdown(), so the commit assumes, uport can be NULL in there. But right after that protection, there is an unprotected "uart_port_dtr_rts(uport, false);" call. That is invoked only if HUPCL is set, so I assume that is the reason why we do not see lots of these reports. Or it cannot be NULL at this point at all for some reason :P. Until the above is investigated, stay on the safe side and move this dereference to the if too. I got this inconsistency from Coverity under CID 1585130. Thanks.(CVE-2024-50058)
In the Linux kernel, the following vulnerability has been resolved: ntb: ntb_hw_switchtec: Fix use after free vulnerability in switchtec_ntb_remove due to race condition In the switchtec_ntb_add function, it can call switchtec_ntb_init_sndev function, then &sndev->check_link_status_work is bound with check_link_status_work. switchtec_ntb_link_notification may be called to start the work. If we remove the module which will call switchtec_ntb_remove to make cleanup, it will free sndev through kfree(sndev), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows: CPU0 CPU1 | check_link_status_work switchtec_ntb_remove | kfree(sndev); | | if (sndev->link_force_down) | // use sndev Fix it by ensuring that the work is canceled before proceeding with the cleanup in switchtec_ntb_remove.(CVE-2024-50059)
In the Linux kernel, the following vulnerability has been resolved: io_uring: check if we need to reschedule during overflow flush In terms of normal application usage, this list will always be empty. And if an application does overflow a bit, it'll have a few entries. However, nothing obviously prevents syzbot from running a test case that generates a ton of overflow entries, and then flushing them can take quite a while. Check for needing to reschedule while flushing, and drop our locks and do so if necessary. There's no state to maintain here as overflows always prune from head-of-list, hence it's fine to drop and reacquire the locks at the end of the loop.(CVE-2024-50060)
In the Linux kernel, the following vulnerability has been resolved: bpf: Prevent tail call between progs attached to different hooks bpf progs can be attached to kernel functions, and the attached functions can take different parameters or return different return values. If prog attached to one kernel function tail calls prog attached to another kernel function, the ctx access or return value verification could be bypassed. For example, if prog1 is attached to func1 which takes only 1 parameter and prog2 is attached to func2 which takes two parameters. Since verifier assumes the bpf ctx passed to prog2 is constructed based on func2's prototype, verifier allows prog2 to access the second parameter from the bpf ctx passed to it. The problem is that verifier does not prevent prog1 from passing its bpf ctx to prog2 via tail call. In this case, the bpf ctx passed to prog2 is constructed from func1 instead of func2, that is, the assumption for ctx access verification is bypassed. Another example, if BPF LSM prog1 is attached to hook file_alloc_security, and BPF LSM prog2 is attached to hook bpf_lsm_audit_rule_known. Verifier knows the return value rules for these two hooks, e.g. it is legal for bpf_lsm_audit_rule_known to return positive number 1, and it is illegal for file_alloc_security to return positive number. So verifier allows prog2 to return positive number 1, but does not allow prog1 to return positive number. The problem is that verifier does not prevent prog1 from calling prog2 via tail call. In this case, prog2's return value 1 will be used as the return value for prog1's hook file_alloc_security. That is, the return value rule is bypassed. This patch adds restriction for tail call to prevent such bypasses.(CVE-2024-50063)
In the Linux kernel, the following vulnerability has been resolved: zram: free secondary algorithms names We need to kfree() secondary algorithms names when reset zram device that had multi-streams, otherwise we leak memory. [senozhatsky@chromium.org: kfree(NULL) is legal] Link: https://lkml.kernel.org/r/20240917013021.868769-1-senozhatsky@chromium.org(CVE-2024-50064)
In the Linux kernel, the following vulnerability has been resolved: uprobe: avoid out-of-bounds memory access of fetching args Uprobe needs to fetch args into a percpu buffer, and then copy to ring buffer to avoid non-atomic context problem. Sometimes user-space strings, arrays can be very large, but the size of percpu buffer is only page size. And store_trace_args() won't check whether these data exceeds a single page or not, caused out-of-bounds memory access. It could be reproduced by following steps: 1. build kernel with CONFIG_KASAN enabled 2. save follow program as test.c \#include <stdio.h> \#include <stdlib.h> \#include <string.h> // If string length large than MAX_STRING_SIZE, the fetch_store_strlen() // will return 0, cause __get_data_size() return shorter size, and // store_trace_args() will not trigger out-of-bounds access. // So make string length less than 4096. \#define STRLEN 4093 void generate_string(char *str, int n) { int i; for (i = 0; i < n; ++i) { char c = i % 26 + 'a'; str[i] = c; } str[n-1] = '\0'; } void print_string(char *str) { printf("%s\n", str); } int main() { char tmp[STRLEN]; generate_string(tmp, STRLEN); print_string(tmp); return 0; } 3. compile program gcc -o test test.c 4. get the offset of print_string() objdump -t test | grep -w print_string 0000000000401199 g F .text 000000000000001b print_string 5. configure uprobe with offset 0x1199 off=0x1199 cd /sys/kernel/debug/tracing/ echo "p /root/test:${off} arg1=+0(%di):ustring arg2=\$comm arg3=+0(%di):ustring" > uprobe_events echo 1 > events/uprobes/enable echo 1 > tracing_on 6. run test, and kasan will report error. ================================================================== BUG: KASAN: use-after-free in strncpy_from_user+0x1d6/0x1f0 Write of size 8 at addr ffff88812311c004 by task test/499CPU: 0 UID: 0 PID: 499 Comm: test Not tainted 6.12.0-rc3+ #18 Hardware name: Red Hat KVM, BIOS 1.16.0-4.al8 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x55/0x70 print_address_description.constprop.0+0x27/0x310 kasan_report+0x10f/0x120 ? strncpy_from_user+0x1d6/0x1f0 strncpy_from_user+0x1d6/0x1f0 ? rmqueue.constprop.0+0x70d/0x2ad0 process_fetch_insn+0xb26/0x1470 ? __pfx_process_fetch_insn+0x10/0x10 ? _raw_spin_lock+0x85/0xe0 ? __pfx__raw_spin_lock+0x10/0x10 ? __pte_offset_map+0x1f/0x2d0 ? unwind_next_frame+0xc5f/0x1f80 ? arch_stack_walk+0x68/0xf0 ? is_bpf_text_address+0x23/0x30 ? kernel_text_address.part.0+0xbb/0xd0 ? __kernel_text_address+0x66/0xb0 ? unwind_get_return_address+0x5e/0xa0 ? __pfx_stack_trace_consume_entry+0x10/0x10 ? arch_stack_walk+0xa2/0xf0 ? _raw_spin_lock_irqsave+0x8b/0xf0 ? __pfx__raw_spin_lock_irqsave+0x10/0x10 ? depot_alloc_stack+0x4c/0x1f0 ? _raw_spin_unlock_irqrestore+0xe/0x30 ? stack_depot_save_flags+0x35d/0x4f0 ? kasan_save_stack+0x34/0x50 ? kasan_save_stack+0x24/0x50 ? mutex_lock+0x91/0xe0 ? __pfx_mutex_lock+0x10/0x10 prepare_uprobe_buffer.part.0+0x2cd/0x500 uprobe_dispatcher+0x2c3/0x6a0 ? __pfx_uprobe_dispatcher+0x10/0x10 ? __kasan_slab_alloc+0x4d/0x90 handler_chain+0xdd/0x3e0 handle_swbp+0x26e/0x3d0 ? __pfx_handle_swbp+0x10/0x10 ? uprobe_pre_sstep_notifier+0x151/0x1b0 irqentry_exit_to_user_mode+0xe2/0x1b0 asm_exc_int3+0x39/0x40 RIP: 0033:0x401199 Code: 01 c2 0f b6 45 fb 88 02 83 45 fc 01 8b 45 fc 3b 45 e4 7c b7 8b 45 e4 48 98 48 8d 50 ff 48 8b 45 e8 48 01 d0 ce RSP: 002b:00007ffdf00576a8 EFLAGS: 00000206 RAX: 00007ffdf00576b0 RBX: 0000000000000000 RCX: 0000000000000ff2 RDX: 0000000000000ffc RSI: 0000000000000ffd RDI: 00007ffdf00576b0 RBP: 00007ffdf00586b0 R08: 00007feb2f9c0d20 R09: 00007feb2f9c0d20 R10: 0000000000000001 R11: 0000000000000202 R12: 0000000000401040 R13: 00007ffdf0058780 R14: 0000000000000000 R15: 0000000000000000 </TASK> This commit enforces the buffer's maxlen less than a page-size to avoid store_trace_args() out-of-memory access.(CVE-2024-50067)
In the Linux kernel, the following vulnerability has been resolved: parport: Proper fix for array out-of-bounds access The recent fix for array out-of-bounds accesses replaced sprintf() calls blindly with snprintf(). However, since snprintf() returns the would-be-printed size, not the actually output size, the length calculation can still go over the given limit. Use scnprintf() instead of snprintf(), which returns the actually output letters, for addressing the potential out-of-bounds access properly.(CVE-2024-50074)
In the Linux kernel, the following vulnerability has been resolved: tcp: fix mptcp DSS corruption due to large pmtu xmit Syzkaller was able to trigger a DSS corruption: TCP: request_sock_subflow_v4: Possible SYN flooding on port [::]:20002. Sending cookies. ------------[ cut here ]------------ WARNING: CPU: 0 PID: 5227 at net/mptcp/protocol.c:695 __mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695 Modules linked in: CPU: 0 UID: 0 PID: 5227 Comm: syz-executor350 Not tainted 6.11.0-syzkaller-08829-gaf9c191ac2a0 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 RIP: 0010:__mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695 Code: 0f b6 dc 31 ff 89 de e8 b5 dd ea f5 89 d8 48 81 c4 50 01 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 98 da ea f5 90 <0f> 0b 90 e9 47 ff ff ff e8 8a da ea f5 90 0f 0b 90 e9 99 e0 ff ff RSP: 0018:ffffc90000006db8 EFLAGS: 00010246 RAX: ffffffff8ba9df18 RBX: 00000000000055f0 RCX: ffff888030023c00 RDX: 0000000000000100 RSI: 00000000000081e5 RDI: 00000000000055f0 RBP: 1ffff110062bf1ae R08: ffffffff8ba9cf12 R09: 1ffff110062bf1b8 R10: dffffc0000000000 R11: ffffed10062bf1b9 R12: 0000000000000000 R13: dffffc0000000000 R14: 00000000700cec61 R15: 00000000000081e5 FS: 000055556679c380(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020287000 CR3: 0000000077892000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <IRQ> move_skbs_to_msk net/mptcp/protocol.c:811 [inline] mptcp_data_ready+0x29c/0xa90 net/mptcp/protocol.c:854 subflow_data_ready+0x34a/0x920 net/mptcp/subflow.c:1490 tcp_data_queue+0x20fd/0x76c0 net/ipv4/tcp_input.c:5283 tcp_rcv_established+0xfba/0x2020 net/ipv4/tcp_input.c:6237 tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915 tcp_v4_rcv+0x2dc0/0x37f0 net/ipv4/tcp_ipv4.c:2350 ip_protocol_deliver_rcu+0x22e/0x440 net/ipv4/ip_input.c:205 ip_local_deliver_finish+0x341/0x5f0 net/ipv4/ip_input.c:233 NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314 NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314 __netif_receive_skb_one_core net/core/dev.c:5662 [inline] __netif_receive_skb+0x2bf/0x650 net/core/dev.c:5775 process_backlog+0x662/0x15b0 net/core/dev.c:6107 __napi_poll+0xcb/0x490 net/core/dev.c:6771 napi_poll net/core/dev.c:6840 [inline] net_rx_action+0x89b/0x1240 net/core/dev.c:6962 handle_softirqs+0x2c5/0x980 kernel/softirq.c:554 do_softirq+0x11b/0x1e0 kernel/softirq.c:455 </IRQ> <TASK> __local_bh_enable_ip+0x1bb/0x200 kernel/softirq.c:382 local_bh_enable include/linux/bottom_half.h:33 [inline] rcu_read_unlock_bh include/linux/rcupdate.h:919 [inline] __dev_queue_xmit+0x1764/0x3e80 net/core/dev.c:4451 dev_queue_xmit include/linux/netdevice.h:3094 [inline] neigh_hh_output include/net/neighbour.h:526 [inline] neigh_output include/net/neighbour.h:540 [inline] ip_finish_output2+0xd41/0x1390 net/ipv4/ip_output.c:236 ip_local_out net/ipv4/ip_output.c:130 [inline] __ip_queue_xmit+0x118c/0x1b80 net/ipv4/ip_output.c:536 __tcp_transmit_skb+0x2544/0x3b30 net/ipv4/tcp_output.c:1466 tcp_transmit_skb net/ipv4/tcp_output.c:1484 [inline] tcp_mtu_probe net/ipv4/tcp_output.c:2547 [inline] tcp_write_xmit+0x641d/0x6bf0 net/ipv4/tcp_output.c:2752 __tcp_push_pending_frames+0x9b/0x360 net/ipv4/tcp_output.c:3015 tcp_push_pending_frames include/net/tcp.h:2107 [inline] tcp_data_snd_check net/ipv4/tcp_input.c:5714 [inline] tcp_rcv_established+0x1026/0x2020 net/ipv4/tcp_input.c:6239 tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915 sk_backlog_rcv include/net/sock.h:1113 [inline] __release_sock+0x214/0x350 net/core/sock.c:3072 release_sock+0x61/0x1f0 net/core/sock.c:3626 mptcp_push_ ---truncated---(CVE-2024-50083)
| URL | Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"kernel-5.10.0-235.0.0.137.oe2203sp3.aarch64.rpm",
"kernel-debuginfo-5.10.0-235.0.0.137.oe2203sp3.aarch64.rpm",
"kernel-debugsource-5.10.0-235.0.0.137.oe2203sp3.aarch64.rpm",
"kernel-devel-5.10.0-235.0.0.137.oe2203sp3.aarch64.rpm",
"kernel-headers-5.10.0-235.0.0.137.oe2203sp3.aarch64.rpm",
"kernel-source-5.10.0-235.0.0.137.oe2203sp3.aarch64.rpm",
"kernel-tools-5.10.0-235.0.0.137.oe2203sp3.aarch64.rpm",
"kernel-tools-debuginfo-5.10.0-235.0.0.137.oe2203sp3.aarch64.rpm",
"kernel-tools-devel-5.10.0-235.0.0.137.oe2203sp3.aarch64.rpm",
"perf-5.10.0-235.0.0.137.oe2203sp3.aarch64.rpm",
"perf-debuginfo-5.10.0-235.0.0.137.oe2203sp3.aarch64.rpm",
"python3-perf-5.10.0-235.0.0.137.oe2203sp3.aarch64.rpm",
"python3-perf-debuginfo-5.10.0-235.0.0.137.oe2203sp3.aarch64.rpm"
],
"src": [
"kernel-5.10.0-235.0.0.137.oe2203sp3.src.rpm"
],
"x86_64": [
"kernel-5.10.0-235.0.0.137.oe2203sp3.x86_64.rpm",
"kernel-debuginfo-5.10.0-235.0.0.137.oe2203sp3.x86_64.rpm",
"kernel-debugsource-5.10.0-235.0.0.137.oe2203sp3.x86_64.rpm",
"kernel-devel-5.10.0-235.0.0.137.oe2203sp3.x86_64.rpm",
"kernel-headers-5.10.0-235.0.0.137.oe2203sp3.x86_64.rpm",
"kernel-source-5.10.0-235.0.0.137.oe2203sp3.x86_64.rpm",
"kernel-tools-5.10.0-235.0.0.137.oe2203sp3.x86_64.rpm",
"kernel-tools-debuginfo-5.10.0-235.0.0.137.oe2203sp3.x86_64.rpm",
"kernel-tools-devel-5.10.0-235.0.0.137.oe2203sp3.x86_64.rpm",
"perf-5.10.0-235.0.0.137.oe2203sp3.x86_64.rpm",
"perf-debuginfo-5.10.0-235.0.0.137.oe2203sp3.x86_64.rpm",
"python3-perf-5.10.0-235.0.0.137.oe2203sp3.x86_64.rpm",
"python3-perf-debuginfo-5.10.0-235.0.0.137.oe2203sp3.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:22.03-LTS-SP3",
"name": "kernel",
"purl": "pkg:rpm/openEuler/kernel\u0026distro=openEuler-22.03-LTS-SP3"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.10.0-235.0.0.137.oe2203sp3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: net: mdio: fix unbalanced fwnode reference count in mdio_device_release() There is warning report about of_node refcount leak while probing mdio device: OF: ERROR: memory leak, expected refcount 1 instead of 2, of_node_get()/of_node_put() unbalanced - destroy cset entry: attach overlay node /spi/soc@0/mdio@710700c0/ethernet@4 In of_mdiobus_register_device(), we increase fwnode refcount by fwnode_handle_get() before associating the of_node with mdio device, but it has never been decreased in normal path. Since that, in mdio_device_release(), it needs to call fwnode_handle_put() in addition instead of calling kfree() directly. After above, just calling mdio_device_free() in the error handle path of of_mdiobus_register_device() is enough to keep the refcount balanced.(CVE-2022-48961)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: gpiolib: fix memory leak in gpiochip_setup_dev() Here is a backtrace report about memory leak detected in gpiochip_setup_dev(): unreferenced object 0xffff88810b406400 (size 512): comm \u0026quot;python3\u0026quot;, pid 1682, jiffies 4295346908 (age 24.090s) backtrace: kmalloc_trace device_add device_private_init at drivers/base/core.c:3361 (inlined by) device_add at drivers/base/core.c:3411 cdev_device_add gpiolib_cdev_register gpiochip_setup_dev gpiochip_add_data_with_key gcdev_register() \u0026amp; gcdev_unregister() would call device_add() \u0026amp; device_del() (no matter CONFIG_GPIO_CDEV is enabled or not) to register/unregister device. However, if device_add() succeeds, some resource (like struct device_private allocated by device_private_init()) is not released by device_del(). Therefore, after device_add() succeeds by gcdev_register(), it needs to call put_device() to release resource in the error handle path. Here we move forward the register of release function, and let it release every piece of resource by put_device() instead of kfree(). While at it, fix another subtle issue, i.e. when gc-\u0026gt;ngpio is equal to 0, we still call kcalloc() and, in case of further error, kfree() on the ZERO_PTR pointer, which is not NULL. It\u0026apos;s not a bug per se, but rather waste of the resources and potentially wrong expectation about contents of the gdev-\u0026gt;descs variable.(CVE-2022-48975)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: riscv: Sync efi page table\u0026apos;s kernel mappings before switching The EFI page table is initially created as a copy of the kernel page table. With VMAP_STACK enabled, kernel stacks are allocated in the vmalloc area: if the stack is allocated in a new PGD (one that was not present at the moment of the efi page table creation or not synced in a previous vmalloc fault), the kernel will take a trap when switching to the efi page table when the vmalloc kernel stack is accessed, resulting in a kernel panic. Fix that by updating the efi kernel mappings before switching to the efi page table.(CVE-2022-49004)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmemcg_write_event_control(): fix a user-triggerable oops\r\n\r\nwe are *not* guaranteed that anything past the terminating NUL\nis mapped (let alone initialized with anything sane).(CVE-2024-45021)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ngtp: fix a potential NULL pointer dereference\r\n\r\nWhen sockfd_lookup() fails, gtp_encap_enable_socket() returns a\nNULL pointer, but its callers only check for error pointers thus miss\nthe NULL pointer case.\r\n\r\nFix it by returning an error pointer with the error code carried from\nsockfd_lookup().\r\n\r\n(I found this bug during code inspection.)(CVE-2024-46677)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Check BIOS images before it is used\r\n\r\nBIOS images may fail to load and null checks are added before they are\nused.\r\n\r\nThis fixes 6 NULL_RETURNS issues reported by Coverity.(CVE-2024-46809)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsmack: tcp: ipv4, fix incorrect labeling\r\n\r\nCurrently, Smack mirrors the label of incoming tcp/ipv4 connections:\nwhen a label \u0026apos;foo\u0026apos; connects to a label \u0026apos;bar\u0026apos; with tcp/ipv4,\n\u0026apos;foo\u0026apos; always gets \u0026apos;foo\u0026apos; in returned ipv4 packets. So,\n1) returned packets are incorrectly labeled (\u0026apos;foo\u0026apos; instead of \u0026apos;bar\u0026apos;)\n2) \u0026apos;bar\u0026apos; can write to \u0026apos;foo\u0026apos; without being authorized to write.\r\n\r\nHere is a scenario how to see this:\r\n\r\n* Take two machines, let\u0026apos;s call them C and S,\n with active Smack in the default state\n (no settings, no rules, no labeled hosts, only builtin labels)\r\n\r\n* At S, add Smack rule \u0026apos;foo bar w\u0026apos;\n (labels \u0026apos;foo\u0026apos; and \u0026apos;bar\u0026apos; are instantiated at S at this moment)\r\n\r\n* At S, at label \u0026apos;bar\u0026apos;, launch a program\n that listens for incoming tcp/ipv4 connections\r\n\r\n* From C, at label \u0026apos;foo\u0026apos;, connect to the listener at S.\n (label \u0026apos;foo\u0026apos; is instantiated at C at this moment)\n Connection succeedes and works.\r\n\r\n* Send some data in both directions.\n* Collect network traffic of this connection.\r\n\r\nAll packets in both directions are labeled with the CIPSO\nof the label \u0026apos;foo\u0026apos;. Hence, label \u0026apos;bar\u0026apos; writes to \u0026apos;foo\u0026apos; without\nbeing authorized, and even without ever being known at C.\r\n\r\nIf anybody cares: exactly the same happens with DCCP.\r\n\r\nThis behavior 1st manifested in release 2.6.29.4 (see Fixes below)\nand it looks unintentional. At least, no explanation was provided.\r\n\r\nI changed returned packes label into the \u0026apos;bar\u0026apos;,\nto bring it into line with the Smack documentation claims.(CVE-2024-47659)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfsnotify: clear PARENT_WATCHED flags lazily\r\n\r\nIn some setups directories can have many (usually negative) dentries.\nHence __fsnotify_update_child_dentry_flags() function can take a\nsignificant amount of time. Since the bulk of this function happens\nunder inode-\u0026gt;i_lock this causes a significant contention on the lock\nwhen we remove the watch from the directory as the\n__fsnotify_update_child_dentry_flags() call from fsnotify_recalc_mask()\nraces with __fsnotify_update_child_dentry_flags() calls from\n__fsnotify_parent() happening on children. This can lead upto softlockup\nreports reported by users.\r\n\r\nFix the problem by calling fsnotify_update_children_dentry_flags() to\nset PARENT_WATCHED flags only when parent starts watching children.\r\n\r\nWhen parent stops watching children, clear false positive PARENT_WATCHED\nflags lazily in __fsnotify_parent() for each accessed child.(CVE-2024-47660)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nlib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc()\r\n\r\nIf we need to increase the tree depth, allocate a new node, and then\nrace with another thread that increased the tree depth before us, we\u0026apos;ll\nstill have a preallocated node that might be used later.\r\n\r\nIf we then use that node for a new non-root node, it\u0026apos;ll still have a\npointer to the old root instead of being zeroed - fix this by zeroing it\nin the cmpxchg failure path.(CVE-2024-47668)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: iwlwifi: mvm: pause TCM when the firmware is stopped\r\n\r\nNot doing so will make us send a host command to the transport while the\nfirmware is not alive, which will trigger a WARNING.\r\n\r\nbad state = 0\nWARNING: CPU: 2 PID: 17434 at drivers/net/wireless/intel/iwlwifi/iwl-trans.c:115 iwl_trans_send_cmd+0x1cb/0x1e0 [iwlwifi]\nRIP: 0010:iwl_trans_send_cmd+0x1cb/0x1e0 [iwlwifi]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n iwl_mvm_send_cmd+0x40/0xc0 [iwlmvm]\n iwl_mvm_config_scan+0x198/0x260 [iwlmvm]\n iwl_mvm_recalc_tcm+0x730/0x11d0 [iwlmvm]\n iwl_mvm_tcm_work+0x1d/0x30 [iwlmvm]\n process_one_work+0x29e/0x640\n worker_thread+0x2df/0x690\n ? rescuer_thread+0x540/0x540\n kthread+0x192/0x1e0\n ? set_kthread_struct+0x90/0x90\n ret_from_fork+0x22/0x30(CVE-2024-47673)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: f2fs: get rid of online repaire on corrupted directory syzbot reports a f2fs bug as below: kernel BUG at fs/f2fs/inode.c:896! RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896 Call Trace: evict+0x532/0x950 fs/inode.c:704 dispose_list fs/inode.c:747 [inline] evict_inodes+0x5f9/0x690 fs/inode.c:797 generic_shutdown_super+0x9d/0x2d0 fs/super.c:627 kill_block_super+0x44/0x90 fs/super.c:1696 kill_f2fs_super+0x344/0x690 fs/f2fs/super.c:4898 deactivate_locked_super+0xc4/0x130 fs/super.c:473 cleanup_mnt+0x41f/0x4b0 fs/namespace.c:1373 task_work_run+0x24f/0x310 kernel/task_work.c:228 ptrace_notify+0x2d2/0x380 kernel/signal.c:2402 ptrace_report_syscall include/linux/ptrace.h:415 [inline] ptrace_report_syscall_exit include/linux/ptrace.h:477 [inline] syscall_exit_work+0xc6/0x190 kernel/entry/common.c:173 syscall_exit_to_user_mode_prepare kernel/entry/common.c:200 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:205 [inline] syscall_exit_to_user_mode+0x279/0x370 kernel/entry/common.c:218 do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896 Online repaire on corrupted directory in f2fs_lookup() can generate dirty data/meta while racing w/ readonly remount, it may leave dirty inode after filesystem becomes readonly, however, checkpoint() will skips flushing dirty inode in a state of readonly mode, result in above panic. Let\u0026apos;s get rid of online repaire in f2fs_lookup(), and leave the work to fsck.f2fs.(CVE-2024-47690)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid use-after-free in f2fs_stop_gc_thread() syzbot reports a f2fs bug as below: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114 print_report+0xe8/0x550 mm/kasan/report.c:491 kasan_report+0x143/0x180 mm/kasan/report.c:601 kasan_check_range+0x282/0x290 mm/kasan/generic.c:189 instrument_atomic_read_write include/linux/instrumented.h:96 [inline] atomic_fetch_add_relaxed include/linux/atomic/atomic-instrumented.h:252 [inline] __refcount_add include/linux/refcount.h:184 [inline] __refcount_inc include/linux/refcount.h:241 [inline] refcount_inc include/linux/refcount.h:258 [inline] get_task_struct include/linux/sched/task.h:118 [inline] kthread_stop+0xca/0x630 kernel/kthread.c:704 f2fs_stop_gc_thread+0x65/0xb0 fs/f2fs/gc.c:210 f2fs_do_shutdown+0x192/0x540 fs/f2fs/file.c:2283 f2fs_ioc_shutdown fs/f2fs/file.c:2325 [inline] __f2fs_ioctl+0x443a/0xbe60 fs/f2fs/file.c:4325 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f The root cause is below race condition, it may cause use-after-free issue in sbi-\u0026gt;gc_th pointer. - remount - f2fs_remount - f2fs_stop_gc_thread - kfree(gc_th) - f2fs_ioc_shutdown - f2fs_do_shutdown - f2fs_stop_gc_thread - kthread_stop(gc_th-\u0026gt;f2fs_gc_task) : sbi-\u0026gt;gc_thread = NULL; We will call f2fs_do_shutdown() in two paths: - for f2fs_ioc_shutdown() path, we should grab sb-\u0026gt;s_umount semaphore for fixing. - for f2fs_shutdown() path, it\u0026apos;s safe since caller has already grabbed sb-\u0026gt;s_umount semaphore.(CVE-2024-47691)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: IB/core: Fix ib_cache_setup_one error flow cleanup When ib_cache_update return an error, we exit ib_cache_setup_one instantly with no proper cleanup, even though before this we had already successfully done gid_table_setup_one, that results in the kernel WARN below. Do proper cleanup using gid_table_cleanup_one before returning the err in order to fix the issue. WARNING: CPU: 4 PID: 922 at drivers/infiniband/core/cache.c:806 gid_table_release_one+0x181/0x1a0 Modules linked in: CPU: 4 UID: 0 PID: 922 Comm: c_repro Not tainted 6.11.0-rc1+ #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:gid_table_release_one+0x181/0x1a0 Code: 44 8b 38 75 0c e8 2f cb 34 ff 4d 8b b5 28 05 00 00 e8 23 cb 34 ff 44 89 f9 89 da 4c 89 f6 48 c7 c7 d0 58 14 83 e8 4f de 21 ff \u0026lt;0f\u0026gt; 0b 4c 8b 75 30 e9 54 ff ff ff 48 8 3 c4 10 5b 5d 41 5c 41 5d 41 RSP: 0018:ffffc90002b835b0 EFLAGS: 00010286 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff811c8527 RDX: 0000000000000000 RSI: ffffffff811c8534 RDI: 0000000000000001 RBP: ffff8881011b3d00 R08: ffff88810b3abe00 R09: 205d303839303631 R10: 666572207972746e R11: 72746e6520444947 R12: 0000000000000001 R13: ffff888106390000 R14: ffff8881011f2110 R15: 0000000000000001 FS: 00007fecc3b70800(0000) GS:ffff88813bd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020000340 CR3: 000000010435a001 CR4: 00000000003706b0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: \u0026lt;TASK\u0026gt; ? show_regs+0x94/0xa0 ? __warn+0x9e/0x1c0 ? gid_table_release_one+0x181/0x1a0 ? report_bug+0x1f9/0x340 ? gid_table_release_one+0x181/0x1a0 ? handle_bug+0xa2/0x110 ? exc_invalid_op+0x31/0xa0 ? asm_exc_invalid_op+0x16/0x20 ? __warn_printk+0xc7/0x180 ? __warn_printk+0xd4/0x180 ? gid_table_release_one+0x181/0x1a0 ib_device_release+0x71/0xe0 ? __pfx_ib_device_release+0x10/0x10 device_release+0x44/0xd0 kobject_put+0x135/0x3d0 put_device+0x20/0x30 rxe_net_add+0x7d/0xa0 rxe_newlink+0xd7/0x190 nldev_newlink+0x1b0/0x2a0 ? __pfx_nldev_newlink+0x10/0x10 rdma_nl_rcv_msg+0x1ad/0x2e0 rdma_nl_rcv_skb.constprop.0+0x176/0x210 netlink_unicast+0x2de/0x400 netlink_sendmsg+0x306/0x660 __sock_sendmsg+0x110/0x120 ____sys_sendmsg+0x30e/0x390 ___sys_sendmsg+0x9b/0xf0 ? kstrtouint+0x6e/0xa0 ? kstrtouint_from_user+0x7c/0xb0 ? get_pid_task+0xb0/0xd0 ? proc_fail_nth_write+0x5b/0x140 ? __fget_light+0x9a/0x200 ? preempt_count_add+0x47/0xa0 __sys_sendmsg+0x61/0xd0 do_syscall_64+0x50/0x110 entry_SYSCALL_64_after_hwframe+0x76/0x7e(CVE-2024-47693)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency In the commit aee2424246f9 (\u0026quot;RDMA/iwcm: Fix a use-after-free related to destroying CM IDs\u0026quot;), the function flush_workqueue is invoked to flush the work queue iwcm_wq. But at that time, the work queue iwcm_wq was created via the function alloc_ordered_workqueue without the flag WQ_MEM_RECLAIM. Because the current process is trying to flush the whole iwcm_wq, if iwcm_wq doesn\u0026apos;t have the flag WQ_MEM_RECLAIM, verify that the current process is not reclaiming memory or running on a workqueue which doesn\u0026apos;t have the flag WQ_MEM_RECLAIM as that can break forward-progress guarantee leading to a deadlock. The call trace is as below: [ 125.350876][ T1430] Call Trace: [ 125.356281][ T1430] \u0026lt;TASK\u0026gt; [ 125.361285][ T1430] ? __warn (kernel/panic.c:693) [ 125.367640][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.375689][ T1430] ? report_bug (lib/bug.c:180 lib/bug.c:219) [ 125.382505][ T1430] ? handle_bug (arch/x86/kernel/traps.c:239) [ 125.388987][ T1430] ? exc_invalid_op (arch/x86/kernel/traps.c:260 (discriminator 1)) [ 125.395831][ T1430] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:621) [ 125.403125][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.410984][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.418764][ T1430] __flush_workqueue (kernel/workqueue.c:3970) [ 125.426021][ T1430] ? __pfx___might_resched (kernel/sched/core.c:10151) [ 125.433431][ T1430] ? destroy_cm_id (drivers/infiniband/core/iwcm.c:375) iw_cm [ 125.441209][ T1430] ? __pfx___flush_workqueue (kernel/workqueue.c:3910) [ 125.473900][ T1430] ? _raw_spin_lock_irqsave (arch/x86/include/asm/atomic.h:107 include/linux/atomic/atomic-arch-fallback.h:2170 include/linux/atomic/atomic-instrumented.h:1302 include/asm-generic/qspinlock.h:111 include/linux/spinlock.h:187 include/linux/spinlock_api_smp.h:111 kernel/locking/spinlock.c:162) [ 125.473909][ T1430] ? __pfx__raw_spin_lock_irqsave (kernel/locking/spinlock.c:161) [ 125.482537][ T1430] _destroy_id (drivers/infiniband/core/cma.c:2044) rdma_cm [ 125.495072][ T1430] nvme_rdma_free_queue (drivers/nvme/host/rdma.c:656 drivers/nvme/host/rdma.c:650) nvme_rdma [ 125.505827][ T1430] nvme_rdma_reset_ctrl_work (drivers/nvme/host/rdma.c:2180) nvme_rdma [ 125.505831][ T1430] process_one_work (kernel/workqueue.c:3231) [ 125.515122][ T1430] worker_thread (kernel/workqueue.c:3306 kernel/workqueue.c:3393) [ 125.515127][ T1430] ? __pfx_worker_thread (kernel/workqueue.c:3339) [ 125.531837][ T1430] kthread (kernel/kthread.c:389) [ 125.539864][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.550628][ T1430] ret_from_fork (arch/x86/kernel/process.c:147) [ 125.558840][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.558844][ T1430] ret_from_fork_asm (arch/x86/entry/entry_64.S:257) [ 125.566487][ T1430] \u0026lt;/TASK\u0026gt; [ 125.566488][ T1430] ---[ end trace 0000000000000000 ]---(CVE-2024-47696)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential null-ptr-deref in nilfs_btree_insert() Patch series \u0026quot;nilfs2: fix potential issues with empty b-tree nodes\u0026quot;. This series addresses three potential issues with empty b-tree nodes that can occur with corrupted filesystem images, including one recently discovered by syzbot. This patch (of 3): If a b-tree is broken on the device, and the b-tree height is greater than 2 (the level of the root node is greater than 1) even if the number of child nodes of the b-tree root is 0, a NULL pointer dereference occurs in nilfs_btree_prepare_insert(), which is called from nilfs_btree_insert(). This is because, when the number of child nodes of the b-tree root is 0, nilfs_btree_do_lookup() does not set the block buffer head in any of path[x].bp_bh, leaving it as the initial value of NULL, but if the level of the b-tree root node is greater than 1, nilfs_btree_get_nonroot_node(), which accesses the buffer memory of path[x].bp_bh, is called. Fix this issue by adding a check to nilfs_btree_root_broken(), which performs sanity checks when reading the root node from the device, to detect this inconsistency. Thanks to Lizhi Xu for trying to solve the bug and clarifying the cause early on.(CVE-2024-47699)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ext4: avoid OOB when system.data xattr changes underneath the filesystem When looking up for an entry in an inlined directory, if e_value_offs is changed underneath the filesystem by some change in the block device, it will lead to an out-of-bounds access that KASAN detects as an UAF. EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none. loop0: detected capacity change from 2048 to 2047 ================================================================== BUG: KASAN: use-after-free in ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500 Read of size 1 at addr ffff88803e91130f by task syz-executor269/5103 CPU: 0 UID: 0 PID: 5103 Comm: syz-executor269 Not tainted 6.11.0-rc4-syzkaller #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Call Trace: \u0026lt;TASK\u0026gt; __dump_stack lib/dump_stack.c:93 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119 print_address_description mm/kasan/report.c:377 [inline] print_report+0x169/0x550 mm/kasan/report.c:488 kasan_report+0x143/0x180 mm/kasan/report.c:601 ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500 ext4_find_inline_entry+0x4be/0x5e0 fs/ext4/inline.c:1697 __ext4_find_entry+0x2b4/0x1b30 fs/ext4/namei.c:1573 ext4_lookup_entry fs/ext4/namei.c:1727 [inline] ext4_lookup+0x15f/0x750 fs/ext4/namei.c:1795 lookup_one_qstr_excl+0x11f/0x260 fs/namei.c:1633 filename_create+0x297/0x540 fs/namei.c:3980 do_symlinkat+0xf9/0x3a0 fs/namei.c:4587 __do_sys_symlinkat fs/namei.c:4610 [inline] __se_sys_symlinkat fs/namei.c:4607 [inline] __x64_sys_symlinkat+0x95/0xb0 fs/namei.c:4607 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f3e73ced469 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 21 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fff4d40c258 EFLAGS: 00000246 ORIG_RAX: 000000000000010a RAX: ffffffffffffffda RBX: 0032656c69662f2e RCX: 00007f3e73ced469 RDX: 0000000020000200 RSI: 00000000ffffff9c RDI: 00000000200001c0 RBP: 0000000000000000 R08: 00007fff4d40c290 R09: 00007fff4d40c290 R10: 0023706f6f6c2f76 R11: 0000000000000246 R12: 00007fff4d40c27c R13: 0000000000000003 R14: 431bde82d7b634db R15: 00007fff4d40c2b0 \u0026lt;/TASK\u0026gt; Calling ext4_xattr_ibody_find right after reading the inode with ext4_get_inode_loc will lead to a check of the validity of the xattrs, avoiding this problem.(CVE-2024-47701)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: bpf, lsm: Add check for BPF LSM return value A bpf prog returning a positive number attached to file_alloc_security hook makes kernel panic. This happens because file system can not filter out the positive number returned by the LSM prog using IS_ERR, and misinterprets this positive number as a file pointer. Given that hook file_alloc_security never returned positive number before the introduction of BPF LSM, and other BPF LSM hooks may encounter similar issues, this patch adds LSM return value check in verifier, to ensure no unexpected value is returned.(CVE-2024-47703)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: block: fix potential invalid pointer dereference in blk_add_partition The blk_add_partition() function initially used a single if-condition (IS_ERR(part)) to check for errors when adding a partition. This was modified to handle the specific case of -ENXIO separately, allowing the function to proceed without logging the error in this case. However, this change unintentionally left a path where md_autodetect_dev() could be called without confirming that part is a valid pointer. This commit separates the error handling logic by splitting the initial if-condition, improving code readability and handling specific error scenarios explicitly. The function now distinguishes the general error case from -ENXIO without altering the existing behavior of md_autodetect_dev() calls.(CVE-2024-47705)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: jfs: fix out-of-bounds in dbNextAG() and diAlloc() In dbNextAG() , there is no check for the case where bmp-\u0026gt;db_numag is greater or same than MAXAG due to a polluted image, which causes an out-of-bounds. Therefore, a bounds check should be added in dbMount(). And in dbNextAG(), a check for the case where agpref is greater than bmp-\u0026gt;db_numag should be added, so an out-of-bounds exception should be prevented. Additionally, a check for the case where agno is greater or same than MAXAG should be added in diAlloc() to prevent out-of-bounds.(CVE-2024-47723)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: f2fs: fix to wait dio completion It should wait all existing dio write IOs before block removal, otherwise, previous direct write IO may overwrite data in the block which may be reused by other inode.(CVE-2024-47726)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: padata: use integer wrap around to prevent deadlock on seq_nr overflow When submitting more than 2^32 padata objects to padata_do_serial, the current sorting implementation incorrectly sorts padata objects with overflowed seq_nr, causing them to be placed before existing objects in the reorder list. This leads to a deadlock in the serialization process as padata_find_next cannot match padata-\u0026gt;seq_nr and pd-\u0026gt;processed because the padata instance with overflowed seq_nr will be selected next. To fix this, we use an unsigned integer wrap around to correctly sort padata objects in scenarios with integer overflow.(CVE-2024-47739)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: firmware_loader: Block path traversal Most firmware names are hardcoded strings, or are constructed from fairly constrained format strings where the dynamic parts are just some hex numbers or such. However, there are a couple codepaths in the kernel where firmware file names contain string components that are passed through from a device or semi-privileged userspace; the ones I could find (not counting interfaces that require root privileges) are: - lpfc_sli4_request_firmware_update() seems to construct the firmware filename from \u0026quot;ModelName\u0026quot;, a string that was previously parsed out of some descriptor (\u0026quot;Vital Product Data\u0026quot;) in lpfc_fill_vpd() - nfp_net_fw_find() seems to construct a firmware filename from a model name coming from nfp_hwinfo_lookup(pf-\u0026gt;hwinfo, \u0026quot;nffw.partno\u0026quot;), which I think parses some descriptor that was read from the device. (But this case likely isn\u0026apos;t exploitable because the format string looks like \u0026quot;netronome/nic_%s\u0026quot;, and there shouldn\u0026apos;t be any *folders* starting with \u0026quot;netronome/nic_\u0026quot;. The previous case was different because there, the \u0026quot;%s\u0026quot; is *at the start* of the format string.) - module_flash_fw_schedule() is reachable from the ETHTOOL_MSG_MODULE_FW_FLASH_ACT netlink command, which is marked as GENL_UNS_ADMIN_PERM (meaning CAP_NET_ADMIN inside a user namespace is enough to pass the privilege check), and takes a userspace-provided firmware name. (But I think to reach this case, you need to have CAP_NET_ADMIN over a network namespace that a special kind of ethernet device is mapped into, so I think this is not a viable attack path in practice.) Fix it by rejecting any firmware names containing \u0026quot;..\u0026quot; path components. For what it\u0026apos;s worth, I went looking and haven\u0026apos;t found any USB device drivers that use the firmware loader dangerously.(CVE-2024-47742)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: vhost_vdpa: assign irq bypass producer token correctly We used to call irq_bypass_unregister_producer() in vhost_vdpa_setup_vq_irq() which is problematic as we don\u0026apos;t know if the token pointer is still valid or not. Actually, we use the eventfd_ctx as the token so the life cycle of the token should be bound to the VHOST_SET_VRING_CALL instead of vhost_vdpa_setup_vq_irq() which could be called by set_status(). Fixing this by setting up irq bypass producer\u0026apos;s token when handling VHOST_SET_VRING_CALL and un-registering the producer before calling vhost_vring_ioctl() to prevent a possible use after free as eventfd could have been released in vhost_vring_ioctl(). And such registering and unregistering will only be done if DRIVER_OK is set.(CVE-2024-47748)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: PCI: keystone: Fix if-statement expression in ks_pcie_quirk() This code accidentally uses \u0026amp;\u0026amp; where || was intended. It potentially results in a NULL dereference. Thus, fix the if-statement expression to use the correct condition. [kwilczynski: commit log](CVE-2024-47756)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: nbd: fix race between timeout and normal completion If request timetout is handled by nbd_requeue_cmd(), normal completion has to be stopped for avoiding to complete this requeued request, other use-after-free can be triggered. Fix the race by clearing NBD_CMD_INFLIGHT in nbd_requeue_cmd(), meantime make sure that cmd-\u0026gt;lock is grabbed for clearing the flag and the requeue.(CVE-2024-49855)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: efistub/tpm: Use ACPI reclaim memory for event log to avoid corruption The TPM event log table is a Linux specific construct, where the data produced by the GetEventLog() boot service is cached in memory, and passed on to the OS using an EFI configuration table. The use of EFI_LOADER_DATA here results in the region being left unreserved in the E820 memory map constructed by the EFI stub, and this is the memory description that is passed on to the incoming kernel by kexec, which is therefore unaware that the region should be reserved. Even though the utility of the TPM2 event log after a kexec is questionable, any corruption might send the parsing code off into the weeds and crash the kernel. So let\u0026apos;s use EFI_ACPI_RECLAIM_MEMORY instead, which is always treated as reserved by the E820 conversion logic.(CVE-2024-49858)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: f2fs: fix to check atomic_file in f2fs ioctl interfaces Some f2fs ioctl interfaces like f2fs_ioc_set_pin_file(), f2fs_move_file_range(), and f2fs_defragment_range() missed to check atomic_write status, which may cause potential race issue, fix it.(CVE-2024-49859)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ACPI: sysfs: validate return type of _STR method Only buffer objects are valid return values of _STR. If something else is returned description_show() will access invalid memory.(CVE-2024-49860)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: powercap: intel_rapl: Fix off by one in get_rpi() The rp-\u0026gt;priv-\u0026gt;rpi array is either rpi_msr or rpi_tpmi which have NR_RAPL_PRIMITIVES number of elements. Thus the \u0026gt; needs to be \u0026gt;= to prevent an off by one access.(CVE-2024-49862)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate When doing cleanup, if flags without OCFS2_BH_READAHEAD, it may trigger NULL pointer dereference in the following ocfs2_set_buffer_uptodate() if bh is NULL.(CVE-2024-49877)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm: omapdrm: Add missing check for alloc_ordered_workqueue As it may return NULL pointer and cause NULL pointer dereference. Add check for the return value of alloc_ordered_workqueue.(CVE-2024-49879)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ext4: update orig_path in ext4_find_extent() In ext4_find_extent(), if the path is not big enough, we free it and set *orig_path to NULL. But after reallocating and successfully initializing the path, we don\u0026apos;t update *orig_path, in which case the caller gets a valid path but a NULL ppath, and this may cause a NULL pointer dereference or a path memory leak. For example: ext4_split_extent path = *ppath = 2000 ext4_find_extent if (depth \u0026gt; path[0].p_maxdepth) kfree(path = 2000); *orig_path = path = NULL; path = kcalloc() = 3000 ext4_split_extent_at(*ppath = NULL) path = *ppath; ex = path[depth].p_ext; // NULL pointer dereference! ================================================================== BUG: kernel NULL pointer dereference, address: 0000000000000010 CPU: 6 UID: 0 PID: 576 Comm: fsstress Not tainted 6.11.0-rc2-dirty #847 RIP: 0010:ext4_split_extent_at+0x6d/0x560 Call Trace: \u0026lt;TASK\u0026gt; ext4_split_extent.isra.0+0xcb/0x1b0 ext4_ext_convert_to_initialized+0x168/0x6c0 ext4_ext_handle_unwritten_extents+0x325/0x4d0 ext4_ext_map_blocks+0x520/0xdb0 ext4_map_blocks+0x2b0/0x690 ext4_iomap_begin+0x20e/0x2c0 [...] ================================================================== Therefore, *orig_path is updated when the extent lookup succeeds, so that the caller can safely use path or *ppath.(CVE-2024-49881)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ext4: fix double brelse() the buffer of the extents path In ext4_ext_try_to_merge_up(), set path[1].p_bh to NULL after it has been released, otherwise it may be released twice. An example of what triggers this is as follows: split2 map split1 |--------|-------|--------| ext4_ext_map_blocks ext4_ext_handle_unwritten_extents ext4_split_convert_extents // path-\u0026gt;p_depth == 0 ext4_split_extent // 1. do split1 ext4_split_extent_at |ext4_ext_insert_extent | ext4_ext_create_new_leaf | ext4_ext_grow_indepth | le16_add_cpu(\u0026amp;neh-\u0026gt;eh_depth, 1) | ext4_find_extent | // return -ENOMEM |// get error and try zeroout |path = ext4_find_extent | path-\u0026gt;p_depth = 1 |ext4_ext_try_to_merge | ext4_ext_try_to_merge_up | path-\u0026gt;p_depth = 0 | brelse(path[1].p_bh) ---\u0026gt; not set to NULL here |// zeroout success // 2. update path ext4_find_extent // 3. do split2 ext4_split_extent_at ext4_ext_insert_extent ext4_ext_create_new_leaf ext4_ext_grow_indepth le16_add_cpu(\u0026amp;neh-\u0026gt;eh_depth, 1) ext4_find_extent path[0].p_bh = NULL; path-\u0026gt;p_depth = 1 read_extent_tree_block ---\u0026gt; return err // path[1].p_bh is still the old value ext4_free_ext_path ext4_ext_drop_refs // path-\u0026gt;p_depth == 1 brelse(path[1].p_bh) ---\u0026gt; brelse a buffer twice Finally got the following WARRNING when removing the buffer from lru: ============================================ VFS: brelse: Trying to free free buffer WARNING: CPU: 2 PID: 72 at fs/buffer.c:1241 __brelse+0x58/0x90 CPU: 2 PID: 72 Comm: kworker/u19:1 Not tainted 6.9.0-dirty #716 RIP: 0010:__brelse+0x58/0x90 Call Trace: \u0026lt;TASK\u0026gt; __find_get_block+0x6e7/0x810 bdev_getblk+0x2b/0x480 __ext4_get_inode_loc+0x48a/0x1240 ext4_get_inode_loc+0xb2/0x150 ext4_reserve_inode_write+0xb7/0x230 __ext4_mark_inode_dirty+0x144/0x6a0 ext4_ext_insert_extent+0x9c8/0x3230 ext4_ext_map_blocks+0xf45/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] ============================================(CVE-2024-49882)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ext4: aovid use-after-free in ext4_ext_insert_extent() As Ojaswin mentioned in Link, in ext4_ext_insert_extent(), if the path is reallocated in ext4_ext_create_new_leaf(), we\u0026apos;ll use the stale path and cause UAF. Below is a sample trace with dummy values: ext4_ext_insert_extent path = *ppath = 2000 ext4_ext_create_new_leaf(ppath) ext4_find_extent(ppath) path = *ppath = 2000 if (depth \u0026gt; path[0].p_maxdepth) kfree(path = 2000); *ppath = path = NULL; path = kcalloc() = 3000 *ppath = 3000; return path; /* here path is still 2000, UAF! */ eh = path[depth].p_hdr ================================================================== BUG: KASAN: slab-use-after-free in ext4_ext_insert_extent+0x26d4/0x3330 Read of size 8 at addr ffff8881027bf7d0 by task kworker/u36:1/179 CPU: 3 UID: 0 PID: 179 Comm: kworker/u6:1 Not tainted 6.11.0-rc2-dirty #866 Call Trace: \u0026lt;TASK\u0026gt; ext4_ext_insert_extent+0x26d4/0x3330 ext4_ext_map_blocks+0xe22/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 [...] Allocated by task 179: ext4_find_extent+0x81c/0x1f70 ext4_ext_map_blocks+0x146/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 ext4_writepages+0x26d/0x4e0 do_writepages+0x175/0x700 [...] Freed by task 179: kfree+0xcb/0x240 ext4_find_extent+0x7c0/0x1f70 ext4_ext_insert_extent+0xa26/0x3330 ext4_ext_map_blocks+0xe22/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 ext4_writepages+0x26d/0x4e0 do_writepages+0x175/0x700 [...] ================================================================== So use *ppath to update the path to avoid the above problem.(CVE-2024-49883)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ext4: fix slab-use-after-free in ext4_split_extent_at() We hit the following use-after-free: ================================================================== BUG: KASAN: slab-use-after-free in ext4_split_extent_at+0xba8/0xcc0 Read of size 2 at addr ffff88810548ed08 by task kworker/u20:0/40 CPU: 0 PID: 40 Comm: kworker/u20:0 Not tainted 6.9.0-dirty #724 Call Trace: \u0026lt;TASK\u0026gt; kasan_report+0x93/0xc0 ext4_split_extent_at+0xba8/0xcc0 ext4_split_extent.isra.0+0x18f/0x500 ext4_split_convert_extents+0x275/0x750 ext4_ext_handle_unwritten_extents+0x73e/0x1580 ext4_ext_map_blocks+0xe20/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] Allocated by task 40: __kmalloc_noprof+0x1ac/0x480 ext4_find_extent+0xf3b/0x1e70 ext4_ext_map_blocks+0x188/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] Freed by task 40: kfree+0xf1/0x2b0 ext4_find_extent+0xa71/0x1e70 ext4_ext_insert_extent+0xa22/0x3260 ext4_split_extent_at+0x3ef/0xcc0 ext4_split_extent.isra.0+0x18f/0x500 ext4_split_convert_extents+0x275/0x750 ext4_ext_handle_unwritten_extents+0x73e/0x1580 ext4_ext_map_blocks+0xe20/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] ================================================================== The flow of issue triggering is as follows: ext4_split_extent_at path = *ppath ext4_ext_insert_extent(ppath) ext4_ext_create_new_leaf(ppath) ext4_find_extent(orig_path) path = *orig_path read_extent_tree_block // return -ENOMEM or -EIO ext4_free_ext_path(path) kfree(path) *orig_path = NULL a. If err is -ENOMEM: ext4_ext_dirty(path + path-\u0026gt;p_depth) // path use-after-free !!! b. If err is -EIO and we have EXT_DEBUG defined: ext4_ext_show_leaf(path) eh = path[depth].p_hdr // path also use-after-free !!! So when trying to zeroout or fix the extent length, call ext4_find_extent() to update the path. In addition we use *ppath directly as an ext4_ext_show_leaf() input to avoid possible use-after-free when EXT_DEBUG is defined, and to avoid unnecessary path updates.(CVE-2024-49884)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: platform/x86: ISST: Fix the KASAN report slab-out-of-bounds bug Attaching SST PCI device to VM causes \u0026quot;BUG: KASAN: slab-out-of-bounds\u0026quot;. kasan report: [ 19.411889] ================================================================== [ 19.413702] BUG: KASAN: slab-out-of-bounds in _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.415634] Read of size 8 at addr ffff888829e65200 by task cpuhp/16/113 [ 19.417368] [ 19.418627] CPU: 16 PID: 113 Comm: cpuhp/16 Tainted: G E 6.9.0 #10 [ 19.420435] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference Platform, BIOS VMW201.00V.20192059.B64.2207280713 07/28/2022 [ 19.422687] Call Trace: [ 19.424091] \u0026lt;TASK\u0026gt; [ 19.425448] dump_stack_lvl+0x5d/0x80 [ 19.426963] ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.428694] print_report+0x19d/0x52e [ 19.430206] ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [ 19.431837] ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.433539] kasan_report+0xf0/0x170 [ 19.435019] ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.436709] _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.438379] ? __pfx_sched_clock_cpu+0x10/0x10 [ 19.439910] isst_if_cpu_online+0x406/0x58f [isst_if_common] [ 19.441573] ? __pfx_isst_if_cpu_online+0x10/0x10 [isst_if_common] [ 19.443263] ? ttwu_queue_wakelist+0x2c1/0x360 [ 19.444797] cpuhp_invoke_callback+0x221/0xec0 [ 19.446337] cpuhp_thread_fun+0x21b/0x610 [ 19.447814] ? __pfx_cpuhp_thread_fun+0x10/0x10 [ 19.449354] smpboot_thread_fn+0x2e7/0x6e0 [ 19.450859] ? __pfx_smpboot_thread_fn+0x10/0x10 [ 19.452405] kthread+0x29c/0x350 [ 19.453817] ? __pfx_kthread+0x10/0x10 [ 19.455253] ret_from_fork+0x31/0x70 [ 19.456685] ? __pfx_kthread+0x10/0x10 [ 19.458114] ret_from_fork_asm+0x1a/0x30 [ 19.459573] \u0026lt;/TASK\u0026gt; [ 19.460853] [ 19.462055] Allocated by task 1198: [ 19.463410] kasan_save_stack+0x30/0x50 [ 19.464788] kasan_save_track+0x14/0x30 [ 19.466139] __kasan_kmalloc+0xaa/0xb0 [ 19.467465] __kmalloc+0x1cd/0x470 [ 19.468748] isst_if_cdev_register+0x1da/0x350 [isst_if_common] [ 19.470233] isst_if_mbox_init+0x108/0xff0 [isst_if_mbox_msr] [ 19.471670] do_one_initcall+0xa4/0x380 [ 19.472903] do_init_module+0x238/0x760 [ 19.474105] load_module+0x5239/0x6f00 [ 19.475285] init_module_from_file+0xd1/0x130 [ 19.476506] idempotent_init_module+0x23b/0x650 [ 19.477725] __x64_sys_finit_module+0xbe/0x130 [ 19.476506] idempotent_init_module+0x23b/0x650 [ 19.477725] __x64_sys_finit_module+0xbe/0x130 [ 19.478920] do_syscall_64+0x82/0x160 [ 19.480036] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 19.481292] [ 19.482205] The buggy address belongs to the object at ffff888829e65000 which belongs to the cache kmalloc-512 of size 512 [ 19.484818] The buggy address is located 0 bytes to the right of allocated 512-byte region [ffff888829e65000, ffff888829e65200) [ 19.487447] [ 19.488328] The buggy address belongs to the physical page: [ 19.489569] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff888829e60c00 pfn:0x829e60 [ 19.491140] head: order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0 [ 19.492466] anon flags: 0x57ffffc0000840(slab|head|node=1|zone=2|lastcpupid=0x1fffff) [ 19.493914] page_type: 0xffffffff() [ 19.494988] raw: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [ 19.496451] raw: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [ 19.497906] head: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [ 19.499379] head: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [ 19.500844] head: 0057ffffc0000003 ffffea0020a79801 ffffea0020a79848 00000000ffffffff [ 19.502316] head: 0000000800000000 0000000000000000 00000000ffffffff 0000000000000000 [ 19.503784] page dumped because: k ---truncated---(CVE-2024-49886)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ext4: avoid use-after-free in ext4_ext_show_leaf() In ext4_find_extent(), path may be freed by error or be reallocated, so using a previously saved *ppath may have been freed and thus may trigger use-after-free, as follows: ext4_split_extent path = *ppath; ext4_split_extent_at(ppath) path = ext4_find_extent(ppath) ext4_split_extent_at(ppath) // ext4_find_extent fails to free path // but zeroout succeeds ext4_ext_show_leaf(inode, path) eh = path[depth].p_hdr // path use-after-free !!! Similar to ext4_split_extent_at(), we use *ppath directly as an input to ext4_ext_show_leaf(). Fix a spelling error by the way. Same problem in ext4_ext_handle_unwritten_extents(). Since \u0026apos;path\u0026apos; is only used in ext4_ext_show_leaf(), remove \u0026apos;path\u0026apos; and use *ppath directly. This issue is triggered only when EXT_DEBUG is defined and therefore does not affect functionality.(CVE-2024-49889)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check stream before comparing them [WHAT \u0026amp; HOW] amdgpu_dm can pass a null stream to dc_is_stream_unchanged. It is necessary to check for null before dereferencing them. This fixes 1 FORWARD_NULL issue reported by Coverity.(CVE-2024-49896)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add null check for top_pipe_to_program in commit_planes_for_stream This commit addresses a null pointer dereference issue in the `commit_planes_for_stream` function at line 4140. The issue could occur when `top_pipe_to_program` is null. The fix adds a check to ensure `top_pipe_to_program` is not null before accessing its stream_res. This prevents a null pointer dereference. Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.c:4140 commit_planes_for_stream() error: we previously assumed \u0026apos;top_pipe_to_program\u0026apos; could be null (see line 3906)(CVE-2024-49913)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add NULL check for clk_mgr and clk_mgr-\u0026gt;funcs in dcn30_init_hw This commit addresses a potential null pointer dereference issue in the `dcn30_init_hw` function. The issue could occur when `dc-\u0026gt;clk_mgr` or `dc-\u0026gt;clk_mgr-\u0026gt;funcs` is null. The fix adds a check to ensure `dc-\u0026gt;clk_mgr` and `dc-\u0026gt;clk_mgr-\u0026gt;funcs` is not null before accessing its functions. This prevents a potential null pointer dereference. Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c:789 dcn30_init_hw() error: we previously assumed \u0026apos;dc-\u0026gt;clk_mgr\u0026apos; could be null (see line 628)(CVE-2024-49917)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check null pointers before using them [WHAT \u0026amp; HOW] These pointers are null checked previously in the same function, indicating they might be null as reported by Coverity. As a result, they need to be checked when used again. This fixes 3 FORWARD_NULL issue reported by Coverity.(CVE-2024-49922)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: fbdev: pxafb: Fix possible use after free in pxafb_task() In the pxafb_probe function, it calls the pxafb_init_fbinfo function, after which \u0026amp;fbi-\u0026gt;task is associated with pxafb_task. Moreover, within this pxafb_init_fbinfo function, the pxafb_blank function within the \u0026amp;pxafb_ops struct is capable of scheduling work. If we remove the module which will call pxafb_remove to make cleanup, it will call unregister_framebuffer function which can call do_unregister_framebuffer to free fbi-\u0026gt;fb through put_fb_info(fb_info), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows: CPU0 CPU1 | pxafb_task pxafb_remove | unregister_framebuffer(info) | do_unregister_framebuffer(fb_info) | put_fb_info(fb_info) | // free fbi-\u0026gt;fb | set_ctrlr_state(fbi, state) | __pxafb_lcd_power(fbi, 0) | fbi-\u0026gt;lcd_power(on, \u0026amp;fbi-\u0026gt;fb.var) | //use fbi-\u0026gt;fb Fix it by ensuring that the work is canceled before proceeding with the cleanup in pxafb_remove. Note that only root user can remove the driver at runtime.(CVE-2024-49924)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: blk_iocost: fix more out of bound shifts Recently running UBSAN caught few out of bound shifts in the ioc_forgive_debts() function: UBSAN: shift-out-of-bounds in block/blk-iocost.c:2142:38 shift exponent 80 is too large for 64-bit type \u0026apos;u64\u0026apos; (aka \u0026apos;unsigned long long\u0026apos;) ... UBSAN: shift-out-of-bounds in block/blk-iocost.c:2144:30 shift exponent 80 is too large for 64-bit type \u0026apos;u64\u0026apos; (aka \u0026apos;unsigned long long\u0026apos;) ... Call Trace: \u0026lt;IRQ\u0026gt; dump_stack_lvl+0xca/0x130 __ubsan_handle_shift_out_of_bounds+0x22c/0x280 ? __lock_acquire+0x6441/0x7c10 ioc_timer_fn+0x6cec/0x7750 ? blk_iocost_init+0x720/0x720 ? call_timer_fn+0x5d/0x470 call_timer_fn+0xfa/0x470 ? blk_iocost_init+0x720/0x720 __run_timer_base+0x519/0x700 ... Actual impact of this issue was not identified but I propose to fix the undefined behaviour. The proposed fix to prevent those out of bound shifts consist of precalculating exponent before using it the shift operations by taking min value from the actual exponent and maximum possible number of bits.(CVE-2024-49933)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: fs/inode: Prevent dump_mapping() accessing invalid dentry.d_name.name It\u0026apos;s observed that a crash occurs during hot-remove a memory device, in which user is accessing the hugetlb. See calltrace as following: ------------[ cut here ]------------ WARNING: CPU: 1 PID: 14045 at arch/x86/mm/fault.c:1278 do_user_addr_fault+0x2a0/0x790 Modules linked in: kmem device_dax cxl_mem cxl_pmem cxl_port cxl_pci dax_hmem dax_pmem nd_pmem cxl_acpi nd_btt cxl_core crc32c_intel nvme virtiofs fuse nvme_core nfit libnvdimm dm_multipath scsi_dh_rdac scsi_dh_emc s mirror dm_region_hash dm_log dm_mod CPU: 1 PID: 14045 Comm: daxctl Not tainted 6.10.0-rc2-lizhijian+ #492 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:do_user_addr_fault+0x2a0/0x790 Code: 48 8b 00 a8 04 0f 84 b5 fe ff ff e9 1c ff ff ff 4c 89 e9 4c 89 e2 be 01 00 00 00 bf 02 00 00 00 e8 b5 ef 24 00 e9 42 fe ff ff \u0026lt;0f\u0026gt; 0b 48 83 c4 08 4c 89 ea 48 89 ee 4c 89 e7 5b 5d 41 5c 41 5d 41 RSP: 0000:ffffc90000a575f0 EFLAGS: 00010046 RAX: ffff88800c303600 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000001000 RSI: ffffffff82504162 RDI: ffffffff824b2c36 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffffc90000a57658 R13: 0000000000001000 R14: ffff88800bc2e040 R15: 0000000000000000 FS: 00007f51cb57d880(0000) GS:ffff88807fd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000001000 CR3: 00000000072e2004 CR4: 00000000001706f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: \u0026lt;TASK\u0026gt; ? __warn+0x8d/0x190 ? do_user_addr_fault+0x2a0/0x790 ? report_bug+0x1c3/0x1d0 ? handle_bug+0x3c/0x70 ? exc_invalid_op+0x14/0x70 ? asm_exc_invalid_op+0x16/0x20 ? do_user_addr_fault+0x2a0/0x790 ? exc_page_fault+0x31/0x200 exc_page_fault+0x68/0x200 \u0026lt;...snip...\u0026gt; BUG: unable to handle page fault for address: 0000000000001000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0 Oops: Oops: 0000 [#1] PREEMPT SMP PTI ---[ end trace 0000000000000000 ]--- BUG: unable to handle page fault for address: 0000000000001000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0 Oops: Oops: 0000 [#1] PREEMPT SMP PTI CPU: 1 PID: 14045 Comm: daxctl Kdump: loaded Tainted: G W 6.10.0-rc2-lizhijian+ #492 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:dentry_name+0x1f4/0x440 \u0026lt;...snip...\u0026gt; ? dentry_name+0x2fa/0x440 vsnprintf+0x1f3/0x4f0 vprintk_store+0x23a/0x540 vprintk_emit+0x6d/0x330 _printk+0x58/0x80 dump_mapping+0x10b/0x1a0 ? __pfx_free_object_rcu+0x10/0x10 __dump_page+0x26b/0x3e0 ? vprintk_emit+0xe0/0x330 ? _printk+0x58/0x80 ? dump_page+0x17/0x50 dump_page+0x17/0x50 do_migrate_range+0x2f7/0x7f0 ? do_migrate_range+0x42/0x7f0 ? offline_pages+0x2f4/0x8c0 offline_pages+0x60a/0x8c0 memory_subsys_offline+0x9f/0x1c0 ? lockdep_hardirqs_on+0x77/0x100 ? _raw_spin_unlock_irqrestore+0x38/0x60 device_offline+0xe3/0x110 state_store+0x6e/0xc0 kernfs_fop_write_iter+0x143/0x200 vfs_write+0x39f/0x560 ksys_write+0x65/0xf0 do_syscall_64+0x62/0x130 Previously, some sanity check have been done in dump_mapping() before the print facility parsing \u0026apos;%pd\u0026apos; though, it\u0026apos;s still possible to run into an invalid dentry.d_name.name. Since dump_mapping() only needs to dump the filename only, retrieve it by itself in a safer way to prevent an unnecessary crash. Note that either retrieving the filename with \u0026apos;%pd\u0026apos; or strncpy_from_kernel_nofault(), the filename could be unreliable.(CVE-2024-49934)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: net/xen-netback: prevent UAF in xenvif_flush_hash() During the list_for_each_entry_rcu iteration call of xenvif_flush_hash, kfree_rcu does not exist inside the rcu read critical section, so if kfree_rcu is called when the rcu grace period ends during the iteration, UAF occurs when accessing head-\u0026gt;next after the entry becomes free. Therefore, to solve this, you need to change it to list_for_each_entry_safe.(CVE-2024-49936)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: l2tp: prevent possible tunnel refcount underflow When a session is created, it sets a backpointer to its tunnel. When the session refcount drops to 0, l2tp_session_free drops the tunnel refcount if session-\u0026gt;tunnel is non-NULL. However, session-\u0026gt;tunnel is set in l2tp_session_create, before the tunnel refcount is incremented by l2tp_session_register, which leaves a small window where session-\u0026gt;tunnel is non-NULL when the tunnel refcount hasn\u0026apos;t been bumped. Moving the assignment to l2tp_session_register is trivial but l2tp_session_create calls l2tp_session_set_header_len which uses session-\u0026gt;tunnel to get the tunnel\u0026apos;s encap. Add an encap arg to l2tp_session_set_header_len to avoid using session-\u0026gt;tunnel. If l2tpv3 sessions have colliding IDs, it is possible for l2tp_v3_session_get to race with l2tp_session_register and fetch a session which doesn\u0026apos;t yet have session-\u0026gt;tunnel set. Add a check for this case.(CVE-2024-49940)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix uaf in l2cap_connect [Syzbot reported] BUG: KASAN: slab-use-after-free in l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949 Read of size 8 at addr ffff8880241e9800 by task kworker/u9:0/54 CPU: 0 UID: 0 PID: 54 Comm: kworker/u9:0 Not tainted 6.11.0-rc6-syzkaller-00268-g788220eee30d #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 Workqueue: hci2 hci_rx_work Call Trace: \u0026lt;TASK\u0026gt; __dump_stack lib/dump_stack.c:93 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:119 print_address_description mm/kasan/report.c:377 [inline] print_report+0xc3/0x620 mm/kasan/report.c:488 kasan_report+0xd9/0x110 mm/kasan/report.c:601 l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949 l2cap_connect_req net/bluetooth/l2cap_core.c:4080 [inline] l2cap_bredr_sig_cmd net/bluetooth/l2cap_core.c:4772 [inline] l2cap_sig_channel net/bluetooth/l2cap_core.c:5543 [inline] l2cap_recv_frame+0xf0b/0x8eb0 net/bluetooth/l2cap_core.c:6825 l2cap_recv_acldata+0x9b4/0xb70 net/bluetooth/l2cap_core.c:7514 hci_acldata_packet net/bluetooth/hci_core.c:3791 [inline] hci_rx_work+0xaab/0x1610 net/bluetooth/hci_core.c:4028 process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231 process_scheduled_works kernel/workqueue.c:3312 [inline] worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389 kthread+0x2c1/0x3a0 kernel/kthread.c:389 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 ... Freed by task 5245: kasan_save_stack+0x33/0x60 mm/kasan/common.c:47 kasan_save_track+0x14/0x30 mm/kasan/common.c:68 kasan_save_free_info+0x3b/0x60 mm/kasan/generic.c:579 poison_slab_object+0xf7/0x160 mm/kasan/common.c:240 __kasan_slab_free+0x32/0x50 mm/kasan/common.c:256 kasan_slab_free include/linux/kasan.h:184 [inline] slab_free_hook mm/slub.c:2256 [inline] slab_free mm/slub.c:4477 [inline] kfree+0x12a/0x3b0 mm/slub.c:4598 l2cap_conn_free net/bluetooth/l2cap_core.c:1810 [inline] kref_put include/linux/kref.h:65 [inline] l2cap_conn_put net/bluetooth/l2cap_core.c:1822 [inline] l2cap_conn_del+0x59d/0x730 net/bluetooth/l2cap_core.c:1802 l2cap_connect_cfm+0x9e6/0xf80 net/bluetooth/l2cap_core.c:7241 hci_connect_cfm include/net/bluetooth/hci_core.h:1960 [inline] hci_conn_failed+0x1c3/0x370 net/bluetooth/hci_conn.c:1265 hci_abort_conn_sync+0x75a/0xb50 net/bluetooth/hci_sync.c:5583 abort_conn_sync+0x197/0x360 net/bluetooth/hci_conn.c:2917 hci_cmd_sync_work+0x1a4/0x410 net/bluetooth/hci_sync.c:328 process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231 process_scheduled_works kernel/workqueue.c:3312 [inline] worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389 kthread+0x2c1/0x3a0 kernel/kthread.c:389 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244(CVE-2024-49950)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: static_call: Replace pointless WARN_ON() in static_call_module_notify() static_call_module_notify() triggers a WARN_ON(), when memory allocation fails in __static_call_add_module(). That\u0026apos;s not really justified, because the failure case must be correctly handled by the well known call chain and the error code is passed through to the initiating userspace application. A memory allocation fail is not a fatal problem, but the WARN_ON() takes the machine out when panic_on_warn is set. Replace it with a pr_warn().(CVE-2024-49954)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ACPI: battery: Fix possible crash when unregistering a battery hook When a battery hook returns an error when adding a new battery, then the battery hook is automatically unregistered. However the battery hook provider cannot know that, so it will later call battery_hook_unregister() on the already unregistered battery hook, resulting in a crash. Fix this by using the list head to mark already unregistered battery hooks as already being unregistered so that they can be ignored by battery_hook_unregister().(CVE-2024-49955)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ocfs2: reserve space for inline xattr before attaching reflink tree One of our customers reported a crash and a corrupted ocfs2 filesystem. The crash was due to the detection of corruption. Upon troubleshooting, the fsck -fn output showed the below corruption [EXTENT_LIST_FREE] Extent list in owner 33080590 claims 230 as the next free chain record, but fsck believes the largest valid value is 227. Clamp the next record value? n The stat output from the debugfs.ocfs2 showed the following corruption where the \u0026quot;Next Free Rec:\u0026quot; had overshot the \u0026quot;Count:\u0026quot; in the root metadata block. Inode: 33080590 Mode: 0640 Generation: 2619713622 (0x9c25a856) FS Generation: 904309833 (0x35e6ac49) CRC32: 00000000 ECC: 0000 Type: Regular Attr: 0x0 Flags: Valid Dynamic Features: (0x16) HasXattr InlineXattr Refcounted Extended Attributes Block: 0 Extended Attributes Inline Size: 256 User: 0 (root) Group: 0 (root) Size: 281320357888 Links: 1 Clusters: 141738 ctime: 0x66911b56 0x316edcb8 -- Fri Jul 12 06:02:30.829349048 2024 atime: 0x66911d6b 0x7f7a28d -- Fri Jul 12 06:11:23.133669517 2024 mtime: 0x66911b56 0x12ed75d7 -- Fri Jul 12 06:02:30.317552087 2024 dtime: 0x0 -- Wed Dec 31 17:00:00 1969 Refcount Block: 2777346 Last Extblk: 2886943 Orphan Slot: 0 Sub Alloc Slot: 0 Sub Alloc Bit: 14 Tree Depth: 1 Count: 227 Next Free Rec: 230 ## Offset Clusters Block# 0 0 2310 2776351 1 2310 2139 2777375 2 4449 1221 2778399 3 5670 731 2779423 4 6401 566 2780447 ....... .... ....... ....... .... ....... The issue was in the reflink workfow while reserving space for inline xattr. The problematic function is ocfs2_reflink_xattr_inline(). By the time this function is called the reflink tree is already recreated at the destination inode from the source inode. At this point, this function reserves space for inline xattrs at the destination inode without even checking if there is space at the root metadata block. It simply reduces the l_count from 243 to 227 thereby making space of 256 bytes for inline xattr whereas the inode already has extents beyond this index (in this case up to 230), thereby causing corruption. The fix for this is to reserve space for inline metadata at the destination inode before the reflink tree gets recreated. The customer has verified the fix.(CVE-2024-49958)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: r8169: add tally counter fields added with RTL8125 RTL8125 added fields to the tally counter, what may result in the chip dma\u0026apos;ing these new fields to unallocated memory. Therefore make sure that the allocated memory area is big enough to hold all of the tally counter values, even if we use only parts of it.(CVE-2024-49973)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: uprobes: fix kernel info leak via \u0026quot;[uprobes]\u0026quot; vma xol_add_vma() maps the uninitialized page allocated by __create_xol_area() into userspace. On some architectures (x86) this memory is readable even without VM_READ, VM_EXEC results in the same pgprot_t as VM_EXEC|VM_READ, although this doesn\u0026apos;t really matter, debugger can read this memory anyway.(CVE-2024-49975)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: gso: fix udp gso fraglist segmentation after pull from frag_list Detect gso fraglist skbs with corrupted geometry (see below) and pass these to skb_segment instead of skb_segment_list, as the first can segment them correctly. Valid SKB_GSO_FRAGLIST skbs - consist of two or more segments - the head_skb holds the protocol headers plus first gso_size - one or more frag_list skbs hold exactly one segment - all but the last must be gso_size Optional datapath hooks such as NAT and BPF (bpf_skb_pull_data) can modify these skbs, breaking these invariants. In extreme cases they pull all data into skb linear. For UDP, this causes a NULL ptr deref in __udpv4_gso_segment_list_csum at udp_hdr(seg-\u0026gt;next)-\u0026gt;dest. Detect invalid geometry due to pull, by checking head_skb size. Don\u0026apos;t just drop, as this may blackhole a destination. Convert to be able to pass to regular skb_segment.(CVE-2024-49978)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: media: venus: fix use after free bug in venus_remove due to race condition in venus_probe, core-\u0026gt;work is bound with venus_sys_error_handler, which is used to handle error. The code use core-\u0026gt;sys_err_done to make sync work. The core-\u0026gt;work is started in venus_event_notify. If we call venus_remove, there might be an unfished work. The possible sequence is as follows: CPU0 CPU1 |venus_sys_error_handler venus_remove | hfi_destroy | venus_hfi_destroy | kfree(hdev); | |hfi_reinit |venus_hfi_queues_reinit |//use hdev Fix it by canceling the work in venus_remove.(CVE-2024-49981)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm/stm: Avoid use-after-free issues with crtc and plane ltdc_load() calls functions drm_crtc_init_with_planes(), drm_universal_plane_init() and drm_encoder_init(). These functions should not be called with parameters allocated with devm_kzalloc() to avoid use-after-free issues [1]. Use allocations managed by the DRM framework. Found by Linux Verification Center (linuxtesting.org). [1] https://lore.kernel.org/lkml/u366i76e3qhh3ra5oxrtngjtm2u5lterkekcz6y2jkndhuxzli@diujon4h7qwb/(CVE-2024-49992)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: tipc: guard against string buffer overrun Smatch reports that copying media_name and if_name to name_parts may overwrite the destination. .../bearer.c:166 bearer_name_validate() error: strcpy() \u0026apos;media_name\u0026apos; too large for \u0026apos;name_parts-\u0026gt;media_name\u0026apos; (32 vs 16) .../bearer.c:167 bearer_name_validate() error: strcpy() \u0026apos;if_name\u0026apos; too large for \u0026apos;name_parts-\u0026gt;if_name\u0026apos; (1010102 vs 16) This does seem to be the case so guard against this possibility by using strscpy() and failing if truncation occurs. Introduced by commit b97bf3fd8f6a (\u0026quot;[TIPC] Initial merge\u0026quot;) Compile tested only.(CVE-2024-49995)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: cifs: Fix buffer overflow when parsing NFS reparse points ReparseDataLength is sum of the InodeType size and DataBuffer size. So to get DataBuffer size it is needed to subtract InodeType\u0026apos;s size from ReparseDataLength. Function cifs_strndup_from_utf16() is currentlly accessing buf-\u0026gt;DataBuffer at position after the end of the buffer because it does not subtract InodeType size from the length. Fix this problem and correctly subtract variable len. Member InodeType is present only when reparse buffer is large enough. Check for ReparseDataLength before accessing InodeType to prevent another invalid memory access. Major and minor rdev values are present also only when reparse buffer is large enough. Check for reparse buffer size before calling reparse_mkdev().(CVE-2024-49996)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: static_call: Handle module init failure correctly in static_call_del_module() Module insertion invokes static_call_add_module() to initialize the static calls in a module. static_call_add_module() invokes __static_call_init(), which allocates a struct static_call_mod to either encapsulate the built-in static call sites of the associated key into it so further modules can be added or to append the module to the module chain. If that allocation fails the function returns with an error code and the module core invokes static_call_del_module() to clean up eventually added static_call_mod entries. This works correctly, when all keys used by the module were converted over to a module chain before the failure. If not then static_call_del_module() causes a #GP as it blindly assumes that key::mods points to a valid struct static_call_mod. The problem is that key::mods is not a individual struct member of struct static_call_key, it\u0026apos;s part of a union to save space: union { /* bit 0: 0 = mods, 1 = sites */ unsigned long type; struct static_call_mod *mods; struct static_call_site *sites; }; key::sites is a pointer to the list of built-in usage sites of the static call. The type of the pointer is differentiated by bit 0. A mods pointer has the bit clear, the sites pointer has the bit set. As static_call_del_module() blidly assumes that the pointer is a valid static_call_mod type, it fails to check for this failure case and dereferences the pointer to the list of built-in call sites, which is obviously bogus. Cure it by checking whether the key has a sites or a mods pointer. If it\u0026apos;s a sites pointer then the key is not to be touched. As the sites are walked in the same order as in __static_call_init() the site walk can be terminated because all subsequent sites have not been touched by the init code due to the error exit. If it was converted before the allocation fail, then the inner loop which searches for a module match will find nothing. A fail in the second allocation in __static_call_init() is harmless and does not require special treatment. The first allocation succeeded and converted the key to a module chain. That first entry has mod::mod == NULL and mod::next == NULL, so the inner loop of static_call_del_module() will neither find a module match nor a module chain. The next site in the walk was either already converted, but can\u0026apos;t match the module, or it will exit the outer loop because it has a static_call_site pointer and not a static_call_mod pointer.(CVE-2024-50002)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ALSA: asihpi: Fix potential OOB array access ASIHPI driver stores some values in the static array upon a response from the driver, and its index depends on the firmware. We shouldn\u0026apos;t trust it blindly. This patch adds a sanity check of the array index to fit in the array size.(CVE-2024-50007)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_cmd_802_11_scan_ext() Replace one-element array with a flexible-array member in `struct host_cmd_ds_802_11_scan_ext`. With this, fix the following warning: elo 16 17:51:58 surfacebook kernel: ------------[ cut here ]------------ elo 16 17:51:58 surfacebook kernel: memcpy: detected field-spanning write (size 243) of single field \u0026quot;ext_scan-\u0026gt;tlv_buffer\u0026quot; at drivers/net/wireless/marvell/mwifiex/scan.c:2239 (size 1) elo 16 17:51:58 surfacebook kernel: WARNING: CPU: 0 PID: 498 at drivers/net/wireless/marvell/mwifiex/scan.c:2239 mwifiex_cmd_802_11_scan_ext+0x83/0x90 [mwifiex](CVE-2024-50008)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ext4: dax: fix overflowing extents beyond inode size when partially writing The dax_iomap_rw() does two things in each iteration: map written blocks and copy user data to blocks. If the process is killed by user(See signal handling in dax_iomap_iter()), the copied data will be returned and added on inode size, which means that the length of written extents may exceed the inode size, then fsck will fail. An example is given as: dd if=/dev/urandom of=file bs=4M count=1 dax_iomap_rw iomap_iter // round 1 ext4_iomap_begin ext4_iomap_alloc // allocate 0~2M extents(written flag) dax_iomap_iter // copy 2M data iomap_iter // round 2 iomap_iter_advance iter-\u0026gt;pos += iter-\u0026gt;processed // iter-\u0026gt;pos = 2M ext4_iomap_begin ext4_iomap_alloc // allocate 2~4M extents(written flag) dax_iomap_iter fatal_signal_pending done = iter-\u0026gt;pos - iocb-\u0026gt;ki_pos // done = 2M ext4_handle_inode_extension ext4_update_inode_size // inode size = 2M fsck reports: Inode 13, i_size is 2097152, should be 4194304. Fix? Fix the problem by truncating extents if the written length is smaller than expected.(CVE-2024-50015)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Avoid overflow assignment in link_dp_cts sampling_rate is an uint8_t but is assigned an unsigned int, and thus it can overflow. As a result, sampling_rate is changed to uint32_t. Similarly, LINK_QUAL_PATTERN_SET has a size of 2 bits, and it should only be assigned to a value less or equal than 4. This fixes 2 INTEGER_OVERFLOW issues reported by Coverity.(CVE-2024-50016)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: thermal: core: Reference count the zone in thermal_zone_get_by_id() There are places in the thermal netlink code where nothing prevents the thermal zone object from going away while being accessed after it has been returned by thermal_zone_get_by_id(). To address this, make thermal_zone_get_by_id() get a reference on the thermal zone device object to be returned with the help of get_device(), under thermal_list_lock, and adjust all of its callers to this change with the help of the cleanup.h infrastructure.(CVE-2024-50028)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: slip: make slhc_remember() more robust against malicious packets syzbot found that slhc_remember() was missing checks against malicious packets [1]. slhc_remember() only checked the size of the packet was at least 20, which is not good enough. We need to make sure the packet includes the IPv4 and TCP header that are supposed to be carried. Add iph and th pointers to make the code more readable. [1] BUG: KMSAN: uninit-value in slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666 slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666 ppp_receive_nonmp_frame+0xe45/0x35e0 drivers/net/ppp/ppp_generic.c:2455 ppp_receive_frame drivers/net/ppp/ppp_generic.c:2372 [inline] ppp_do_recv+0x65f/0x40d0 drivers/net/ppp/ppp_generic.c:2212 ppp_input+0x7dc/0xe60 drivers/net/ppp/ppp_generic.c:2327 pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379 sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113 __release_sock+0x1da/0x330 net/core/sock.c:3072 release_sock+0x6b/0x250 net/core/sock.c:3626 pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 ____sys_sendmsg+0x903/0xb60 net/socket.c:2602 ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was created at: slab_post_alloc_hook mm/slub.c:4091 [inline] slab_alloc_node mm/slub.c:4134 [inline] kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4186 kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587 __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678 alloc_skb include/linux/skbuff.h:1322 [inline] sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732 pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 ____sys_sendmsg+0x903/0xb60 net/socket.c:2602 ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f CPU: 0 UID: 0 PID: 5460 Comm: syz.2.33 Not tainted 6.12.0-rc2-syzkaller-00006-g87d6aab2389e #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50033)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ppp: fix ppp_async_encode() illegal access syzbot reported an issue in ppp_async_encode() [1] In this case, pppoe_sendmsg() is called with a zero size. Then ppp_async_encode() is called with an empty skb. BUG: KMSAN: uninit-value in ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline] BUG: KMSAN: uninit-value in ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675 ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline] ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675 ppp_async_send+0x130/0x1b0 drivers/net/ppp/ppp_async.c:634 ppp_channel_bridge_input drivers/net/ppp/ppp_generic.c:2280 [inline] ppp_input+0x1f1/0xe60 drivers/net/ppp/ppp_generic.c:2304 pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379 sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113 __release_sock+0x1da/0x330 net/core/sock.c:3072 release_sock+0x6b/0x250 net/core/sock.c:3626 pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 ____sys_sendmsg+0x903/0xb60 net/socket.c:2602 ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was created at: slab_post_alloc_hook mm/slub.c:4092 [inline] slab_alloc_node mm/slub.c:4135 [inline] kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4187 kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587 __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678 alloc_skb include/linux/skbuff.h:1322 [inline] sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732 pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 ____sys_sendmsg+0x903/0xb60 net/socket.c:2602 ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f CPU: 1 UID: 0 PID: 5411 Comm: syz.1.14 Not tainted 6.12.0-rc1-syzkaller-00165-g360c1f1f24c6 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50035)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: igb: Do not bring the device up after non-fatal error Commit 004d25060c78 (\u0026quot;igb: Fix igb_down hung on surprise removal\u0026quot;) changed igb_io_error_detected() to ignore non-fatal pcie errors in order to avoid hung task that can happen when igb_down() is called multiple times. This caused an issue when processing transient non-fatal errors. igb_io_resume(), which is called after igb_io_error_detected(), assumes that device is brought down by igb_io_error_detected() if the interface is up. This resulted in panic with stacktrace below. [ T3256] igb 0000:09:00.0 haeth0: igb: haeth0 NIC Link is Down [ T292] pcieport 0000:00:1c.5: AER: Uncorrected (Non-Fatal) error received: 0000:09:00.0 [ T292] igb 0000:09:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [ T292] igb 0000:09:00.0: device [8086:1537] error status/mask=00004000/00000000 [ T292] igb 0000:09:00.0: [14] CmpltTO [ 200.105524,009][ T292] igb 0000:09:00.0: AER: TLP Header: 00000000 00000000 00000000 00000000 [ T292] pcieport 0000:00:1c.5: AER: broadcast error_detected message [ T292] igb 0000:09:00.0: Non-correctable non-fatal error reported. [ T292] pcieport 0000:00:1c.5: AER: broadcast mmio_enabled message [ T292] pcieport 0000:00:1c.5: AER: broadcast resume message [ T292] ------------[ cut here ]------------ [ T292] kernel BUG at net/core/dev.c:6539! [ T292] invalid opcode: 0000 [#1] PREEMPT SMP [ T292] RIP: 0010:napi_enable+0x37/0x40 [ T292] Call Trace: [ T292] \u0026lt;TASK\u0026gt; [ T292] ? die+0x33/0x90 [ T292] ? do_trap+0xdc/0x110 [ T292] ? napi_enable+0x37/0x40 [ T292] ? do_error_trap+0x70/0xb0 [ T292] ? napi_enable+0x37/0x40 [ T292] ? napi_enable+0x37/0x40 [ T292] ? exc_invalid_op+0x4e/0x70 [ T292] ? napi_enable+0x37/0x40 [ T292] ? asm_exc_invalid_op+0x16/0x20 [ T292] ? napi_enable+0x37/0x40 [ T292] igb_up+0x41/0x150 [ T292] igb_io_resume+0x25/0x70 [ T292] report_resume+0x54/0x70 [ T292] ? report_frozen_detected+0x20/0x20 [ T292] pci_walk_bus+0x6c/0x90 [ T292] ? aer_print_port_info+0xa0/0xa0 [ T292] pcie_do_recovery+0x22f/0x380 [ T292] aer_process_err_devices+0x110/0x160 [ T292] aer_isr+0x1c1/0x1e0 [ T292] ? disable_irq_nosync+0x10/0x10 [ T292] irq_thread_fn+0x1a/0x60 [ T292] irq_thread+0xe3/0x1a0 [ T292] ? irq_set_affinity_notifier+0x120/0x120 [ T292] ? irq_affinity_notify+0x100/0x100 [ T292] kthread+0xe2/0x110 [ T292] ? kthread_complete_and_exit+0x20/0x20 [ T292] ret_from_fork+0x2d/0x50 [ T292] ? kthread_complete_and_exit+0x20/0x20 [ T292] ret_from_fork_asm+0x11/0x20 [ T292] \u0026lt;/TASK\u0026gt; To fix this issue igb_io_resume() checks if the interface is running and the device is not down this means igb_io_error_detected() did not bring the device down and there is no need to bring it up.(CVE-2024-50040)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: smb: client: fix UAF in async decryption Doing an async decryption (large read) crashes with a slab-use-after-free way down in the crypto API. Reproducer: # mount.cifs -o ...,seal,esize=1 //srv/share /mnt # dd if=/mnt/largefile of=/dev/null ... [ 194.196391] ================================================================== [ 194.196844] BUG: KASAN: slab-use-after-free in gf128mul_4k_lle+0xc1/0x110 [ 194.197269] Read of size 8 at addr ffff888112bd0448 by task kworker/u77:2/899 [ 194.197707] [ 194.197818] CPU: 12 UID: 0 PID: 899 Comm: kworker/u77:2 Not tainted 6.11.0-lku-00028-gfca3ca14a17a-dirty #43 [ 194.198400] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.2-3-gd478f380-prebuilt.qemu.org 04/01/2014 [ 194.199046] Workqueue: smb3decryptd smb2_decrypt_offload [cifs] [ 194.200032] Call Trace: [ 194.200191] \u0026lt;TASK\u0026gt; [ 194.200327] dump_stack_lvl+0x4e/0x70 [ 194.200558] ? gf128mul_4k_lle+0xc1/0x110 [ 194.200809] print_report+0x174/0x505 [ 194.201040] ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [ 194.201352] ? srso_return_thunk+0x5/0x5f [ 194.201604] ? __virt_addr_valid+0xdf/0x1c0 [ 194.201868] ? gf128mul_4k_lle+0xc1/0x110 [ 194.202128] kasan_report+0xc8/0x150 [ 194.202361] ? gf128mul_4k_lle+0xc1/0x110 [ 194.202616] gf128mul_4k_lle+0xc1/0x110 [ 194.202863] ghash_update+0x184/0x210 [ 194.203103] shash_ahash_update+0x184/0x2a0 [ 194.203377] ? __pfx_shash_ahash_update+0x10/0x10 [ 194.203651] ? srso_return_thunk+0x5/0x5f [ 194.203877] ? crypto_gcm_init_common+0x1ba/0x340 [ 194.204142] gcm_hash_assoc_remain_continue+0x10a/0x140 [ 194.204434] crypt_message+0xec1/0x10a0 [cifs] [ 194.206489] ? __pfx_crypt_message+0x10/0x10 [cifs] [ 194.208507] ? srso_return_thunk+0x5/0x5f [ 194.209205] ? srso_return_thunk+0x5/0x5f [ 194.209925] ? srso_return_thunk+0x5/0x5f [ 194.210443] ? srso_return_thunk+0x5/0x5f [ 194.211037] decrypt_raw_data+0x15f/0x250 [cifs] [ 194.212906] ? __pfx_decrypt_raw_data+0x10/0x10 [cifs] [ 194.214670] ? srso_return_thunk+0x5/0x5f [ 194.215193] smb2_decrypt_offload+0x12a/0x6c0 [cifs] This is because TFM is being used in parallel. Fix this by allocating a new AEAD TFM for async decryption, but keep the existing one for synchronous READ cases (similar to what is done in smb3_calc_signature()). Also remove the calls to aead_request_set_callback() and crypto_wait_req() since it\u0026apos;s always going to be a synchronous operation.(CVE-2024-50047)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: serial: protect uart_port_dtr_rts() in uart_shutdown() too Commit af224ca2df29 (serial: core: Prevent unsafe uart port access, part 3) added few uport == NULL checks. It added one to uart_shutdown(), so the commit assumes, uport can be NULL in there. But right after that protection, there is an unprotected \u0026quot;uart_port_dtr_rts(uport, false);\u0026quot; call. That is invoked only if HUPCL is set, so I assume that is the reason why we do not see lots of these reports. Or it cannot be NULL at this point at all for some reason :P. Until the above is investigated, stay on the safe side and move this dereference to the if too. I got this inconsistency from Coverity under CID 1585130. Thanks.(CVE-2024-50058)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ntb: ntb_hw_switchtec: Fix use after free vulnerability in switchtec_ntb_remove due to race condition In the switchtec_ntb_add function, it can call switchtec_ntb_init_sndev function, then \u0026amp;sndev-\u0026gt;check_link_status_work is bound with check_link_status_work. switchtec_ntb_link_notification may be called to start the work. If we remove the module which will call switchtec_ntb_remove to make cleanup, it will free sndev through kfree(sndev), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows: CPU0 CPU1 | check_link_status_work switchtec_ntb_remove | kfree(sndev); | | if (sndev-\u0026gt;link_force_down) | // use sndev Fix it by ensuring that the work is canceled before proceeding with the cleanup in switchtec_ntb_remove.(CVE-2024-50059)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: io_uring: check if we need to reschedule during overflow flush In terms of normal application usage, this list will always be empty. And if an application does overflow a bit, it\u0026apos;ll have a few entries. However, nothing obviously prevents syzbot from running a test case that generates a ton of overflow entries, and then flushing them can take quite a while. Check for needing to reschedule while flushing, and drop our locks and do so if necessary. There\u0026apos;s no state to maintain here as overflows always prune from head-of-list, hence it\u0026apos;s fine to drop and reacquire the locks at the end of the loop.(CVE-2024-50060)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: bpf: Prevent tail call between progs attached to different hooks bpf progs can be attached to kernel functions, and the attached functions can take different parameters or return different return values. If prog attached to one kernel function tail calls prog attached to another kernel function, the ctx access or return value verification could be bypassed. For example, if prog1 is attached to func1 which takes only 1 parameter and prog2 is attached to func2 which takes two parameters. Since verifier assumes the bpf ctx passed to prog2 is constructed based on func2\u0026apos;s prototype, verifier allows prog2 to access the second parameter from the bpf ctx passed to it. The problem is that verifier does not prevent prog1 from passing its bpf ctx to prog2 via tail call. In this case, the bpf ctx passed to prog2 is constructed from func1 instead of func2, that is, the assumption for ctx access verification is bypassed. Another example, if BPF LSM prog1 is attached to hook file_alloc_security, and BPF LSM prog2 is attached to hook bpf_lsm_audit_rule_known. Verifier knows the return value rules for these two hooks, e.g. it is legal for bpf_lsm_audit_rule_known to return positive number 1, and it is illegal for file_alloc_security to return positive number. So verifier allows prog2 to return positive number 1, but does not allow prog1 to return positive number. The problem is that verifier does not prevent prog1 from calling prog2 via tail call. In this case, prog2\u0026apos;s return value 1 will be used as the return value for prog1\u0026apos;s hook file_alloc_security. That is, the return value rule is bypassed. This patch adds restriction for tail call to prevent such bypasses.(CVE-2024-50063)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: zram: free secondary algorithms names We need to kfree() secondary algorithms names when reset zram device that had multi-streams, otherwise we leak memory. [senozhatsky@chromium.org: kfree(NULL) is legal] Link: https://lkml.kernel.org/r/20240917013021.868769-1-senozhatsky@chromium.org(CVE-2024-50064)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: uprobe: avoid out-of-bounds memory access of fetching args Uprobe needs to fetch args into a percpu buffer, and then copy to ring buffer to avoid non-atomic context problem. Sometimes user-space strings, arrays can be very large, but the size of percpu buffer is only page size. And store_trace_args() won\u0026apos;t check whether these data exceeds a single page or not, caused out-of-bounds memory access. It could be reproduced by following steps: 1. build kernel with CONFIG_KASAN enabled 2. save follow program as test.c ``` \\#include \u0026lt;stdio.h\u0026gt; \\#include \u0026lt;stdlib.h\u0026gt; \\#include \u0026lt;string.h\u0026gt; // If string length large than MAX_STRING_SIZE, the fetch_store_strlen() // will return 0, cause __get_data_size() return shorter size, and // store_trace_args() will not trigger out-of-bounds access. // So make string length less than 4096. \\#define STRLEN 4093 void generate_string(char *str, int n) { int i; for (i = 0; i \u0026lt; n; ++i) { char c = i % 26 + \u0026apos;a\u0026apos;; str[i] = c; } str[n-1] = \u0026apos;\\0\u0026apos;; } void print_string(char *str) { printf(\u0026quot;%s\\n\u0026quot;, str); } int main() { char tmp[STRLEN]; generate_string(tmp, STRLEN); print_string(tmp); return 0; } ``` 3. compile program `gcc -o test test.c` 4. get the offset of `print_string()` ``` objdump -t test | grep -w print_string 0000000000401199 g F .text 000000000000001b print_string ``` 5. configure uprobe with offset 0x1199 ``` off=0x1199 cd /sys/kernel/debug/tracing/ echo \u0026quot;p /root/test:${off} arg1=+0(%di):ustring arg2=\\$comm arg3=+0(%di):ustring\u0026quot; \u0026gt; uprobe_events echo 1 \u0026gt; events/uprobes/enable echo 1 \u0026gt; tracing_on ``` 6. run `test`, and kasan will report error. ================================================================== BUG: KASAN: use-after-free in strncpy_from_user+0x1d6/0x1f0 Write of size 8 at addr ffff88812311c004 by task test/499CPU: 0 UID: 0 PID: 499 Comm: test Not tainted 6.12.0-rc3+ #18 Hardware name: Red Hat KVM, BIOS 1.16.0-4.al8 04/01/2014 Call Trace: \u0026lt;TASK\u0026gt; dump_stack_lvl+0x55/0x70 print_address_description.constprop.0+0x27/0x310 kasan_report+0x10f/0x120 ? strncpy_from_user+0x1d6/0x1f0 strncpy_from_user+0x1d6/0x1f0 ? rmqueue.constprop.0+0x70d/0x2ad0 process_fetch_insn+0xb26/0x1470 ? __pfx_process_fetch_insn+0x10/0x10 ? _raw_spin_lock+0x85/0xe0 ? __pfx__raw_spin_lock+0x10/0x10 ? __pte_offset_map+0x1f/0x2d0 ? unwind_next_frame+0xc5f/0x1f80 ? arch_stack_walk+0x68/0xf0 ? is_bpf_text_address+0x23/0x30 ? kernel_text_address.part.0+0xbb/0xd0 ? __kernel_text_address+0x66/0xb0 ? unwind_get_return_address+0x5e/0xa0 ? __pfx_stack_trace_consume_entry+0x10/0x10 ? arch_stack_walk+0xa2/0xf0 ? _raw_spin_lock_irqsave+0x8b/0xf0 ? __pfx__raw_spin_lock_irqsave+0x10/0x10 ? depot_alloc_stack+0x4c/0x1f0 ? _raw_spin_unlock_irqrestore+0xe/0x30 ? stack_depot_save_flags+0x35d/0x4f0 ? kasan_save_stack+0x34/0x50 ? kasan_save_stack+0x24/0x50 ? mutex_lock+0x91/0xe0 ? __pfx_mutex_lock+0x10/0x10 prepare_uprobe_buffer.part.0+0x2cd/0x500 uprobe_dispatcher+0x2c3/0x6a0 ? __pfx_uprobe_dispatcher+0x10/0x10 ? __kasan_slab_alloc+0x4d/0x90 handler_chain+0xdd/0x3e0 handle_swbp+0x26e/0x3d0 ? __pfx_handle_swbp+0x10/0x10 ? uprobe_pre_sstep_notifier+0x151/0x1b0 irqentry_exit_to_user_mode+0xe2/0x1b0 asm_exc_int3+0x39/0x40 RIP: 0033:0x401199 Code: 01 c2 0f b6 45 fb 88 02 83 45 fc 01 8b 45 fc 3b 45 e4 7c b7 8b 45 e4 48 98 48 8d 50 ff 48 8b 45 e8 48 01 d0 ce RSP: 002b:00007ffdf00576a8 EFLAGS: 00000206 RAX: 00007ffdf00576b0 RBX: 0000000000000000 RCX: 0000000000000ff2 RDX: 0000000000000ffc RSI: 0000000000000ffd RDI: 00007ffdf00576b0 RBP: 00007ffdf00586b0 R08: 00007feb2f9c0d20 R09: 00007feb2f9c0d20 R10: 0000000000000001 R11: 0000000000000202 R12: 0000000000401040 R13: 00007ffdf0058780 R14: 0000000000000000 R15: 0000000000000000 \u0026lt;/TASK\u0026gt; This commit enforces the buffer\u0026apos;s maxlen less than a page-size to avoid store_trace_args() out-of-memory access.(CVE-2024-50067)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: parport: Proper fix for array out-of-bounds access The recent fix for array out-of-bounds accesses replaced sprintf() calls blindly with snprintf(). However, since snprintf() returns the would-be-printed size, not the actually output size, the length calculation can still go over the given limit. Use scnprintf() instead of snprintf(), which returns the actually output letters, for addressing the potential out-of-bounds access properly.(CVE-2024-50074)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: tcp: fix mptcp DSS corruption due to large pmtu xmit Syzkaller was able to trigger a DSS corruption: TCP: request_sock_subflow_v4: Possible SYN flooding on port [::]:20002. Sending cookies. ------------[ cut here ]------------ WARNING: CPU: 0 PID: 5227 at net/mptcp/protocol.c:695 __mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695 Modules linked in: CPU: 0 UID: 0 PID: 5227 Comm: syz-executor350 Not tainted 6.11.0-syzkaller-08829-gaf9c191ac2a0 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 RIP: 0010:__mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695 Code: 0f b6 dc 31 ff 89 de e8 b5 dd ea f5 89 d8 48 81 c4 50 01 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 98 da ea f5 90 \u0026lt;0f\u0026gt; 0b 90 e9 47 ff ff ff e8 8a da ea f5 90 0f 0b 90 e9 99 e0 ff ff RSP: 0018:ffffc90000006db8 EFLAGS: 00010246 RAX: ffffffff8ba9df18 RBX: 00000000000055f0 RCX: ffff888030023c00 RDX: 0000000000000100 RSI: 00000000000081e5 RDI: 00000000000055f0 RBP: 1ffff110062bf1ae R08: ffffffff8ba9cf12 R09: 1ffff110062bf1b8 R10: dffffc0000000000 R11: ffffed10062bf1b9 R12: 0000000000000000 R13: dffffc0000000000 R14: 00000000700cec61 R15: 00000000000081e5 FS: 000055556679c380(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020287000 CR3: 0000000077892000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: \u0026lt;IRQ\u0026gt; move_skbs_to_msk net/mptcp/protocol.c:811 [inline] mptcp_data_ready+0x29c/0xa90 net/mptcp/protocol.c:854 subflow_data_ready+0x34a/0x920 net/mptcp/subflow.c:1490 tcp_data_queue+0x20fd/0x76c0 net/ipv4/tcp_input.c:5283 tcp_rcv_established+0xfba/0x2020 net/ipv4/tcp_input.c:6237 tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915 tcp_v4_rcv+0x2dc0/0x37f0 net/ipv4/tcp_ipv4.c:2350 ip_protocol_deliver_rcu+0x22e/0x440 net/ipv4/ip_input.c:205 ip_local_deliver_finish+0x341/0x5f0 net/ipv4/ip_input.c:233 NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314 NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314 __netif_receive_skb_one_core net/core/dev.c:5662 [inline] __netif_receive_skb+0x2bf/0x650 net/core/dev.c:5775 process_backlog+0x662/0x15b0 net/core/dev.c:6107 __napi_poll+0xcb/0x490 net/core/dev.c:6771 napi_poll net/core/dev.c:6840 [inline] net_rx_action+0x89b/0x1240 net/core/dev.c:6962 handle_softirqs+0x2c5/0x980 kernel/softirq.c:554 do_softirq+0x11b/0x1e0 kernel/softirq.c:455 \u0026lt;/IRQ\u0026gt; \u0026lt;TASK\u0026gt; __local_bh_enable_ip+0x1bb/0x200 kernel/softirq.c:382 local_bh_enable include/linux/bottom_half.h:33 [inline] rcu_read_unlock_bh include/linux/rcupdate.h:919 [inline] __dev_queue_xmit+0x1764/0x3e80 net/core/dev.c:4451 dev_queue_xmit include/linux/netdevice.h:3094 [inline] neigh_hh_output include/net/neighbour.h:526 [inline] neigh_output include/net/neighbour.h:540 [inline] ip_finish_output2+0xd41/0x1390 net/ipv4/ip_output.c:236 ip_local_out net/ipv4/ip_output.c:130 [inline] __ip_queue_xmit+0x118c/0x1b80 net/ipv4/ip_output.c:536 __tcp_transmit_skb+0x2544/0x3b30 net/ipv4/tcp_output.c:1466 tcp_transmit_skb net/ipv4/tcp_output.c:1484 [inline] tcp_mtu_probe net/ipv4/tcp_output.c:2547 [inline] tcp_write_xmit+0x641d/0x6bf0 net/ipv4/tcp_output.c:2752 __tcp_push_pending_frames+0x9b/0x360 net/ipv4/tcp_output.c:3015 tcp_push_pending_frames include/net/tcp.h:2107 [inline] tcp_data_snd_check net/ipv4/tcp_input.c:5714 [inline] tcp_rcv_established+0x1026/0x2020 net/ipv4/tcp_input.c:6239 tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915 sk_backlog_rcv include/net/sock.h:1113 [inline] __release_sock+0x214/0x350 net/core/sock.c:3072 release_sock+0x61/0x1f0 net/core/sock.c:3626 mptcp_push_ ---truncated---(CVE-2024-50083)",
"id": "OESA-2024-2369",
"modified": "2026-08-06T11:07:50Z",
"published": "2024-11-08T11:07:50Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2369"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48961"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48975"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-49004"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-45021"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-46677"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-46809"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47659"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47660"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47668"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47673"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47690"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47691"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47693"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47696"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47699"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47701"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47703"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47705"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47723"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47726"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47739"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47742"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47748"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47756"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49855"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49858"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49859"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49860"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49862"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49877"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49879"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49881"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49882"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49883"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49884"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49886"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49889"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49896"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49913"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49917"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49922"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49924"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49933"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49934"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49936"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49940"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49950"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49954"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49955"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49958"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49973"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49975"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49978"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49981"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49992"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49995"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49996"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50002"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50007"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50008"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50015"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50016"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50028"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50033"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50035"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50040"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50047"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50058"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50059"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50060"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50063"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50064"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50067"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50074"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50083"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "kernel security update",
"upstream": [
"CVE-2022-48961",
"CVE-2022-48975",
"CVE-2022-49004",
"CVE-2024-45021",
"CVE-2024-46677",
"CVE-2024-46809",
"CVE-2024-47659",
"CVE-2024-47660",
"CVE-2024-47668",
"CVE-2024-47673",
"CVE-2024-47690",
"CVE-2024-47691",
"CVE-2024-47693",
"CVE-2024-47696",
"CVE-2024-47699",
"CVE-2024-47701",
"CVE-2024-47703",
"CVE-2024-47705",
"CVE-2024-47723",
"CVE-2024-47726",
"CVE-2024-47739",
"CVE-2024-47742",
"CVE-2024-47748",
"CVE-2024-47756",
"CVE-2024-49855",
"CVE-2024-49858",
"CVE-2024-49859",
"CVE-2024-49860",
"CVE-2024-49862",
"CVE-2024-49877",
"CVE-2024-49879",
"CVE-2024-49881",
"CVE-2024-49882",
"CVE-2024-49883",
"CVE-2024-49884",
"CVE-2024-49886",
"CVE-2024-49889",
"CVE-2024-49896",
"CVE-2024-49913",
"CVE-2024-49917",
"CVE-2024-49922",
"CVE-2024-49924",
"CVE-2024-49933",
"CVE-2024-49934",
"CVE-2024-49936",
"CVE-2024-49940",
"CVE-2024-49950",
"CVE-2024-49954",
"CVE-2024-49955",
"CVE-2024-49958",
"CVE-2024-49973",
"CVE-2024-49975",
"CVE-2024-49978",
"CVE-2024-49981",
"CVE-2024-49992",
"CVE-2024-49995",
"CVE-2024-49996",
"CVE-2024-50002",
"CVE-2024-50007",
"CVE-2024-50008",
"CVE-2024-50015",
"CVE-2024-50016",
"CVE-2024-50028",
"CVE-2024-50033",
"CVE-2024-50035",
"CVE-2024-50040",
"CVE-2024-50047",
"CVE-2024-50058",
"CVE-2024-50059",
"CVE-2024-50060",
"CVE-2024-50063",
"CVE-2024-50064",
"CVE-2024-50067",
"CVE-2024-50074",
"CVE-2024-50083"
]
}
OESA-2024-2370 (CVE-2022-48948)
Vulnerability from osv_openeuler – Published: 2024-11-08 11:07 – Updated: 2026-08-06 11:07 – Source websiteThe Linux Kernel, the operating system core itself.
Security Fix(es):
In the Linux kernel, the following vulnerability has been resolved: usb: gadget: uvc: Prevent buffer overflow in setup handler Setup function uvc_function_setup permits control transfer requests with up to 64 bytes of payload (UVC_MAX_REQUEST_SIZE), data stage handler for OUT transfer uses memcpy to copy req->actual bytes to uvc_event->data.data array of size 60. This may result in an overflow of 4 bytes.(CVE-2022-48948)
In the Linux kernel, the following vulnerability has been resolved: igb: Initialize mailbox message for VF reset When a MAC address is not assigned to the VF, that portion of the message sent to the VF is not set. The memory, however, is allocated from the stack meaning that information may be leaked to the VM. Initialize the message buffer to 0 so that no information is passed to the VM in this case.(CVE-2022-48949)
In the Linux kernel, the following vulnerability has been resolved: net: hisilicon: Fix potential use-after-free in hix5hd2_rx() The skb is delivered to napi_gro_receive() which may free it, after calling this, dereferencing skb may trigger use-after-free.(CVE-2022-48960)
In the Linux kernel, the following vulnerability has been resolved: net: hisilicon: Fix potential use-after-free in hisi_femac_rx() The skb is delivered to napi_gro_receive() which may free it, after calling this, dereferencing skb may trigger use-after-free.(CVE-2022-48962)
In the Linux kernel, the following vulnerability has been resolved: net: mvneta: Prevent out of bounds read in mvneta_config_rss() The pp->indir[0] value comes from the user. It is passed to: if (cpu_online(pp->rxq_def)) inside the mvneta_percpu_elect() function. It needs bounds checkeding to ensure that it is not beyond the end of the cpu bitmap.(CVE-2022-48966)
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix not cleanup led when bt_init fails bt_init() calls bt_leds_init() to register led, but if it fails later, bt_leds_cleanup() is not called to unregister it. This can cause panic if the argument "bluetooth-power" in text is freed and then another led_trigger_register() tries to access it: BUG: unable to handle page fault for address: ffffffffc06d3bc0 RIP: 0010:strcmp+0xc/0x30 Call Trace: <TASK> led_trigger_register+0x10d/0x4f0 led_trigger_register_simple+0x7d/0x100 bt_init+0x39/0xf7 [bluetooth] do_one_initcall+0xd0/0x4e0(CVE-2022-48971)
In the Linux kernel, the following vulnerability has been resolved: mac802154: fix missing INIT_LIST_HEAD in ieee802154_if_add() Kernel fault injection test reports null-ptr-deref as follows: BUG: kernel NULL pointer dereference, address: 0000000000000008 RIP: 0010:cfg802154_netdev_notifier_call+0x120/0x310 include/linux/list.h:114 Call Trace: <TASK> raw_notifier_call_chain+0x6d/0xa0 kernel/notifier.c:87 call_netdevice_notifiers_info+0x6e/0xc0 net/core/dev.c:1944 unregister_netdevice_many_notify+0x60d/0xcb0 net/core/dev.c:1982 unregister_netdevice_queue+0x154/0x1a0 net/core/dev.c:10879 register_netdevice+0x9a8/0xb90 net/core/dev.c:10083 ieee802154_if_add+0x6ed/0x7e0 net/mac802154/iface.c:659 ieee802154_register_hw+0x29c/0x330 net/mac802154/main.c:229 mcr20a_probe+0xaaa/0xcb1 drivers/net/ieee802154/mcr20a.c:1316 ieee802154_if_add() allocates wpan_dev as netdev's private data, but not init the list in struct wpan_dev. cfg802154_netdev_notifier_call() manage the list when device register/unregister, and may lead to null-ptr-deref. Use INIT_LIST_HEAD() on it to initialize it correctly.(CVE-2022-48972)
In the Linux kernel, the following vulnerability has been resolved: HID: core: fix shift-out-of-bounds in hid_report_raw_event Syzbot reported shift-out-of-bounds in hid_report_raw_event. microsoft 0003:045E:07DA.0001: hid_field_extract() called with n (128) > 32! (swapper/0) ====================================================================== UBSAN: shift-out-of-bounds in drivers/hid/hid-core.c:1323:20 shift exponent 127 is too large for 32-bit type 'int' CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.1.0-rc4-syzkaller-00159-g4bbf3422df78 #0 Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Call Trace: <IRQ> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106 ubsan_epilogue lib/ubsan.c:151 [inline] __ubsan_handle_shift_out_of_bounds+0x3a6/0x420 lib/ubsan.c:322 snto32 drivers/hid/hid-core.c:1323 [inline] hid_input_fetch_field drivers/hid/hid-core.c:1572 [inline] hid_process_report drivers/hid/hid-core.c:1665 [inline] hid_report_raw_event+0xd56/0x18b0 drivers/hid/hid-core.c:1998 hid_input_report+0x408/0x4f0 drivers/hid/hid-core.c:2066 hid_irq_in+0x459/0x690 drivers/hid/usbhid/hid-core.c:284 __usb_hcd_giveback_urb+0x369/0x530 drivers/usb/core/hcd.c:1671 dummy_timer+0x86b/0x3110 drivers/usb/gadget/udc/dummy_hcd.c:1988 call_timer_fn+0xf5/0x210 kernel/time/timer.c:1474 expire_timers kernel/time/timer.c:1519 [inline] __run_timers+0x76a/0x980 kernel/time/timer.c:1790 run_timer_softirq+0x63/0xf0 kernel/time/timer.c:1803 __do_softirq+0x277/0x75b kernel/softirq.c:571 __irq_exit_rcu+0xec/0x170 kernel/softirq.c:650 irq_exit_rcu+0x5/0x20 kernel/softirq.c:662 sysvec_apic_timer_interrupt+0x91/0xb0 arch/x86/kernel/apic/apic.c:1107 ====================================================================== If the size of the integer (unsigned n) is bigger than 32 in snto32(), shift exponent will be too large for 32-bit type 'int', resulting in a shift-out-of-bounds bug. Fix this by adding a check on the size of the integer (unsigned n) in snto32(). To add support for n greater than 32 bits, set n to 32, if n is greater than 32.(CVE-2022-48978)
In the Linux kernel, the following vulnerability has been resolved: ASoC: soc-pcm: Add NULL check in BE reparenting Add NULL check in dpcm_be_reparent API, to handle kernel NULL pointer dereference error. The issue occurred in fuzzing test.(CVE-2022-48992)
In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Fix PCI device refcount leak in dmar_dev_scope_init() for_each_pci_dev() is implemented by pci_get_device(). The comment of pci_get_device() says that it will increase the reference count for the returned pci_dev and also decrease the reference count for the input pci_dev @from if it is not NULL. If we break for_each_pci_dev() loop with pdev not NULL, we need to call pci_dev_put() to decrease the reference count. Add the missing pci_dev_put() for the error path to avoid reference count leak.(CVE-2022-49002)
In the Linux kernel, the following vulnerability has been resolved: ASoC: ops: Fix bounds check for _sx controls For _sx controls the semantics of the max field is not the usual one, max is the number of steps rather than the maximum value. This means that our check in snd_soc_put_volsw_sx() needs to just check against the maximum value.(CVE-2022-49005)
In the Linux kernel, the following vulnerability has been resolved: hwmon: (coretemp) fix pci device refcount leak in nv1a_ram_new() As comment of pci_get_domain_bus_and_slot() says, it returns a pci device with refcount increment, when finish using it, the caller must decrement the reference count by calling pci_dev_put(). So call it after using to avoid refcount leak.(CVE-2022-49011)
In the Linux kernel, the following vulnerability has been resolved: net/9p: Fix a potential socket leak in p9_socket_open Both p9_fd_create_tcp() and p9_fd_create_unix() will call p9_socket_open(). If the creation of p9_trans_fd fails, p9_fd_create_tcp() and p9_fd_create_unix() will return an error directly instead of releasing the cscoket, which will result in a socket leak. This patch adds sock_release() to fix the leak issue.(CVE-2022-49020)
In the Linux kernel, the following vulnerability has been resolved: net: phy: fix null-ptr-deref while probe() failed I got a null-ptr-deref report as following when doing fault injection test: BUG: kernel NULL pointer dereference, address: 0000000000000058 Oops: 0000 [#1] PREEMPT SMP KASAN PTI CPU: 1 PID: 253 Comm: 507-spi-dm9051 Tainted: G B N 6.1.0-rc3+ Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: 0010:klist_put+0x2d/0xd0 Call Trace: <TASK> klist_remove+0xf1/0x1c0 device_release_driver_internal+0x23e/0x2d0 bus_remove_device+0x1bd/0x240 device_del+0x357/0x770 phy_device_remove+0x11/0x30 mdiobus_unregister+0xa5/0x140 release_nodes+0x6a/0xa0 devres_release_all+0xf8/0x150 device_unbind_cleanup+0x19/0xd0 //probe path: phy_device_register() device_add() phy_connect phy_attach_direct() //set device driver probe() //it's failed, driver is not bound device_bind_driver() // probe failed, it's not called //remove path: phy_device_remove() device_del() device_release_driver_internal() __device_release_driver() //dev->drv is not NULL klist_remove() <- knode_driver is not added yet, cause null-ptr-deref In phy_attach_direct(), after setting the 'dev->driver', probe() fails, device_bind_driver() is not called, so the knode_driver->n_klist is not set, then it causes null-ptr-deref in __device_release_driver() while deleting device. Fix this by setting dev->driver to NULL in the error path in phy_attach_direct().(CVE-2022-49021)
In the Linux kernel, the following vulnerability has been resolved: iio: health: afe4403: Fix oob read in afe4403_read_raw KASAN report out-of-bounds read as follows: BUG: KASAN: global-out-of-bounds in afe4403_read_raw+0x42e/0x4c0 Read of size 4 at addr ffffffffc02ac638 by task cat/279 Call Trace: afe4403_read_raw iio_read_channel_info dev_attr_show The buggy address belongs to the variable: afe4403_channel_leds+0x18/0xffffffffffffe9e0 This issue can be reproduced by singe command: $ cat /sys/bus/spi/devices/spi0.0/iio\:device0/in_intensity6_raw The array size of afe4403_channel_leds is less than channels, so access with chan->address cause OOB read in afe4403_read_raw. Fix it by moving access before use it.(CVE-2022-49031)
In the Linux kernel, the following vulnerability has been resolved: iio: health: afe4404: Fix oob read in afe4404_[read|write]raw KASAN report out-of-bounds read as follows: BUG: KASAN: global-out-of-bounds in afe4404_read_raw+0x2ce/0x380 Read of size 4 at addr ffffffffc00e4658 by task cat/278 Call Trace: afe4404_read_raw iio_read_channel_info dev_attr_show The buggy address belongs to the variable: afe4404_channel_leds+0x18/0xffffffffffffe9c0 This issue can be reproduce by singe command: $ cat /sys/bus/i2c/devices/0-0058/iio\:device0/in_intensity6_raw The array size of afe4404_channel_leds and afe4404_channel_offdacs are less than channels, so access with chan->address cause OOB read in afe4404[read|write]_raw. Fix it by moving access before use them.(CVE-2022-49032)
In the Linux kernel, the following vulnerability has been resolved:
smack: tcp: ipv4, fix incorrect labeling
Currently, Smack mirrors the label of incoming tcp/ipv4 connections: when a label 'foo' connects to a label 'bar' with tcp/ipv4, 'foo' always gets 'foo' in returned ipv4 packets. So, 1) returned packets are incorrectly labeled ('foo' instead of 'bar') 2) 'bar' can write to 'foo' without being authorized to write.
Here is a scenario how to see this:
-
Take two machines, let's call them C and S, with active Smack in the default state (no settings, no rules, no labeled hosts, only builtin labels)
-
At S, add Smack rule 'foo bar w' (labels 'foo' and 'bar' are instantiated at S at this moment)
-
At S, at label 'bar', launch a program that listens for incoming tcp/ipv4 connections
-
From C, at label 'foo', connect to the listener at S. (label 'foo' is instantiated at C at this moment) Connection succeedes and works.
-
Send some data in both directions.
- Collect network traffic of this connection.
All packets in both directions are labeled with the CIPSO of the label 'foo'. Hence, label 'bar' writes to 'foo' without being authorized, and even without ever being known at C.
If anybody cares: exactly the same happens with DCCP.
This behavior 1st manifested in release 2.6.29.4 (see Fixes below) and it looks unintentional. At least, no explanation was provided.
I changed returned packes label into the 'bar', to bring it into line with the Smack documentation claims.(CVE-2024-47659)
In the Linux kernel, the following vulnerability has been resolved:
nilfs2: fix state management in error path of log writing function
After commit a694291a6211 ("nilfs2: separate wait function from nilfs_segctor_write") was applied, the log writing function nilfs_segctor_do_construct() was able to issue I/O requests continuously even if user data blocks were split into multiple logs across segments, but two potential flaws were introduced in its error handling.
First, if nilfs_segctor_begin_construction() fails while creating the second or subsequent logs, the log writing function returns without calling nilfs_segctor_abort_construction(), so the writeback flag set on pages/folios will remain uncleared. This causes page cache operations to hang waiting for the writeback flag. For example, truncate_inode_pages_final(), which is called via nilfs_evict_inode() when an inode is evicted from memory, will hang.
Second, the NILFS_I_COLLECTED flag set on normal inodes remain uncleared. As a result, if the next log write involves checkpoint creation, that's fine, but if a partial log write is performed that does not, inodes with NILFS_I_COLLECTED set are erroneously removed from the "sc_dirty_files" list, and their data and b-tree blocks may not be written to the device, corrupting the block mapping.
Fix these issues by uniformly calling nilfs_segctor_abort_construction() on failure of each step in the loop in nilfs_segctor_do_construct(), having it clean up logs and segment usages according to progress, and correcting the conditions for calling nilfs_redirty_inodes() to ensure that the NILFS_I_COLLECTED flag is cleared.(CVE-2024-47669)
In the Linux kernel, the following vulnerability has been resolved: RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency In the commit aee2424246f9 ("RDMA/iwcm: Fix a use-after-free related to destroying CM IDs"), the function flush_workqueue is invoked to flush the work queue iwcm_wq. But at that time, the work queue iwcm_wq was created via the function alloc_ordered_workqueue without the flag WQ_MEM_RECLAIM. Because the current process is trying to flush the whole iwcm_wq, if iwcm_wq doesn't have the flag WQ_MEM_RECLAIM, verify that the current process is not reclaiming memory or running on a workqueue which doesn't have the flag WQ_MEM_RECLAIM as that can break forward-progress guarantee leading to a deadlock. The call trace is as below: [ 125.350876][ T1430] Call Trace: [ 125.356281][ T1430] <TASK> [ 125.361285][ T1430] ? __warn (kernel/panic.c:693) [ 125.367640][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.375689][ T1430] ? report_bug (lib/bug.c:180 lib/bug.c:219) [ 125.382505][ T1430] ? handle_bug (arch/x86/kernel/traps.c:239) [ 125.388987][ T1430] ? exc_invalid_op (arch/x86/kernel/traps.c:260 (discriminator 1)) [ 125.395831][ T1430] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:621) [ 125.403125][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.410984][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.418764][ T1430] __flush_workqueue (kernel/workqueue.c:3970) [ 125.426021][ T1430] ? __pfxmightresched (kernel/sched/core.c:10151) [ 125.433431][ T1430] ? destroy_cm_id (drivers/infiniband/core/iwcm.c:375) iw_cm [ 125.441209][ T1430] ? pfxflushworkqueue (kernel/workqueue.c:3910) [ 125.473900][ T1430] ? _raw_spin_lock_irqsave (arch/x86/include/asm/atomic.h:107 include/linux/atomic/atomic-arch-fallback.h:2170 include/linux/atomic/atomic-instrumented.h:1302 include/asm-generic/qspinlock.h:111 include/linux/spinlock.h:187 include/linux/spinlock_api_smp.h:111 kernel/locking/spinlock.c:162) [ 125.473909][ T1430] ? pfx__raw_spin_lock_irqsave (kernel/locking/spinlock.c:161) [ 125.482537][ T1430] _destroy_id (drivers/infiniband/core/cma.c:2044) rdma_cm [ 125.495072][ T1430] nvme_rdma_free_queue (drivers/nvme/host/rdma.c:656 drivers/nvme/host/rdma.c:650) nvme_rdma [ 125.505827][ T1430] nvme_rdma_reset_ctrl_work (drivers/nvme/host/rdma.c:2180) nvme_rdma [ 125.505831][ T1430] process_one_work (kernel/workqueue.c:3231) [ 125.515122][ T1430] worker_thread (kernel/workqueue.c:3306 kernel/workqueue.c:3393) [ 125.515127][ T1430] ? __pfx_worker_thread (kernel/workqueue.c:3339) [ 125.531837][ T1430] kthread (kernel/kthread.c:389) [ 125.539864][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.550628][ T1430] ret_from_fork (arch/x86/kernel/process.c:147) [ 125.558840][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.558844][ T1430] ret_from_fork_asm (arch/x86/entry/entry_64.S:257) [ 125.566487][ T1430] </TASK> [ 125.566488][ T1430] ---[ end trace 0000000000000000 ]---(CVE-2024-47696)
In the Linux kernel, the following vulnerability has been resolved: drivers: media: dvb-frontends/rtl2830: fix an out-of-bounds write error Ensure index in rtl2830_pid_filter does not exceed 31 to prevent out-of-bounds access. dev->filters is a 32-bit value, so set_bit and clear_bit functions should only operate on indices from 0 to 31. If index is 32, it will attempt to access a non-existent 33rd bit, leading to out-of-bounds access. Change the boundary check from index > 32 to index >= 32 to resolve this issue.(CVE-2024-47697)
In the Linux kernel, the following vulnerability has been resolved: ext4: avoid OOB when system.data xattr changes underneath the filesystem When looking up for an entry in an inlined directory, if e_value_offs is changed underneath the filesystem by some change in the block device, it will lead to an out-of-bounds access that KASAN detects as an UAF. EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none. loop0: detected capacity change from 2048 to 2047 ================================================================== BUG: KASAN: use-after-free in ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500 Read of size 1 at addr ffff88803e91130f by task syz-executor269/5103 CPU: 0 UID: 0 PID: 5103 Comm: syz-executor269 Not tainted 6.11.0-rc4-syzkaller #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Call Trace: <TASK> __dump_stack lib/dump_stack.c:93 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119 print_address_description mm/kasan/report.c:377 [inline] print_report+0x169/0x550 mm/kasan/report.c:488 kasan_report+0x143/0x180 mm/kasan/report.c:601 ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500 ext4_find_inline_entry+0x4be/0x5e0 fs/ext4/inline.c:1697 __ext4_find_entry+0x2b4/0x1b30 fs/ext4/namei.c:1573 ext4_lookup_entry fs/ext4/namei.c:1727 [inline] ext4_lookup+0x15f/0x750 fs/ext4/namei.c:1795 lookup_one_qstr_excl+0x11f/0x260 fs/namei.c:1633 filename_create+0x297/0x540 fs/namei.c:3980 do_symlinkat+0xf9/0x3a0 fs/namei.c:4587 __do_sys_symlinkat fs/namei.c:4610 [inline] __se_sys_symlinkat fs/namei.c:4607 [inline] __x64_sys_symlinkat+0x95/0xb0 fs/namei.c:4607 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f3e73ced469 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 21 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fff4d40c258 EFLAGS: 00000246 ORIG_RAX: 000000000000010a RAX: ffffffffffffffda RBX: 0032656c69662f2e RCX: 00007f3e73ced469 RDX: 0000000020000200 RSI: 00000000ffffff9c RDI: 00000000200001c0 RBP: 0000000000000000 R08: 00007fff4d40c290 R09: 00007fff4d40c290 R10: 0023706f6f6c2f76 R11: 0000000000000246 R12: 00007fff4d40c27c R13: 0000000000000003 R14: 431bde82d7b634db R15: 00007fff4d40c2b0 </TASK> Calling ext4_xattr_ibody_find right after reading the inode with ext4_get_inode_loc will lead to a check of the validity of the xattrs, avoiding this problem.(CVE-2024-47701)
In the Linux kernel, the following vulnerability has been resolved: firmware_loader: Block path traversal Most firmware names are hardcoded strings, or are constructed from fairly constrained format strings where the dynamic parts are just some hex numbers or such. However, there are a couple codepaths in the kernel where firmware file names contain string components that are passed through from a device or semi-privileged userspace; the ones I could find (not counting interfaces that require root privileges) are: - lpfc_sli4_request_firmware_update() seems to construct the firmware filename from "ModelName", a string that was previously parsed out of some descriptor ("Vital Product Data") in lpfc_fill_vpd() - nfp_net_fw_find() seems to construct a firmware filename from a model name coming from nfp_hwinfo_lookup(pf->hwinfo, "nffw.partno"), which I think parses some descriptor that was read from the device. (But this case likely isn't exploitable because the format string looks like "netronome/nic_%s", and there shouldn't be any folders starting with "netronome/nic_". The previous case was different because there, the "%s" is at the start of the format string.) - module_flash_fw_schedule() is reachable from the ETHTOOL_MSG_MODULE_FW_FLASH_ACT netlink command, which is marked as GENL_UNS_ADMIN_PERM (meaning CAP_NET_ADMIN inside a user namespace is enough to pass the privilege check), and takes a userspace-provided firmware name. (But I think to reach this case, you need to have CAP_NET_ADMIN over a network namespace that a special kind of ethernet device is mapped into, so I think this is not a viable attack path in practice.) Fix it by rejecting any firmware names containing ".." path components. For what it's worth, I went looking and haven't found any USB device drivers that use the firmware loader dangerously.(CVE-2024-47742)
In the Linux kernel, the following vulnerability has been resolved: ACPI: sysfs: validate return type of _STR method Only buffer objects are valid return values of _STR. If something else is returned description_show() will access invalid memory.(CVE-2024-49860)
In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate When doing cleanup, if flags without OCFS2_BH_READAHEAD, it may trigger NULL pointer dereference in the following ocfs2_set_buffer_uptodate() if bh is NULL.(CVE-2024-49877)
In the Linux kernel, the following vulnerability has been resolved: resource: fix region_intersects() vs add_memory_driver_managed() On a system with CXL memory, the resource tree (/proc/iomem) related to CXL memory may look like something as follows. 490000000-50fffffff : CXL Window 0 490000000-50fffffff : region0 490000000-50fffffff : dax0.0 490000000-50fffffff : System RAM (kmem) Because drivers/dax/kmem.c calls add_memory_driver_managed() during onlining CXL memory, which makes "System RAM (kmem)" a descendant of "CXL Window X". This confuses region_intersects(), which expects all "System RAM" resources to be at the top level of iomem_resource. This can lead to bugs. For example, when the following command line is executed to write some memory in CXL memory range via /dev/mem, $ dd if=data of=/dev/mem bs=$((1 << 10)) seek=$((0x490000000 >> 10)) count=1 dd: error writing '/dev/mem': Bad address 1+0 records in 0+0 records out 0 bytes copied, 0.0283507 s, 0.0 kB/s the command fails as expected. However, the error code is wrong. It should be "Operation not permitted" instead of "Bad address". More seriously, the /dev/mem permission checking in devmem_is_allowed() passes incorrectly. Although the accessing is prevented later because ioremap() isn't allowed to map system RAM, it is a potential security issue. During command executing, the following warning is reported in the kernel log for calling ioremap() on system RAM. ioremap on RAM at 0x0000000490000000 - 0x0000000490000fff WARNING: CPU: 2 PID: 416 at arch/x86/mm/ioremap.c:216 __ioremap_caller.constprop.0+0x131/0x35d Call Trace: memremap+0xcb/0x184 xlate_dev_mem_ptr+0x25/0x2f write_mem+0x94/0xfb vfs_write+0x128/0x26d ksys_write+0xac/0xfe do_syscall_64+0x9a/0xfd entry_SYSCALL_64_after_hwframe+0x4b/0x53 The details of command execution process are as follows. In the above resource tree, "System RAM" is a descendant of "CXL Window 0" instead of a top level resource. So, region_intersects() will report no System RAM resources in the CXL memory region incorrectly, because it only checks the top level resources. Consequently, devmem_is_allowed() will return 1 (allow access via /dev/mem) for CXL memory region incorrectly. Fortunately, ioremap() doesn't allow to map System RAM and reject the access. So, region_intersects() needs to be fixed to work correctly with the resource tree with "System RAM" not at top level as above. To fix it, if we found a unmatched resource in the top level, we will continue to search matched resources in its descendant resources. So, we will not miss any matched resources in resource tree anymore. In the new implementation, an example resource tree |------------- "CXL Window 0" ------------| |-- "System RAM" --| will behave similar as the following fake resource tree for region_intersects(, IORESOURCE_SYSTEM_RAM, ), |-- "System RAM" --||-- "CXL Window 0a" --| Where "CXL Window 0a" is part of the original "CXL Window 0" that isn't covered by "System RAM".(CVE-2024-49878)
In the Linux kernel, the following vulnerability has been resolved: ext4: update orig_path in ext4_find_extent() In ext4_find_extent(), if the path is not big enough, we free it and set orig_path to NULL. But after reallocating and successfully initializing the path, we don't update orig_path, in which case the caller gets a valid path but a NULL ppath, and this may cause a NULL pointer dereference or a path memory leak. For example: ext4_split_extent path = ppath = 2000 ext4_find_extent if (depth > path[0].p_maxdepth) kfree(path = 2000); orig_path = path = NULL; path = kcalloc() = 3000 ext4_split_extent_at(ppath = NULL) path = ppath; ex = path[depth].p_ext; // NULL pointer dereference! ================================================================== BUG: kernel NULL pointer dereference, address: 0000000000000010 CPU: 6 UID: 0 PID: 576 Comm: fsstress Not tainted 6.11.0-rc2-dirty #847 RIP: 0010:ext4_split_extent_at+0x6d/0x560 Call Trace: <TASK> ext4_split_extent.isra.0+0xcb/0x1b0 ext4_ext_convert_to_initialized+0x168/0x6c0 ext4_ext_handle_unwritten_extents+0x325/0x4d0 ext4_ext_map_blocks+0x520/0xdb0 ext4_map_blocks+0x2b0/0x690 ext4_iomap_begin+0x20e/0x2c0 [...] ================================================================== Therefore, orig_path is updated when the extent lookup succeeds, so that the caller can safely use path or ppath.(CVE-2024-49881)
In the Linux kernel, the following vulnerability has been resolved: ext4: fix double brelse() the buffer of the extents path In ext4_ext_try_to_merge_up(), set path[1].p_bh to NULL after it has been released, otherwise it may be released twice. An example of what triggers this is as follows: split2 map split1 |--------|-------|--------| ext4_ext_map_blocks ext4_ext_handle_unwritten_extents ext4_split_convert_extents // path->p_depth == 0 ext4_split_extent // 1. do split1 ext4_split_extent_at |ext4_ext_insert_extent | ext4_ext_create_new_leaf | ext4_ext_grow_indepth | le16_add_cpu(&neh->eh_depth, 1) | ext4_find_extent | // return -ENOMEM |// get error and try zeroout |path = ext4_find_extent | path->p_depth = 1 |ext4_ext_try_to_merge | ext4_ext_try_to_merge_up | path->p_depth = 0 | brelse(path[1].p_bh) ---> not set to NULL here |// zeroout success // 2. update path ext4_find_extent // 3. do split2 ext4_split_extent_at ext4_ext_insert_extent ext4_ext_create_new_leaf ext4_ext_grow_indepth le16_add_cpu(&neh->eh_depth, 1) ext4_find_extent path[0].p_bh = NULL; path->p_depth = 1 read_extent_tree_block ---> return err // path[1].p_bh is still the old value ext4_free_ext_path ext4_ext_drop_refs // path->p_depth == 1 brelse(path[1].p_bh) ---> brelse a buffer twice Finally got the following WARRNING when removing the buffer from lru: ============================================ VFS: brelse: Trying to free free buffer WARNING: CPU: 2 PID: 72 at fs/buffer.c:1241 __brelse+0x58/0x90 CPU: 2 PID: 72 Comm: kworker/u19:1 Not tainted 6.9.0-dirty #716 RIP: 0010:__brelse+0x58/0x90 Call Trace: <TASK> __find_get_block+0x6e7/0x810 bdev_getblk+0x2b/0x480 __ext4_get_inode_loc+0x48a/0x1240 ext4_get_inode_loc+0xb2/0x150 ext4_reserve_inode_write+0xb7/0x230 __ext4_mark_inode_dirty+0x144/0x6a0 ext4_ext_insert_extent+0x9c8/0x3230 ext4_ext_map_blocks+0xf45/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] ============================================(CVE-2024-49882)
In the Linux kernel, the following vulnerability has been resolved: ext4: aovid use-after-free in ext4_ext_insert_extent() As Ojaswin mentioned in Link, in ext4_ext_insert_extent(), if the path is reallocated in ext4_ext_create_new_leaf(), we'll use the stale path and cause UAF. Below is a sample trace with dummy values: ext4_ext_insert_extent path = ppath = 2000 ext4_ext_create_new_leaf(ppath) ext4_find_extent(ppath) path = ppath = 2000 if (depth > path[0].p_maxdepth) kfree(path = 2000); ppath = path = NULL; path = kcalloc() = 3000 ppath = 3000; return path; / here path is still 2000, UAF! / eh = path[depth].p_hdr ================================================================== BUG: KASAN: slab-use-after-free in ext4_ext_insert_extent+0x26d4/0x3330 Read of size 8 at addr ffff8881027bf7d0 by task kworker/u36:1/179 CPU: 3 UID: 0 PID: 179 Comm: kworker/u6:1 Not tainted 6.11.0-rc2-dirty #866 Call Trace: <TASK> ext4_ext_insert_extent+0x26d4/0x3330 ext4_ext_map_blocks+0xe22/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 [...] Allocated by task 179: ext4_find_extent+0x81c/0x1f70 ext4_ext_map_blocks+0x146/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 ext4_writepages+0x26d/0x4e0 do_writepages+0x175/0x700 [...] Freed by task 179: kfree+0xcb/0x240 ext4_find_extent+0x7c0/0x1f70 ext4_ext_insert_extent+0xa26/0x3330 ext4_ext_map_blocks+0xe22/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 ext4_writepages+0x26d/0x4e0 do_writepages+0x175/0x700 [...] ================================================================== So use *ppath to update the path to avoid the above problem.(CVE-2024-49883)
In the Linux kernel, the following vulnerability has been resolved: ext4: fix slab-use-after-free in ext4_split_extent_at() We hit the following use-after-free: ================================================================== BUG: KASAN: slab-use-after-free in ext4_split_extent_at+0xba8/0xcc0 Read of size 2 at addr ffff88810548ed08 by task kworker/u20:0/40 CPU: 0 PID: 40 Comm: kworker/u20:0 Not tainted 6.9.0-dirty #724 Call Trace: <TASK> kasan_report+0x93/0xc0 ext4_split_extent_at+0xba8/0xcc0 ext4_split_extent.isra.0+0x18f/0x500 ext4_split_convert_extents+0x275/0x750 ext4_ext_handle_unwritten_extents+0x73e/0x1580 ext4_ext_map_blocks+0xe20/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] Allocated by task 40: __kmalloc_noprof+0x1ac/0x480 ext4_find_extent+0xf3b/0x1e70 ext4_ext_map_blocks+0x188/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] Freed by task 40: kfree+0xf1/0x2b0 ext4_find_extent+0xa71/0x1e70 ext4_ext_insert_extent+0xa22/0x3260 ext4_split_extent_at+0x3ef/0xcc0 ext4_split_extent.isra.0+0x18f/0x500 ext4_split_convert_extents+0x275/0x750 ext4_ext_handle_unwritten_extents+0x73e/0x1580 ext4_ext_map_blocks+0xe20/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] ================================================================== The flow of issue triggering is as follows: ext4_split_extent_at path = ppath ext4_ext_insert_extent(ppath) ext4_ext_create_new_leaf(ppath) ext4_find_extent(orig_path) path = orig_path read_extent_tree_block // return -ENOMEM or -EIO ext4_free_ext_path(path) kfree(path) orig_path = NULL a. If err is -ENOMEM: ext4_ext_dirty(path + path->p_depth) // path use-after-free !!! b. If err is -EIO and we have EXT_DEBUG defined: ext4_ext_show_leaf(path) eh = path[depth].p_hdr // path also use-after-free !!! So when trying to zeroout or fix the extent length, call ext4_find_extent() to update the path. In addition we use ppath directly as an ext4_ext_show_leaf() input to avoid possible use-after-free when EXT_DEBUG is defined, and to avoid unnecessary path updates.(CVE-2024-49884)
In the Linux kernel, the following vulnerability has been resolved: ext4: avoid use-after-free in ext4_ext_show_leaf() In ext4_find_extent(), path may be freed by error or be reallocated, so using a previously saved ppath may have been freed and thus may trigger use-after-free, as follows: ext4_split_extent path = ppath; ext4_split_extent_at(ppath) path = ext4_find_extent(ppath) ext4_split_extent_at(ppath) // ext4_find_extent fails to free path // but zeroout succeeds ext4_ext_show_leaf(inode, path) eh = path[depth].p_hdr // path use-after-free !!! Similar to ext4_split_extent_at(), we use ppath directly as an input to ext4_ext_show_leaf(). Fix a spelling error by the way. Same problem in ext4_ext_handle_unwritten_extents(). Since 'path' is only used in ext4_ext_show_leaf(), remove 'path' and use ppath directly. This issue is triggered only when EXT_DEBUG is defined and therefore does not affect functionality.(CVE-2024-49889)
In the Linux kernel, the following vulnerability has been resolved: fbdev: pxafb: Fix possible use after free in pxafb_task() In the pxafb_probe function, it calls the pxafb_init_fbinfo function, after which &fbi->task is associated with pxafb_task. Moreover, within this pxafb_init_fbinfo function, the pxafb_blank function within the &pxafb_ops struct is capable of scheduling work. If we remove the module which will call pxafb_remove to make cleanup, it will call unregister_framebuffer function which can call do_unregister_framebuffer to free fbi->fb through put_fb_info(fb_info), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows: CPU0 CPU1 | pxafb_task pxafb_remove | unregister_framebuffer(info) | do_unregister_framebuffer(fb_info) | put_fb_info(fb_info) | // free fbi->fb | set_ctrlr_state(fbi, state) | __pxafb_lcd_power(fbi, 0) | fbi->lcd_power(on, &fbi->fb.var) | //use fbi->fb Fix it by ensuring that the work is canceled before proceeding with the cleanup in pxafb_remove. Note that only root user can remove the driver at runtime.(CVE-2024-49924)
In the Linux kernel, the following vulnerability has been resolved: net/xen-netback: prevent UAF in xenvif_flush_hash() During the list_for_each_entry_rcu iteration call of xenvif_flush_hash, kfree_rcu does not exist inside the rcu read critical section, so if kfree_rcu is called when the rcu grace period ends during the iteration, UAF occurs when accessing head->next after the entry becomes free. Therefore, to solve this, you need to change it to list_for_each_entry_safe.(CVE-2024-49936)
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix uaf in l2cap_connect [Syzbot reported] BUG: KASAN: slab-use-after-free in l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949 Read of size 8 at addr ffff8880241e9800 by task kworker/u9:0/54 CPU: 0 UID: 0 PID: 54 Comm: kworker/u9:0 Not tainted 6.11.0-rc6-syzkaller-00268-g788220eee30d #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 Workqueue: hci2 hci_rx_work Call Trace: <TASK> __dump_stack lib/dump_stack.c:93 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:119 print_address_description mm/kasan/report.c:377 [inline] print_report+0xc3/0x620 mm/kasan/report.c:488 kasan_report+0xd9/0x110 mm/kasan/report.c:601 l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949 l2cap_connect_req net/bluetooth/l2cap_core.c:4080 [inline] l2cap_bredr_sig_cmd net/bluetooth/l2cap_core.c:4772 [inline] l2cap_sig_channel net/bluetooth/l2cap_core.c:5543 [inline] l2cap_recv_frame+0xf0b/0x8eb0 net/bluetooth/l2cap_core.c:6825 l2cap_recv_acldata+0x9b4/0xb70 net/bluetooth/l2cap_core.c:7514 hci_acldata_packet net/bluetooth/hci_core.c:3791 [inline] hci_rx_work+0xaab/0x1610 net/bluetooth/hci_core.c:4028 process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231 process_scheduled_works kernel/workqueue.c:3312 [inline] worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389 kthread+0x2c1/0x3a0 kernel/kthread.c:389 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 ... Freed by task 5245: kasan_save_stack+0x33/0x60 mm/kasan/common.c:47 kasan_save_track+0x14/0x30 mm/kasan/common.c:68 kasan_save_free_info+0x3b/0x60 mm/kasan/generic.c:579 poison_slab_object+0xf7/0x160 mm/kasan/common.c:240 __kasan_slab_free+0x32/0x50 mm/kasan/common.c:256 kasan_slab_free include/linux/kasan.h:184 [inline] slab_free_hook mm/slub.c:2256 [inline] slab_free mm/slub.c:4477 [inline] kfree+0x12a/0x3b0 mm/slub.c:4598 l2cap_conn_free net/bluetooth/l2cap_core.c:1810 [inline] kref_put include/linux/kref.h:65 [inline] l2cap_conn_put net/bluetooth/l2cap_core.c:1822 [inline] l2cap_conn_del+0x59d/0x730 net/bluetooth/l2cap_core.c:1802 l2cap_connect_cfm+0x9e6/0xf80 net/bluetooth/l2cap_core.c:7241 hci_connect_cfm include/net/bluetooth/hci_core.h:1960 [inline] hci_conn_failed+0x1c3/0x370 net/bluetooth/hci_conn.c:1265 hci_abort_conn_sync+0x75a/0xb50 net/bluetooth/hci_sync.c:5583 abort_conn_sync+0x197/0x360 net/bluetooth/hci_conn.c:2917 hci_cmd_sync_work+0x1a4/0x410 net/bluetooth/hci_sync.c:328 process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231 process_scheduled_works kernel/workqueue.c:3312 [inline] worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389 kthread+0x2c1/0x3a0 kernel/kthread.c:389 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244(CVE-2024-49950)
In the Linux kernel, the following vulnerability has been resolved: media: venus: fix use after free bug in venus_remove due to race condition in venus_probe, core->work is bound with venus_sys_error_handler, which is used to handle error. The code use core->sys_err_done to make sync work. The core->work is started in venus_event_notify. If we call venus_remove, there might be an unfished work. The possible sequence is as follows: CPU0 CPU1 |venus_sys_error_handler venus_remove | hfi_destroy | venus_hfi_destroy | kfree(hdev); | |hfi_reinit |venus_hfi_queues_reinit |//use hdev Fix it by canceling the work in venus_remove.(CVE-2024-49981)
In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: amdkfd_free_gtt_mem clear the correct pointer Pass pointer reference to amdgpu_bo_unref to clear the correct pointer, otherwise amdgpu_bo_unref clear the local variable, the original pointer not set to NULL, this could cause use-after-free bug.(CVE-2024-49991)
In the Linux kernel, the following vulnerability has been resolved: tipc: guard against string buffer overrun Smatch reports that copying media_name and if_name to name_parts may overwrite the destination. .../bearer.c:166 bearer_name_validate() error: strcpy() 'media_name' too large for 'name_parts->media_name' (32 vs 16) .../bearer.c:167 bearer_name_validate() error: strcpy() 'if_name' too large for 'name_parts->if_name' (1010102 vs 16) This does seem to be the case so guard against this possibility by using strscpy() and failing if truncation occurs. Introduced by commit b97bf3fd8f6a ("[TIPC] Initial merge") Compile tested only.(CVE-2024-49995)
In the Linux kernel, the following vulnerability has been resolved: slip: make slhc_remember() more robust against malicious packets syzbot found that slhc_remember() was missing checks against malicious packets [1]. slhc_remember() only checked the size of the packet was at least 20, which is not good enough. We need to make sure the packet includes the IPv4 and TCP header that are supposed to be carried. Add iph and th pointers to make the code more readable. [1] BUG: KMSAN: uninit-value in slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666 slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666 ppp_receive_nonmp_frame+0xe45/0x35e0 drivers/net/ppp/ppp_generic.c:2455 ppp_receive_frame drivers/net/ppp/ppp_generic.c:2372 [inline] ppp_do_recv+0x65f/0x40d0 drivers/net/ppp/ppp_generic.c:2212 ppp_input+0x7dc/0xe60 drivers/net/ppp/ppp_generic.c:2327 pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379 sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113 __release_sock+0x1da/0x330 net/core/sock.c:3072 release_sock+0x6b/0x250 net/core/sock.c:3626 pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 _syssendmsg+0x903/0xb60 net/socket.c:2602 _sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was created at: slab_post_alloc_hook mm/slub.c:4091 [inline] slab_alloc_node mm/slub.c:4134 [inline] kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4186 kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587 __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678 alloc_skb include/linux/skbuff.h:1322 [inline] sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732 pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 _syssendmsg+0x903/0xb60 net/socket.c:2602 _sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f CPU: 0 UID: 0 PID: 5460 Comm: syz.2.33 Not tainted 6.12.0-rc2-syzkaller-00006-g87d6aab2389e #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50033)
In the Linux kernel, the following vulnerability has been resolved: ppp: fix ppp_async_encode() illegal access syzbot reported an issue in ppp_async_encode() [1] In this case, pppoe_sendmsg() is called with a zero size. Then ppp_async_encode() is called with an empty skb. BUG: KMSAN: uninit-value in ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline] BUG: KMSAN: uninit-value in ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675 ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline] ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675 ppp_async_send+0x130/0x1b0 drivers/net/ppp/ppp_async.c:634 ppp_channel_bridge_input drivers/net/ppp/ppp_generic.c:2280 [inline] ppp_input+0x1f1/0xe60 drivers/net/ppp/ppp_generic.c:2304 pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379 sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113 __release_sock+0x1da/0x330 net/core/sock.c:3072 release_sock+0x6b/0x250 net/core/sock.c:3626 pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 _syssendmsg+0x903/0xb60 net/socket.c:2602 _sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was created at: slab_post_alloc_hook mm/slub.c:4092 [inline] slab_alloc_node mm/slub.c:4135 [inline] kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4187 kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587 __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678 alloc_skb include/linux/skbuff.h:1322 [inline] sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732 pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 _syssendmsg+0x903/0xb60 net/socket.c:2602 _sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f CPU: 1 UID: 0 PID: 5411 Comm: syz.1.14 Not tainted 6.12.0-rc1-syzkaller-00165-g360c1f1f24c6 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50035)
In the Linux kernel, the following vulnerability has been resolved: serial: protect uart_port_dtr_rts() in uart_shutdown() too Commit af224ca2df29 (serial: core: Prevent unsafe uart port access, part 3) added few uport == NULL checks. It added one to uart_shutdown(), so the commit assumes, uport can be NULL in there. But right after that protection, there is an unprotected "uart_port_dtr_rts(uport, false);" call. That is invoked only if HUPCL is set, so I assume that is the reason why we do not see lots of these reports. Or it cannot be NULL at this point at all for some reason :P. Until the above is investigated, stay on the safe side and move this dereference to the if too. I got this inconsistency from Coverity under CID 1585130. Thanks.(CVE-2024-50058)
In the Linux kernel, the following vulnerability has been resolved: tty: n_gsm: Fix use-after-free in gsm_cleanup_mux BUG: KASAN: slab-use-after-free in gsm_cleanup_mux+0x77b/0x7b0 drivers/tty/n_gsm.c:3160 [n_gsm] Read of size 8 at addr ffff88815fe99c00 by task poc/3379 CPU: 0 UID: 0 PID: 3379 Comm: poc Not tainted 6.11.0+ #56 Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 11/12/2020 Call Trace: <TASK> gsm_cleanup_mux+0x77b/0x7b0 drivers/tty/n_gsm.c:3160 [n_gsm] __pfx_gsm_cleanup_mux+0x10/0x10 drivers/tty/n_gsm.c:3124 [n_gsm] __pfx_sched_clock_cpu+0x10/0x10 kernel/sched/clock.c:389 update_load_avg+0x1c1/0x27b0 kernel/sched/fair.c:4500 __pfx_min_vruntime_cb_rotate+0x10/0x10 kernel/sched/fair.c:846 __rb_insert_augmented+0x492/0xbf0 lib/rbtree.c:161 gsmld_ioctl+0x395/0x1450 drivers/tty/n_gsm.c:3408 [n_gsm] _raw_spin_lock_irqsave+0x92/0xf0 arch/x86/include/asm/atomic.h:107 __pfx_gsmld_ioctl+0x10/0x10 drivers/tty/n_gsm.c:3822 [n_gsm] ktime_get+0x5e/0x140 kernel/time/timekeeping.c:195 ldsem_down_read+0x94/0x4e0 arch/x86/include/asm/atomic64_64.h:79 __pfx_ldsem_down_read+0x10/0x10 drivers/tty/tty_ldsem.c:338 __pfx_do_vfs_ioctl+0x10/0x10 fs/ioctl.c:805 tty_ioctl+0x643/0x1100 drivers/tty/tty_io.c:2818 Allocated by task 65: gsm_data_alloc.constprop.0+0x27/0x190 drivers/tty/n_gsm.c:926 [n_gsm] gsm_send+0x2c/0x580 drivers/tty/n_gsm.c:819 [n_gsm] gsm1_receive+0x547/0xad0 drivers/tty/n_gsm.c:3038 [n_gsm] gsmld_receive_buf+0x176/0x280 drivers/tty/n_gsm.c:3609 [n_gsm] tty_ldisc_receive_buf+0x101/0x1e0 drivers/tty/tty_buffer.c:391 tty_port_default_receive_buf+0x61/0xa0 drivers/tty/tty_port.c:39 flush_to_ldisc+0x1b0/0x750 drivers/tty/tty_buffer.c:445 process_scheduled_works+0x2b0/0x10d0 kernel/workqueue.c:3229 worker_thread+0x3dc/0x950 kernel/workqueue.c:3391 kthread+0x2a3/0x370 kernel/kthread.c:389 ret_from_fork+0x2d/0x70 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:257 Freed by task 3367: kfree+0x126/0x420 mm/slub.c:4580 gsm_cleanup_mux+0x36c/0x7b0 drivers/tty/n_gsm.c:3160 [n_gsm] gsmld_ioctl+0x395/0x1450 drivers/tty/n_gsm.c:3408 [n_gsm] tty_ioctl+0x643/0x1100 drivers/tty/tty_io.c:2818 [Analysis] gsm_msg on the tx_ctrl_list or tx_data_list of gsm_mux can be freed by multi threads through ioctl,which leads to the occurrence of uaf. Protect it by gsm tx lock.(CVE-2024-50073)
| URL | Type | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"bpftool-4.19.90-2411.2.0.0302.oe2003sp4.aarch64.rpm",
"bpftool-debuginfo-4.19.90-2411.2.0.0302.oe2003sp4.aarch64.rpm",
"kernel-4.19.90-2411.2.0.0302.oe2003sp4.aarch64.rpm",
"kernel-debuginfo-4.19.90-2411.2.0.0302.oe2003sp4.aarch64.rpm",
"kernel-debugsource-4.19.90-2411.2.0.0302.oe2003sp4.aarch64.rpm",
"kernel-devel-4.19.90-2411.2.0.0302.oe2003sp4.aarch64.rpm",
"kernel-source-4.19.90-2411.2.0.0302.oe2003sp4.aarch64.rpm",
"kernel-tools-4.19.90-2411.2.0.0302.oe2003sp4.aarch64.rpm",
"kernel-tools-debuginfo-4.19.90-2411.2.0.0302.oe2003sp4.aarch64.rpm",
"kernel-tools-devel-4.19.90-2411.2.0.0302.oe2003sp4.aarch64.rpm",
"perf-4.19.90-2411.2.0.0302.oe2003sp4.aarch64.rpm",
"perf-debuginfo-4.19.90-2411.2.0.0302.oe2003sp4.aarch64.rpm",
"python2-perf-4.19.90-2411.2.0.0302.oe2003sp4.aarch64.rpm",
"python2-perf-debuginfo-4.19.90-2411.2.0.0302.oe2003sp4.aarch64.rpm",
"python3-perf-4.19.90-2411.2.0.0302.oe2003sp4.aarch64.rpm",
"python3-perf-debuginfo-4.19.90-2411.2.0.0302.oe2003sp4.aarch64.rpm"
],
"src": [
"kernel-4.19.90-2411.2.0.0302.oe2003sp4.src.rpm"
],
"x86_64": [
"bpftool-4.19.90-2411.2.0.0302.oe2003sp4.x86_64.rpm",
"bpftool-debuginfo-4.19.90-2411.2.0.0302.oe2003sp4.x86_64.rpm",
"kernel-4.19.90-2411.2.0.0302.oe2003sp4.x86_64.rpm",
"kernel-debuginfo-4.19.90-2411.2.0.0302.oe2003sp4.x86_64.rpm",
"kernel-debugsource-4.19.90-2411.2.0.0302.oe2003sp4.x86_64.rpm",
"kernel-devel-4.19.90-2411.2.0.0302.oe2003sp4.x86_64.rpm",
"kernel-source-4.19.90-2411.2.0.0302.oe2003sp4.x86_64.rpm",
"kernel-tools-4.19.90-2411.2.0.0302.oe2003sp4.x86_64.rpm",
"kernel-tools-debuginfo-4.19.90-2411.2.0.0302.oe2003sp4.x86_64.rpm",
"kernel-tools-devel-4.19.90-2411.2.0.0302.oe2003sp4.x86_64.rpm",
"perf-4.19.90-2411.2.0.0302.oe2003sp4.x86_64.rpm",
"perf-debuginfo-4.19.90-2411.2.0.0302.oe2003sp4.x86_64.rpm",
"python2-perf-4.19.90-2411.2.0.0302.oe2003sp4.x86_64.rpm",
"python2-perf-debuginfo-4.19.90-2411.2.0.0302.oe2003sp4.x86_64.rpm",
"python3-perf-4.19.90-2411.2.0.0302.oe2003sp4.x86_64.rpm",
"python3-perf-debuginfo-4.19.90-2411.2.0.0302.oe2003sp4.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS-SP4",
"name": "kernel",
"purl": "pkg:rpm/openEuler/kernel\u0026distro=openEuler-20.03-LTS-SP4"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.19.90-2411.2.0.0302.oe2003sp4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: usb: gadget: uvc: Prevent buffer overflow in setup handler Setup function uvc_function_setup permits control transfer requests with up to 64 bytes of payload (UVC_MAX_REQUEST_SIZE), data stage handler for OUT transfer uses memcpy to copy req-\u0026gt;actual bytes to uvc_event-\u0026gt;data.data array of size 60. This may result in an overflow of 4 bytes.(CVE-2022-48948)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: igb: Initialize mailbox message for VF reset When a MAC address is not assigned to the VF, that portion of the message sent to the VF is not set. The memory, however, is allocated from the stack meaning that information may be leaked to the VM. Initialize the message buffer to 0 so that no information is passed to the VM in this case.(CVE-2022-48949)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: net: hisilicon: Fix potential use-after-free in hix5hd2_rx() The skb is delivered to napi_gro_receive() which may free it, after calling this, dereferencing skb may trigger use-after-free.(CVE-2022-48960)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: net: hisilicon: Fix potential use-after-free in hisi_femac_rx() The skb is delivered to napi_gro_receive() which may free it, after calling this, dereferencing skb may trigger use-after-free.(CVE-2022-48962)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: net: mvneta: Prevent out of bounds read in mvneta_config_rss() The pp-\u0026gt;indir[0] value comes from the user. It is passed to: if (cpu_online(pp-\u0026gt;rxq_def)) inside the mvneta_percpu_elect() function. It needs bounds checkeding to ensure that it is not beyond the end of the cpu bitmap.(CVE-2022-48966)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix not cleanup led when bt_init fails bt_init() calls bt_leds_init() to register led, but if it fails later, bt_leds_cleanup() is not called to unregister it. This can cause panic if the argument \u0026quot;bluetooth-power\u0026quot; in text is freed and then another led_trigger_register() tries to access it: BUG: unable to handle page fault for address: ffffffffc06d3bc0 RIP: 0010:strcmp+0xc/0x30 Call Trace: \u0026lt;TASK\u0026gt; led_trigger_register+0x10d/0x4f0 led_trigger_register_simple+0x7d/0x100 bt_init+0x39/0xf7 [bluetooth] do_one_initcall+0xd0/0x4e0(CVE-2022-48971)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: mac802154: fix missing INIT_LIST_HEAD in ieee802154_if_add() Kernel fault injection test reports null-ptr-deref as follows: BUG: kernel NULL pointer dereference, address: 0000000000000008 RIP: 0010:cfg802154_netdev_notifier_call+0x120/0x310 include/linux/list.h:114 Call Trace: \u0026lt;TASK\u0026gt; raw_notifier_call_chain+0x6d/0xa0 kernel/notifier.c:87 call_netdevice_notifiers_info+0x6e/0xc0 net/core/dev.c:1944 unregister_netdevice_many_notify+0x60d/0xcb0 net/core/dev.c:1982 unregister_netdevice_queue+0x154/0x1a0 net/core/dev.c:10879 register_netdevice+0x9a8/0xb90 net/core/dev.c:10083 ieee802154_if_add+0x6ed/0x7e0 net/mac802154/iface.c:659 ieee802154_register_hw+0x29c/0x330 net/mac802154/main.c:229 mcr20a_probe+0xaaa/0xcb1 drivers/net/ieee802154/mcr20a.c:1316 ieee802154_if_add() allocates wpan_dev as netdev\u0026apos;s private data, but not init the list in struct wpan_dev. cfg802154_netdev_notifier_call() manage the list when device register/unregister, and may lead to null-ptr-deref. Use INIT_LIST_HEAD() on it to initialize it correctly.(CVE-2022-48972)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: HID: core: fix shift-out-of-bounds in hid_report_raw_event Syzbot reported shift-out-of-bounds in hid_report_raw_event. microsoft 0003:045E:07DA.0001: hid_field_extract() called with n (128) \u0026gt; 32! (swapper/0) ====================================================================== UBSAN: shift-out-of-bounds in drivers/hid/hid-core.c:1323:20 shift exponent 127 is too large for 32-bit type \u0026apos;int\u0026apos; CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.1.0-rc4-syzkaller-00159-g4bbf3422df78 #0 Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Call Trace: \u0026lt;IRQ\u0026gt; __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106 ubsan_epilogue lib/ubsan.c:151 [inline] __ubsan_handle_shift_out_of_bounds+0x3a6/0x420 lib/ubsan.c:322 snto32 drivers/hid/hid-core.c:1323 [inline] hid_input_fetch_field drivers/hid/hid-core.c:1572 [inline] hid_process_report drivers/hid/hid-core.c:1665 [inline] hid_report_raw_event+0xd56/0x18b0 drivers/hid/hid-core.c:1998 hid_input_report+0x408/0x4f0 drivers/hid/hid-core.c:2066 hid_irq_in+0x459/0x690 drivers/hid/usbhid/hid-core.c:284 __usb_hcd_giveback_urb+0x369/0x530 drivers/usb/core/hcd.c:1671 dummy_timer+0x86b/0x3110 drivers/usb/gadget/udc/dummy_hcd.c:1988 call_timer_fn+0xf5/0x210 kernel/time/timer.c:1474 expire_timers kernel/time/timer.c:1519 [inline] __run_timers+0x76a/0x980 kernel/time/timer.c:1790 run_timer_softirq+0x63/0xf0 kernel/time/timer.c:1803 __do_softirq+0x277/0x75b kernel/softirq.c:571 __irq_exit_rcu+0xec/0x170 kernel/softirq.c:650 irq_exit_rcu+0x5/0x20 kernel/softirq.c:662 sysvec_apic_timer_interrupt+0x91/0xb0 arch/x86/kernel/apic/apic.c:1107 ====================================================================== If the size of the integer (unsigned n) is bigger than 32 in snto32(), shift exponent will be too large for 32-bit type \u0026apos;int\u0026apos;, resulting in a shift-out-of-bounds bug. Fix this by adding a check on the size of the integer (unsigned n) in snto32(). To add support for n greater than 32 bits, set n to 32, if n is greater than 32.(CVE-2022-48978)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ASoC: soc-pcm: Add NULL check in BE reparenting Add NULL check in dpcm_be_reparent API, to handle kernel NULL pointer dereference error. The issue occurred in fuzzing test.(CVE-2022-48992)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Fix PCI device refcount leak in dmar_dev_scope_init() for_each_pci_dev() is implemented by pci_get_device(). The comment of pci_get_device() says that it will increase the reference count for the returned pci_dev and also decrease the reference count for the input pci_dev @from if it is not NULL. If we break for_each_pci_dev() loop with pdev not NULL, we need to call pci_dev_put() to decrease the reference count. Add the missing pci_dev_put() for the error path to avoid reference count leak.(CVE-2022-49002)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ASoC: ops: Fix bounds check for _sx controls For _sx controls the semantics of the max field is not the usual one, max is the number of steps rather than the maximum value. This means that our check in snd_soc_put_volsw_sx() needs to just check against the maximum value.(CVE-2022-49005)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: hwmon: (coretemp) fix pci device refcount leak in nv1a_ram_new() As comment of pci_get_domain_bus_and_slot() says, it returns a pci device with refcount increment, when finish using it, the caller must decrement the reference count by calling pci_dev_put(). So call it after using to avoid refcount leak.(CVE-2022-49011)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: net/9p: Fix a potential socket leak in p9_socket_open Both p9_fd_create_tcp() and p9_fd_create_unix() will call p9_socket_open(). If the creation of p9_trans_fd fails, p9_fd_create_tcp() and p9_fd_create_unix() will return an error directly instead of releasing the cscoket, which will result in a socket leak. This patch adds sock_release() to fix the leak issue.(CVE-2022-49020)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: net: phy: fix null-ptr-deref while probe() failed I got a null-ptr-deref report as following when doing fault injection test: BUG: kernel NULL pointer dereference, address: 0000000000000058 Oops: 0000 [#1] PREEMPT SMP KASAN PTI CPU: 1 PID: 253 Comm: 507-spi-dm9051 Tainted: G B N 6.1.0-rc3+ Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: 0010:klist_put+0x2d/0xd0 Call Trace: \u0026lt;TASK\u0026gt; klist_remove+0xf1/0x1c0 device_release_driver_internal+0x23e/0x2d0 bus_remove_device+0x1bd/0x240 device_del+0x357/0x770 phy_device_remove+0x11/0x30 mdiobus_unregister+0xa5/0x140 release_nodes+0x6a/0xa0 devres_release_all+0xf8/0x150 device_unbind_cleanup+0x19/0xd0 //probe path: phy_device_register() device_add() phy_connect phy_attach_direct() //set device driver probe() //it\u0026apos;s failed, driver is not bound device_bind_driver() // probe failed, it\u0026apos;s not called //remove path: phy_device_remove() device_del() device_release_driver_internal() __device_release_driver() //dev-\u0026gt;drv is not NULL klist_remove() \u0026lt;- knode_driver is not added yet, cause null-ptr-deref In phy_attach_direct(), after setting the \u0026apos;dev-\u0026gt;driver\u0026apos;, probe() fails, device_bind_driver() is not called, so the knode_driver-\u0026gt;n_klist is not set, then it causes null-ptr-deref in __device_release_driver() while deleting device. Fix this by setting dev-\u0026gt;driver to NULL in the error path in phy_attach_direct().(CVE-2022-49021)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: iio: health: afe4403: Fix oob read in afe4403_read_raw KASAN report out-of-bounds read as follows: BUG: KASAN: global-out-of-bounds in afe4403_read_raw+0x42e/0x4c0 Read of size 4 at addr ffffffffc02ac638 by task cat/279 Call Trace: afe4403_read_raw iio_read_channel_info dev_attr_show The buggy address belongs to the variable: afe4403_channel_leds+0x18/0xffffffffffffe9e0 This issue can be reproduced by singe command: $ cat /sys/bus/spi/devices/spi0.0/iio\\:device0/in_intensity6_raw The array size of afe4403_channel_leds is less than channels, so access with chan-\u0026gt;address cause OOB read in afe4403_read_raw. Fix it by moving access before use it.(CVE-2022-49031)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: iio: health: afe4404: Fix oob read in afe4404_[read|write]_raw KASAN report out-of-bounds read as follows: BUG: KASAN: global-out-of-bounds in afe4404_read_raw+0x2ce/0x380 Read of size 4 at addr ffffffffc00e4658 by task cat/278 Call Trace: afe4404_read_raw iio_read_channel_info dev_attr_show The buggy address belongs to the variable: afe4404_channel_leds+0x18/0xffffffffffffe9c0 This issue can be reproduce by singe command: $ cat /sys/bus/i2c/devices/0-0058/iio\\:device0/in_intensity6_raw The array size of afe4404_channel_leds and afe4404_channel_offdacs are less than channels, so access with chan-\u0026gt;address cause OOB read in afe4404_[read|write]_raw. Fix it by moving access before use them.(CVE-2022-49032)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsmack: tcp: ipv4, fix incorrect labeling\r\n\r\nCurrently, Smack mirrors the label of incoming tcp/ipv4 connections:\nwhen a label \u0026apos;foo\u0026apos; connects to a label \u0026apos;bar\u0026apos; with tcp/ipv4,\n\u0026apos;foo\u0026apos; always gets \u0026apos;foo\u0026apos; in returned ipv4 packets. So,\n1) returned packets are incorrectly labeled (\u0026apos;foo\u0026apos; instead of \u0026apos;bar\u0026apos;)\n2) \u0026apos;bar\u0026apos; can write to \u0026apos;foo\u0026apos; without being authorized to write.\r\n\r\nHere is a scenario how to see this:\r\n\r\n* Take two machines, let\u0026apos;s call them C and S,\n with active Smack in the default state\n (no settings, no rules, no labeled hosts, only builtin labels)\r\n\r\n* At S, add Smack rule \u0026apos;foo bar w\u0026apos;\n (labels \u0026apos;foo\u0026apos; and \u0026apos;bar\u0026apos; are instantiated at S at this moment)\r\n\r\n* At S, at label \u0026apos;bar\u0026apos;, launch a program\n that listens for incoming tcp/ipv4 connections\r\n\r\n* From C, at label \u0026apos;foo\u0026apos;, connect to the listener at S.\n (label \u0026apos;foo\u0026apos; is instantiated at C at this moment)\n Connection succeedes and works.\r\n\r\n* Send some data in both directions.\n* Collect network traffic of this connection.\r\n\r\nAll packets in both directions are labeled with the CIPSO\nof the label \u0026apos;foo\u0026apos;. Hence, label \u0026apos;bar\u0026apos; writes to \u0026apos;foo\u0026apos; without\nbeing authorized, and even without ever being known at C.\r\n\r\nIf anybody cares: exactly the same happens with DCCP.\r\n\r\nThis behavior 1st manifested in release 2.6.29.4 (see Fixes below)\nand it looks unintentional. At least, no explanation was provided.\r\n\r\nI changed returned packes label into the \u0026apos;bar\u0026apos;,\nto bring it into line with the Smack documentation claims.(CVE-2024-47659)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnilfs2: fix state management in error path of log writing function\r\n\r\nAfter commit a694291a6211 (\u0026quot;nilfs2: separate wait function from\nnilfs_segctor_write\u0026quot;) was applied, the log writing function\nnilfs_segctor_do_construct() was able to issue I/O requests continuously\neven if user data blocks were split into multiple logs across segments,\nbut two potential flaws were introduced in its error handling.\r\n\r\nFirst, if nilfs_segctor_begin_construction() fails while creating the\nsecond or subsequent logs, the log writing function returns without\ncalling nilfs_segctor_abort_construction(), so the writeback flag set on\npages/folios will remain uncleared. This causes page cache operations to\nhang waiting for the writeback flag. For example,\ntruncate_inode_pages_final(), which is called via nilfs_evict_inode() when\nan inode is evicted from memory, will hang.\r\n\r\nSecond, the NILFS_I_COLLECTED flag set on normal inodes remain uncleared. \nAs a result, if the next log write involves checkpoint creation, that\u0026apos;s\nfine, but if a partial log write is performed that does not, inodes with\nNILFS_I_COLLECTED set are erroneously removed from the \u0026quot;sc_dirty_files\u0026quot;\nlist, and their data and b-tree blocks may not be written to the device,\ncorrupting the block mapping.\r\n\r\nFix these issues by uniformly calling nilfs_segctor_abort_construction()\non failure of each step in the loop in nilfs_segctor_do_construct(),\nhaving it clean up logs and segment usages according to progress, and\ncorrecting the conditions for calling nilfs_redirty_inodes() to ensure\nthat the NILFS_I_COLLECTED flag is cleared.(CVE-2024-47669)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency In the commit aee2424246f9 (\u0026quot;RDMA/iwcm: Fix a use-after-free related to destroying CM IDs\u0026quot;), the function flush_workqueue is invoked to flush the work queue iwcm_wq. But at that time, the work queue iwcm_wq was created via the function alloc_ordered_workqueue without the flag WQ_MEM_RECLAIM. Because the current process is trying to flush the whole iwcm_wq, if iwcm_wq doesn\u0026apos;t have the flag WQ_MEM_RECLAIM, verify that the current process is not reclaiming memory or running on a workqueue which doesn\u0026apos;t have the flag WQ_MEM_RECLAIM as that can break forward-progress guarantee leading to a deadlock. The call trace is as below: [ 125.350876][ T1430] Call Trace: [ 125.356281][ T1430] \u0026lt;TASK\u0026gt; [ 125.361285][ T1430] ? __warn (kernel/panic.c:693) [ 125.367640][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.375689][ T1430] ? report_bug (lib/bug.c:180 lib/bug.c:219) [ 125.382505][ T1430] ? handle_bug (arch/x86/kernel/traps.c:239) [ 125.388987][ T1430] ? exc_invalid_op (arch/x86/kernel/traps.c:260 (discriminator 1)) [ 125.395831][ T1430] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:621) [ 125.403125][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.410984][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.418764][ T1430] __flush_workqueue (kernel/workqueue.c:3970) [ 125.426021][ T1430] ? __pfx___might_resched (kernel/sched/core.c:10151) [ 125.433431][ T1430] ? destroy_cm_id (drivers/infiniband/core/iwcm.c:375) iw_cm [ 125.441209][ T1430] ? __pfx___flush_workqueue (kernel/workqueue.c:3910) [ 125.473900][ T1430] ? _raw_spin_lock_irqsave (arch/x86/include/asm/atomic.h:107 include/linux/atomic/atomic-arch-fallback.h:2170 include/linux/atomic/atomic-instrumented.h:1302 include/asm-generic/qspinlock.h:111 include/linux/spinlock.h:187 include/linux/spinlock_api_smp.h:111 kernel/locking/spinlock.c:162) [ 125.473909][ T1430] ? __pfx__raw_spin_lock_irqsave (kernel/locking/spinlock.c:161) [ 125.482537][ T1430] _destroy_id (drivers/infiniband/core/cma.c:2044) rdma_cm [ 125.495072][ T1430] nvme_rdma_free_queue (drivers/nvme/host/rdma.c:656 drivers/nvme/host/rdma.c:650) nvme_rdma [ 125.505827][ T1430] nvme_rdma_reset_ctrl_work (drivers/nvme/host/rdma.c:2180) nvme_rdma [ 125.505831][ T1430] process_one_work (kernel/workqueue.c:3231) [ 125.515122][ T1430] worker_thread (kernel/workqueue.c:3306 kernel/workqueue.c:3393) [ 125.515127][ T1430] ? __pfx_worker_thread (kernel/workqueue.c:3339) [ 125.531837][ T1430] kthread (kernel/kthread.c:389) [ 125.539864][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.550628][ T1430] ret_from_fork (arch/x86/kernel/process.c:147) [ 125.558840][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.558844][ T1430] ret_from_fork_asm (arch/x86/entry/entry_64.S:257) [ 125.566487][ T1430] \u0026lt;/TASK\u0026gt; [ 125.566488][ T1430] ---[ end trace 0000000000000000 ]---(CVE-2024-47696)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drivers: media: dvb-frontends/rtl2830: fix an out-of-bounds write error Ensure index in rtl2830_pid_filter does not exceed 31 to prevent out-of-bounds access. dev-\u0026gt;filters is a 32-bit value, so set_bit and clear_bit functions should only operate on indices from 0 to 31. If index is 32, it will attempt to access a non-existent 33rd bit, leading to out-of-bounds access. Change the boundary check from index \u0026gt; 32 to index \u0026gt;= 32 to resolve this issue.(CVE-2024-47697)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ext4: avoid OOB when system.data xattr changes underneath the filesystem When looking up for an entry in an inlined directory, if e_value_offs is changed underneath the filesystem by some change in the block device, it will lead to an out-of-bounds access that KASAN detects as an UAF. EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none. loop0: detected capacity change from 2048 to 2047 ================================================================== BUG: KASAN: use-after-free in ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500 Read of size 1 at addr ffff88803e91130f by task syz-executor269/5103 CPU: 0 UID: 0 PID: 5103 Comm: syz-executor269 Not tainted 6.11.0-rc4-syzkaller #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Call Trace: \u0026lt;TASK\u0026gt; __dump_stack lib/dump_stack.c:93 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119 print_address_description mm/kasan/report.c:377 [inline] print_report+0x169/0x550 mm/kasan/report.c:488 kasan_report+0x143/0x180 mm/kasan/report.c:601 ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500 ext4_find_inline_entry+0x4be/0x5e0 fs/ext4/inline.c:1697 __ext4_find_entry+0x2b4/0x1b30 fs/ext4/namei.c:1573 ext4_lookup_entry fs/ext4/namei.c:1727 [inline] ext4_lookup+0x15f/0x750 fs/ext4/namei.c:1795 lookup_one_qstr_excl+0x11f/0x260 fs/namei.c:1633 filename_create+0x297/0x540 fs/namei.c:3980 do_symlinkat+0xf9/0x3a0 fs/namei.c:4587 __do_sys_symlinkat fs/namei.c:4610 [inline] __se_sys_symlinkat fs/namei.c:4607 [inline] __x64_sys_symlinkat+0x95/0xb0 fs/namei.c:4607 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f3e73ced469 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 21 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fff4d40c258 EFLAGS: 00000246 ORIG_RAX: 000000000000010a RAX: ffffffffffffffda RBX: 0032656c69662f2e RCX: 00007f3e73ced469 RDX: 0000000020000200 RSI: 00000000ffffff9c RDI: 00000000200001c0 RBP: 0000000000000000 R08: 00007fff4d40c290 R09: 00007fff4d40c290 R10: 0023706f6f6c2f76 R11: 0000000000000246 R12: 00007fff4d40c27c R13: 0000000000000003 R14: 431bde82d7b634db R15: 00007fff4d40c2b0 \u0026lt;/TASK\u0026gt; Calling ext4_xattr_ibody_find right after reading the inode with ext4_get_inode_loc will lead to a check of the validity of the xattrs, avoiding this problem.(CVE-2024-47701)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: firmware_loader: Block path traversal Most firmware names are hardcoded strings, or are constructed from fairly constrained format strings where the dynamic parts are just some hex numbers or such. However, there are a couple codepaths in the kernel where firmware file names contain string components that are passed through from a device or semi-privileged userspace; the ones I could find (not counting interfaces that require root privileges) are: - lpfc_sli4_request_firmware_update() seems to construct the firmware filename from \u0026quot;ModelName\u0026quot;, a string that was previously parsed out of some descriptor (\u0026quot;Vital Product Data\u0026quot;) in lpfc_fill_vpd() - nfp_net_fw_find() seems to construct a firmware filename from a model name coming from nfp_hwinfo_lookup(pf-\u0026gt;hwinfo, \u0026quot;nffw.partno\u0026quot;), which I think parses some descriptor that was read from the device. (But this case likely isn\u0026apos;t exploitable because the format string looks like \u0026quot;netronome/nic_%s\u0026quot;, and there shouldn\u0026apos;t be any *folders* starting with \u0026quot;netronome/nic_\u0026quot;. The previous case was different because there, the \u0026quot;%s\u0026quot; is *at the start* of the format string.) - module_flash_fw_schedule() is reachable from the ETHTOOL_MSG_MODULE_FW_FLASH_ACT netlink command, which is marked as GENL_UNS_ADMIN_PERM (meaning CAP_NET_ADMIN inside a user namespace is enough to pass the privilege check), and takes a userspace-provided firmware name. (But I think to reach this case, you need to have CAP_NET_ADMIN over a network namespace that a special kind of ethernet device is mapped into, so I think this is not a viable attack path in practice.) Fix it by rejecting any firmware names containing \u0026quot;..\u0026quot; path components. For what it\u0026apos;s worth, I went looking and haven\u0026apos;t found any USB device drivers that use the firmware loader dangerously.(CVE-2024-47742)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ACPI: sysfs: validate return type of _STR method Only buffer objects are valid return values of _STR. If something else is returned description_show() will access invalid memory.(CVE-2024-49860)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate When doing cleanup, if flags without OCFS2_BH_READAHEAD, it may trigger NULL pointer dereference in the following ocfs2_set_buffer_uptodate() if bh is NULL.(CVE-2024-49877)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: resource: fix region_intersects() vs add_memory_driver_managed() On a system with CXL memory, the resource tree (/proc/iomem) related to CXL memory may look like something as follows. 490000000-50fffffff : CXL Window 0 490000000-50fffffff : region0 490000000-50fffffff : dax0.0 490000000-50fffffff : System RAM (kmem) Because drivers/dax/kmem.c calls add_memory_driver_managed() during onlining CXL memory, which makes \u0026quot;System RAM (kmem)\u0026quot; a descendant of \u0026quot;CXL Window X\u0026quot;. This confuses region_intersects(), which expects all \u0026quot;System RAM\u0026quot; resources to be at the top level of iomem_resource. This can lead to bugs. For example, when the following command line is executed to write some memory in CXL memory range via /dev/mem, $ dd if=data of=/dev/mem bs=$((1 \u0026lt;\u0026lt; 10)) seek=$((0x490000000 \u0026gt;\u0026gt; 10)) count=1 dd: error writing \u0026apos;/dev/mem\u0026apos;: Bad address 1+0 records in 0+0 records out 0 bytes copied, 0.0283507 s, 0.0 kB/s the command fails as expected. However, the error code is wrong. It should be \u0026quot;Operation not permitted\u0026quot; instead of \u0026quot;Bad address\u0026quot;. More seriously, the /dev/mem permission checking in devmem_is_allowed() passes incorrectly. Although the accessing is prevented later because ioremap() isn\u0026apos;t allowed to map system RAM, it is a potential security issue. During command executing, the following warning is reported in the kernel log for calling ioremap() on system RAM. ioremap on RAM at 0x0000000490000000 - 0x0000000490000fff WARNING: CPU: 2 PID: 416 at arch/x86/mm/ioremap.c:216 __ioremap_caller.constprop.0+0x131/0x35d Call Trace: memremap+0xcb/0x184 xlate_dev_mem_ptr+0x25/0x2f write_mem+0x94/0xfb vfs_write+0x128/0x26d ksys_write+0xac/0xfe do_syscall_64+0x9a/0xfd entry_SYSCALL_64_after_hwframe+0x4b/0x53 The details of command execution process are as follows. In the above resource tree, \u0026quot;System RAM\u0026quot; is a descendant of \u0026quot;CXL Window 0\u0026quot; instead of a top level resource. So, region_intersects() will report no System RAM resources in the CXL memory region incorrectly, because it only checks the top level resources. Consequently, devmem_is_allowed() will return 1 (allow access via /dev/mem) for CXL memory region incorrectly. Fortunately, ioremap() doesn\u0026apos;t allow to map System RAM and reject the access. So, region_intersects() needs to be fixed to work correctly with the resource tree with \u0026quot;System RAM\u0026quot; not at top level as above. To fix it, if we found a unmatched resource in the top level, we will continue to search matched resources in its descendant resources. So, we will not miss any matched resources in resource tree anymore. In the new implementation, an example resource tree |------------- \u0026quot;CXL Window 0\u0026quot; ------------| |-- \u0026quot;System RAM\u0026quot; --| will behave similar as the following fake resource tree for region_intersects(, IORESOURCE_SYSTEM_RAM, ), |-- \u0026quot;System RAM\u0026quot; --||-- \u0026quot;CXL Window 0a\u0026quot; --| Where \u0026quot;CXL Window 0a\u0026quot; is part of the original \u0026quot;CXL Window 0\u0026quot; that isn\u0026apos;t covered by \u0026quot;System RAM\u0026quot;.(CVE-2024-49878)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ext4: update orig_path in ext4_find_extent() In ext4_find_extent(), if the path is not big enough, we free it and set *orig_path to NULL. But after reallocating and successfully initializing the path, we don\u0026apos;t update *orig_path, in which case the caller gets a valid path but a NULL ppath, and this may cause a NULL pointer dereference or a path memory leak. For example: ext4_split_extent path = *ppath = 2000 ext4_find_extent if (depth \u0026gt; path[0].p_maxdepth) kfree(path = 2000); *orig_path = path = NULL; path = kcalloc() = 3000 ext4_split_extent_at(*ppath = NULL) path = *ppath; ex = path[depth].p_ext; // NULL pointer dereference! ================================================================== BUG: kernel NULL pointer dereference, address: 0000000000000010 CPU: 6 UID: 0 PID: 576 Comm: fsstress Not tainted 6.11.0-rc2-dirty #847 RIP: 0010:ext4_split_extent_at+0x6d/0x560 Call Trace: \u0026lt;TASK\u0026gt; ext4_split_extent.isra.0+0xcb/0x1b0 ext4_ext_convert_to_initialized+0x168/0x6c0 ext4_ext_handle_unwritten_extents+0x325/0x4d0 ext4_ext_map_blocks+0x520/0xdb0 ext4_map_blocks+0x2b0/0x690 ext4_iomap_begin+0x20e/0x2c0 [...] ================================================================== Therefore, *orig_path is updated when the extent lookup succeeds, so that the caller can safely use path or *ppath.(CVE-2024-49881)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ext4: fix double brelse() the buffer of the extents path In ext4_ext_try_to_merge_up(), set path[1].p_bh to NULL after it has been released, otherwise it may be released twice. An example of what triggers this is as follows: split2 map split1 |--------|-------|--------| ext4_ext_map_blocks ext4_ext_handle_unwritten_extents ext4_split_convert_extents // path-\u0026gt;p_depth == 0 ext4_split_extent // 1. do split1 ext4_split_extent_at |ext4_ext_insert_extent | ext4_ext_create_new_leaf | ext4_ext_grow_indepth | le16_add_cpu(\u0026amp;neh-\u0026gt;eh_depth, 1) | ext4_find_extent | // return -ENOMEM |// get error and try zeroout |path = ext4_find_extent | path-\u0026gt;p_depth = 1 |ext4_ext_try_to_merge | ext4_ext_try_to_merge_up | path-\u0026gt;p_depth = 0 | brelse(path[1].p_bh) ---\u0026gt; not set to NULL here |// zeroout success // 2. update path ext4_find_extent // 3. do split2 ext4_split_extent_at ext4_ext_insert_extent ext4_ext_create_new_leaf ext4_ext_grow_indepth le16_add_cpu(\u0026amp;neh-\u0026gt;eh_depth, 1) ext4_find_extent path[0].p_bh = NULL; path-\u0026gt;p_depth = 1 read_extent_tree_block ---\u0026gt; return err // path[1].p_bh is still the old value ext4_free_ext_path ext4_ext_drop_refs // path-\u0026gt;p_depth == 1 brelse(path[1].p_bh) ---\u0026gt; brelse a buffer twice Finally got the following WARRNING when removing the buffer from lru: ============================================ VFS: brelse: Trying to free free buffer WARNING: CPU: 2 PID: 72 at fs/buffer.c:1241 __brelse+0x58/0x90 CPU: 2 PID: 72 Comm: kworker/u19:1 Not tainted 6.9.0-dirty #716 RIP: 0010:__brelse+0x58/0x90 Call Trace: \u0026lt;TASK\u0026gt; __find_get_block+0x6e7/0x810 bdev_getblk+0x2b/0x480 __ext4_get_inode_loc+0x48a/0x1240 ext4_get_inode_loc+0xb2/0x150 ext4_reserve_inode_write+0xb7/0x230 __ext4_mark_inode_dirty+0x144/0x6a0 ext4_ext_insert_extent+0x9c8/0x3230 ext4_ext_map_blocks+0xf45/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] ============================================(CVE-2024-49882)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ext4: aovid use-after-free in ext4_ext_insert_extent() As Ojaswin mentioned in Link, in ext4_ext_insert_extent(), if the path is reallocated in ext4_ext_create_new_leaf(), we\u0026apos;ll use the stale path and cause UAF. Below is a sample trace with dummy values: ext4_ext_insert_extent path = *ppath = 2000 ext4_ext_create_new_leaf(ppath) ext4_find_extent(ppath) path = *ppath = 2000 if (depth \u0026gt; path[0].p_maxdepth) kfree(path = 2000); *ppath = path = NULL; path = kcalloc() = 3000 *ppath = 3000; return path; /* here path is still 2000, UAF! */ eh = path[depth].p_hdr ================================================================== BUG: KASAN: slab-use-after-free in ext4_ext_insert_extent+0x26d4/0x3330 Read of size 8 at addr ffff8881027bf7d0 by task kworker/u36:1/179 CPU: 3 UID: 0 PID: 179 Comm: kworker/u6:1 Not tainted 6.11.0-rc2-dirty #866 Call Trace: \u0026lt;TASK\u0026gt; ext4_ext_insert_extent+0x26d4/0x3330 ext4_ext_map_blocks+0xe22/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 [...] Allocated by task 179: ext4_find_extent+0x81c/0x1f70 ext4_ext_map_blocks+0x146/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 ext4_writepages+0x26d/0x4e0 do_writepages+0x175/0x700 [...] Freed by task 179: kfree+0xcb/0x240 ext4_find_extent+0x7c0/0x1f70 ext4_ext_insert_extent+0xa26/0x3330 ext4_ext_map_blocks+0xe22/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 ext4_writepages+0x26d/0x4e0 do_writepages+0x175/0x700 [...] ================================================================== So use *ppath to update the path to avoid the above problem.(CVE-2024-49883)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ext4: fix slab-use-after-free in ext4_split_extent_at() We hit the following use-after-free: ================================================================== BUG: KASAN: slab-use-after-free in ext4_split_extent_at+0xba8/0xcc0 Read of size 2 at addr ffff88810548ed08 by task kworker/u20:0/40 CPU: 0 PID: 40 Comm: kworker/u20:0 Not tainted 6.9.0-dirty #724 Call Trace: \u0026lt;TASK\u0026gt; kasan_report+0x93/0xc0 ext4_split_extent_at+0xba8/0xcc0 ext4_split_extent.isra.0+0x18f/0x500 ext4_split_convert_extents+0x275/0x750 ext4_ext_handle_unwritten_extents+0x73e/0x1580 ext4_ext_map_blocks+0xe20/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] Allocated by task 40: __kmalloc_noprof+0x1ac/0x480 ext4_find_extent+0xf3b/0x1e70 ext4_ext_map_blocks+0x188/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] Freed by task 40: kfree+0xf1/0x2b0 ext4_find_extent+0xa71/0x1e70 ext4_ext_insert_extent+0xa22/0x3260 ext4_split_extent_at+0x3ef/0xcc0 ext4_split_extent.isra.0+0x18f/0x500 ext4_split_convert_extents+0x275/0x750 ext4_ext_handle_unwritten_extents+0x73e/0x1580 ext4_ext_map_blocks+0xe20/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] ================================================================== The flow of issue triggering is as follows: ext4_split_extent_at path = *ppath ext4_ext_insert_extent(ppath) ext4_ext_create_new_leaf(ppath) ext4_find_extent(orig_path) path = *orig_path read_extent_tree_block // return -ENOMEM or -EIO ext4_free_ext_path(path) kfree(path) *orig_path = NULL a. If err is -ENOMEM: ext4_ext_dirty(path + path-\u0026gt;p_depth) // path use-after-free !!! b. If err is -EIO and we have EXT_DEBUG defined: ext4_ext_show_leaf(path) eh = path[depth].p_hdr // path also use-after-free !!! So when trying to zeroout or fix the extent length, call ext4_find_extent() to update the path. In addition we use *ppath directly as an ext4_ext_show_leaf() input to avoid possible use-after-free when EXT_DEBUG is defined, and to avoid unnecessary path updates.(CVE-2024-49884)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ext4: avoid use-after-free in ext4_ext_show_leaf() In ext4_find_extent(), path may be freed by error or be reallocated, so using a previously saved *ppath may have been freed and thus may trigger use-after-free, as follows: ext4_split_extent path = *ppath; ext4_split_extent_at(ppath) path = ext4_find_extent(ppath) ext4_split_extent_at(ppath) // ext4_find_extent fails to free path // but zeroout succeeds ext4_ext_show_leaf(inode, path) eh = path[depth].p_hdr // path use-after-free !!! Similar to ext4_split_extent_at(), we use *ppath directly as an input to ext4_ext_show_leaf(). Fix a spelling error by the way. Same problem in ext4_ext_handle_unwritten_extents(). Since \u0026apos;path\u0026apos; is only used in ext4_ext_show_leaf(), remove \u0026apos;path\u0026apos; and use *ppath directly. This issue is triggered only when EXT_DEBUG is defined and therefore does not affect functionality.(CVE-2024-49889)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: fbdev: pxafb: Fix possible use after free in pxafb_task() In the pxafb_probe function, it calls the pxafb_init_fbinfo function, after which \u0026amp;fbi-\u0026gt;task is associated with pxafb_task. Moreover, within this pxafb_init_fbinfo function, the pxafb_blank function within the \u0026amp;pxafb_ops struct is capable of scheduling work. If we remove the module which will call pxafb_remove to make cleanup, it will call unregister_framebuffer function which can call do_unregister_framebuffer to free fbi-\u0026gt;fb through put_fb_info(fb_info), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows: CPU0 CPU1 | pxafb_task pxafb_remove | unregister_framebuffer(info) | do_unregister_framebuffer(fb_info) | put_fb_info(fb_info) | // free fbi-\u0026gt;fb | set_ctrlr_state(fbi, state) | __pxafb_lcd_power(fbi, 0) | fbi-\u0026gt;lcd_power(on, \u0026amp;fbi-\u0026gt;fb.var) | //use fbi-\u0026gt;fb Fix it by ensuring that the work is canceled before proceeding with the cleanup in pxafb_remove. Note that only root user can remove the driver at runtime.(CVE-2024-49924)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: net/xen-netback: prevent UAF in xenvif_flush_hash() During the list_for_each_entry_rcu iteration call of xenvif_flush_hash, kfree_rcu does not exist inside the rcu read critical section, so if kfree_rcu is called when the rcu grace period ends during the iteration, UAF occurs when accessing head-\u0026gt;next after the entry becomes free. Therefore, to solve this, you need to change it to list_for_each_entry_safe.(CVE-2024-49936)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix uaf in l2cap_connect [Syzbot reported] BUG: KASAN: slab-use-after-free in l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949 Read of size 8 at addr ffff8880241e9800 by task kworker/u9:0/54 CPU: 0 UID: 0 PID: 54 Comm: kworker/u9:0 Not tainted 6.11.0-rc6-syzkaller-00268-g788220eee30d #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 Workqueue: hci2 hci_rx_work Call Trace: \u0026lt;TASK\u0026gt; __dump_stack lib/dump_stack.c:93 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:119 print_address_description mm/kasan/report.c:377 [inline] print_report+0xc3/0x620 mm/kasan/report.c:488 kasan_report+0xd9/0x110 mm/kasan/report.c:601 l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949 l2cap_connect_req net/bluetooth/l2cap_core.c:4080 [inline] l2cap_bredr_sig_cmd net/bluetooth/l2cap_core.c:4772 [inline] l2cap_sig_channel net/bluetooth/l2cap_core.c:5543 [inline] l2cap_recv_frame+0xf0b/0x8eb0 net/bluetooth/l2cap_core.c:6825 l2cap_recv_acldata+0x9b4/0xb70 net/bluetooth/l2cap_core.c:7514 hci_acldata_packet net/bluetooth/hci_core.c:3791 [inline] hci_rx_work+0xaab/0x1610 net/bluetooth/hci_core.c:4028 process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231 process_scheduled_works kernel/workqueue.c:3312 [inline] worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389 kthread+0x2c1/0x3a0 kernel/kthread.c:389 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 ... Freed by task 5245: kasan_save_stack+0x33/0x60 mm/kasan/common.c:47 kasan_save_track+0x14/0x30 mm/kasan/common.c:68 kasan_save_free_info+0x3b/0x60 mm/kasan/generic.c:579 poison_slab_object+0xf7/0x160 mm/kasan/common.c:240 __kasan_slab_free+0x32/0x50 mm/kasan/common.c:256 kasan_slab_free include/linux/kasan.h:184 [inline] slab_free_hook mm/slub.c:2256 [inline] slab_free mm/slub.c:4477 [inline] kfree+0x12a/0x3b0 mm/slub.c:4598 l2cap_conn_free net/bluetooth/l2cap_core.c:1810 [inline] kref_put include/linux/kref.h:65 [inline] l2cap_conn_put net/bluetooth/l2cap_core.c:1822 [inline] l2cap_conn_del+0x59d/0x730 net/bluetooth/l2cap_core.c:1802 l2cap_connect_cfm+0x9e6/0xf80 net/bluetooth/l2cap_core.c:7241 hci_connect_cfm include/net/bluetooth/hci_core.h:1960 [inline] hci_conn_failed+0x1c3/0x370 net/bluetooth/hci_conn.c:1265 hci_abort_conn_sync+0x75a/0xb50 net/bluetooth/hci_sync.c:5583 abort_conn_sync+0x197/0x360 net/bluetooth/hci_conn.c:2917 hci_cmd_sync_work+0x1a4/0x410 net/bluetooth/hci_sync.c:328 process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231 process_scheduled_works kernel/workqueue.c:3312 [inline] worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389 kthread+0x2c1/0x3a0 kernel/kthread.c:389 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244(CVE-2024-49950)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: media: venus: fix use after free bug in venus_remove due to race condition in venus_probe, core-\u0026gt;work is bound with venus_sys_error_handler, which is used to handle error. The code use core-\u0026gt;sys_err_done to make sync work. The core-\u0026gt;work is started in venus_event_notify. If we call venus_remove, there might be an unfished work. The possible sequence is as follows: CPU0 CPU1 |venus_sys_error_handler venus_remove | hfi_destroy | venus_hfi_destroy | kfree(hdev); | |hfi_reinit |venus_hfi_queues_reinit |//use hdev Fix it by canceling the work in venus_remove.(CVE-2024-49981)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: amdkfd_free_gtt_mem clear the correct pointer Pass pointer reference to amdgpu_bo_unref to clear the correct pointer, otherwise amdgpu_bo_unref clear the local variable, the original pointer not set to NULL, this could cause use-after-free bug.(CVE-2024-49991)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: tipc: guard against string buffer overrun Smatch reports that copying media_name and if_name to name_parts may overwrite the destination. .../bearer.c:166 bearer_name_validate() error: strcpy() \u0026apos;media_name\u0026apos; too large for \u0026apos;name_parts-\u0026gt;media_name\u0026apos; (32 vs 16) .../bearer.c:167 bearer_name_validate() error: strcpy() \u0026apos;if_name\u0026apos; too large for \u0026apos;name_parts-\u0026gt;if_name\u0026apos; (1010102 vs 16) This does seem to be the case so guard against this possibility by using strscpy() and failing if truncation occurs. Introduced by commit b97bf3fd8f6a (\u0026quot;[TIPC] Initial merge\u0026quot;) Compile tested only.(CVE-2024-49995)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: slip: make slhc_remember() more robust against malicious packets syzbot found that slhc_remember() was missing checks against malicious packets [1]. slhc_remember() only checked the size of the packet was at least 20, which is not good enough. We need to make sure the packet includes the IPv4 and TCP header that are supposed to be carried. Add iph and th pointers to make the code more readable. [1] BUG: KMSAN: uninit-value in slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666 slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666 ppp_receive_nonmp_frame+0xe45/0x35e0 drivers/net/ppp/ppp_generic.c:2455 ppp_receive_frame drivers/net/ppp/ppp_generic.c:2372 [inline] ppp_do_recv+0x65f/0x40d0 drivers/net/ppp/ppp_generic.c:2212 ppp_input+0x7dc/0xe60 drivers/net/ppp/ppp_generic.c:2327 pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379 sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113 __release_sock+0x1da/0x330 net/core/sock.c:3072 release_sock+0x6b/0x250 net/core/sock.c:3626 pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 ____sys_sendmsg+0x903/0xb60 net/socket.c:2602 ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was created at: slab_post_alloc_hook mm/slub.c:4091 [inline] slab_alloc_node mm/slub.c:4134 [inline] kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4186 kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587 __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678 alloc_skb include/linux/skbuff.h:1322 [inline] sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732 pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 ____sys_sendmsg+0x903/0xb60 net/socket.c:2602 ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f CPU: 0 UID: 0 PID: 5460 Comm: syz.2.33 Not tainted 6.12.0-rc2-syzkaller-00006-g87d6aab2389e #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50033)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ppp: fix ppp_async_encode() illegal access syzbot reported an issue in ppp_async_encode() [1] In this case, pppoe_sendmsg() is called with a zero size. Then ppp_async_encode() is called with an empty skb. BUG: KMSAN: uninit-value in ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline] BUG: KMSAN: uninit-value in ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675 ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline] ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675 ppp_async_send+0x130/0x1b0 drivers/net/ppp/ppp_async.c:634 ppp_channel_bridge_input drivers/net/ppp/ppp_generic.c:2280 [inline] ppp_input+0x1f1/0xe60 drivers/net/ppp/ppp_generic.c:2304 pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379 sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113 __release_sock+0x1da/0x330 net/core/sock.c:3072 release_sock+0x6b/0x250 net/core/sock.c:3626 pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 ____sys_sendmsg+0x903/0xb60 net/socket.c:2602 ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was created at: slab_post_alloc_hook mm/slub.c:4092 [inline] slab_alloc_node mm/slub.c:4135 [inline] kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4187 kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587 __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678 alloc_skb include/linux/skbuff.h:1322 [inline] sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732 pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 ____sys_sendmsg+0x903/0xb60 net/socket.c:2602 ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f CPU: 1 UID: 0 PID: 5411 Comm: syz.1.14 Not tainted 6.12.0-rc1-syzkaller-00165-g360c1f1f24c6 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50035)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: serial: protect uart_port_dtr_rts() in uart_shutdown() too Commit af224ca2df29 (serial: core: Prevent unsafe uart port access, part 3) added few uport == NULL checks. It added one to uart_shutdown(), so the commit assumes, uport can be NULL in there. But right after that protection, there is an unprotected \u0026quot;uart_port_dtr_rts(uport, false);\u0026quot; call. That is invoked only if HUPCL is set, so I assume that is the reason why we do not see lots of these reports. Or it cannot be NULL at this point at all for some reason :P. Until the above is investigated, stay on the safe side and move this dereference to the if too. I got this inconsistency from Coverity under CID 1585130. Thanks.(CVE-2024-50058)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: tty: n_gsm: Fix use-after-free in gsm_cleanup_mux BUG: KASAN: slab-use-after-free in gsm_cleanup_mux+0x77b/0x7b0 drivers/tty/n_gsm.c:3160 [n_gsm] Read of size 8 at addr ffff88815fe99c00 by task poc/3379 CPU: 0 UID: 0 PID: 3379 Comm: poc Not tainted 6.11.0+ #56 Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 11/12/2020 Call Trace: \u0026lt;TASK\u0026gt; gsm_cleanup_mux+0x77b/0x7b0 drivers/tty/n_gsm.c:3160 [n_gsm] __pfx_gsm_cleanup_mux+0x10/0x10 drivers/tty/n_gsm.c:3124 [n_gsm] __pfx_sched_clock_cpu+0x10/0x10 kernel/sched/clock.c:389 update_load_avg+0x1c1/0x27b0 kernel/sched/fair.c:4500 __pfx_min_vruntime_cb_rotate+0x10/0x10 kernel/sched/fair.c:846 __rb_insert_augmented+0x492/0xbf0 lib/rbtree.c:161 gsmld_ioctl+0x395/0x1450 drivers/tty/n_gsm.c:3408 [n_gsm] _raw_spin_lock_irqsave+0x92/0xf0 arch/x86/include/asm/atomic.h:107 __pfx_gsmld_ioctl+0x10/0x10 drivers/tty/n_gsm.c:3822 [n_gsm] ktime_get+0x5e/0x140 kernel/time/timekeeping.c:195 ldsem_down_read+0x94/0x4e0 arch/x86/include/asm/atomic64_64.h:79 __pfx_ldsem_down_read+0x10/0x10 drivers/tty/tty_ldsem.c:338 __pfx_do_vfs_ioctl+0x10/0x10 fs/ioctl.c:805 tty_ioctl+0x643/0x1100 drivers/tty/tty_io.c:2818 Allocated by task 65: gsm_data_alloc.constprop.0+0x27/0x190 drivers/tty/n_gsm.c:926 [n_gsm] gsm_send+0x2c/0x580 drivers/tty/n_gsm.c:819 [n_gsm] gsm1_receive+0x547/0xad0 drivers/tty/n_gsm.c:3038 [n_gsm] gsmld_receive_buf+0x176/0x280 drivers/tty/n_gsm.c:3609 [n_gsm] tty_ldisc_receive_buf+0x101/0x1e0 drivers/tty/tty_buffer.c:391 tty_port_default_receive_buf+0x61/0xa0 drivers/tty/tty_port.c:39 flush_to_ldisc+0x1b0/0x750 drivers/tty/tty_buffer.c:445 process_scheduled_works+0x2b0/0x10d0 kernel/workqueue.c:3229 worker_thread+0x3dc/0x950 kernel/workqueue.c:3391 kthread+0x2a3/0x370 kernel/kthread.c:389 ret_from_fork+0x2d/0x70 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:257 Freed by task 3367: kfree+0x126/0x420 mm/slub.c:4580 gsm_cleanup_mux+0x36c/0x7b0 drivers/tty/n_gsm.c:3160 [n_gsm] gsmld_ioctl+0x395/0x1450 drivers/tty/n_gsm.c:3408 [n_gsm] tty_ioctl+0x643/0x1100 drivers/tty/tty_io.c:2818 [Analysis] gsm_msg on the tx_ctrl_list or tx_data_list of gsm_mux can be freed by multi threads through ioctl,which leads to the occurrence of uaf. Protect it by gsm tx lock.(CVE-2024-50073)",
"id": "OESA-2024-2370",
"modified": "2026-08-06T11:07:50Z",
"published": "2024-11-08T11:07:50Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2370"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48948"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48949"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48960"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48962"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48966"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48971"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48972"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48978"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48992"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-49002"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-49005"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-49011"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-49020"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-49021"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-49031"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-49032"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47659"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47669"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47696"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47697"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47701"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47742"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49860"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49877"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49878"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49881"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49882"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49883"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49884"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49889"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49924"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49936"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49950"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49981"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49991"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49995"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50033"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50035"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50058"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50073"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "kernel security update",
"upstream": [
"CVE-2022-48948",
"CVE-2022-48949",
"CVE-2022-48960",
"CVE-2022-48962",
"CVE-2022-48966",
"CVE-2022-48971",
"CVE-2022-48972",
"CVE-2022-48978",
"CVE-2022-48992",
"CVE-2022-49002",
"CVE-2022-49005",
"CVE-2022-49011",
"CVE-2022-49020",
"CVE-2022-49021",
"CVE-2022-49031",
"CVE-2022-49032",
"CVE-2024-47659",
"CVE-2024-47669",
"CVE-2024-47696",
"CVE-2024-47697",
"CVE-2024-47701",
"CVE-2024-47742",
"CVE-2024-49860",
"CVE-2024-49877",
"CVE-2024-49878",
"CVE-2024-49881",
"CVE-2024-49882",
"CVE-2024-49883",
"CVE-2024-49884",
"CVE-2024-49889",
"CVE-2024-49924",
"CVE-2024-49936",
"CVE-2024-49950",
"CVE-2024-49981",
"CVE-2024-49991",
"CVE-2024-49995",
"CVE-2024-50033",
"CVE-2024-50035",
"CVE-2024-50058",
"CVE-2024-50073"
]
}
OESA-2024-2371 (CVE-2022-48956)
Vulnerability from osv_openeuler – Published: 2024-11-08 11:07 – Updated: 2026-08-06 11:07 – Source websiteThe Linux Kernel, the operating system core itself.
Security Fix(es):
In the Linux kernel, the following vulnerability has been resolved: ipv6: avoid use-after-free in ip6_fragment() Blamed commit claimed rcu_read_lock() was held by ip6_fragment() callers. It seems to not be always true, at least for UDP stack. syzbot reported: BUG: KASAN: use-after-free in ip6_dst_idev include/net/ip6_fib.h:245 [inline] BUG: KASAN: use-after-free in ip6_fragment+0x2724/0x2770 net/ipv6/ip6_output.c:951 Read of size 8 at addr ffff88801d403e80 by task syz-executor.3/7618 CPU: 1 PID: 7618 Comm: syz-executor.3 Not tainted 6.1.0-rc6-syzkaller-00012-g4312098baf37 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd1/0x138 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:284 [inline] print_report+0x15e/0x45d mm/kasan/report.c:395 kasan_report+0xbf/0x1f0 mm/kasan/report.c:495 ip6_dst_idev include/net/ip6_fib.h:245 [inline] ip6_fragment+0x2724/0x2770 net/ipv6/ip6_output.c:951 __ip6_finish_output net/ipv6/ip6_output.c:193 [inline] ip6_finish_output+0x9a3/0x1170 net/ipv6/ip6_output.c:206 NF_HOOK_COND include/linux/netfilter.h:291 [inline] ip6_output+0x1f1/0x540 net/ipv6/ip6_output.c:227 dst_output include/net/dst.h:445 [inline] ip6_local_out+0xb3/0x1a0 net/ipv6/output_core.c:161 ip6_send_skb+0xbb/0x340 net/ipv6/ip6_output.c:1966 udp_v6_send_skb+0x82a/0x18a0 net/ipv6/udp.c:1286 udp_v6_push_pending_frames+0x140/0x200 net/ipv6/udp.c:1313 udpv6_sendmsg+0x18da/0x2c80 net/ipv6/udp.c:1606 inet6_sendmsg+0x9d/0xe0 net/ipv6/af_inet6.c:665 sock_sendmsg_nosec net/socket.c:714 [inline] sock_sendmsg+0xd3/0x120 net/socket.c:734 sock_write_iter+0x295/0x3d0 net/socket.c:1108 call_write_iter include/linux/fs.h:2191 [inline] new_sync_write fs/read_write.c:491 [inline] vfs_write+0x9ed/0xdd0 fs/read_write.c:584 ksys_write+0x1ec/0x250 fs/read_write.c:637 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7fde3588c0d9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fde365b6168 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 00007fde359ac050 RCX: 00007fde3588c0d9 RDX: 000000000000ffdc RSI: 00000000200000c0 RDI: 000000000000000a RBP: 00007fde358e7ae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fde35acfb1f R14: 00007fde365b6300 R15: 0000000000022000 </TASK> Allocated by task 7618: kasan_save_stack+0x22/0x40 mm/kasan/common.c:45 kasan_set_track+0x25/0x30 mm/kasan/common.c:52 __kasan_slab_alloc+0x82/0x90 mm/kasan/common.c:325 kasan_slab_alloc include/linux/kasan.h:201 [inline] slab_post_alloc_hook mm/slab.h:737 [inline] slab_alloc_node mm/slub.c:3398 [inline] slab_alloc mm/slub.c:3406 [inline] __kmem_cache_alloc_lru mm/slub.c:3413 [inline] kmem_cache_alloc+0x2b4/0x3d0 mm/slub.c:3422 dst_alloc+0x14a/0x1f0 net/core/dst.c:92 ip6_dst_alloc+0x32/0xa0 net/ipv6/route.c:344 ip6_rt_pcpu_alloc net/ipv6/route.c:1369 [inline] rt6_make_pcpu_route net/ipv6/route.c:1417 [inline] ip6_pol_route+0x901/0x1190 net/ipv6/route.c:2254 pol_lookup_func include/net/ip6_fib.h:582 [inline] fib6_rule_lookup+0x52e/0x6f0 net/ipv6/fib6_rules.c:121 ip6_route_output_flags_noref+0x2e6/0x380 net/ipv6/route.c:2625 ip6_route_output_flags+0x76/0x320 net/ipv6/route.c:2638 ip6_route_output include/net/ip6_route.h:98 [inline] ip6_dst_lookup_tail+0x5ab/0x1620 net/ipv6/ip6_output.c:1092 ip6_dst_lookup_flow+0x90/0x1d0 net/ipv6/ip6_output.c:1222 ip6_sk_dst_lookup_flow+0x553/0x980 net/ipv6/ip6_output.c:1260 udpv6_sendmsg+0x151d/0x2c80 net/ipv6/udp.c:1554 inet6_sendmsg+0x9d/0xe0 net/ipv6/af_inet6.c:665 sock_sendmsg_nosec n ---truncated---(CVE-2022-48956)
In the Linux kernel, the following vulnerability has been resolved: ethernet: aeroflex: fix potential skb leak in greth_init_rings() The greth_init_rings() function won't free the newly allocated skb when dma_mapping_error() returns error, so add dev_kfree_skb() to fix it. Compile tested only.(CVE-2022-48958)
In the Linux kernel, the following vulnerability has been resolved: net: hisilicon: Fix potential use-after-free in hix5hd2_rx() The skb is delivered to napi_gro_receive() which may free it, after calling this, dereferencing skb may trigger use-after-free.(CVE-2022-48960)
In the Linux kernel, the following vulnerability has been resolved: net: mdio: fix unbalanced fwnode reference count in mdio_device_release() There is warning report about of_node refcount leak while probing mdio device: OF: ERROR: memory leak, expected refcount 1 instead of 2, of_node_get()/of_node_put() unbalanced - destroy cset entry: attach overlay node /spi/soc@0/mdio@710700c0/ethernet@4 In of_mdiobus_register_device(), we increase fwnode refcount by fwnode_handle_get() before associating the of_node with mdio device, but it has never been decreased in normal path. Since that, in mdio_device_release(), it needs to call fwnode_handle_put() in addition instead of calling kfree() directly. After above, just calling mdio_device_free() in the error handle path of of_mdiobus_register_device() is enough to keep the refcount balanced.(CVE-2022-48961)
In the Linux kernel, the following vulnerability has been resolved: net: hisilicon: Fix potential use-after-free in hisi_femac_rx() The skb is delivered to napi_gro_receive() which may free it, after calling this, dereferencing skb may trigger use-after-free.(CVE-2022-48962)
In the Linux kernel, the following vulnerability has been resolved: net: mvneta: Prevent out of bounds read in mvneta_config_rss() The pp->indir[0] value comes from the user. It is passed to: if (cpu_online(pp->rxq_def)) inside the mvneta_percpu_elect() function. It needs bounds checkeding to ensure that it is not beyond the end of the cpu bitmap.(CVE-2022-48966)
In the Linux kernel, the following vulnerability has been resolved: mac802154: fix missing INIT_LIST_HEAD in ieee802154_if_add() Kernel fault injection test reports null-ptr-deref as follows: BUG: kernel NULL pointer dereference, address: 0000000000000008 RIP: 0010:cfg802154_netdev_notifier_call+0x120/0x310 include/linux/list.h:114 Call Trace: <TASK> raw_notifier_call_chain+0x6d/0xa0 kernel/notifier.c:87 call_netdevice_notifiers_info+0x6e/0xc0 net/core/dev.c:1944 unregister_netdevice_many_notify+0x60d/0xcb0 net/core/dev.c:1982 unregister_netdevice_queue+0x154/0x1a0 net/core/dev.c:10879 register_netdevice+0x9a8/0xb90 net/core/dev.c:10083 ieee802154_if_add+0x6ed/0x7e0 net/mac802154/iface.c:659 ieee802154_register_hw+0x29c/0x330 net/mac802154/main.c:229 mcr20a_probe+0xaaa/0xcb1 drivers/net/ieee802154/mcr20a.c:1316 ieee802154_if_add() allocates wpan_dev as netdev's private data, but not init the list in struct wpan_dev. cfg802154_netdev_notifier_call() manage the list when device register/unregister, and may lead to null-ptr-deref. Use INIT_LIST_HEAD() on it to initialize it correctly.(CVE-2022-48972)
In the Linux kernel, the following vulnerability has been resolved: gpiolib: fix memory leak in gpiochip_setup_dev() Here is a backtrace report about memory leak detected in gpiochip_setup_dev(): unreferenced object 0xffff88810b406400 (size 512): comm "python3", pid 1682, jiffies 4295346908 (age 24.090s) backtrace: kmalloc_trace device_add device_private_init at drivers/base/core.c:3361 (inlined by) device_add at drivers/base/core.c:3411 cdev_device_add gpiolib_cdev_register gpiochip_setup_dev gpiochip_add_data_with_key gcdev_register() & gcdev_unregister() would call device_add() & device_del() (no matter CONFIG_GPIO_CDEV is enabled or not) to register/unregister device. However, if device_add() succeeds, some resource (like struct device_private allocated by device_private_init()) is not released by device_del(). Therefore, after device_add() succeeds by gcdev_register(), it needs to call put_device() to release resource in the error handle path. Here we move forward the register of release function, and let it release every piece of resource by put_device() instead of kfree(). While at it, fix another subtle issue, i.e. when gc->ngpio is equal to 0, we still call kcalloc() and, in case of further error, kfree() on the ZERO_PTR pointer, which is not NULL. It's not a bug per se, but rather waste of the resources and potentially wrong expectation about contents of the gdev->descs variable.(CVE-2022-48975)
In the Linux kernel, the following vulnerability has been resolved: drm/shmem-helper: Remove errant put in error path drm_gem_shmem_mmap() doesn't own this reference, resulting in the GEM object getting prematurely freed leading to a later use-after-free.(CVE-2022-48981)
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix crash when replugging CSR fake controllers It seems fake CSR 5.0 clones can cause the suspend notifier to be registered twice causing the following kernel panic: [ 71.986122] Call Trace: [ 71.986124] <TASK> [ 71.986125] blocking_notifier_chain_register+0x33/0x60 [ 71.986130] hci_register_dev+0x316/0x3d0 [bluetooth 99b5497ea3d09708fa1366c1dc03288bf3cca8da] [ 71.986154] btusb_probe+0x979/0xd85 [btusb e1e0605a4f4c01984a4b9c8ac58c3666ae287477] [ 71.986159] ? __pm_runtime_set_status+0x1a9/0x300 [ 71.986162] ? ktime_get_mono_fast_ns+0x3e/0x90 [ 71.986167] usb_probe_interface+0xe3/0x2b0 [ 71.986171] really_probe+0xdb/0x380 [ 71.986174] ? pm_runtime_barrier+0x54/0x90 [ 71.986177] __driver_probe_device+0x78/0x170 [ 71.986180] driver_probe_device+0x1f/0x90 [ 71.986183] __device_attach_driver+0x89/0x110 [ 71.986186] ? driver_allows_async_probing+0x70/0x70 [ 71.986189] bus_for_each_drv+0x8c/0xe0 [ 71.986192] __device_attach+0xb2/0x1e0 [ 71.986195] bus_probe_device+0x92/0xb0 [ 71.986198] device_add+0x422/0x9a0 [ 71.986201] ? sysfs_merge_group+0xd4/0x110 [ 71.986205] usb_set_configuration+0x57a/0x820 [ 71.986208] usb_generic_driver_probe+0x4f/0x70 [ 71.986211] usb_probe_device+0x3a/0x110 [ 71.986213] really_probe+0xdb/0x380 [ 71.986216] ? pm_runtime_barrier+0x54/0x90 [ 71.986219] __driver_probe_device+0x78/0x170 [ 71.986221] driver_probe_device+0x1f/0x90 [ 71.986224] __device_attach_driver+0x89/0x110 [ 71.986227] ? driver_allows_async_probing+0x70/0x70 [ 71.986230] bus_for_each_drv+0x8c/0xe0 [ 71.986232] __device_attach+0xb2/0x1e0 [ 71.986235] bus_probe_device+0x92/0xb0 [ 71.986237] device_add+0x422/0x9a0 [ 71.986239] ? _dev_info+0x7d/0x98 [ 71.986242] ? blake2s_update+0x4c/0xc0 [ 71.986246] usb_new_device.cold+0x148/0x36d [ 71.986250] hub_event+0xa8a/0x1910 [ 71.986255] process_one_work+0x1c4/0x380 [ 71.986259] worker_thread+0x51/0x390 [ 71.986262] ? rescuer_thread+0x3b0/0x3b0 [ 71.986264] kthread+0xdb/0x110 [ 71.986266] ? kthread_complete_and_exit+0x20/0x20 [ 71.986268] ret_from_fork+0x1f/0x30 [ 71.986273] </TASK> [ 71.986274] ---[ end trace 0000000000000000 ]--- [ 71.986284] btusb: probe of 2-1.6:1.0 failed with error -17(CVE-2022-48982)
In the Linux kernel, the following vulnerability has been resolved: ASoC: soc-pcm: Add NULL check in BE reparenting Add NULL check in dpcm_be_reparent API, to handle kernel NULL pointer dereference error. The issue occurred in fuzzing test.(CVE-2022-48992)
In the Linux kernel, the following vulnerability has been resolved: Input: raydium_ts_i2c - fix memory leak in raydium_i2c_send() There is a kmemleak when test the raydium_i2c_ts with bpf mock device: unreferenced object 0xffff88812d3675a0 (size 8): comm "python3", pid 349, jiffies 4294741067 (age 95.695s) hex dump (first 8 bytes): 11 0e 10 c0 01 00 04 00 ........ backtrace: [<0000000068427125>] __kmalloc+0x46/0x1b0 [<0000000090180f91>] raydium_i2c_send+0xd4/0x2bf [raydium_i2c_ts] [<000000006e631aee>] raydium_i2c_initialize.cold+0xbc/0x3e4 [raydium_i2c_ts] [<00000000dc6fcf38>] raydium_i2c_probe+0x3cd/0x6bc [raydium_i2c_ts] [<00000000a310de16>] i2c_device_probe+0x651/0x680 [<00000000f5a96bf3>] really_probe+0x17c/0x3f0 [<00000000096ba499>] __driver_probe_device+0xe3/0x170 [<00000000c5acb4d9>] driver_probe_device+0x49/0x120 [<00000000264fe082>] __device_attach_driver+0xf7/0x150 [<00000000f919423c>] bus_for_each_drv+0x114/0x180 [<00000000e067feca>] __device_attach+0x1e5/0x2d0 [<0000000054301fc2>] bus_probe_device+0x126/0x140 [<00000000aad93b22>] device_add+0x810/0x1130 [<00000000c086a53f>] i2c_new_client_device+0x352/0x4e0 [<000000003c2c248c>] of_i2c_register_device+0xf1/0x110 [<00000000ffec4177>] of_i2c_notify+0x100/0x160 unreferenced object 0xffff88812d3675c8 (size 8): comm "python3", pid 349, jiffies 4294741070 (age 95.692s) hex dump (first 8 bytes): 22 00 36 2d 81 88 ff ff ".6-.... backtrace: [<0000000068427125>] __kmalloc+0x46/0x1b0 [<0000000090180f91>] raydium_i2c_send+0xd4/0x2bf [raydium_i2c_ts] [<000000001d5c9620>] raydium_i2c_initialize.cold+0x223/0x3e4 [raydium_i2c_ts] [<00000000dc6fcf38>] raydium_i2c_probe+0x3cd/0x6bc [raydium_i2c_ts] [<00000000a310de16>] i2c_device_probe+0x651/0x680 [<00000000f5a96bf3>] really_probe+0x17c/0x3f0 [<00000000096ba499>] __driver_probe_device+0xe3/0x170 [<00000000c5acb4d9>] driver_probe_device+0x49/0x120 [<00000000264fe082>] __device_attach_driver+0xf7/0x150 [<00000000f919423c>] bus_for_each_drv+0x114/0x180 [<00000000e067feca>] __device_attach+0x1e5/0x2d0 [<0000000054301fc2>] bus_probe_device+0x126/0x140 [<00000000aad93b22>] device_add+0x810/0x1130 [<00000000c086a53f>] i2c_new_client_device+0x352/0x4e0 [<000000003c2c248c>] of_i2c_register_device+0xf1/0x110 [<00000000ffec4177>] of_i2c_notify+0x100/0x160 After BANK_SWITCH command from i2c BUS, no matter success or error happened, the tx_buf should be freed.(CVE-2022-48995)
In the Linux kernel, the following vulnerability has been resolved: riscv: Sync efi page table's kernel mappings before switching The EFI page table is initially created as a copy of the kernel page table. With VMAP_STACK enabled, kernel stacks are allocated in the vmalloc area: if the stack is allocated in a new PGD (one that was not present at the moment of the efi page table creation or not synced in a previous vmalloc fault), the kernel will take a trap when switching to the efi page table when the vmalloc kernel stack is accessed, resulting in a kernel panic. Fix that by updating the efi kernel mappings before switching to the efi page table.(CVE-2022-49004)
In the Linux kernel, the following vulnerability has been resolved: ASoC: ops: Fix bounds check for _sx controls For _sx controls the semantics of the max field is not the usual one, max is the number of steps rather than the maximum value. This means that our check in snd_soc_put_volsw_sx() needs to just check against the maximum value.(CVE-2022-49005)
In the Linux kernel, the following vulnerability has been resolved: hwmon: (coretemp) fix pci device refcount leak in nv1a_ram_new() As comment of pci_get_domain_bus_and_slot() says, it returns a pci device with refcount increment, when finish using it, the caller must decrement the reference count by calling pci_dev_put(). So call it after using to avoid refcount leak.(CVE-2022-49011)
In the Linux kernel, the following vulnerability has been resolved: tipc: re-fetch skb cb after tipc_msg_validate As the call trace shows, the original skb was freed in tipc_msg_validate(), and dereferencing the old skb cb would cause an use-after-free crash. BUG: KASAN: use-after-free in tipc_crypto_rcv_complete+0x1835/0x2240 [tipc] Call Trace: <IRQ> tipc_crypto_rcv_complete+0x1835/0x2240 [tipc] tipc_crypto_rcv+0xd32/0x1ec0 [tipc] tipc_rcv+0x744/0x1150 [tipc] ... Allocated by task 47078: kmem_cache_alloc_node+0x158/0x4d0 __alloc_skb+0x1c1/0x270 tipc_buf_acquire+0x1e/0xe0 [tipc] tipc_msg_create+0x33/0x1c0 [tipc] tipc_link_build_proto_msg+0x38a/0x2100 [tipc] tipc_link_timeout+0x8b8/0xef0 [tipc] tipc_node_timeout+0x2a1/0x960 [tipc] call_timer_fn+0x2d/0x1c0 ... Freed by task 47078: tipc_msg_validate+0x7b/0x440 [tipc] tipc_crypto_rcv_complete+0x4b5/0x2240 [tipc] tipc_crypto_rcv+0xd32/0x1ec0 [tipc] tipc_rcv+0x744/0x1150 [tipc] This patch fixes it by re-fetching the skb cb from the new allocated skb after calling tipc_msg_validate().(CVE-2022-49017)
In the Linux kernel, the following vulnerability has been resolved: net/9p: Fix a potential socket leak in p9_socket_open Both p9_fd_create_tcp() and p9_fd_create_unix() will call p9_socket_open(). If the creation of p9_trans_fd fails, p9_fd_create_tcp() and p9_fd_create_unix() will return an error directly instead of releasing the cscoket, which will result in a socket leak. This patch adds sock_release() to fix the leak issue.(CVE-2022-49020)
In the Linux kernel, the following vulnerability has been resolved: net: phy: fix null-ptr-deref while probe() failed I got a null-ptr-deref report as following when doing fault injection test: BUG: kernel NULL pointer dereference, address: 0000000000000058 Oops: 0000 [#1] PREEMPT SMP KASAN PTI CPU: 1 PID: 253 Comm: 507-spi-dm9051 Tainted: G B N 6.1.0-rc3+ Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: 0010:klist_put+0x2d/0xd0 Call Trace: <TASK> klist_remove+0xf1/0x1c0 device_release_driver_internal+0x23e/0x2d0 bus_remove_device+0x1bd/0x240 device_del+0x357/0x770 phy_device_remove+0x11/0x30 mdiobus_unregister+0xa5/0x140 release_nodes+0x6a/0xa0 devres_release_all+0xf8/0x150 device_unbind_cleanup+0x19/0xd0 //probe path: phy_device_register() device_add() phy_connect phy_attach_direct() //set device driver probe() //it's failed, driver is not bound device_bind_driver() // probe failed, it's not called //remove path: phy_device_remove() device_del() device_release_driver_internal() __device_release_driver() //dev->drv is not NULL klist_remove() <- knode_driver is not added yet, cause null-ptr-deref In phy_attach_direct(), after setting the 'dev->driver', probe() fails, device_bind_driver() is not called, so the knode_driver->n_klist is not set, then it causes null-ptr-deref in __device_release_driver() while deleting device. Fix this by setting dev->driver to NULL in the error path in phy_attach_direct().(CVE-2022-49021)
In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: fix buffer overflow in elem comparison For vendor elements, the code here assumes that 5 octets are present without checking. Since the element itself is already checked to fit, we only need to check the length.(CVE-2022-49023)
In the Linux kernel, the following vulnerability has been resolved: iio: health: afe4403: Fix oob read in afe4403_read_raw KASAN report out-of-bounds read as follows: BUG: KASAN: global-out-of-bounds in afe4403_read_raw+0x42e/0x4c0 Read of size 4 at addr ffffffffc02ac638 by task cat/279 Call Trace: afe4403_read_raw iio_read_channel_info dev_attr_show The buggy address belongs to the variable: afe4403_channel_leds+0x18/0xffffffffffffe9e0 This issue can be reproduced by singe command: $ cat /sys/bus/spi/devices/spi0.0/iio\:device0/in_intensity6_raw The array size of afe4403_channel_leds is less than channels, so access with chan->address cause OOB read in afe4403_read_raw. Fix it by moving access before use it.(CVE-2022-49031)
In the Linux kernel, the following vulnerability has been resolved: iio: health: afe4404: Fix oob read in afe4404_[read|write]raw KASAN report out-of-bounds read as follows: BUG: KASAN: global-out-of-bounds in afe4404_read_raw+0x2ce/0x380 Read of size 4 at addr ffffffffc00e4658 by task cat/278 Call Trace: afe4404_read_raw iio_read_channel_info dev_attr_show The buggy address belongs to the variable: afe4404_channel_leds+0x18/0xffffffffffffe9c0 This issue can be reproduce by singe command: $ cat /sys/bus/i2c/devices/0-0058/iio\:device0/in_intensity6_raw The array size of afe4404_channel_leds and afe4404_channel_offdacs are less than channels, so access with chan->address cause OOB read in afe4404[read|write]_raw. Fix it by moving access before use them.(CVE-2022-49032)
In the Linux kernel, the following vulnerability has been resolved:
memcg_write_event_control(): fix a user-triggerable oops
we are not guaranteed that anything past the terminating NUL is mapped (let alone initialized with anything sane).(CVE-2024-45021)
In the Linux kernel, the following vulnerability has been resolved:
gtp: fix a potential NULL pointer dereference
When sockfd_lookup() fails, gtp_encap_enable_socket() returns a NULL pointer, but its callers only check for error pointers thus miss the NULL pointer case.
Fix it by returning an error pointer with the error code carried from sockfd_lookup().
(I found this bug during code inspection.)(CVE-2024-46677)
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Check BIOS images before it is used
BIOS images may fail to load and null checks are added before they are used.
This fixes 6 NULL_RETURNS issues reported by Coverity.(CVE-2024-46809)
In the Linux kernel, the following vulnerability has been resolved:
smack: tcp: ipv4, fix incorrect labeling
Currently, Smack mirrors the label of incoming tcp/ipv4 connections: when a label 'foo' connects to a label 'bar' with tcp/ipv4, 'foo' always gets 'foo' in returned ipv4 packets. So, 1) returned packets are incorrectly labeled ('foo' instead of 'bar') 2) 'bar' can write to 'foo' without being authorized to write.
Here is a scenario how to see this:
-
Take two machines, let's call them C and S, with active Smack in the default state (no settings, no rules, no labeled hosts, only builtin labels)
-
At S, add Smack rule 'foo bar w' (labels 'foo' and 'bar' are instantiated at S at this moment)
-
At S, at label 'bar', launch a program that listens for incoming tcp/ipv4 connections
-
From C, at label 'foo', connect to the listener at S. (label 'foo' is instantiated at C at this moment) Connection succeedes and works.
-
Send some data in both directions.
- Collect network traffic of this connection.
All packets in both directions are labeled with the CIPSO of the label 'foo'. Hence, label 'bar' writes to 'foo' without being authorized, and even without ever being known at C.
If anybody cares: exactly the same happens with DCCP.
This behavior 1st manifested in release 2.6.29.4 (see Fixes below) and it looks unintentional. At least, no explanation was provided.
I changed returned packes label into the 'bar', to bring it into line with the Smack documentation claims.(CVE-2024-47659)
In the Linux kernel, the following vulnerability has been resolved:
fsnotify: clear PARENT_WATCHED flags lazily
In some setups directories can have many (usually negative) dentries. Hence __fsnotify_update_child_dentry_flags() function can take a significant amount of time. Since the bulk of this function happens under inode->i_lock this causes a significant contention on the lock when we remove the watch from the directory as the __fsnotify_update_child_dentry_flags() call from fsnotify_recalc_mask() races with __fsnotify_update_child_dentry_flags() calls from __fsnotify_parent() happening on children. This can lead upto softlockup reports reported by users.
Fix the problem by calling fsnotify_update_children_dentry_flags() to set PARENT_WATCHED flags only when parent starts watching children.
When parent stops watching children, clear false positive PARENT_WATCHED flags lazily in __fsnotify_parent() for each accessed child.(CVE-2024-47660)
In the Linux kernel, the following vulnerability has been resolved:
lib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc()
If we need to increase the tree depth, allocate a new node, and then race with another thread that increased the tree depth before us, we'll still have a preallocated node that might be used later.
If we then use that node for a new non-root node, it'll still have a pointer to the old root instead of being zeroed - fix this by zeroing it in the cmpxchg failure path.(CVE-2024-47668)
In the Linux kernel, the following vulnerability has been resolved:
wifi: iwlwifi: mvm: pause TCM when the firmware is stopped
Not doing so will make us send a host command to the transport while the firmware is not alive, which will trigger a WARNING.
bad state = 0 WARNING: CPU: 2 PID: 17434 at drivers/net/wireless/intel/iwlwifi/iwl-trans.c:115 iwl_trans_send_cmd+0x1cb/0x1e0 [iwlwifi] RIP: 0010:iwl_trans_send_cmd+0x1cb/0x1e0 [iwlwifi] Call Trace: <TASK> iwl_mvm_send_cmd+0x40/0xc0 [iwlmvm] iwl_mvm_config_scan+0x198/0x260 [iwlmvm] iwl_mvm_recalc_tcm+0x730/0x11d0 [iwlmvm] iwl_mvm_tcm_work+0x1d/0x30 [iwlmvm] process_one_work+0x29e/0x640 worker_thread+0x2df/0x690 ? rescuer_thread+0x540/0x540 kthread+0x192/0x1e0 ? set_kthread_struct+0x90/0x90 ret_from_fork+0x22/0x30(CVE-2024-47673)
In the Linux kernel, the following vulnerability has been resolved: f2fs: get rid of online repaire on corrupted directory syzbot reports a f2fs bug as below: kernel BUG at fs/f2fs/inode.c:896! RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896 Call Trace: evict+0x532/0x950 fs/inode.c:704 dispose_list fs/inode.c:747 [inline] evict_inodes+0x5f9/0x690 fs/inode.c:797 generic_shutdown_super+0x9d/0x2d0 fs/super.c:627 kill_block_super+0x44/0x90 fs/super.c:1696 kill_f2fs_super+0x344/0x690 fs/f2fs/super.c:4898 deactivate_locked_super+0xc4/0x130 fs/super.c:473 cleanup_mnt+0x41f/0x4b0 fs/namespace.c:1373 task_work_run+0x24f/0x310 kernel/task_work.c:228 ptrace_notify+0x2d2/0x380 kernel/signal.c:2402 ptrace_report_syscall include/linux/ptrace.h:415 [inline] ptrace_report_syscall_exit include/linux/ptrace.h:477 [inline] syscall_exit_work+0xc6/0x190 kernel/entry/common.c:173 syscall_exit_to_user_mode_prepare kernel/entry/common.c:200 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:205 [inline] syscall_exit_to_user_mode+0x279/0x370 kernel/entry/common.c:218 do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896 Online repaire on corrupted directory in f2fs_lookup() can generate dirty data/meta while racing w/ readonly remount, it may leave dirty inode after filesystem becomes readonly, however, checkpoint() will skips flushing dirty inode in a state of readonly mode, result in above panic. Let's get rid of online repaire in f2fs_lookup(), and leave the work to fsck.f2fs.(CVE-2024-47690)
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid use-after-free in f2fs_stop_gc_thread() syzbot reports a f2fs bug as below: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114 print_report+0xe8/0x550 mm/kasan/report.c:491 kasan_report+0x143/0x180 mm/kasan/report.c:601 kasan_check_range+0x282/0x290 mm/kasan/generic.c:189 instrument_atomic_read_write include/linux/instrumented.h:96 [inline] atomic_fetch_add_relaxed include/linux/atomic/atomic-instrumented.h:252 [inline] __refcount_add include/linux/refcount.h:184 [inline] __refcount_inc include/linux/refcount.h:241 [inline] refcount_inc include/linux/refcount.h:258 [inline] get_task_struct include/linux/sched/task.h:118 [inline] kthread_stop+0xca/0x630 kernel/kthread.c:704 f2fs_stop_gc_thread+0x65/0xb0 fs/f2fs/gc.c:210 f2fs_do_shutdown+0x192/0x540 fs/f2fs/file.c:2283 f2fs_ioc_shutdown fs/f2fs/file.c:2325 [inline] __f2fs_ioctl+0x443a/0xbe60 fs/f2fs/file.c:4325 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f The root cause is below race condition, it may cause use-after-free issue in sbi->gc_th pointer. - remount - f2fs_remount - f2fs_stop_gc_thread - kfree(gc_th) - f2fs_ioc_shutdown - f2fs_do_shutdown - f2fs_stop_gc_thread - kthread_stop(gc_th->f2fs_gc_task) : sbi->gc_thread = NULL; We will call f2fs_do_shutdown() in two paths: - for f2fs_ioc_shutdown() path, we should grab sb->s_umount semaphore for fixing. - for f2fs_shutdown() path, it's safe since caller has already grabbed sb->s_umount semaphore.(CVE-2024-47691)
In the Linux kernel, the following vulnerability has been resolved: nfsd: return -EINVAL when namelen is 0 When we have a corrupted main.sqlite in /var/lib/nfs/nfsdcld/, it may result in namelen being 0, which will cause memdup_user() to return ZERO_SIZE_PTR. When we access the name.data that has been assigned the value of ZERO_SIZE_PTR in nfs4_client_to_reclaim(), null pointer dereference is triggered. [ T1205] ================================================================== [ T1205] BUG: KASAN: null-ptr-deref in nfs4_client_to_reclaim+0xe9/0x260 [ T1205] Read of size 1 at addr 0000000000000010 by task nfsdcld/1205 [ T1205] [ T1205] CPU: 11 PID: 1205 Comm: nfsdcld Not tainted 5.10.0-00003-g2c1423731b8d #406 [ T1205] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS ?-20190727_073836-buildvm-ppc64le-16.ppc.fedoraproject.org-3.fc31 04/01/2014 [ T1205] Call Trace: [ T1205] dump_stack+0x9a/0xd0 [ T1205] ? nfs4_client_to_reclaim+0xe9/0x260 [ T1205] __kasan_report.cold+0x34/0x84 [ T1205] ? nfs4_client_to_reclaim+0xe9/0x260 [ T1205] kasan_report+0x3a/0x50 [ T1205] nfs4_client_to_reclaim+0xe9/0x260 [ T1205] ? nfsd4_release_lockowner+0x410/0x410 [ T1205] cld_pipe_downcall+0x5ca/0x760 [ T1205] ? nfsd4_cld_tracking_exit+0x1d0/0x1d0 [ T1205] ? down_write_killable_nested+0x170/0x170 [ T1205] ? avc_policy_seqno+0x28/0x40 [ T1205] ? selinux_file_permission+0x1b4/0x1e0 [ T1205] rpc_pipe_write+0x84/0xb0 [ T1205] vfs_write+0x143/0x520 [ T1205] ksys_write+0xc9/0x170 [ T1205] ? __ia32_sys_read+0x50/0x50 [ T1205] ? ktime_get_coarse_real_ts64+0xfe/0x110 [ T1205] ? ktime_get_coarse_real_ts64+0xa2/0x110 [ T1205] do_syscall_64+0x33/0x40 [ T1205] entry_SYSCALL_64_after_hwframe+0x67/0xd1 [ T1205] RIP: 0033:0x7fdbdb761bc7 [ T1205] Code: 0f 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 0f 1f 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 514 [ T1205] RSP: 002b:00007fff8c4b7248 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 [ T1205] RAX: ffffffffffffffda RBX: 000000000000042b RCX: 00007fdbdb761bc7 [ T1205] RDX: 000000000000042b RSI: 00007fff8c4b75f0 RDI: 0000000000000008 [ T1205] RBP: 00007fdbdb761bb0 R08: 0000000000000000 R09: 0000000000000001 [ T1205] R10: 0000000000000000 R11: 0000000000000246 R12: 000000000000042b [ T1205] R13: 0000000000000008 R14: 00007fff8c4b75f0 R15: 0000000000000000 [ T1205] ================================================================== Fix it by checking namelen.(CVE-2024-47692)
In the Linux kernel, the following vulnerability has been resolved: IB/core: Fix ib_cache_setup_one error flow cleanup When ib_cache_update return an error, we exit ib_cache_setup_one instantly with no proper cleanup, even though before this we had already successfully done gid_table_setup_one, that results in the kernel WARN below. Do proper cleanup using gid_table_cleanup_one before returning the err in order to fix the issue. WARNING: CPU: 4 PID: 922 at drivers/infiniband/core/cache.c:806 gid_table_release_one+0x181/0x1a0 Modules linked in: CPU: 4 UID: 0 PID: 922 Comm: c_repro Not tainted 6.11.0-rc1+ #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:gid_table_release_one+0x181/0x1a0 Code: 44 8b 38 75 0c e8 2f cb 34 ff 4d 8b b5 28 05 00 00 e8 23 cb 34 ff 44 89 f9 89 da 4c 89 f6 48 c7 c7 d0 58 14 83 e8 4f de 21 ff <0f> 0b 4c 8b 75 30 e9 54 ff ff ff 48 8 3 c4 10 5b 5d 41 5c 41 5d 41 RSP: 0018:ffffc90002b835b0 EFLAGS: 00010286 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff811c8527 RDX: 0000000000000000 RSI: ffffffff811c8534 RDI: 0000000000000001 RBP: ffff8881011b3d00 R08: ffff88810b3abe00 R09: 205d303839303631 R10: 666572207972746e R11: 72746e6520444947 R12: 0000000000000001 R13: ffff888106390000 R14: ffff8881011f2110 R15: 0000000000000001 FS: 00007fecc3b70800(0000) GS:ffff88813bd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020000340 CR3: 000000010435a001 CR4: 00000000003706b0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ? show_regs+0x94/0xa0 ? __warn+0x9e/0x1c0 ? gid_table_release_one+0x181/0x1a0 ? report_bug+0x1f9/0x340 ? gid_table_release_one+0x181/0x1a0 ? handle_bug+0xa2/0x110 ? exc_invalid_op+0x31/0xa0 ? asm_exc_invalid_op+0x16/0x20 ? __warn_printk+0xc7/0x180 ? __warn_printk+0xd4/0x180 ? gid_table_release_one+0x181/0x1a0 ib_device_release+0x71/0xe0 ? __pfx_ib_device_release+0x10/0x10 device_release+0x44/0xd0 kobject_put+0x135/0x3d0 put_device+0x20/0x30 rxe_net_add+0x7d/0xa0 rxe_newlink+0xd7/0x190 nldev_newlink+0x1b0/0x2a0 ? __pfx_nldev_newlink+0x10/0x10 rdma_nl_rcv_msg+0x1ad/0x2e0 rdma_nl_rcv_skb.constprop.0+0x176/0x210 netlink_unicast+0x2de/0x400 netlink_sendmsg+0x306/0x660 __sock_sendmsg+0x110/0x120 _syssendmsg+0x30e/0x390 _sys_sendmsg+0x9b/0xf0 ? kstrtouint+0x6e/0xa0 ? kstrtouint_from_user+0x7c/0xb0 ? get_pid_task+0xb0/0xd0 ? proc_fail_nth_write+0x5b/0x140 ? __fget_light+0x9a/0x200 ? preempt_count_add+0x47/0xa0 __sys_sendmsg+0x61/0xd0 do_syscall_64+0x50/0x110 entry_SYSCALL_64_after_hwframe+0x76/0x7e(CVE-2024-47693)
In the Linux kernel, the following vulnerability has been resolved: RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency In the commit aee2424246f9 ("RDMA/iwcm: Fix a use-after-free related to destroying CM IDs"), the function flush_workqueue is invoked to flush the work queue iwcm_wq. But at that time, the work queue iwcm_wq was created via the function alloc_ordered_workqueue without the flag WQ_MEM_RECLAIM. Because the current process is trying to flush the whole iwcm_wq, if iwcm_wq doesn't have the flag WQ_MEM_RECLAIM, verify that the current process is not reclaiming memory or running on a workqueue which doesn't have the flag WQ_MEM_RECLAIM as that can break forward-progress guarantee leading to a deadlock. The call trace is as below: [ 125.350876][ T1430] Call Trace: [ 125.356281][ T1430] <TASK> [ 125.361285][ T1430] ? __warn (kernel/panic.c:693) [ 125.367640][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.375689][ T1430] ? report_bug (lib/bug.c:180 lib/bug.c:219) [ 125.382505][ T1430] ? handle_bug (arch/x86/kernel/traps.c:239) [ 125.388987][ T1430] ? exc_invalid_op (arch/x86/kernel/traps.c:260 (discriminator 1)) [ 125.395831][ T1430] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:621) [ 125.403125][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.410984][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.418764][ T1430] __flush_workqueue (kernel/workqueue.c:3970) [ 125.426021][ T1430] ? __pfxmightresched (kernel/sched/core.c:10151) [ 125.433431][ T1430] ? destroy_cm_id (drivers/infiniband/core/iwcm.c:375) iw_cm [ 125.441209][ T1430] ? pfxflushworkqueue (kernel/workqueue.c:3910) [ 125.473900][ T1430] ? _raw_spin_lock_irqsave (arch/x86/include/asm/atomic.h:107 include/linux/atomic/atomic-arch-fallback.h:2170 include/linux/atomic/atomic-instrumented.h:1302 include/asm-generic/qspinlock.h:111 include/linux/spinlock.h:187 include/linux/spinlock_api_smp.h:111 kernel/locking/spinlock.c:162) [ 125.473909][ T1430] ? pfx__raw_spin_lock_irqsave (kernel/locking/spinlock.c:161) [ 125.482537][ T1430] _destroy_id (drivers/infiniband/core/cma.c:2044) rdma_cm [ 125.495072][ T1430] nvme_rdma_free_queue (drivers/nvme/host/rdma.c:656 drivers/nvme/host/rdma.c:650) nvme_rdma [ 125.505827][ T1430] nvme_rdma_reset_ctrl_work (drivers/nvme/host/rdma.c:2180) nvme_rdma [ 125.505831][ T1430] process_one_work (kernel/workqueue.c:3231) [ 125.515122][ T1430] worker_thread (kernel/workqueue.c:3306 kernel/workqueue.c:3393) [ 125.515127][ T1430] ? __pfx_worker_thread (kernel/workqueue.c:3339) [ 125.531837][ T1430] kthread (kernel/kthread.c:389) [ 125.539864][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.550628][ T1430] ret_from_fork (arch/x86/kernel/process.c:147) [ 125.558840][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.558844][ T1430] ret_from_fork_asm (arch/x86/entry/entry_64.S:257) [ 125.566487][ T1430] </TASK> [ 125.566488][ T1430] ---[ end trace 0000000000000000 ]---(CVE-2024-47696)
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential null-ptr-deref in nilfs_btree_insert() Patch series "nilfs2: fix potential issues with empty b-tree nodes". This series addresses three potential issues with empty b-tree nodes that can occur with corrupted filesystem images, including one recently discovered by syzbot. This patch (of 3): If a b-tree is broken on the device, and the b-tree height is greater than 2 (the level of the root node is greater than 1) even if the number of child nodes of the b-tree root is 0, a NULL pointer dereference occurs in nilfs_btree_prepare_insert(), which is called from nilfs_btree_insert(). This is because, when the number of child nodes of the b-tree root is 0, nilfs_btree_do_lookup() does not set the block buffer head in any of path[x].bp_bh, leaving it as the initial value of NULL, but if the level of the b-tree root node is greater than 1, nilfs_btree_get_nonroot_node(), which accesses the buffer memory of path[x].bp_bh, is called. Fix this issue by adding a check to nilfs_btree_root_broken(), which performs sanity checks when reading the root node from the device, to detect this inconsistency. Thanks to Lizhi Xu for trying to solve the bug and clarifying the cause early on.(CVE-2024-47699)
In the Linux kernel, the following vulnerability has been resolved: ext4: avoid OOB when system.data xattr changes underneath the filesystem When looking up for an entry in an inlined directory, if e_value_offs is changed underneath the filesystem by some change in the block device, it will lead to an out-of-bounds access that KASAN detects as an UAF. EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none. loop0: detected capacity change from 2048 to 2047 ================================================================== BUG: KASAN: use-after-free in ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500 Read of size 1 at addr ffff88803e91130f by task syz-executor269/5103 CPU: 0 UID: 0 PID: 5103 Comm: syz-executor269 Not tainted 6.11.0-rc4-syzkaller #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Call Trace: <TASK> __dump_stack lib/dump_stack.c:93 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119 print_address_description mm/kasan/report.c:377 [inline] print_report+0x169/0x550 mm/kasan/report.c:488 kasan_report+0x143/0x180 mm/kasan/report.c:601 ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500 ext4_find_inline_entry+0x4be/0x5e0 fs/ext4/inline.c:1697 __ext4_find_entry+0x2b4/0x1b30 fs/ext4/namei.c:1573 ext4_lookup_entry fs/ext4/namei.c:1727 [inline] ext4_lookup+0x15f/0x750 fs/ext4/namei.c:1795 lookup_one_qstr_excl+0x11f/0x260 fs/namei.c:1633 filename_create+0x297/0x540 fs/namei.c:3980 do_symlinkat+0xf9/0x3a0 fs/namei.c:4587 __do_sys_symlinkat fs/namei.c:4610 [inline] __se_sys_symlinkat fs/namei.c:4607 [inline] __x64_sys_symlinkat+0x95/0xb0 fs/namei.c:4607 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f3e73ced469 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 21 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fff4d40c258 EFLAGS: 00000246 ORIG_RAX: 000000000000010a RAX: ffffffffffffffda RBX: 0032656c69662f2e RCX: 00007f3e73ced469 RDX: 0000000020000200 RSI: 00000000ffffff9c RDI: 00000000200001c0 RBP: 0000000000000000 R08: 00007fff4d40c290 R09: 00007fff4d40c290 R10: 0023706f6f6c2f76 R11: 0000000000000246 R12: 00007fff4d40c27c R13: 0000000000000003 R14: 431bde82d7b634db R15: 00007fff4d40c2b0 </TASK> Calling ext4_xattr_ibody_find right after reading the inode with ext4_get_inode_loc will lead to a check of the validity of the xattrs, avoiding this problem.(CVE-2024-47701)
In the Linux kernel, the following vulnerability has been resolved: bpf, lsm: Add check for BPF LSM return value A bpf prog returning a positive number attached to file_alloc_security hook makes kernel panic. This happens because file system can not filter out the positive number returned by the LSM prog using IS_ERR, and misinterprets this positive number as a file pointer. Given that hook file_alloc_security never returned positive number before the introduction of BPF LSM, and other BPF LSM hooks may encounter similar issues, this patch adds LSM return value check in verifier, to ensure no unexpected value is returned.(CVE-2024-47703)
In the Linux kernel, the following vulnerability has been resolved: block: fix potential invalid pointer dereference in blk_add_partition The blk_add_partition() function initially used a single if-condition (IS_ERR(part)) to check for errors when adding a partition. This was modified to handle the specific case of -ENXIO separately, allowing the function to proceed without logging the error in this case. However, this change unintentionally left a path where md_autodetect_dev() could be called without confirming that part is a valid pointer. This commit separates the error handling logic by splitting the initial if-condition, improving code readability and handling specific error scenarios explicitly. The function now distinguishes the general error case from -ENXIO without altering the existing behavior of md_autodetect_dev() calls.(CVE-2024-47705)
In the Linux kernel, the following vulnerability has been resolved: jfs: fix out-of-bounds in dbNextAG() and diAlloc() In dbNextAG() , there is no check for the case where bmp->db_numag is greater or same than MAXAG due to a polluted image, which causes an out-of-bounds. Therefore, a bounds check should be added in dbMount(). And in dbNextAG(), a check for the case where agpref is greater than bmp->db_numag should be added, so an out-of-bounds exception should be prevented. Additionally, a check for the case where agno is greater or same than MAXAG should be added in diAlloc() to prevent out-of-bounds.(CVE-2024-47723)
In the Linux kernel, the following vulnerability has been resolved: padata: use integer wrap around to prevent deadlock on seq_nr overflow When submitting more than 2^32 padata objects to padata_do_serial, the current sorting implementation incorrectly sorts padata objects with overflowed seq_nr, causing them to be placed before existing objects in the reorder list. This leads to a deadlock in the serialization process as padata_find_next cannot match padata->seq_nr and pd->processed because the padata instance with overflowed seq_nr will be selected next. To fix this, we use an unsigned integer wrap around to correctly sort padata objects in scenarios with integer overflow.(CVE-2024-47739)
In the Linux kernel, the following vulnerability has been resolved: firmware_loader: Block path traversal Most firmware names are hardcoded strings, or are constructed from fairly constrained format strings where the dynamic parts are just some hex numbers or such. However, there are a couple codepaths in the kernel where firmware file names contain string components that are passed through from a device or semi-privileged userspace; the ones I could find (not counting interfaces that require root privileges) are: - lpfc_sli4_request_firmware_update() seems to construct the firmware filename from "ModelName", a string that was previously parsed out of some descriptor ("Vital Product Data") in lpfc_fill_vpd() - nfp_net_fw_find() seems to construct a firmware filename from a model name coming from nfp_hwinfo_lookup(pf->hwinfo, "nffw.partno"), which I think parses some descriptor that was read from the device. (But this case likely isn't exploitable because the format string looks like "netronome/nic_%s", and there shouldn't be any folders starting with "netronome/nic_". The previous case was different because there, the "%s" is at the start of the format string.) - module_flash_fw_schedule() is reachable from the ETHTOOL_MSG_MODULE_FW_FLASH_ACT netlink command, which is marked as GENL_UNS_ADMIN_PERM (meaning CAP_NET_ADMIN inside a user namespace is enough to pass the privilege check), and takes a userspace-provided firmware name. (But I think to reach this case, you need to have CAP_NET_ADMIN over a network namespace that a special kind of ethernet device is mapped into, so I think this is not a viable attack path in practice.) Fix it by rejecting any firmware names containing ".." path components. For what it's worth, I went looking and haven't found any USB device drivers that use the firmware loader dangerously.(CVE-2024-47742)
In the Linux kernel, the following vulnerability has been resolved: vhost_vdpa: assign irq bypass producer token correctly We used to call irq_bypass_unregister_producer() in vhost_vdpa_setup_vq_irq() which is problematic as we don't know if the token pointer is still valid or not. Actually, we use the eventfd_ctx as the token so the life cycle of the token should be bound to the VHOST_SET_VRING_CALL instead of vhost_vdpa_setup_vq_irq() which could be called by set_status(). Fixing this by setting up irq bypass producer's token when handling VHOST_SET_VRING_CALL and un-registering the producer before calling vhost_vring_ioctl() to prevent a possible use after free as eventfd could have been released in vhost_vring_ioctl(). And such registering and unregistering will only be done if DRIVER_OK is set.(CVE-2024-47748)
In the Linux kernel, the following vulnerability has been resolved: PCI: keystone: Fix if-statement expression in ks_pcie_quirk() This code accidentally uses && where || was intended. It potentially results in a NULL dereference. Thus, fix the if-statement expression to use the correct condition. kwilczynski: commit log
In the Linux kernel, the following vulnerability has been resolved: nbd: fix race between timeout and normal completion If request timetout is handled by nbd_requeue_cmd(), normal completion has to be stopped for avoiding to complete this requeued request, other use-after-free can be triggered. Fix the race by clearing NBD_CMD_INFLIGHT in nbd_requeue_cmd(), meantime make sure that cmd->lock is grabbed for clearing the flag and the requeue.(CVE-2024-49855)
In the Linux kernel, the following vulnerability has been resolved: efistub/tpm: Use ACPI reclaim memory for event log to avoid corruption The TPM event log table is a Linux specific construct, where the data produced by the GetEventLog() boot service is cached in memory, and passed on to the OS using an EFI configuration table. The use of EFI_LOADER_DATA here results in the region being left unreserved in the E820 memory map constructed by the EFI stub, and this is the memory description that is passed on to the incoming kernel by kexec, which is therefore unaware that the region should be reserved. Even though the utility of the TPM2 event log after a kexec is questionable, any corruption might send the parsing code off into the weeds and crash the kernel. So let's use EFI_ACPI_RECLAIM_MEMORY instead, which is always treated as reserved by the E820 conversion logic.(CVE-2024-49858)
In the Linux kernel, the following vulnerability has been resolved: ACPI: sysfs: validate return type of _STR method Only buffer objects are valid return values of _STR. If something else is returned description_show() will access invalid memory.(CVE-2024-49860)
In the Linux kernel, the following vulnerability has been resolved: vhost/scsi: null-ptr-dereference in vhost_scsi_get_req() Since commit 3f8ca2e115e5 ("vhost/scsi: Extract common handling code from control queue handler") a null pointer dereference bug can be triggered when guest sends an SCSI AN request. In vhost_scsi_ctl_handle_vq(), vc.target is assigned with &v_req.tmf.lun[1] within a switch-case block and is then passed to vhost_scsi_get_req() which extracts vc->req and tpg. However, for a VIRTIO_SCSI_T_AN_* request, tpg is not required, so vc.target is set to NULL in this branch. Later, in vhost_scsi_get_req(), vc->target is dereferenced without being checked, leading to a null pointer dereference bug. This bug can be triggered from guest. When this bug occurs, the vhost_worker process is killed while holding vq->mutex and the corresponding tpg will remain occupied indefinitely. Below is the KASAN report: Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] CPU: 1 PID: 840 Comm: poc Not tainted 6.10.0+ #1 Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:vhost_scsi_get_req+0x165/0x3a0 Code: 00 fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 2b 02 00 00 48 b8 00 00 00 00 00 fc ff df 4d 8b 65 30 4c 89 e2 48 c1 ea 03 <0f> b6 04 02 4c 89 e2 83 e2 07 38 d0 7f 08 84 c0 0f 85 be 01 00 00 RSP: 0018:ffff888017affb50 EFLAGS: 00010246 RAX: dffffc0000000000 RBX: ffff88801b000000 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff888017affcb8 RBP: ffff888017affb80 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 R13: ffff888017affc88 R14: ffff888017affd1c R15: ffff888017993000 FS: 000055556e076500(0000) GS:ffff88806b100000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000200027c0 CR3: 0000000010ed0004 CR4: 0000000000370ef0 Call Trace: <TASK> ? show_regs+0x86/0xa0 ? die_addr+0x4b/0xd0 ? exc_general_protection+0x163/0x260 ? asm_exc_general_protection+0x27/0x30 ? vhost_scsi_get_req+0x165/0x3a0 vhost_scsi_ctl_handle_vq+0x2a4/0xca0 ? __pfx_vhost_scsi_ctl_handle_vq+0x10/0x10 ? __switch_to+0x721/0xeb0 ? __schedule+0xda5/0x5710 ? __kasan_check_write+0x14/0x30 ? _raw_spin_lock+0x82/0xf0 vhost_scsi_ctl_handle_kick+0x52/0x90 vhost_run_work_list+0x134/0x1b0 vhost_task_fn+0x121/0x350 ... </TASK> ---[ end trace 0000000000000000 ]--- Let's add a check in vhost_scsi_get_req. whitespace fixes
In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate When doing cleanup, if flags without OCFS2_BH_READAHEAD, it may trigger NULL pointer dereference in the following ocfs2_set_buffer_uptodate() if bh is NULL.(CVE-2024-49877)
In the Linux kernel, the following vulnerability has been resolved: drm: omapdrm: Add missing check for alloc_ordered_workqueue As it may return NULL pointer and cause NULL pointer dereference. Add check for the return value of alloc_ordered_workqueue.(CVE-2024-49879)
In the Linux kernel, the following vulnerability has been resolved: ext4: update orig_path in ext4_find_extent() In ext4_find_extent(), if the path is not big enough, we free it and set orig_path to NULL. But after reallocating and successfully initializing the path, we don't update orig_path, in which case the caller gets a valid path but a NULL ppath, and this may cause a NULL pointer dereference or a path memory leak. For example: ext4_split_extent path = ppath = 2000 ext4_find_extent if (depth > path[0].p_maxdepth) kfree(path = 2000); orig_path = path = NULL; path = kcalloc() = 3000 ext4_split_extent_at(ppath = NULL) path = ppath; ex = path[depth].p_ext; // NULL pointer dereference! ================================================================== BUG: kernel NULL pointer dereference, address: 0000000000000010 CPU: 6 UID: 0 PID: 576 Comm: fsstress Not tainted 6.11.0-rc2-dirty #847 RIP: 0010:ext4_split_extent_at+0x6d/0x560 Call Trace: <TASK> ext4_split_extent.isra.0+0xcb/0x1b0 ext4_ext_convert_to_initialized+0x168/0x6c0 ext4_ext_handle_unwritten_extents+0x325/0x4d0 ext4_ext_map_blocks+0x520/0xdb0 ext4_map_blocks+0x2b0/0x690 ext4_iomap_begin+0x20e/0x2c0 [...] ================================================================== Therefore, orig_path is updated when the extent lookup succeeds, so that the caller can safely use path or ppath.(CVE-2024-49881)
In the Linux kernel, the following vulnerability has been resolved: ext4: fix double brelse() the buffer of the extents path In ext4_ext_try_to_merge_up(), set path[1].p_bh to NULL after it has been released, otherwise it may be released twice. An example of what triggers this is as follows: split2 map split1 |--------|-------|--------| ext4_ext_map_blocks ext4_ext_handle_unwritten_extents ext4_split_convert_extents // path->p_depth == 0 ext4_split_extent // 1. do split1 ext4_split_extent_at |ext4_ext_insert_extent | ext4_ext_create_new_leaf | ext4_ext_grow_indepth | le16_add_cpu(&neh->eh_depth, 1) | ext4_find_extent | // return -ENOMEM |// get error and try zeroout |path = ext4_find_extent | path->p_depth = 1 |ext4_ext_try_to_merge | ext4_ext_try_to_merge_up | path->p_depth = 0 | brelse(path[1].p_bh) ---> not set to NULL here |// zeroout success // 2. update path ext4_find_extent // 3. do split2 ext4_split_extent_at ext4_ext_insert_extent ext4_ext_create_new_leaf ext4_ext_grow_indepth le16_add_cpu(&neh->eh_depth, 1) ext4_find_extent path[0].p_bh = NULL; path->p_depth = 1 read_extent_tree_block ---> return err // path[1].p_bh is still the old value ext4_free_ext_path ext4_ext_drop_refs // path->p_depth == 1 brelse(path[1].p_bh) ---> brelse a buffer twice Finally got the following WARRNING when removing the buffer from lru: ============================================ VFS: brelse: Trying to free free buffer WARNING: CPU: 2 PID: 72 at fs/buffer.c:1241 __brelse+0x58/0x90 CPU: 2 PID: 72 Comm: kworker/u19:1 Not tainted 6.9.0-dirty #716 RIP: 0010:__brelse+0x58/0x90 Call Trace: <TASK> __find_get_block+0x6e7/0x810 bdev_getblk+0x2b/0x480 __ext4_get_inode_loc+0x48a/0x1240 ext4_get_inode_loc+0xb2/0x150 ext4_reserve_inode_write+0xb7/0x230 __ext4_mark_inode_dirty+0x144/0x6a0 ext4_ext_insert_extent+0x9c8/0x3230 ext4_ext_map_blocks+0xf45/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] ============================================(CVE-2024-49882)
In the Linux kernel, the following vulnerability has been resolved: ext4: aovid use-after-free in ext4_ext_insert_extent() As Ojaswin mentioned in Link, in ext4_ext_insert_extent(), if the path is reallocated in ext4_ext_create_new_leaf(), we'll use the stale path and cause UAF. Below is a sample trace with dummy values: ext4_ext_insert_extent path = ppath = 2000 ext4_ext_create_new_leaf(ppath) ext4_find_extent(ppath) path = ppath = 2000 if (depth > path[0].p_maxdepth) kfree(path = 2000); ppath = path = NULL; path = kcalloc() = 3000 ppath = 3000; return path; / here path is still 2000, UAF! / eh = path[depth].p_hdr ================================================================== BUG: KASAN: slab-use-after-free in ext4_ext_insert_extent+0x26d4/0x3330 Read of size 8 at addr ffff8881027bf7d0 by task kworker/u36:1/179 CPU: 3 UID: 0 PID: 179 Comm: kworker/u6:1 Not tainted 6.11.0-rc2-dirty #866 Call Trace: <TASK> ext4_ext_insert_extent+0x26d4/0x3330 ext4_ext_map_blocks+0xe22/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 [...] Allocated by task 179: ext4_find_extent+0x81c/0x1f70 ext4_ext_map_blocks+0x146/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 ext4_writepages+0x26d/0x4e0 do_writepages+0x175/0x700 [...] Freed by task 179: kfree+0xcb/0x240 ext4_find_extent+0x7c0/0x1f70 ext4_ext_insert_extent+0xa26/0x3330 ext4_ext_map_blocks+0xe22/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 ext4_writepages+0x26d/0x4e0 do_writepages+0x175/0x700 [...] ================================================================== So use *ppath to update the path to avoid the above problem.(CVE-2024-49883)
In the Linux kernel, the following vulnerability has been resolved: ext4: fix slab-use-after-free in ext4_split_extent_at() We hit the following use-after-free: ================================================================== BUG: KASAN: slab-use-after-free in ext4_split_extent_at+0xba8/0xcc0 Read of size 2 at addr ffff88810548ed08 by task kworker/u20:0/40 CPU: 0 PID: 40 Comm: kworker/u20:0 Not tainted 6.9.0-dirty #724 Call Trace: <TASK> kasan_report+0x93/0xc0 ext4_split_extent_at+0xba8/0xcc0 ext4_split_extent.isra.0+0x18f/0x500 ext4_split_convert_extents+0x275/0x750 ext4_ext_handle_unwritten_extents+0x73e/0x1580 ext4_ext_map_blocks+0xe20/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] Allocated by task 40: __kmalloc_noprof+0x1ac/0x480 ext4_find_extent+0xf3b/0x1e70 ext4_ext_map_blocks+0x188/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] Freed by task 40: kfree+0xf1/0x2b0 ext4_find_extent+0xa71/0x1e70 ext4_ext_insert_extent+0xa22/0x3260 ext4_split_extent_at+0x3ef/0xcc0 ext4_split_extent.isra.0+0x18f/0x500 ext4_split_convert_extents+0x275/0x750 ext4_ext_handle_unwritten_extents+0x73e/0x1580 ext4_ext_map_blocks+0xe20/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] ================================================================== The flow of issue triggering is as follows: ext4_split_extent_at path = ppath ext4_ext_insert_extent(ppath) ext4_ext_create_new_leaf(ppath) ext4_find_extent(orig_path) path = orig_path read_extent_tree_block // return -ENOMEM or -EIO ext4_free_ext_path(path) kfree(path) orig_path = NULL a. If err is -ENOMEM: ext4_ext_dirty(path + path->p_depth) // path use-after-free !!! b. If err is -EIO and we have EXT_DEBUG defined: ext4_ext_show_leaf(path) eh = path[depth].p_hdr // path also use-after-free !!! So when trying to zeroout or fix the extent length, call ext4_find_extent() to update the path. In addition we use ppath directly as an ext4_ext_show_leaf() input to avoid possible use-after-free when EXT_DEBUG is defined, and to avoid unnecessary path updates.(CVE-2024-49884)
In the Linux kernel, the following vulnerability has been resolved: platform/x86: ISST: Fix the KASAN report slab-out-of-bounds bug Attaching SST PCI device to VM causes "BUG: KASAN: slab-out-of-bounds". kasan report: [ 19.411889] ================================================================== [ 19.413702] BUG: KASAN: slab-out-of-bounds in _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.415634] Read of size 8 at addr ffff888829e65200 by task cpuhp/16/113 [ 19.417368] [ 19.418627] CPU: 16 PID: 113 Comm: cpuhp/16 Tainted: G E 6.9.0 #10 [ 19.420435] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference Platform, BIOS VMW201.00V.20192059.B64.2207280713 07/28/2022 [ 19.422687] Call Trace: [ 19.424091] <TASK> [ 19.425448] dump_stack_lvl+0x5d/0x80 [ 19.426963] ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.428694] print_report+0x19d/0x52e [ 19.430206] ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [ 19.431837] ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.433539] kasan_report+0xf0/0x170 [ 19.435019] ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.436709] _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.438379] ? __pfx_sched_clock_cpu+0x10/0x10 [ 19.439910] isst_if_cpu_online+0x406/0x58f [isst_if_common] [ 19.441573] ? __pfx_isst_if_cpu_online+0x10/0x10 [isst_if_common] [ 19.443263] ? ttwu_queue_wakelist+0x2c1/0x360 [ 19.444797] cpuhp_invoke_callback+0x221/0xec0 [ 19.446337] cpuhp_thread_fun+0x21b/0x610 [ 19.447814] ? __pfx_cpuhp_thread_fun+0x10/0x10 [ 19.449354] smpboot_thread_fn+0x2e7/0x6e0 [ 19.450859] ? __pfx_smpboot_thread_fn+0x10/0x10 [ 19.452405] kthread+0x29c/0x350 [ 19.453817] ? __pfx_kthread+0x10/0x10 [ 19.455253] ret_from_fork+0x31/0x70 [ 19.456685] ? __pfx_kthread+0x10/0x10 [ 19.458114] ret_from_fork_asm+0x1a/0x30 [ 19.459573] </TASK> [ 19.460853] [ 19.462055] Allocated by task 1198: [ 19.463410] kasan_save_stack+0x30/0x50 [ 19.464788] kasan_save_track+0x14/0x30 [ 19.466139] __kasan_kmalloc+0xaa/0xb0 [ 19.467465] __kmalloc+0x1cd/0x470 [ 19.468748] isst_if_cdev_register+0x1da/0x350 [isst_if_common] [ 19.470233] isst_if_mbox_init+0x108/0xff0 [isst_if_mbox_msr] [ 19.471670] do_one_initcall+0xa4/0x380 [ 19.472903] do_init_module+0x238/0x760 [ 19.474105] load_module+0x5239/0x6f00 [ 19.475285] init_module_from_file+0xd1/0x130 [ 19.476506] idempotent_init_module+0x23b/0x650 [ 19.477725] __x64_sys_finit_module+0xbe/0x130 [ 19.476506] idempotent_init_module+0x23b/0x650 [ 19.477725] __x64_sys_finit_module+0xbe/0x130 [ 19.478920] do_syscall_64+0x82/0x160 [ 19.480036] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 19.481292] [ 19.482205] The buggy address belongs to the object at ffff888829e65000 which belongs to the cache kmalloc-512 of size 512 [ 19.484818] The buggy address is located 0 bytes to the right of allocated 512-byte region [ffff888829e65000, ffff888829e65200) [ 19.487447] [ 19.488328] The buggy address belongs to the physical page: [ 19.489569] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff888829e60c00 pfn:0x829e60 [ 19.491140] head: order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0 [ 19.492466] anon flags: 0x57ffffc0000840(slab|head|node=1|zone=2|lastcpupid=0x1fffff) [ 19.493914] page_type: 0xffffffff() [ 19.494988] raw: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [ 19.496451] raw: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [ 19.497906] head: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [ 19.499379] head: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [ 19.500844] head: 0057ffffc0000003 ffffea0020a79801 ffffea0020a79848 00000000ffffffff [ 19.502316] head: 0000000800000000 0000000000000000 00000000ffffffff 0000000000000000 [ 19.503784] page dumped because: k ---truncated---(CVE-2024-49886)
In the Linux kernel, the following vulnerability has been resolved: ext4: avoid use-after-free in ext4_ext_show_leaf() In ext4_find_extent(), path may be freed by error or be reallocated, so using a previously saved ppath may have been freed and thus may trigger use-after-free, as follows: ext4_split_extent path = ppath; ext4_split_extent_at(ppath) path = ext4_find_extent(ppath) ext4_split_extent_at(ppath) // ext4_find_extent fails to free path // but zeroout succeeds ext4_ext_show_leaf(inode, path) eh = path[depth].p_hdr // path use-after-free !!! Similar to ext4_split_extent_at(), we use ppath directly as an input to ext4_ext_show_leaf(). Fix a spelling error by the way. Same problem in ext4_ext_handle_unwritten_extents(). Since 'path' is only used in ext4_ext_show_leaf(), remove 'path' and use ppath directly. This issue is triggered only when EXT_DEBUG is defined and therefore does not affect functionality.(CVE-2024-49889)
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add null check for top_pipe_to_program in commit_planes_for_stream This commit addresses a null pointer dereference issue in the commit_planes_for_stream function at line 4140. The issue could occur when top_pipe_to_program is null. The fix adds a check to ensure top_pipe_to_program is not null before accessing its stream_res. This prevents a null pointer dereference. Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.c:4140 commit_planes_for_stream() error: we previously assumed 'top_pipe_to_program' could be null (see line 3906)(CVE-2024-49913)
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add NULL check for clk_mgr and clk_mgr->funcs in dcn30_init_hw This commit addresses a potential null pointer dereference issue in the dcn30_init_hw function. The issue could occur when dc->clk_mgr or dc->clk_mgr->funcs is null. The fix adds a check to ensure dc->clk_mgr and dc->clk_mgr->funcs is not null before accessing its functions. This prevents a potential null pointer dereference. Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c:789 dcn30_init_hw() error: we previously assumed 'dc->clk_mgr' could be null (see line 628)(CVE-2024-49917)
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check null pointers before using them [WHAT & HOW] These pointers are null checked previously in the same function, indicating they might be null as reported by Coverity. As a result, they need to be checked when used again. This fixes 3 FORWARD_NULL issue reported by Coverity.(CVE-2024-49922)
In the Linux kernel, the following vulnerability has been resolved: fbdev: pxafb: Fix possible use after free in pxafb_task() In the pxafb_probe function, it calls the pxafb_init_fbinfo function, after which &fbi->task is associated with pxafb_task. Moreover, within this pxafb_init_fbinfo function, the pxafb_blank function within the &pxafb_ops struct is capable of scheduling work. If we remove the module which will call pxafb_remove to make cleanup, it will call unregister_framebuffer function which can call do_unregister_framebuffer to free fbi->fb through put_fb_info(fb_info), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows: CPU0 CPU1 | pxafb_task pxafb_remove | unregister_framebuffer(info) | do_unregister_framebuffer(fb_info) | put_fb_info(fb_info) | // free fbi->fb | set_ctrlr_state(fbi, state) | __pxafb_lcd_power(fbi, 0) | fbi->lcd_power(on, &fbi->fb.var) | //use fbi->fb Fix it by ensuring that the work is canceled before proceeding with the cleanup in pxafb_remove. Note that only root user can remove the driver at runtime.(CVE-2024-49924)
In the Linux kernel, the following vulnerability has been resolved: blk_iocost: fix more out of bound shifts Recently running UBSAN caught few out of bound shifts in the ioc_forgive_debts() function: UBSAN: shift-out-of-bounds in block/blk-iocost.c:2142:38 shift exponent 80 is too large for 64-bit type 'u64' (aka 'unsigned long long') ... UBSAN: shift-out-of-bounds in block/blk-iocost.c:2144:30 shift exponent 80 is too large for 64-bit type 'u64' (aka 'unsigned long long') ... Call Trace: <IRQ> dump_stack_lvl+0xca/0x130 __ubsan_handle_shift_out_of_bounds+0x22c/0x280 ? __lock_acquire+0x6441/0x7c10 ioc_timer_fn+0x6cec/0x7750 ? blk_iocost_init+0x720/0x720 ? call_timer_fn+0x5d/0x470 call_timer_fn+0xfa/0x470 ? blk_iocost_init+0x720/0x720 __run_timer_base+0x519/0x700 ... Actual impact of this issue was not identified but I propose to fix the undefined behaviour. The proposed fix to prevent those out of bound shifts consist of precalculating exponent before using it the shift operations by taking min value from the actual exponent and maximum possible number of bits.(CVE-2024-49933)
In the Linux kernel, the following vulnerability has been resolved: fs/inode: Prevent dump_mapping() accessing invalid dentry.d_name.name It's observed that a crash occurs during hot-remove a memory device, in which user is accessing the hugetlb. See calltrace as following: ------------[ cut here ]------------ WARNING: CPU: 1 PID: 14045 at arch/x86/mm/fault.c:1278 do_user_addr_fault+0x2a0/0x790 Modules linked in: kmem device_dax cxl_mem cxl_pmem cxl_port cxl_pci dax_hmem dax_pmem nd_pmem cxl_acpi nd_btt cxl_core crc32c_intel nvme virtiofs fuse nvme_core nfit libnvdimm dm_multipath scsi_dh_rdac scsi_dh_emc s mirror dm_region_hash dm_log dm_mod CPU: 1 PID: 14045 Comm: daxctl Not tainted 6.10.0-rc2-lizhijian+ #492 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:do_user_addr_fault+0x2a0/0x790 Code: 48 8b 00 a8 04 0f 84 b5 fe ff ff e9 1c ff ff ff 4c 89 e9 4c 89 e2 be 01 00 00 00 bf 02 00 00 00 e8 b5 ef 24 00 e9 42 fe ff ff <0f> 0b 48 83 c4 08 4c 89 ea 48 89 ee 4c 89 e7 5b 5d 41 5c 41 5d 41 RSP: 0000:ffffc90000a575f0 EFLAGS: 00010046 RAX: ffff88800c303600 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000001000 RSI: ffffffff82504162 RDI: ffffffff824b2c36 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffffc90000a57658 R13: 0000000000001000 R14: ffff88800bc2e040 R15: 0000000000000000 FS: 00007f51cb57d880(0000) GS:ffff88807fd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000001000 CR3: 00000000072e2004 CR4: 00000000001706f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ? __warn+0x8d/0x190 ? do_user_addr_fault+0x2a0/0x790 ? report_bug+0x1c3/0x1d0 ? handle_bug+0x3c/0x70 ? exc_invalid_op+0x14/0x70 ? asm_exc_invalid_op+0x16/0x20 ? do_user_addr_fault+0x2a0/0x790 ? exc_page_fault+0x31/0x200 exc_page_fault+0x68/0x200 <...snip...> BUG: unable to handle page fault for address: 0000000000001000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0 Oops: Oops: 0000 [#1] PREEMPT SMP PTI ---[ end trace 0000000000000000 ]--- BUG: unable to handle page fault for address: 0000000000001000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0 Oops: Oops: 0000 [#1] PREEMPT SMP PTI CPU: 1 PID: 14045 Comm: daxctl Kdump: loaded Tainted: G W 6.10.0-rc2-lizhijian+ #492 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:dentry_name+0x1f4/0x440 <...snip...> ? dentry_name+0x2fa/0x440 vsnprintf+0x1f3/0x4f0 vprintk_store+0x23a/0x540 vprintk_emit+0x6d/0x330 _printk+0x58/0x80 dump_mapping+0x10b/0x1a0 ? __pfx_free_object_rcu+0x10/0x10 __dump_page+0x26b/0x3e0 ? vprintk_emit+0xe0/0x330 ? _printk+0x58/0x80 ? dump_page+0x17/0x50 dump_page+0x17/0x50 do_migrate_range+0x2f7/0x7f0 ? do_migrate_range+0x42/0x7f0 ? offline_pages+0x2f4/0x8c0 offline_pages+0x60a/0x8c0 memory_subsys_offline+0x9f/0x1c0 ? lockdep_hardirqs_on+0x77/0x100 ? _raw_spin_unlock_irqrestore+0x38/0x60 device_offline+0xe3/0x110 state_store+0x6e/0xc0 kernfs_fop_write_iter+0x143/0x200 vfs_write+0x39f/0x560 ksys_write+0x65/0xf0 do_syscall_64+0x62/0x130 Previously, some sanity check have been done in dump_mapping() before the print facility parsing '%pd' though, it's still possible to run into an invalid dentry.d_name.name. Since dump_mapping() only needs to dump the filename only, retrieve it by itself in a safer way to prevent an unnecessary crash. Note that either retrieving the filename with '%pd' or strncpy_from_kernel_nofault(), the filename could be unreliable.(CVE-2024-49934)
In the Linux kernel, the following vulnerability has been resolved: net/xen-netback: prevent UAF in xenvif_flush_hash() During the list_for_each_entry_rcu iteration call of xenvif_flush_hash, kfree_rcu does not exist inside the rcu read critical section, so if kfree_rcu is called when the rcu grace period ends during the iteration, UAF occurs when accessing head->next after the entry becomes free. Therefore, to solve this, you need to change it to list_for_each_entry_safe.(CVE-2024-49936)
In the Linux kernel, the following vulnerability has been resolved: l2tp: prevent possible tunnel refcount underflow When a session is created, it sets a backpointer to its tunnel. When the session refcount drops to 0, l2tp_session_free drops the tunnel refcount if session->tunnel is non-NULL. However, session->tunnel is set in l2tp_session_create, before the tunnel refcount is incremented by l2tp_session_register, which leaves a small window where session->tunnel is non-NULL when the tunnel refcount hasn't been bumped. Moving the assignment to l2tp_session_register is trivial but l2tp_session_create calls l2tp_session_set_header_len which uses session->tunnel to get the tunnel's encap. Add an encap arg to l2tp_session_set_header_len to avoid using session->tunnel. If l2tpv3 sessions have colliding IDs, it is possible for l2tp_v3_session_get to race with l2tp_session_register and fetch a session which doesn't yet have session->tunnel set. Add a check for this case.(CVE-2024-49940)
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix uaf in l2cap_connect [Syzbot reported] BUG: KASAN: slab-use-after-free in l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949 Read of size 8 at addr ffff8880241e9800 by task kworker/u9:0/54 CPU: 0 UID: 0 PID: 54 Comm: kworker/u9:0 Not tainted 6.11.0-rc6-syzkaller-00268-g788220eee30d #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 Workqueue: hci2 hci_rx_work Call Trace: <TASK> __dump_stack lib/dump_stack.c:93 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:119 print_address_description mm/kasan/report.c:377 [inline] print_report+0xc3/0x620 mm/kasan/report.c:488 kasan_report+0xd9/0x110 mm/kasan/report.c:601 l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949 l2cap_connect_req net/bluetooth/l2cap_core.c:4080 [inline] l2cap_bredr_sig_cmd net/bluetooth/l2cap_core.c:4772 [inline] l2cap_sig_channel net/bluetooth/l2cap_core.c:5543 [inline] l2cap_recv_frame+0xf0b/0x8eb0 net/bluetooth/l2cap_core.c:6825 l2cap_recv_acldata+0x9b4/0xb70 net/bluetooth/l2cap_core.c:7514 hci_acldata_packet net/bluetooth/hci_core.c:3791 [inline] hci_rx_work+0xaab/0x1610 net/bluetooth/hci_core.c:4028 process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231 process_scheduled_works kernel/workqueue.c:3312 [inline] worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389 kthread+0x2c1/0x3a0 kernel/kthread.c:389 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 ... Freed by task 5245: kasan_save_stack+0x33/0x60 mm/kasan/common.c:47 kasan_save_track+0x14/0x30 mm/kasan/common.c:68 kasan_save_free_info+0x3b/0x60 mm/kasan/generic.c:579 poison_slab_object+0xf7/0x160 mm/kasan/common.c:240 __kasan_slab_free+0x32/0x50 mm/kasan/common.c:256 kasan_slab_free include/linux/kasan.h:184 [inline] slab_free_hook mm/slub.c:2256 [inline] slab_free mm/slub.c:4477 [inline] kfree+0x12a/0x3b0 mm/slub.c:4598 l2cap_conn_free net/bluetooth/l2cap_core.c:1810 [inline] kref_put include/linux/kref.h:65 [inline] l2cap_conn_put net/bluetooth/l2cap_core.c:1822 [inline] l2cap_conn_del+0x59d/0x730 net/bluetooth/l2cap_core.c:1802 l2cap_connect_cfm+0x9e6/0xf80 net/bluetooth/l2cap_core.c:7241 hci_connect_cfm include/net/bluetooth/hci_core.h:1960 [inline] hci_conn_failed+0x1c3/0x370 net/bluetooth/hci_conn.c:1265 hci_abort_conn_sync+0x75a/0xb50 net/bluetooth/hci_sync.c:5583 abort_conn_sync+0x197/0x360 net/bluetooth/hci_conn.c:2917 hci_cmd_sync_work+0x1a4/0x410 net/bluetooth/hci_sync.c:328 process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231 process_scheduled_works kernel/workqueue.c:3312 [inline] worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389 kthread+0x2c1/0x3a0 kernel/kthread.c:389 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244(CVE-2024-49950)
In the Linux kernel, the following vulnerability has been resolved: static_call: Replace pointless WARN_ON() in static_call_module_notify() static_call_module_notify() triggers a WARN_ON(), when memory allocation fails in __static_call_add_module(). That's not really justified, because the failure case must be correctly handled by the well known call chain and the error code is passed through to the initiating userspace application. A memory allocation fail is not a fatal problem, but the WARN_ON() takes the machine out when panic_on_warn is set. Replace it with a pr_warn().(CVE-2024-49954)
In the Linux kernel, the following vulnerability has been resolved: ACPI: battery: Fix possible crash when unregistering a battery hook When a battery hook returns an error when adding a new battery, then the battery hook is automatically unregistered. However the battery hook provider cannot know that, so it will later call battery_hook_unregister() on the already unregistered battery hook, resulting in a crash. Fix this by using the list head to mark already unregistered battery hooks as already being unregistered so that they can be ignored by battery_hook_unregister().(CVE-2024-49955)
In the Linux kernel, the following vulnerability has been resolved: ocfs2: reserve space for inline xattr before attaching reflink tree One of our customers reported a crash and a corrupted ocfs2 filesystem. The crash was due to the detection of corruption. Upon troubleshooting, the fsck -fn output showed the below corruption [EXTENT_LIST_FREE] Extent list in owner 33080590 claims 230 as the next free chain record, but fsck believes the largest valid value is 227. Clamp the next record value? n The stat output from the debugfs.ocfs2 showed the following corruption where the "Next Free Rec:" had overshot the "Count:" in the root metadata block. Inode: 33080590 Mode: 0640 Generation: 2619713622 (0x9c25a856) FS Generation: 904309833 (0x35e6ac49) CRC32: 00000000 ECC: 0000 Type: Regular Attr: 0x0 Flags: Valid Dynamic Features: (0x16) HasXattr InlineXattr Refcounted Extended Attributes Block: 0 Extended Attributes Inline Size: 256 User: 0 (root) Group: 0 (root) Size: 281320357888 Links: 1 Clusters: 141738 ctime: 0x66911b56 0x316edcb8 -- Fri Jul 12 06:02:30.829349048 2024 atime: 0x66911d6b 0x7f7a28d -- Fri Jul 12 06:11:23.133669517 2024 mtime: 0x66911b56 0x12ed75d7 -- Fri Jul 12 06:02:30.317552087 2024 dtime: 0x0 -- Wed Dec 31 17:00:00 1969 Refcount Block: 2777346 Last Extblk: 2886943 Orphan Slot: 0 Sub Alloc Slot: 0 Sub Alloc Bit: 14 Tree Depth: 1 Count: 227 Next Free Rec: 230 ## Offset Clusters Block# 0 0 2310 2776351 1 2310 2139 2777375 2 4449 1221 2778399 3 5670 731 2779423 4 6401 566 2780447 ....... .... ....... ....... .... ....... The issue was in the reflink workfow while reserving space for inline xattr. The problematic function is ocfs2_reflink_xattr_inline(). By the time this function is called the reflink tree is already recreated at the destination inode from the source inode. At this point, this function reserves space for inline xattrs at the destination inode without even checking if there is space at the root metadata block. It simply reduces the l_count from 243 to 227 thereby making space of 256 bytes for inline xattr whereas the inode already has extents beyond this index (in this case up to 230), thereby causing corruption. The fix for this is to reserve space for inline metadata at the destination inode before the reflink tree gets recreated. The customer has verified the fix.(CVE-2024-49958)
In the Linux kernel, the following vulnerability has been resolved: ocfs2: remove unreasonable unlock in ocfs2_read_blocks Patch series "Misc fixes for ocfs2_read_blocks", v5. This series contains 2 fixes for ocfs2_read_blocks(). The first patch fix the issue reported by syzbot, which detects bad unlock balance in ocfs2_read_blocks(). The second patch fixes an issue reported by Heming Zhao when reviewing above fix. This patch (of 2): There was a lock release before exiting, so remove the unreasonable unlock.(CVE-2024-49965)
In the Linux kernel, the following vulnerability has been resolved: r8169: add tally counter fields added with RTL8125 RTL8125 added fields to the tally counter, what may result in the chip dma'ing these new fields to unallocated memory. Therefore make sure that the allocated memory area is big enough to hold all of the tally counter values, even if we use only parts of it.(CVE-2024-49973)
In the Linux kernel, the following vulnerability has been resolved: uprobes: fix kernel info leak via "[uprobes]" vma xol_add_vma() maps the uninitialized page allocated by __create_xol_area() into userspace. On some architectures (x86) this memory is readable even without VM_READ, VM_EXEC results in the same pgprot_t as VM_EXEC|VM_READ, although this doesn't really matter, debugger can read this memory anyway.(CVE-2024-49975)
In the Linux kernel, the following vulnerability has been resolved: gso: fix udp gso fraglist segmentation after pull from frag_list Detect gso fraglist skbs with corrupted geometry (see below) and pass these to skb_segment instead of skb_segment_list, as the first can segment them correctly. Valid SKB_GSO_FRAGLIST skbs - consist of two or more segments - the head_skb holds the protocol headers plus first gso_size - one or more frag_list skbs hold exactly one segment - all but the last must be gso_size Optional datapath hooks such as NAT and BPF (bpf_skb_pull_data) can modify these skbs, breaking these invariants. In extreme cases they pull all data into skb linear. For UDP, this causes a NULL ptr deref in __udpv4_gso_segment_list_csum at udp_hdr(seg->next)->dest. Detect invalid geometry due to pull, by checking head_skb size. Don't just drop, as this may blackhole a destination. Convert to be able to pass to regular skb_segment.(CVE-2024-49978)
In the Linux kernel, the following vulnerability has been resolved: media: venus: fix use after free bug in venus_remove due to race condition in venus_probe, core->work is bound with venus_sys_error_handler, which is used to handle error. The code use core->sys_err_done to make sync work. The core->work is started in venus_event_notify. If we call venus_remove, there might be an unfished work. The possible sequence is as follows: CPU0 CPU1 |venus_sys_error_handler venus_remove | hfi_destroy | venus_hfi_destroy | kfree(hdev); | |hfi_reinit |venus_hfi_queues_reinit |//use hdev Fix it by canceling the work in venus_remove.(CVE-2024-49981)
In the Linux kernel, the following vulnerability has been resolved: drm/stm: Avoid use-after-free issues with crtc and plane ltdc_load() calls functions drm_crtc_init_with_planes(), drm_universal_plane_init() and drm_encoder_init(). These functions should not be called with parameters allocated with devm_kzalloc() to avoid use-after-free issues [1]. Use allocations managed by the DRM framework. Found by Linux Verification Center (linuxtesting.org). [1] https://lore.kernel.org/lkml/u366i76e3qhh3ra5oxrtngjtm2u5lterkekcz6y2jkndhuxzli@diujon4h7qwb/(CVE-2024-49992)
In the Linux kernel, the following vulnerability has been resolved: tipc: guard against string buffer overrun Smatch reports that copying media_name and if_name to name_parts may overwrite the destination. .../bearer.c:166 bearer_name_validate() error: strcpy() 'media_name' too large for 'name_parts->media_name' (32 vs 16) .../bearer.c:167 bearer_name_validate() error: strcpy() 'if_name' too large for 'name_parts->if_name' (1010102 vs 16) This does seem to be the case so guard against this possibility by using strscpy() and failing if truncation occurs. Introduced by commit b97bf3fd8f6a ("[TIPC] Initial merge") Compile tested only.(CVE-2024-49995)
In the Linux kernel, the following vulnerability has been resolved: cifs: Fix buffer overflow when parsing NFS reparse points ReparseDataLength is sum of the InodeType size and DataBuffer size. So to get DataBuffer size it is needed to subtract InodeType's size from ReparseDataLength. Function cifs_strndup_from_utf16() is currentlly accessing buf->DataBuffer at position after the end of the buffer because it does not subtract InodeType size from the length. Fix this problem and correctly subtract variable len. Member InodeType is present only when reparse buffer is large enough. Check for ReparseDataLength before accessing InodeType to prevent another invalid memory access. Major and minor rdev values are present also only when reparse buffer is large enough. Check for reparse buffer size before calling reparse_mkdev().(CVE-2024-49996)
In the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_cmd_802_11_scan_ext() Replace one-element array with a flexible-array member in struct host_cmd_ds_802_11_scan_ext. With this, fix the following warning: elo 16 17:51:58 surfacebook kernel: ------------[ cut here ]------------ elo 16 17:51:58 surfacebook kernel: memcpy: detected field-spanning write (size 243) of single field "ext_scan->tlv_buffer" at drivers/net/wireless/marvell/mwifiex/scan.c:2239 (size 1) elo 16 17:51:58 surfacebook kernel: WARNING: CPU: 0 PID: 498 at drivers/net/wireless/marvell/mwifiex/scan.c:2239 mwifiex_cmd_802_11_scan_ext+0x83/0x90 mwifiex
In the Linux kernel, the following vulnerability has been resolved: ext4: dax: fix overflowing extents beyond inode size when partially writing The dax_iomap_rw() does two things in each iteration: map written blocks and copy user data to blocks. If the process is killed by user(See signal handling in dax_iomap_iter()), the copied data will be returned and added on inode size, which means that the length of written extents may exceed the inode size, then fsck will fail. An example is given as: dd if=/dev/urandom of=file bs=4M count=1 dax_iomap_rw iomap_iter // round 1 ext4_iomap_begin ext4_iomap_alloc // allocate 0~2M extents(written flag) dax_iomap_iter // copy 2M data iomap_iter // round 2 iomap_iter_advance iter->pos += iter->processed // iter->pos = 2M ext4_iomap_begin ext4_iomap_alloc // allocate 2~4M extents(written flag) dax_iomap_iter fatal_signal_pending done = iter->pos - iocb->ki_pos // done = 2M ext4_handle_inode_extension ext4_update_inode_size // inode size = 2M fsck reports: Inode 13, i_size is 2097152, should be 4194304. Fix? Fix the problem by truncating extents if the written length is smaller than expected.(CVE-2024-50015)
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Avoid overflow assignment in link_dp_cts sampling_rate is an uint8_t but is assigned an unsigned int, and thus it can overflow. As a result, sampling_rate is changed to uint32_t. Similarly, LINK_QUAL_PATTERN_SET has a size of 2 bits, and it should only be assigned to a value less or equal than 4. This fixes 2 INTEGER_OVERFLOW issues reported by Coverity.(CVE-2024-50016)
In the Linux kernel, the following vulnerability has been resolved: thermal: core: Reference count the zone in thermal_zone_get_by_id() There are places in the thermal netlink code where nothing prevents the thermal zone object from going away while being accessed after it has been returned by thermal_zone_get_by_id(). To address this, make thermal_zone_get_by_id() get a reference on the thermal zone device object to be returned with the help of get_device(), under thermal_list_lock, and adjust all of its callers to this change with the help of the cleanup.h infrastructure.(CVE-2024-50028)
In the Linux kernel, the following vulnerability has been resolved: slip: make slhc_remember() more robust against malicious packets syzbot found that slhc_remember() was missing checks against malicious packets [1]. slhc_remember() only checked the size of the packet was at least 20, which is not good enough. We need to make sure the packet includes the IPv4 and TCP header that are supposed to be carried. Add iph and th pointers to make the code more readable. [1] BUG: KMSAN: uninit-value in slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666 slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666 ppp_receive_nonmp_frame+0xe45/0x35e0 drivers/net/ppp/ppp_generic.c:2455 ppp_receive_frame drivers/net/ppp/ppp_generic.c:2372 [inline] ppp_do_recv+0x65f/0x40d0 drivers/net/ppp/ppp_generic.c:2212 ppp_input+0x7dc/0xe60 drivers/net/ppp/ppp_generic.c:2327 pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379 sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113 __release_sock+0x1da/0x330 net/core/sock.c:3072 release_sock+0x6b/0x250 net/core/sock.c:3626 pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 _syssendmsg+0x903/0xb60 net/socket.c:2602 _sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was created at: slab_post_alloc_hook mm/slub.c:4091 [inline] slab_alloc_node mm/slub.c:4134 [inline] kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4186 kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587 __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678 alloc_skb include/linux/skbuff.h:1322 [inline] sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732 pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 _syssendmsg+0x903/0xb60 net/socket.c:2602 _sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f CPU: 0 UID: 0 PID: 5460 Comm: syz.2.33 Not tainted 6.12.0-rc2-syzkaller-00006-g87d6aab2389e #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50033)
In the Linux kernel, the following vulnerability has been resolved: ppp: fix ppp_async_encode() illegal access syzbot reported an issue in ppp_async_encode() [1] In this case, pppoe_sendmsg() is called with a zero size. Then ppp_async_encode() is called with an empty skb. BUG: KMSAN: uninit-value in ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline] BUG: KMSAN: uninit-value in ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675 ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline] ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675 ppp_async_send+0x130/0x1b0 drivers/net/ppp/ppp_async.c:634 ppp_channel_bridge_input drivers/net/ppp/ppp_generic.c:2280 [inline] ppp_input+0x1f1/0xe60 drivers/net/ppp/ppp_generic.c:2304 pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379 sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113 __release_sock+0x1da/0x330 net/core/sock.c:3072 release_sock+0x6b/0x250 net/core/sock.c:3626 pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 _syssendmsg+0x903/0xb60 net/socket.c:2602 _sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was created at: slab_post_alloc_hook mm/slub.c:4092 [inline] slab_alloc_node mm/slub.c:4135 [inline] kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4187 kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587 __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678 alloc_skb include/linux/skbuff.h:1322 [inline] sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732 pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 _syssendmsg+0x903/0xb60 net/socket.c:2602 _sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f CPU: 1 UID: 0 PID: 5411 Comm: syz.1.14 Not tainted 6.12.0-rc1-syzkaller-00165-g360c1f1f24c6 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50035)
In the Linux kernel, the following vulnerability has been resolved: NFSv4: Prevent NULL-pointer dereference in nfs42_complete_copies() On the node of an NFS client, some files saved in the mountpoint of the NFS server were copied to another location of the same NFS server. Accidentally, the nfs42_complete_copies() got a NULL-pointer dereference crash with the following syslog: [232064.838881] NFSv4: state recovery failed for open file nfs/pvc-12b5200d-cd0f-46a3-b9f0-af8f4fe0ef64.qcow2, error = -116 [232064.839360] NFSv4: state recovery failed for open file nfs/pvc-12b5200d-cd0f-46a3-b9f0-af8f4fe0ef64.qcow2, error = -116 [232066.588183] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000058 [232066.588586] Mem abort info: [232066.588701] ESR = 0x0000000096000007 [232066.588862] EC = 0x25: DABT (current EL), IL = 32 bits [232066.589084] SET = 0, FnV = 0 [232066.589216] EA = 0, S1PTW = 0 [232066.589340] FSC = 0x07: level 3 translation fault [232066.589559] Data abort info: [232066.589683] ISV = 0, ISS = 0x00000007 [232066.589842] CM = 0, WnR = 0 [232066.589967] user pgtable: 64k pages, 48-bit VAs, pgdp=00002000956ff400 [232066.590231] [0000000000000058] pgd=08001100ae100003, p4d=08001100ae100003, pud=08001100ae100003, pmd=08001100b3c00003, pte=0000000000000000 [232066.590757] Internal error: Oops: 96000007 [#1] SMP [232066.590958] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace fscache netfs ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm vhost_net vhost vhost_iotlb tap tun ipt_rpfilter xt_multiport ip_set_hash_ip ip_set_hash_net xfrm_interface xfrm6_tunnel tunnel4 tunnel6 esp4 ah4 wireguard libcurve25519_generic veth xt_addrtype xt_set nf_conntrack_netlink ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_bitmap_port ip_set_hash_ipport dummy ip_set ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs iptable_filter sch_ingress nfnetlink_cttimeout vport_gre ip_gre ip_tunnel gre vport_geneve geneve vport_vxlan vxlan ip6_udp_tunnel udp_tunnel openvswitch nf_conncount dm_round_robin dm_service_time dm_multipath xt_nat xt_MASQUERADE nft_chain_nat nf_nat xt_mark xt_conntrack xt_comment nft_compat nft_counter nf_tables nfnetlink ocfs2 ocfs2_nodemanager ocfs2_stackglue iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ipmi_ssif nbd overlay 8021q garp mrp bonding tls rfkill sunrpc ext4 mbcache jbd2 [232066.591052] vfat fat cas_cache cas_disk ses enclosure scsi_transport_sas sg acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler ip_tables vfio_pci vfio_pci_core vfio_virqfd vfio_iommu_type1 vfio dm_mirror dm_region_hash dm_log dm_mod nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter bridge stp llc fuse xfs libcrc32c ast drm_vram_helper qla2xxx drm_kms_helper syscopyarea crct10dif_ce sysfillrect ghash_ce sysimgblt sha2_ce fb_sys_fops cec sha256_arm64 sha1_ce drm_ttm_helper ttm nvme_fc igb sbsa_gwdt nvme_fabrics drm nvme_core i2c_algo_bit i40e scsi_transport_fc megaraid_sas aes_neon_bs [232066.596953] CPU: 6 PID: 4124696 Comm: 10.253.166.125- Kdump: loaded Not tainted 5.15.131-9.cl9_ocfs2.aarch64 #1 [232066.597356] Hardware name: Great Wall .\x93\x8e...RF6260 V5/GWMSSE2GL1T, BIOS T656FBE_V3.0.18 2024-01-06 [232066.597721] pstate: 20400009 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [232066.598034] pc : nfs4_reclaim_open_state+0x220/0x800 [nfsv4] [232066.598327] lr : nfs4_reclaim_open_state+0x12c/0x800 [nfsv4] [232066.598595] sp : ffff8000f568fc70 [232066.598731] x29: ffff8000f568fc70 x28: 0000000000001000 x27: ffff21003db33000 [232066.599030] x26: ffff800005521ae0 x25: ffff0100f98fa3f0 x24: 0000000000000001 [232066.599319] x23: ffff800009920008 x22: ffff21003db33040 x21: ffff21003db33050 [232066.599628] x20: ffff410172fe9e40 x19: ffff410172fe9e00 x18: 0000000000000000 [232066.599914] x17: 0000000000000000 x16: 0000000000000004 x15: 0000000000000000 [232066.600195] x14: 0000000000000000 x13: ffff800008e685a8 x12: 00000000eac0c6e6 [232066.600498] x11: 00000000000000 ---truncated---(CVE-2024-50046)
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix UAF in async decryption Doing an async decryption (large read) crashes with a slab-use-after-free way down in the crypto API. Reproducer: # mount.cifs -o ...,seal,esize=1 //srv/share /mnt # dd if=/mnt/largefile of=/dev/null ... [ 194.196391] ================================================================== [ 194.196844] BUG: KASAN: slab-use-after-free in gf128mul_4k_lle+0xc1/0x110 [ 194.197269] Read of size 8 at addr ffff888112bd0448 by task kworker/u77:2/899 [ 194.197707] [ 194.197818] CPU: 12 UID: 0 PID: 899 Comm: kworker/u77:2 Not tainted 6.11.0-lku-00028-gfca3ca14a17a-dirty #43 [ 194.198400] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.2-3-gd478f380-prebuilt.qemu.org 04/01/2014 [ 194.199046] Workqueue: smb3decryptd smb2_decrypt_offload [cifs] [ 194.200032] Call Trace: [ 194.200191] <TASK> [ 194.200327] dump_stack_lvl+0x4e/0x70 [ 194.200558] ? gf128mul_4k_lle+0xc1/0x110 [ 194.200809] print_report+0x174/0x505 [ 194.201040] ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [ 194.201352] ? srso_return_thunk+0x5/0x5f [ 194.201604] ? __virt_addr_valid+0xdf/0x1c0 [ 194.201868] ? gf128mul_4k_lle+0xc1/0x110 [ 194.202128] kasan_report+0xc8/0x150 [ 194.202361] ? gf128mul_4k_lle+0xc1/0x110 [ 194.202616] gf128mul_4k_lle+0xc1/0x110 [ 194.202863] ghash_update+0x184/0x210 [ 194.203103] shash_ahash_update+0x184/0x2a0 [ 194.203377] ? __pfx_shash_ahash_update+0x10/0x10 [ 194.203651] ? srso_return_thunk+0x5/0x5f [ 194.203877] ? crypto_gcm_init_common+0x1ba/0x340 [ 194.204142] gcm_hash_assoc_remain_continue+0x10a/0x140 [ 194.204434] crypt_message+0xec1/0x10a0 [cifs] [ 194.206489] ? __pfx_crypt_message+0x10/0x10 [cifs] [ 194.208507] ? srso_return_thunk+0x5/0x5f [ 194.209205] ? srso_return_thunk+0x5/0x5f [ 194.209925] ? srso_return_thunk+0x5/0x5f [ 194.210443] ? srso_return_thunk+0x5/0x5f [ 194.211037] decrypt_raw_data+0x15f/0x250 [cifs] [ 194.212906] ? __pfx_decrypt_raw_data+0x10/0x10 [cifs] [ 194.214670] ? srso_return_thunk+0x5/0x5f [ 194.215193] smb2_decrypt_offload+0x12a/0x6c0 [cifs] This is because TFM is being used in parallel. Fix this by allocating a new AEAD TFM for async decryption, but keep the existing one for synchronous READ cases (similar to what is done in smb3_calc_signature()). Also remove the calls to aead_request_set_callback() and crypto_wait_req() since it's always going to be a synchronous operation.(CVE-2024-50047)
In the Linux kernel, the following vulnerability has been resolved: serial: protect uart_port_dtr_rts() in uart_shutdown() too Commit af224ca2df29 (serial: core: Prevent unsafe uart port access, part 3) added few uport == NULL checks. It added one to uart_shutdown(), so the commit assumes, uport can be NULL in there. But right after that protection, there is an unprotected "uart_port_dtr_rts(uport, false);" call. That is invoked only if HUPCL is set, so I assume that is the reason why we do not see lots of these reports. Or it cannot be NULL at this point at all for some reason :P. Until the above is investigated, stay on the safe side and move this dereference to the if too. I got this inconsistency from Coverity under CID 1585130. Thanks.(CVE-2024-50058)
In the Linux kernel, the following vulnerability has been resolved: ntb: ntb_hw_switchtec: Fix use after free vulnerability in switchtec_ntb_remove due to race condition In the switchtec_ntb_add function, it can call switchtec_ntb_init_sndev function, then &sndev->check_link_status_work is bound with check_link_status_work. switchtec_ntb_link_notification may be called to start the work. If we remove the module which will call switchtec_ntb_remove to make cleanup, it will free sndev through kfree(sndev), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows: CPU0 CPU1 | check_link_status_work switchtec_ntb_remove | kfree(sndev); | | if (sndev->link_force_down) | // use sndev Fix it by ensuring that the work is canceled before proceeding with the cleanup in switchtec_ntb_remove.(CVE-2024-50059)
In the Linux kernel, the following vulnerability has been resolved: io_uring: check if we need to reschedule during overflow flush In terms of normal application usage, this list will always be empty. And if an application does overflow a bit, it'll have a few entries. However, nothing obviously prevents syzbot from running a test case that generates a ton of overflow entries, and then flushing them can take quite a while. Check for needing to reschedule while flushing, and drop our locks and do so if necessary. There's no state to maintain here as overflows always prune from head-of-list, hence it's fine to drop and reacquire the locks at the end of the loop.(CVE-2024-50060)
In the Linux kernel, the following vulnerability has been resolved: bpf: Prevent tail call between progs attached to different hooks bpf progs can be attached to kernel functions, and the attached functions can take different parameters or return different return values. If prog attached to one kernel function tail calls prog attached to another kernel function, the ctx access or return value verification could be bypassed. For example, if prog1 is attached to func1 which takes only 1 parameter and prog2 is attached to func2 which takes two parameters. Since verifier assumes the bpf ctx passed to prog2 is constructed based on func2's prototype, verifier allows prog2 to access the second parameter from the bpf ctx passed to it. The problem is that verifier does not prevent prog1 from passing its bpf ctx to prog2 via tail call. In this case, the bpf ctx passed to prog2 is constructed from func1 instead of func2, that is, the assumption for ctx access verification is bypassed. Another example, if BPF LSM prog1 is attached to hook file_alloc_security, and BPF LSM prog2 is attached to hook bpf_lsm_audit_rule_known. Verifier knows the return value rules for these two hooks, e.g. it is legal for bpf_lsm_audit_rule_known to return positive number 1, and it is illegal for file_alloc_security to return positive number. So verifier allows prog2 to return positive number 1, but does not allow prog1 to return positive number. The problem is that verifier does not prevent prog1 from calling prog2 via tail call. In this case, prog2's return value 1 will be used as the return value for prog1's hook file_alloc_security. That is, the return value rule is bypassed. This patch adds restriction for tail call to prevent such bypasses.(CVE-2024-50063)
In the Linux kernel, the following vulnerability has been resolved: uprobe: avoid out-of-bounds memory access of fetching args Uprobe needs to fetch args into a percpu buffer, and then copy to ring buffer to avoid non-atomic context problem. Sometimes user-space strings, arrays can be very large, but the size of percpu buffer is only page size. And store_trace_args() won't check whether these data exceeds a single page or not, caused out-of-bounds memory access. It could be reproduced by following steps: 1. build kernel with CONFIG_KASAN enabled 2. save follow program as test.c \#include <stdio.h> \#include <stdlib.h> \#include <string.h> // If string length large than MAX_STRING_SIZE, the fetch_store_strlen() // will return 0, cause __get_data_size() return shorter size, and // store_trace_args() will not trigger out-of-bounds access. // So make string length less than 4096. \#define STRLEN 4093 void generate_string(char *str, int n) { int i; for (i = 0; i < n; ++i) { char c = i % 26 + 'a'; str[i] = c; } str[n-1] = '\0'; } void print_string(char *str) { printf("%s\n", str); } int main() { char tmp[STRLEN]; generate_string(tmp, STRLEN); print_string(tmp); return 0; } 3. compile program gcc -o test test.c 4. get the offset of print_string() objdump -t test | grep -w print_string 0000000000401199 g F .text 000000000000001b print_string 5. configure uprobe with offset 0x1199 off=0x1199 cd /sys/kernel/debug/tracing/ echo "p /root/test:${off} arg1=+0(%di):ustring arg2=\$comm arg3=+0(%di):ustring" > uprobe_events echo 1 > events/uprobes/enable echo 1 > tracing_on 6. run test, and kasan will report error. ================================================================== BUG: KASAN: use-after-free in strncpy_from_user+0x1d6/0x1f0 Write of size 8 at addr ffff88812311c004 by task test/499CPU: 0 UID: 0 PID: 499 Comm: test Not tainted 6.12.0-rc3+ #18 Hardware name: Red Hat KVM, BIOS 1.16.0-4.al8 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x55/0x70 print_address_description.constprop.0+0x27/0x310 kasan_report+0x10f/0x120 ? strncpy_from_user+0x1d6/0x1f0 strncpy_from_user+0x1d6/0x1f0 ? rmqueue.constprop.0+0x70d/0x2ad0 process_fetch_insn+0xb26/0x1470 ? __pfx_process_fetch_insn+0x10/0x10 ? _raw_spin_lock+0x85/0xe0 ? __pfx__raw_spin_lock+0x10/0x10 ? __pte_offset_map+0x1f/0x2d0 ? unwind_next_frame+0xc5f/0x1f80 ? arch_stack_walk+0x68/0xf0 ? is_bpf_text_address+0x23/0x30 ? kernel_text_address.part.0+0xbb/0xd0 ? __kernel_text_address+0x66/0xb0 ? unwind_get_return_address+0x5e/0xa0 ? __pfx_stack_trace_consume_entry+0x10/0x10 ? arch_stack_walk+0xa2/0xf0 ? _raw_spin_lock_irqsave+0x8b/0xf0 ? __pfx__raw_spin_lock_irqsave+0x10/0x10 ? depot_alloc_stack+0x4c/0x1f0 ? _raw_spin_unlock_irqrestore+0xe/0x30 ? stack_depot_save_flags+0x35d/0x4f0 ? kasan_save_stack+0x34/0x50 ? kasan_save_stack+0x24/0x50 ? mutex_lock+0x91/0xe0 ? __pfx_mutex_lock+0x10/0x10 prepare_uprobe_buffer.part.0+0x2cd/0x500 uprobe_dispatcher+0x2c3/0x6a0 ? __pfx_uprobe_dispatcher+0x10/0x10 ? __kasan_slab_alloc+0x4d/0x90 handler_chain+0xdd/0x3e0 handle_swbp+0x26e/0x3d0 ? __pfx_handle_swbp+0x10/0x10 ? uprobe_pre_sstep_notifier+0x151/0x1b0 irqentry_exit_to_user_mode+0xe2/0x1b0 asm_exc_int3+0x39/0x40 RIP: 0033:0x401199 Code: 01 c2 0f b6 45 fb 88 02 83 45 fc 01 8b 45 fc 3b 45 e4 7c b7 8b 45 e4 48 98 48 8d 50 ff 48 8b 45 e8 48 01 d0 ce RSP: 002b:00007ffdf00576a8 EFLAGS: 00000206 RAX: 00007ffdf00576b0 RBX: 0000000000000000 RCX: 0000000000000ff2 RDX: 0000000000000ffc RSI: 0000000000000ffd RDI: 00007ffdf00576b0 RBP: 00007ffdf00586b0 R08: 00007feb2f9c0d20 R09: 00007feb2f9c0d20 R10: 0000000000000001 R11: 0000000000000202 R12: 0000000000401040 R13: 00007ffdf0058780 R14: 0000000000000000 R15: 0000000000000000 </TASK> This commit enforces the buffer's maxlen less than a page-size to avoid store_trace_args() out-of-memory access.(CVE-2024-50067)
In the Linux kernel, the following vulnerability has been resolved: parport: Proper fix for array out-of-bounds access The recent fix for array out-of-bounds accesses replaced sprintf() calls blindly with snprintf(). However, since snprintf() returns the would-be-printed size, not the actually output size, the length calculation can still go over the given limit. Use scnprintf() instead of snprintf(), which returns the actually output letters, for addressing the potential out-of-bounds access properly.(CVE-2024-50074)
In the Linux kernel, the following vulnerability has been resolved: tcp: fix mptcp DSS corruption due to large pmtu xmit Syzkaller was able to trigger a DSS corruption: TCP: request_sock_subflow_v4: Possible SYN flooding on port [::]:20002. Sending cookies. ------------[ cut here ]------------ WARNING: CPU: 0 PID: 5227 at net/mptcp/protocol.c:695 __mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695 Modules linked in: CPU: 0 UID: 0 PID: 5227 Comm: syz-executor350 Not tainted 6.11.0-syzkaller-08829-gaf9c191ac2a0 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 RIP: 0010:__mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695 Code: 0f b6 dc 31 ff 89 de e8 b5 dd ea f5 89 d8 48 81 c4 50 01 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 98 da ea f5 90 <0f> 0b 90 e9 47 ff ff ff e8 8a da ea f5 90 0f 0b 90 e9 99 e0 ff ff RSP: 0018:ffffc90000006db8 EFLAGS: 00010246 RAX: ffffffff8ba9df18 RBX: 00000000000055f0 RCX: ffff888030023c00 RDX: 0000000000000100 RSI: 00000000000081e5 RDI: 00000000000055f0 RBP: 1ffff110062bf1ae R08: ffffffff8ba9cf12 R09: 1ffff110062bf1b8 R10: dffffc0000000000 R11: ffffed10062bf1b9 R12: 0000000000000000 R13: dffffc0000000000 R14: 00000000700cec61 R15: 00000000000081e5 FS: 000055556679c380(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020287000 CR3: 0000000077892000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <IRQ> move_skbs_to_msk net/mptcp/protocol.c:811 [inline] mptcp_data_ready+0x29c/0xa90 net/mptcp/protocol.c:854 subflow_data_ready+0x34a/0x920 net/mptcp/subflow.c:1490 tcp_data_queue+0x20fd/0x76c0 net/ipv4/tcp_input.c:5283 tcp_rcv_established+0xfba/0x2020 net/ipv4/tcp_input.c:6237 tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915 tcp_v4_rcv+0x2dc0/0x37f0 net/ipv4/tcp_ipv4.c:2350 ip_protocol_deliver_rcu+0x22e/0x440 net/ipv4/ip_input.c:205 ip_local_deliver_finish+0x341/0x5f0 net/ipv4/ip_input.c:233 NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314 NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314 __netif_receive_skb_one_core net/core/dev.c:5662 [inline] __netif_receive_skb+0x2bf/0x650 net/core/dev.c:5775 process_backlog+0x662/0x15b0 net/core/dev.c:6107 __napi_poll+0xcb/0x490 net/core/dev.c:6771 napi_poll net/core/dev.c:6840 [inline] net_rx_action+0x89b/0x1240 net/core/dev.c:6962 handle_softirqs+0x2c5/0x980 kernel/softirq.c:554 do_softirq+0x11b/0x1e0 kernel/softirq.c:455 </IRQ> <TASK> __local_bh_enable_ip+0x1bb/0x200 kernel/softirq.c:382 local_bh_enable include/linux/bottom_half.h:33 [inline] rcu_read_unlock_bh include/linux/rcupdate.h:919 [inline] __dev_queue_xmit+0x1764/0x3e80 net/core/dev.c:4451 dev_queue_xmit include/linux/netdevice.h:3094 [inline] neigh_hh_output include/net/neighbour.h:526 [inline] neigh_output include/net/neighbour.h:540 [inline] ip_finish_output2+0xd41/0x1390 net/ipv4/ip_output.c:236 ip_local_out net/ipv4/ip_output.c:130 [inline] __ip_queue_xmit+0x118c/0x1b80 net/ipv4/ip_output.c:536 __tcp_transmit_skb+0x2544/0x3b30 net/ipv4/tcp_output.c:1466 tcp_transmit_skb net/ipv4/tcp_output.c:1484 [inline] tcp_mtu_probe net/ipv4/tcp_output.c:2547 [inline] tcp_write_xmit+0x641d/0x6bf0 net/ipv4/tcp_output.c:2752 __tcp_push_pending_frames+0x9b/0x360 net/ipv4/tcp_output.c:3015 tcp_push_pending_frames include/net/tcp.h:2107 [inline] tcp_data_snd_check net/ipv4/tcp_input.c:5714 [inline] tcp_rcv_established+0x1026/0x2020 net/ipv4/tcp_input.c:6239 tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915 sk_backlog_rcv include/net/sock.h:1113 [inline] __release_sock+0x214/0x350 net/core/sock.c:3072 release_sock+0x61/0x1f0 net/core/sock.c:3626 mptcp_push_ ---truncated---(CVE-2024-50083)
| URL | Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"kernel-5.10.0-136.100.0.181.oe2203sp1.aarch64.rpm",
"kernel-debuginfo-5.10.0-136.100.0.181.oe2203sp1.aarch64.rpm",
"kernel-debugsource-5.10.0-136.100.0.181.oe2203sp1.aarch64.rpm",
"kernel-devel-5.10.0-136.100.0.181.oe2203sp1.aarch64.rpm",
"kernel-headers-5.10.0-136.100.0.181.oe2203sp1.aarch64.rpm",
"kernel-source-5.10.0-136.100.0.181.oe2203sp1.aarch64.rpm",
"kernel-tools-5.10.0-136.100.0.181.oe2203sp1.aarch64.rpm",
"kernel-tools-debuginfo-5.10.0-136.100.0.181.oe2203sp1.aarch64.rpm",
"kernel-tools-devel-5.10.0-136.100.0.181.oe2203sp1.aarch64.rpm",
"perf-5.10.0-136.100.0.181.oe2203sp1.aarch64.rpm",
"perf-debuginfo-5.10.0-136.100.0.181.oe2203sp1.aarch64.rpm",
"python3-perf-5.10.0-136.100.0.181.oe2203sp1.aarch64.rpm",
"python3-perf-debuginfo-5.10.0-136.100.0.181.oe2203sp1.aarch64.rpm"
],
"src": [
"kernel-5.10.0-136.100.0.181.oe2203sp1.src.rpm"
],
"x86_64": [
"kernel-5.10.0-136.100.0.181.oe2203sp1.x86_64.rpm",
"kernel-debuginfo-5.10.0-136.100.0.181.oe2203sp1.x86_64.rpm",
"kernel-debugsource-5.10.0-136.100.0.181.oe2203sp1.x86_64.rpm",
"kernel-devel-5.10.0-136.100.0.181.oe2203sp1.x86_64.rpm",
"kernel-headers-5.10.0-136.100.0.181.oe2203sp1.x86_64.rpm",
"kernel-source-5.10.0-136.100.0.181.oe2203sp1.x86_64.rpm",
"kernel-tools-5.10.0-136.100.0.181.oe2203sp1.x86_64.rpm",
"kernel-tools-debuginfo-5.10.0-136.100.0.181.oe2203sp1.x86_64.rpm",
"kernel-tools-devel-5.10.0-136.100.0.181.oe2203sp1.x86_64.rpm",
"perf-5.10.0-136.100.0.181.oe2203sp1.x86_64.rpm",
"perf-debuginfo-5.10.0-136.100.0.181.oe2203sp1.x86_64.rpm",
"python3-perf-5.10.0-136.100.0.181.oe2203sp1.x86_64.rpm",
"python3-perf-debuginfo-5.10.0-136.100.0.181.oe2203sp1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:22.03-LTS-SP1",
"name": "kernel",
"purl": "pkg:rpm/openEuler/kernel\u0026distro=openEuler-22.03-LTS-SP1"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.10.0-136.100.0.181.oe2203sp1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ipv6: avoid use-after-free in ip6_fragment() Blamed commit claimed rcu_read_lock() was held by ip6_fragment() callers. It seems to not be always true, at least for UDP stack. syzbot reported: BUG: KASAN: use-after-free in ip6_dst_idev include/net/ip6_fib.h:245 [inline] BUG: KASAN: use-after-free in ip6_fragment+0x2724/0x2770 net/ipv6/ip6_output.c:951 Read of size 8 at addr ffff88801d403e80 by task syz-executor.3/7618 CPU: 1 PID: 7618 Comm: syz-executor.3 Not tainted 6.1.0-rc6-syzkaller-00012-g4312098baf37 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Call Trace: \u0026lt;TASK\u0026gt; __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd1/0x138 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:284 [inline] print_report+0x15e/0x45d mm/kasan/report.c:395 kasan_report+0xbf/0x1f0 mm/kasan/report.c:495 ip6_dst_idev include/net/ip6_fib.h:245 [inline] ip6_fragment+0x2724/0x2770 net/ipv6/ip6_output.c:951 __ip6_finish_output net/ipv6/ip6_output.c:193 [inline] ip6_finish_output+0x9a3/0x1170 net/ipv6/ip6_output.c:206 NF_HOOK_COND include/linux/netfilter.h:291 [inline] ip6_output+0x1f1/0x540 net/ipv6/ip6_output.c:227 dst_output include/net/dst.h:445 [inline] ip6_local_out+0xb3/0x1a0 net/ipv6/output_core.c:161 ip6_send_skb+0xbb/0x340 net/ipv6/ip6_output.c:1966 udp_v6_send_skb+0x82a/0x18a0 net/ipv6/udp.c:1286 udp_v6_push_pending_frames+0x140/0x200 net/ipv6/udp.c:1313 udpv6_sendmsg+0x18da/0x2c80 net/ipv6/udp.c:1606 inet6_sendmsg+0x9d/0xe0 net/ipv6/af_inet6.c:665 sock_sendmsg_nosec net/socket.c:714 [inline] sock_sendmsg+0xd3/0x120 net/socket.c:734 sock_write_iter+0x295/0x3d0 net/socket.c:1108 call_write_iter include/linux/fs.h:2191 [inline] new_sync_write fs/read_write.c:491 [inline] vfs_write+0x9ed/0xdd0 fs/read_write.c:584 ksys_write+0x1ec/0x250 fs/read_write.c:637 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7fde3588c0d9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fde365b6168 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 00007fde359ac050 RCX: 00007fde3588c0d9 RDX: 000000000000ffdc RSI: 00000000200000c0 RDI: 000000000000000a RBP: 00007fde358e7ae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fde35acfb1f R14: 00007fde365b6300 R15: 0000000000022000 \u0026lt;/TASK\u0026gt; Allocated by task 7618: kasan_save_stack+0x22/0x40 mm/kasan/common.c:45 kasan_set_track+0x25/0x30 mm/kasan/common.c:52 __kasan_slab_alloc+0x82/0x90 mm/kasan/common.c:325 kasan_slab_alloc include/linux/kasan.h:201 [inline] slab_post_alloc_hook mm/slab.h:737 [inline] slab_alloc_node mm/slub.c:3398 [inline] slab_alloc mm/slub.c:3406 [inline] __kmem_cache_alloc_lru mm/slub.c:3413 [inline] kmem_cache_alloc+0x2b4/0x3d0 mm/slub.c:3422 dst_alloc+0x14a/0x1f0 net/core/dst.c:92 ip6_dst_alloc+0x32/0xa0 net/ipv6/route.c:344 ip6_rt_pcpu_alloc net/ipv6/route.c:1369 [inline] rt6_make_pcpu_route net/ipv6/route.c:1417 [inline] ip6_pol_route+0x901/0x1190 net/ipv6/route.c:2254 pol_lookup_func include/net/ip6_fib.h:582 [inline] fib6_rule_lookup+0x52e/0x6f0 net/ipv6/fib6_rules.c:121 ip6_route_output_flags_noref+0x2e6/0x380 net/ipv6/route.c:2625 ip6_route_output_flags+0x76/0x320 net/ipv6/route.c:2638 ip6_route_output include/net/ip6_route.h:98 [inline] ip6_dst_lookup_tail+0x5ab/0x1620 net/ipv6/ip6_output.c:1092 ip6_dst_lookup_flow+0x90/0x1d0 net/ipv6/ip6_output.c:1222 ip6_sk_dst_lookup_flow+0x553/0x980 net/ipv6/ip6_output.c:1260 udpv6_sendmsg+0x151d/0x2c80 net/ipv6/udp.c:1554 inet6_sendmsg+0x9d/0xe0 net/ipv6/af_inet6.c:665 sock_sendmsg_nosec n ---truncated---(CVE-2022-48956)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ethernet: aeroflex: fix potential skb leak in greth_init_rings() The greth_init_rings() function won\u0026apos;t free the newly allocated skb when dma_mapping_error() returns error, so add dev_kfree_skb() to fix it. Compile tested only.(CVE-2022-48958)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: net: hisilicon: Fix potential use-after-free in hix5hd2_rx() The skb is delivered to napi_gro_receive() which may free it, after calling this, dereferencing skb may trigger use-after-free.(CVE-2022-48960)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: net: mdio: fix unbalanced fwnode reference count in mdio_device_release() There is warning report about of_node refcount leak while probing mdio device: OF: ERROR: memory leak, expected refcount 1 instead of 2, of_node_get()/of_node_put() unbalanced - destroy cset entry: attach overlay node /spi/soc@0/mdio@710700c0/ethernet@4 In of_mdiobus_register_device(), we increase fwnode refcount by fwnode_handle_get() before associating the of_node with mdio device, but it has never been decreased in normal path. Since that, in mdio_device_release(), it needs to call fwnode_handle_put() in addition instead of calling kfree() directly. After above, just calling mdio_device_free() in the error handle path of of_mdiobus_register_device() is enough to keep the refcount balanced.(CVE-2022-48961)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: net: hisilicon: Fix potential use-after-free in hisi_femac_rx() The skb is delivered to napi_gro_receive() which may free it, after calling this, dereferencing skb may trigger use-after-free.(CVE-2022-48962)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: net: mvneta: Prevent out of bounds read in mvneta_config_rss() The pp-\u0026gt;indir[0] value comes from the user. It is passed to: if (cpu_online(pp-\u0026gt;rxq_def)) inside the mvneta_percpu_elect() function. It needs bounds checkeding to ensure that it is not beyond the end of the cpu bitmap.(CVE-2022-48966)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: mac802154: fix missing INIT_LIST_HEAD in ieee802154_if_add() Kernel fault injection test reports null-ptr-deref as follows: BUG: kernel NULL pointer dereference, address: 0000000000000008 RIP: 0010:cfg802154_netdev_notifier_call+0x120/0x310 include/linux/list.h:114 Call Trace: \u0026lt;TASK\u0026gt; raw_notifier_call_chain+0x6d/0xa0 kernel/notifier.c:87 call_netdevice_notifiers_info+0x6e/0xc0 net/core/dev.c:1944 unregister_netdevice_many_notify+0x60d/0xcb0 net/core/dev.c:1982 unregister_netdevice_queue+0x154/0x1a0 net/core/dev.c:10879 register_netdevice+0x9a8/0xb90 net/core/dev.c:10083 ieee802154_if_add+0x6ed/0x7e0 net/mac802154/iface.c:659 ieee802154_register_hw+0x29c/0x330 net/mac802154/main.c:229 mcr20a_probe+0xaaa/0xcb1 drivers/net/ieee802154/mcr20a.c:1316 ieee802154_if_add() allocates wpan_dev as netdev\u0026apos;s private data, but not init the list in struct wpan_dev. cfg802154_netdev_notifier_call() manage the list when device register/unregister, and may lead to null-ptr-deref. Use INIT_LIST_HEAD() on it to initialize it correctly.(CVE-2022-48972)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: gpiolib: fix memory leak in gpiochip_setup_dev() Here is a backtrace report about memory leak detected in gpiochip_setup_dev(): unreferenced object 0xffff88810b406400 (size 512): comm \u0026quot;python3\u0026quot;, pid 1682, jiffies 4295346908 (age 24.090s) backtrace: kmalloc_trace device_add device_private_init at drivers/base/core.c:3361 (inlined by) device_add at drivers/base/core.c:3411 cdev_device_add gpiolib_cdev_register gpiochip_setup_dev gpiochip_add_data_with_key gcdev_register() \u0026amp; gcdev_unregister() would call device_add() \u0026amp; device_del() (no matter CONFIG_GPIO_CDEV is enabled or not) to register/unregister device. However, if device_add() succeeds, some resource (like struct device_private allocated by device_private_init()) is not released by device_del(). Therefore, after device_add() succeeds by gcdev_register(), it needs to call put_device() to release resource in the error handle path. Here we move forward the register of release function, and let it release every piece of resource by put_device() instead of kfree(). While at it, fix another subtle issue, i.e. when gc-\u0026gt;ngpio is equal to 0, we still call kcalloc() and, in case of further error, kfree() on the ZERO_PTR pointer, which is not NULL. It\u0026apos;s not a bug per se, but rather waste of the resources and potentially wrong expectation about contents of the gdev-\u0026gt;descs variable.(CVE-2022-48975)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm/shmem-helper: Remove errant put in error path drm_gem_shmem_mmap() doesn\u0026apos;t own this reference, resulting in the GEM object getting prematurely freed leading to a later use-after-free.(CVE-2022-48981)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix crash when replugging CSR fake controllers It seems fake CSR 5.0 clones can cause the suspend notifier to be registered twice causing the following kernel panic: [ 71.986122] Call Trace: [ 71.986124] \u0026lt;TASK\u0026gt; [ 71.986125] blocking_notifier_chain_register+0x33/0x60 [ 71.986130] hci_register_dev+0x316/0x3d0 [bluetooth 99b5497ea3d09708fa1366c1dc03288bf3cca8da] [ 71.986154] btusb_probe+0x979/0xd85 [btusb e1e0605a4f4c01984a4b9c8ac58c3666ae287477] [ 71.986159] ? __pm_runtime_set_status+0x1a9/0x300 [ 71.986162] ? ktime_get_mono_fast_ns+0x3e/0x90 [ 71.986167] usb_probe_interface+0xe3/0x2b0 [ 71.986171] really_probe+0xdb/0x380 [ 71.986174] ? pm_runtime_barrier+0x54/0x90 [ 71.986177] __driver_probe_device+0x78/0x170 [ 71.986180] driver_probe_device+0x1f/0x90 [ 71.986183] __device_attach_driver+0x89/0x110 [ 71.986186] ? driver_allows_async_probing+0x70/0x70 [ 71.986189] bus_for_each_drv+0x8c/0xe0 [ 71.986192] __device_attach+0xb2/0x1e0 [ 71.986195] bus_probe_device+0x92/0xb0 [ 71.986198] device_add+0x422/0x9a0 [ 71.986201] ? sysfs_merge_group+0xd4/0x110 [ 71.986205] usb_set_configuration+0x57a/0x820 [ 71.986208] usb_generic_driver_probe+0x4f/0x70 [ 71.986211] usb_probe_device+0x3a/0x110 [ 71.986213] really_probe+0xdb/0x380 [ 71.986216] ? pm_runtime_barrier+0x54/0x90 [ 71.986219] __driver_probe_device+0x78/0x170 [ 71.986221] driver_probe_device+0x1f/0x90 [ 71.986224] __device_attach_driver+0x89/0x110 [ 71.986227] ? driver_allows_async_probing+0x70/0x70 [ 71.986230] bus_for_each_drv+0x8c/0xe0 [ 71.986232] __device_attach+0xb2/0x1e0 [ 71.986235] bus_probe_device+0x92/0xb0 [ 71.986237] device_add+0x422/0x9a0 [ 71.986239] ? _dev_info+0x7d/0x98 [ 71.986242] ? blake2s_update+0x4c/0xc0 [ 71.986246] usb_new_device.cold+0x148/0x36d [ 71.986250] hub_event+0xa8a/0x1910 [ 71.986255] process_one_work+0x1c4/0x380 [ 71.986259] worker_thread+0x51/0x390 [ 71.986262] ? rescuer_thread+0x3b0/0x3b0 [ 71.986264] kthread+0xdb/0x110 [ 71.986266] ? kthread_complete_and_exit+0x20/0x20 [ 71.986268] ret_from_fork+0x1f/0x30 [ 71.986273] \u0026lt;/TASK\u0026gt; [ 71.986274] ---[ end trace 0000000000000000 ]--- [ 71.986284] btusb: probe of 2-1.6:1.0 failed with error -17(CVE-2022-48982)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ASoC: soc-pcm: Add NULL check in BE reparenting Add NULL check in dpcm_be_reparent API, to handle kernel NULL pointer dereference error. The issue occurred in fuzzing test.(CVE-2022-48992)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: Input: raydium_ts_i2c - fix memory leak in raydium_i2c_send() There is a kmemleak when test the raydium_i2c_ts with bpf mock device: unreferenced object 0xffff88812d3675a0 (size 8): comm \u0026quot;python3\u0026quot;, pid 349, jiffies 4294741067 (age 95.695s) hex dump (first 8 bytes): 11 0e 10 c0 01 00 04 00 ........ backtrace: [\u0026lt;0000000068427125\u0026gt;] __kmalloc+0x46/0x1b0 [\u0026lt;0000000090180f91\u0026gt;] raydium_i2c_send+0xd4/0x2bf [raydium_i2c_ts] [\u0026lt;000000006e631aee\u0026gt;] raydium_i2c_initialize.cold+0xbc/0x3e4 [raydium_i2c_ts] [\u0026lt;00000000dc6fcf38\u0026gt;] raydium_i2c_probe+0x3cd/0x6bc [raydium_i2c_ts] [\u0026lt;00000000a310de16\u0026gt;] i2c_device_probe+0x651/0x680 [\u0026lt;00000000f5a96bf3\u0026gt;] really_probe+0x17c/0x3f0 [\u0026lt;00000000096ba499\u0026gt;] __driver_probe_device+0xe3/0x170 [\u0026lt;00000000c5acb4d9\u0026gt;] driver_probe_device+0x49/0x120 [\u0026lt;00000000264fe082\u0026gt;] __device_attach_driver+0xf7/0x150 [\u0026lt;00000000f919423c\u0026gt;] bus_for_each_drv+0x114/0x180 [\u0026lt;00000000e067feca\u0026gt;] __device_attach+0x1e5/0x2d0 [\u0026lt;0000000054301fc2\u0026gt;] bus_probe_device+0x126/0x140 [\u0026lt;00000000aad93b22\u0026gt;] device_add+0x810/0x1130 [\u0026lt;00000000c086a53f\u0026gt;] i2c_new_client_device+0x352/0x4e0 [\u0026lt;000000003c2c248c\u0026gt;] of_i2c_register_device+0xf1/0x110 [\u0026lt;00000000ffec4177\u0026gt;] of_i2c_notify+0x100/0x160 unreferenced object 0xffff88812d3675c8 (size 8): comm \u0026quot;python3\u0026quot;, pid 349, jiffies 4294741070 (age 95.692s) hex dump (first 8 bytes): 22 00 36 2d 81 88 ff ff \u0026quot;.6-.... backtrace: [\u0026lt;0000000068427125\u0026gt;] __kmalloc+0x46/0x1b0 [\u0026lt;0000000090180f91\u0026gt;] raydium_i2c_send+0xd4/0x2bf [raydium_i2c_ts] [\u0026lt;000000001d5c9620\u0026gt;] raydium_i2c_initialize.cold+0x223/0x3e4 [raydium_i2c_ts] [\u0026lt;00000000dc6fcf38\u0026gt;] raydium_i2c_probe+0x3cd/0x6bc [raydium_i2c_ts] [\u0026lt;00000000a310de16\u0026gt;] i2c_device_probe+0x651/0x680 [\u0026lt;00000000f5a96bf3\u0026gt;] really_probe+0x17c/0x3f0 [\u0026lt;00000000096ba499\u0026gt;] __driver_probe_device+0xe3/0x170 [\u0026lt;00000000c5acb4d9\u0026gt;] driver_probe_device+0x49/0x120 [\u0026lt;00000000264fe082\u0026gt;] __device_attach_driver+0xf7/0x150 [\u0026lt;00000000f919423c\u0026gt;] bus_for_each_drv+0x114/0x180 [\u0026lt;00000000e067feca\u0026gt;] __device_attach+0x1e5/0x2d0 [\u0026lt;0000000054301fc2\u0026gt;] bus_probe_device+0x126/0x140 [\u0026lt;00000000aad93b22\u0026gt;] device_add+0x810/0x1130 [\u0026lt;00000000c086a53f\u0026gt;] i2c_new_client_device+0x352/0x4e0 [\u0026lt;000000003c2c248c\u0026gt;] of_i2c_register_device+0xf1/0x110 [\u0026lt;00000000ffec4177\u0026gt;] of_i2c_notify+0x100/0x160 After BANK_SWITCH command from i2c BUS, no matter success or error happened, the tx_buf should be freed.(CVE-2022-48995)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: riscv: Sync efi page table\u0026apos;s kernel mappings before switching The EFI page table is initially created as a copy of the kernel page table. With VMAP_STACK enabled, kernel stacks are allocated in the vmalloc area: if the stack is allocated in a new PGD (one that was not present at the moment of the efi page table creation or not synced in a previous vmalloc fault), the kernel will take a trap when switching to the efi page table when the vmalloc kernel stack is accessed, resulting in a kernel panic. Fix that by updating the efi kernel mappings before switching to the efi page table.(CVE-2022-49004)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ASoC: ops: Fix bounds check for _sx controls For _sx controls the semantics of the max field is not the usual one, max is the number of steps rather than the maximum value. This means that our check in snd_soc_put_volsw_sx() needs to just check against the maximum value.(CVE-2022-49005)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: hwmon: (coretemp) fix pci device refcount leak in nv1a_ram_new() As comment of pci_get_domain_bus_and_slot() says, it returns a pci device with refcount increment, when finish using it, the caller must decrement the reference count by calling pci_dev_put(). So call it after using to avoid refcount leak.(CVE-2022-49011)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: tipc: re-fetch skb cb after tipc_msg_validate As the call trace shows, the original skb was freed in tipc_msg_validate(), and dereferencing the old skb cb would cause an use-after-free crash. BUG: KASAN: use-after-free in tipc_crypto_rcv_complete+0x1835/0x2240 [tipc] Call Trace: \u0026lt;IRQ\u0026gt; tipc_crypto_rcv_complete+0x1835/0x2240 [tipc] tipc_crypto_rcv+0xd32/0x1ec0 [tipc] tipc_rcv+0x744/0x1150 [tipc] ... Allocated by task 47078: kmem_cache_alloc_node+0x158/0x4d0 __alloc_skb+0x1c1/0x270 tipc_buf_acquire+0x1e/0xe0 [tipc] tipc_msg_create+0x33/0x1c0 [tipc] tipc_link_build_proto_msg+0x38a/0x2100 [tipc] tipc_link_timeout+0x8b8/0xef0 [tipc] tipc_node_timeout+0x2a1/0x960 [tipc] call_timer_fn+0x2d/0x1c0 ... Freed by task 47078: tipc_msg_validate+0x7b/0x440 [tipc] tipc_crypto_rcv_complete+0x4b5/0x2240 [tipc] tipc_crypto_rcv+0xd32/0x1ec0 [tipc] tipc_rcv+0x744/0x1150 [tipc] This patch fixes it by re-fetching the skb cb from the new allocated skb after calling tipc_msg_validate().(CVE-2022-49017)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: net/9p: Fix a potential socket leak in p9_socket_open Both p9_fd_create_tcp() and p9_fd_create_unix() will call p9_socket_open(). If the creation of p9_trans_fd fails, p9_fd_create_tcp() and p9_fd_create_unix() will return an error directly instead of releasing the cscoket, which will result in a socket leak. This patch adds sock_release() to fix the leak issue.(CVE-2022-49020)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: net: phy: fix null-ptr-deref while probe() failed I got a null-ptr-deref report as following when doing fault injection test: BUG: kernel NULL pointer dereference, address: 0000000000000058 Oops: 0000 [#1] PREEMPT SMP KASAN PTI CPU: 1 PID: 253 Comm: 507-spi-dm9051 Tainted: G B N 6.1.0-rc3+ Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 RIP: 0010:klist_put+0x2d/0xd0 Call Trace: \u0026lt;TASK\u0026gt; klist_remove+0xf1/0x1c0 device_release_driver_internal+0x23e/0x2d0 bus_remove_device+0x1bd/0x240 device_del+0x357/0x770 phy_device_remove+0x11/0x30 mdiobus_unregister+0xa5/0x140 release_nodes+0x6a/0xa0 devres_release_all+0xf8/0x150 device_unbind_cleanup+0x19/0xd0 //probe path: phy_device_register() device_add() phy_connect phy_attach_direct() //set device driver probe() //it\u0026apos;s failed, driver is not bound device_bind_driver() // probe failed, it\u0026apos;s not called //remove path: phy_device_remove() device_del() device_release_driver_internal() __device_release_driver() //dev-\u0026gt;drv is not NULL klist_remove() \u0026lt;- knode_driver is not added yet, cause null-ptr-deref In phy_attach_direct(), after setting the \u0026apos;dev-\u0026gt;driver\u0026apos;, probe() fails, device_bind_driver() is not called, so the knode_driver-\u0026gt;n_klist is not set, then it causes null-ptr-deref in __device_release_driver() while deleting device. Fix this by setting dev-\u0026gt;driver to NULL in the error path in phy_attach_direct().(CVE-2022-49021)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: fix buffer overflow in elem comparison For vendor elements, the code here assumes that 5 octets are present without checking. Since the element itself is already checked to fit, we only need to check the length.(CVE-2022-49023)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: iio: health: afe4403: Fix oob read in afe4403_read_raw KASAN report out-of-bounds read as follows: BUG: KASAN: global-out-of-bounds in afe4403_read_raw+0x42e/0x4c0 Read of size 4 at addr ffffffffc02ac638 by task cat/279 Call Trace: afe4403_read_raw iio_read_channel_info dev_attr_show The buggy address belongs to the variable: afe4403_channel_leds+0x18/0xffffffffffffe9e0 This issue can be reproduced by singe command: $ cat /sys/bus/spi/devices/spi0.0/iio\\:device0/in_intensity6_raw The array size of afe4403_channel_leds is less than channels, so access with chan-\u0026gt;address cause OOB read in afe4403_read_raw. Fix it by moving access before use it.(CVE-2022-49031)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: iio: health: afe4404: Fix oob read in afe4404_[read|write]_raw KASAN report out-of-bounds read as follows: BUG: KASAN: global-out-of-bounds in afe4404_read_raw+0x2ce/0x380 Read of size 4 at addr ffffffffc00e4658 by task cat/278 Call Trace: afe4404_read_raw iio_read_channel_info dev_attr_show The buggy address belongs to the variable: afe4404_channel_leds+0x18/0xffffffffffffe9c0 This issue can be reproduce by singe command: $ cat /sys/bus/i2c/devices/0-0058/iio\\:device0/in_intensity6_raw The array size of afe4404_channel_leds and afe4404_channel_offdacs are less than channels, so access with chan-\u0026gt;address cause OOB read in afe4404_[read|write]_raw. Fix it by moving access before use them.(CVE-2022-49032)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmemcg_write_event_control(): fix a user-triggerable oops\r\n\r\nwe are *not* guaranteed that anything past the terminating NUL\nis mapped (let alone initialized with anything sane).(CVE-2024-45021)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ngtp: fix a potential NULL pointer dereference\r\n\r\nWhen sockfd_lookup() fails, gtp_encap_enable_socket() returns a\nNULL pointer, but its callers only check for error pointers thus miss\nthe NULL pointer case.\r\n\r\nFix it by returning an error pointer with the error code carried from\nsockfd_lookup().\r\n\r\n(I found this bug during code inspection.)(CVE-2024-46677)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Check BIOS images before it is used\r\n\r\nBIOS images may fail to load and null checks are added before they are\nused.\r\n\r\nThis fixes 6 NULL_RETURNS issues reported by Coverity.(CVE-2024-46809)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsmack: tcp: ipv4, fix incorrect labeling\r\n\r\nCurrently, Smack mirrors the label of incoming tcp/ipv4 connections:\nwhen a label \u0026apos;foo\u0026apos; connects to a label \u0026apos;bar\u0026apos; with tcp/ipv4,\n\u0026apos;foo\u0026apos; always gets \u0026apos;foo\u0026apos; in returned ipv4 packets. So,\n1) returned packets are incorrectly labeled (\u0026apos;foo\u0026apos; instead of \u0026apos;bar\u0026apos;)\n2) \u0026apos;bar\u0026apos; can write to \u0026apos;foo\u0026apos; without being authorized to write.\r\n\r\nHere is a scenario how to see this:\r\n\r\n* Take two machines, let\u0026apos;s call them C and S,\n with active Smack in the default state\n (no settings, no rules, no labeled hosts, only builtin labels)\r\n\r\n* At S, add Smack rule \u0026apos;foo bar w\u0026apos;\n (labels \u0026apos;foo\u0026apos; and \u0026apos;bar\u0026apos; are instantiated at S at this moment)\r\n\r\n* At S, at label \u0026apos;bar\u0026apos;, launch a program\n that listens for incoming tcp/ipv4 connections\r\n\r\n* From C, at label \u0026apos;foo\u0026apos;, connect to the listener at S.\n (label \u0026apos;foo\u0026apos; is instantiated at C at this moment)\n Connection succeedes and works.\r\n\r\n* Send some data in both directions.\n* Collect network traffic of this connection.\r\n\r\nAll packets in both directions are labeled with the CIPSO\nof the label \u0026apos;foo\u0026apos;. Hence, label \u0026apos;bar\u0026apos; writes to \u0026apos;foo\u0026apos; without\nbeing authorized, and even without ever being known at C.\r\n\r\nIf anybody cares: exactly the same happens with DCCP.\r\n\r\nThis behavior 1st manifested in release 2.6.29.4 (see Fixes below)\nand it looks unintentional. At least, no explanation was provided.\r\n\r\nI changed returned packes label into the \u0026apos;bar\u0026apos;,\nto bring it into line with the Smack documentation claims.(CVE-2024-47659)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nfsnotify: clear PARENT_WATCHED flags lazily\r\n\r\nIn some setups directories can have many (usually negative) dentries.\nHence __fsnotify_update_child_dentry_flags() function can take a\nsignificant amount of time. Since the bulk of this function happens\nunder inode-\u0026gt;i_lock this causes a significant contention on the lock\nwhen we remove the watch from the directory as the\n__fsnotify_update_child_dentry_flags() call from fsnotify_recalc_mask()\nraces with __fsnotify_update_child_dentry_flags() calls from\n__fsnotify_parent() happening on children. This can lead upto softlockup\nreports reported by users.\r\n\r\nFix the problem by calling fsnotify_update_children_dentry_flags() to\nset PARENT_WATCHED flags only when parent starts watching children.\r\n\r\nWhen parent stops watching children, clear false positive PARENT_WATCHED\nflags lazily in __fsnotify_parent() for each accessed child.(CVE-2024-47660)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nlib/generic-radix-tree.c: Fix rare race in __genradix_ptr_alloc()\r\n\r\nIf we need to increase the tree depth, allocate a new node, and then\nrace with another thread that increased the tree depth before us, we\u0026apos;ll\nstill have a preallocated node that might be used later.\r\n\r\nIf we then use that node for a new non-root node, it\u0026apos;ll still have a\npointer to the old root instead of being zeroed - fix this by zeroing it\nin the cmpxchg failure path.(CVE-2024-47668)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: iwlwifi: mvm: pause TCM when the firmware is stopped\r\n\r\nNot doing so will make us send a host command to the transport while the\nfirmware is not alive, which will trigger a WARNING.\r\n\r\nbad state = 0\nWARNING: CPU: 2 PID: 17434 at drivers/net/wireless/intel/iwlwifi/iwl-trans.c:115 iwl_trans_send_cmd+0x1cb/0x1e0 [iwlwifi]\nRIP: 0010:iwl_trans_send_cmd+0x1cb/0x1e0 [iwlwifi]\nCall Trace:\n \u0026lt;TASK\u0026gt;\n iwl_mvm_send_cmd+0x40/0xc0 [iwlmvm]\n iwl_mvm_config_scan+0x198/0x260 [iwlmvm]\n iwl_mvm_recalc_tcm+0x730/0x11d0 [iwlmvm]\n iwl_mvm_tcm_work+0x1d/0x30 [iwlmvm]\n process_one_work+0x29e/0x640\n worker_thread+0x2df/0x690\n ? rescuer_thread+0x540/0x540\n kthread+0x192/0x1e0\n ? set_kthread_struct+0x90/0x90\n ret_from_fork+0x22/0x30(CVE-2024-47673)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: f2fs: get rid of online repaire on corrupted directory syzbot reports a f2fs bug as below: kernel BUG at fs/f2fs/inode.c:896! RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896 Call Trace: evict+0x532/0x950 fs/inode.c:704 dispose_list fs/inode.c:747 [inline] evict_inodes+0x5f9/0x690 fs/inode.c:797 generic_shutdown_super+0x9d/0x2d0 fs/super.c:627 kill_block_super+0x44/0x90 fs/super.c:1696 kill_f2fs_super+0x344/0x690 fs/f2fs/super.c:4898 deactivate_locked_super+0xc4/0x130 fs/super.c:473 cleanup_mnt+0x41f/0x4b0 fs/namespace.c:1373 task_work_run+0x24f/0x310 kernel/task_work.c:228 ptrace_notify+0x2d2/0x380 kernel/signal.c:2402 ptrace_report_syscall include/linux/ptrace.h:415 [inline] ptrace_report_syscall_exit include/linux/ptrace.h:477 [inline] syscall_exit_work+0xc6/0x190 kernel/entry/common.c:173 syscall_exit_to_user_mode_prepare kernel/entry/common.c:200 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:205 [inline] syscall_exit_to_user_mode+0x279/0x370 kernel/entry/common.c:218 do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0010:f2fs_evict_inode+0x1598/0x15c0 fs/f2fs/inode.c:896 Online repaire on corrupted directory in f2fs_lookup() can generate dirty data/meta while racing w/ readonly remount, it may leave dirty inode after filesystem becomes readonly, however, checkpoint() will skips flushing dirty inode in a state of readonly mode, result in above panic. Let\u0026apos;s get rid of online repaire in f2fs_lookup(), and leave the work to fsck.f2fs.(CVE-2024-47690)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid use-after-free in f2fs_stop_gc_thread() syzbot reports a f2fs bug as below: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114 print_report+0xe8/0x550 mm/kasan/report.c:491 kasan_report+0x143/0x180 mm/kasan/report.c:601 kasan_check_range+0x282/0x290 mm/kasan/generic.c:189 instrument_atomic_read_write include/linux/instrumented.h:96 [inline] atomic_fetch_add_relaxed include/linux/atomic/atomic-instrumented.h:252 [inline] __refcount_add include/linux/refcount.h:184 [inline] __refcount_inc include/linux/refcount.h:241 [inline] refcount_inc include/linux/refcount.h:258 [inline] get_task_struct include/linux/sched/task.h:118 [inline] kthread_stop+0xca/0x630 kernel/kthread.c:704 f2fs_stop_gc_thread+0x65/0xb0 fs/f2fs/gc.c:210 f2fs_do_shutdown+0x192/0x540 fs/f2fs/file.c:2283 f2fs_ioc_shutdown fs/f2fs/file.c:2325 [inline] __f2fs_ioctl+0x443a/0xbe60 fs/f2fs/file.c:4325 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f The root cause is below race condition, it may cause use-after-free issue in sbi-\u0026gt;gc_th pointer. - remount - f2fs_remount - f2fs_stop_gc_thread - kfree(gc_th) - f2fs_ioc_shutdown - f2fs_do_shutdown - f2fs_stop_gc_thread - kthread_stop(gc_th-\u0026gt;f2fs_gc_task) : sbi-\u0026gt;gc_thread = NULL; We will call f2fs_do_shutdown() in two paths: - for f2fs_ioc_shutdown() path, we should grab sb-\u0026gt;s_umount semaphore for fixing. - for f2fs_shutdown() path, it\u0026apos;s safe since caller has already grabbed sb-\u0026gt;s_umount semaphore.(CVE-2024-47691)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: nfsd: return -EINVAL when namelen is 0 When we have a corrupted main.sqlite in /var/lib/nfs/nfsdcld/, it may result in namelen being 0, which will cause memdup_user() to return ZERO_SIZE_PTR. When we access the name.data that has been assigned the value of ZERO_SIZE_PTR in nfs4_client_to_reclaim(), null pointer dereference is triggered. [ T1205] ================================================================== [ T1205] BUG: KASAN: null-ptr-deref in nfs4_client_to_reclaim+0xe9/0x260 [ T1205] Read of size 1 at addr 0000000000000010 by task nfsdcld/1205 [ T1205] [ T1205] CPU: 11 PID: 1205 Comm: nfsdcld Not tainted 5.10.0-00003-g2c1423731b8d #406 [ T1205] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS ?-20190727_073836-buildvm-ppc64le-16.ppc.fedoraproject.org-3.fc31 04/01/2014 [ T1205] Call Trace: [ T1205] dump_stack+0x9a/0xd0 [ T1205] ? nfs4_client_to_reclaim+0xe9/0x260 [ T1205] __kasan_report.cold+0x34/0x84 [ T1205] ? nfs4_client_to_reclaim+0xe9/0x260 [ T1205] kasan_report+0x3a/0x50 [ T1205] nfs4_client_to_reclaim+0xe9/0x260 [ T1205] ? nfsd4_release_lockowner+0x410/0x410 [ T1205] cld_pipe_downcall+0x5ca/0x760 [ T1205] ? nfsd4_cld_tracking_exit+0x1d0/0x1d0 [ T1205] ? down_write_killable_nested+0x170/0x170 [ T1205] ? avc_policy_seqno+0x28/0x40 [ T1205] ? selinux_file_permission+0x1b4/0x1e0 [ T1205] rpc_pipe_write+0x84/0xb0 [ T1205] vfs_write+0x143/0x520 [ T1205] ksys_write+0xc9/0x170 [ T1205] ? __ia32_sys_read+0x50/0x50 [ T1205] ? ktime_get_coarse_real_ts64+0xfe/0x110 [ T1205] ? ktime_get_coarse_real_ts64+0xa2/0x110 [ T1205] do_syscall_64+0x33/0x40 [ T1205] entry_SYSCALL_64_after_hwframe+0x67/0xd1 [ T1205] RIP: 0033:0x7fdbdb761bc7 [ T1205] Code: 0f 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 0f 1f 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 514 [ T1205] RSP: 002b:00007fff8c4b7248 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 [ T1205] RAX: ffffffffffffffda RBX: 000000000000042b RCX: 00007fdbdb761bc7 [ T1205] RDX: 000000000000042b RSI: 00007fff8c4b75f0 RDI: 0000000000000008 [ T1205] RBP: 00007fdbdb761bb0 R08: 0000000000000000 R09: 0000000000000001 [ T1205] R10: 0000000000000000 R11: 0000000000000246 R12: 000000000000042b [ T1205] R13: 0000000000000008 R14: 00007fff8c4b75f0 R15: 0000000000000000 [ T1205] ================================================================== Fix it by checking namelen.(CVE-2024-47692)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: IB/core: Fix ib_cache_setup_one error flow cleanup When ib_cache_update return an error, we exit ib_cache_setup_one instantly with no proper cleanup, even though before this we had already successfully done gid_table_setup_one, that results in the kernel WARN below. Do proper cleanup using gid_table_cleanup_one before returning the err in order to fix the issue. WARNING: CPU: 4 PID: 922 at drivers/infiniband/core/cache.c:806 gid_table_release_one+0x181/0x1a0 Modules linked in: CPU: 4 UID: 0 PID: 922 Comm: c_repro Not tainted 6.11.0-rc1+ #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:gid_table_release_one+0x181/0x1a0 Code: 44 8b 38 75 0c e8 2f cb 34 ff 4d 8b b5 28 05 00 00 e8 23 cb 34 ff 44 89 f9 89 da 4c 89 f6 48 c7 c7 d0 58 14 83 e8 4f de 21 ff \u0026lt;0f\u0026gt; 0b 4c 8b 75 30 e9 54 ff ff ff 48 8 3 c4 10 5b 5d 41 5c 41 5d 41 RSP: 0018:ffffc90002b835b0 EFLAGS: 00010286 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff811c8527 RDX: 0000000000000000 RSI: ffffffff811c8534 RDI: 0000000000000001 RBP: ffff8881011b3d00 R08: ffff88810b3abe00 R09: 205d303839303631 R10: 666572207972746e R11: 72746e6520444947 R12: 0000000000000001 R13: ffff888106390000 R14: ffff8881011f2110 R15: 0000000000000001 FS: 00007fecc3b70800(0000) GS:ffff88813bd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020000340 CR3: 000000010435a001 CR4: 00000000003706b0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: \u0026lt;TASK\u0026gt; ? show_regs+0x94/0xa0 ? __warn+0x9e/0x1c0 ? gid_table_release_one+0x181/0x1a0 ? report_bug+0x1f9/0x340 ? gid_table_release_one+0x181/0x1a0 ? handle_bug+0xa2/0x110 ? exc_invalid_op+0x31/0xa0 ? asm_exc_invalid_op+0x16/0x20 ? __warn_printk+0xc7/0x180 ? __warn_printk+0xd4/0x180 ? gid_table_release_one+0x181/0x1a0 ib_device_release+0x71/0xe0 ? __pfx_ib_device_release+0x10/0x10 device_release+0x44/0xd0 kobject_put+0x135/0x3d0 put_device+0x20/0x30 rxe_net_add+0x7d/0xa0 rxe_newlink+0xd7/0x190 nldev_newlink+0x1b0/0x2a0 ? __pfx_nldev_newlink+0x10/0x10 rdma_nl_rcv_msg+0x1ad/0x2e0 rdma_nl_rcv_skb.constprop.0+0x176/0x210 netlink_unicast+0x2de/0x400 netlink_sendmsg+0x306/0x660 __sock_sendmsg+0x110/0x120 ____sys_sendmsg+0x30e/0x390 ___sys_sendmsg+0x9b/0xf0 ? kstrtouint+0x6e/0xa0 ? kstrtouint_from_user+0x7c/0xb0 ? get_pid_task+0xb0/0xd0 ? proc_fail_nth_write+0x5b/0x140 ? __fget_light+0x9a/0x200 ? preempt_count_add+0x47/0xa0 __sys_sendmsg+0x61/0xd0 do_syscall_64+0x50/0x110 entry_SYSCALL_64_after_hwframe+0x76/0x7e(CVE-2024-47693)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: RDMA/iwcm: Fix WARNING:at_kernel/workqueue.c:#check_flush_dependency In the commit aee2424246f9 (\u0026quot;RDMA/iwcm: Fix a use-after-free related to destroying CM IDs\u0026quot;), the function flush_workqueue is invoked to flush the work queue iwcm_wq. But at that time, the work queue iwcm_wq was created via the function alloc_ordered_workqueue without the flag WQ_MEM_RECLAIM. Because the current process is trying to flush the whole iwcm_wq, if iwcm_wq doesn\u0026apos;t have the flag WQ_MEM_RECLAIM, verify that the current process is not reclaiming memory or running on a workqueue which doesn\u0026apos;t have the flag WQ_MEM_RECLAIM as that can break forward-progress guarantee leading to a deadlock. The call trace is as below: [ 125.350876][ T1430] Call Trace: [ 125.356281][ T1430] \u0026lt;TASK\u0026gt; [ 125.361285][ T1430] ? __warn (kernel/panic.c:693) [ 125.367640][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.375689][ T1430] ? report_bug (lib/bug.c:180 lib/bug.c:219) [ 125.382505][ T1430] ? handle_bug (arch/x86/kernel/traps.c:239) [ 125.388987][ T1430] ? exc_invalid_op (arch/x86/kernel/traps.c:260 (discriminator 1)) [ 125.395831][ T1430] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:621) [ 125.403125][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.410984][ T1430] ? check_flush_dependency (kernel/workqueue.c:3706 (discriminator 9)) [ 125.418764][ T1430] __flush_workqueue (kernel/workqueue.c:3970) [ 125.426021][ T1430] ? __pfx___might_resched (kernel/sched/core.c:10151) [ 125.433431][ T1430] ? destroy_cm_id (drivers/infiniband/core/iwcm.c:375) iw_cm [ 125.441209][ T1430] ? __pfx___flush_workqueue (kernel/workqueue.c:3910) [ 125.473900][ T1430] ? _raw_spin_lock_irqsave (arch/x86/include/asm/atomic.h:107 include/linux/atomic/atomic-arch-fallback.h:2170 include/linux/atomic/atomic-instrumented.h:1302 include/asm-generic/qspinlock.h:111 include/linux/spinlock.h:187 include/linux/spinlock_api_smp.h:111 kernel/locking/spinlock.c:162) [ 125.473909][ T1430] ? __pfx__raw_spin_lock_irqsave (kernel/locking/spinlock.c:161) [ 125.482537][ T1430] _destroy_id (drivers/infiniband/core/cma.c:2044) rdma_cm [ 125.495072][ T1430] nvme_rdma_free_queue (drivers/nvme/host/rdma.c:656 drivers/nvme/host/rdma.c:650) nvme_rdma [ 125.505827][ T1430] nvme_rdma_reset_ctrl_work (drivers/nvme/host/rdma.c:2180) nvme_rdma [ 125.505831][ T1430] process_one_work (kernel/workqueue.c:3231) [ 125.515122][ T1430] worker_thread (kernel/workqueue.c:3306 kernel/workqueue.c:3393) [ 125.515127][ T1430] ? __pfx_worker_thread (kernel/workqueue.c:3339) [ 125.531837][ T1430] kthread (kernel/kthread.c:389) [ 125.539864][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.550628][ T1430] ret_from_fork (arch/x86/kernel/process.c:147) [ 125.558840][ T1430] ? __pfx_kthread (kernel/kthread.c:342) [ 125.558844][ T1430] ret_from_fork_asm (arch/x86/entry/entry_64.S:257) [ 125.566487][ T1430] \u0026lt;/TASK\u0026gt; [ 125.566488][ T1430] ---[ end trace 0000000000000000 ]---(CVE-2024-47696)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential null-ptr-deref in nilfs_btree_insert() Patch series \u0026quot;nilfs2: fix potential issues with empty b-tree nodes\u0026quot;. This series addresses three potential issues with empty b-tree nodes that can occur with corrupted filesystem images, including one recently discovered by syzbot. This patch (of 3): If a b-tree is broken on the device, and the b-tree height is greater than 2 (the level of the root node is greater than 1) even if the number of child nodes of the b-tree root is 0, a NULL pointer dereference occurs in nilfs_btree_prepare_insert(), which is called from nilfs_btree_insert(). This is because, when the number of child nodes of the b-tree root is 0, nilfs_btree_do_lookup() does not set the block buffer head in any of path[x].bp_bh, leaving it as the initial value of NULL, but if the level of the b-tree root node is greater than 1, nilfs_btree_get_nonroot_node(), which accesses the buffer memory of path[x].bp_bh, is called. Fix this issue by adding a check to nilfs_btree_root_broken(), which performs sanity checks when reading the root node from the device, to detect this inconsistency. Thanks to Lizhi Xu for trying to solve the bug and clarifying the cause early on.(CVE-2024-47699)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ext4: avoid OOB when system.data xattr changes underneath the filesystem When looking up for an entry in an inlined directory, if e_value_offs is changed underneath the filesystem by some change in the block device, it will lead to an out-of-bounds access that KASAN detects as an UAF. EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 r/w without journal. Quota mode: none. loop0: detected capacity change from 2048 to 2047 ================================================================== BUG: KASAN: use-after-free in ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500 Read of size 1 at addr ffff88803e91130f by task syz-executor269/5103 CPU: 0 UID: 0 PID: 5103 Comm: syz-executor269 Not tainted 6.11.0-rc4-syzkaller #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Call Trace: \u0026lt;TASK\u0026gt; __dump_stack lib/dump_stack.c:93 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:119 print_address_description mm/kasan/report.c:377 [inline] print_report+0x169/0x550 mm/kasan/report.c:488 kasan_report+0x143/0x180 mm/kasan/report.c:601 ext4_search_dir+0xf2/0x1c0 fs/ext4/namei.c:1500 ext4_find_inline_entry+0x4be/0x5e0 fs/ext4/inline.c:1697 __ext4_find_entry+0x2b4/0x1b30 fs/ext4/namei.c:1573 ext4_lookup_entry fs/ext4/namei.c:1727 [inline] ext4_lookup+0x15f/0x750 fs/ext4/namei.c:1795 lookup_one_qstr_excl+0x11f/0x260 fs/namei.c:1633 filename_create+0x297/0x540 fs/namei.c:3980 do_symlinkat+0xf9/0x3a0 fs/namei.c:4587 __do_sys_symlinkat fs/namei.c:4610 [inline] __se_sys_symlinkat fs/namei.c:4607 [inline] __x64_sys_symlinkat+0x95/0xb0 fs/namei.c:4607 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f3e73ced469 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 21 18 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fff4d40c258 EFLAGS: 00000246 ORIG_RAX: 000000000000010a RAX: ffffffffffffffda RBX: 0032656c69662f2e RCX: 00007f3e73ced469 RDX: 0000000020000200 RSI: 00000000ffffff9c RDI: 00000000200001c0 RBP: 0000000000000000 R08: 00007fff4d40c290 R09: 00007fff4d40c290 R10: 0023706f6f6c2f76 R11: 0000000000000246 R12: 00007fff4d40c27c R13: 0000000000000003 R14: 431bde82d7b634db R15: 00007fff4d40c2b0 \u0026lt;/TASK\u0026gt; Calling ext4_xattr_ibody_find right after reading the inode with ext4_get_inode_loc will lead to a check of the validity of the xattrs, avoiding this problem.(CVE-2024-47701)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: bpf, lsm: Add check for BPF LSM return value A bpf prog returning a positive number attached to file_alloc_security hook makes kernel panic. This happens because file system can not filter out the positive number returned by the LSM prog using IS_ERR, and misinterprets this positive number as a file pointer. Given that hook file_alloc_security never returned positive number before the introduction of BPF LSM, and other BPF LSM hooks may encounter similar issues, this patch adds LSM return value check in verifier, to ensure no unexpected value is returned.(CVE-2024-47703)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: block: fix potential invalid pointer dereference in blk_add_partition The blk_add_partition() function initially used a single if-condition (IS_ERR(part)) to check for errors when adding a partition. This was modified to handle the specific case of -ENXIO separately, allowing the function to proceed without logging the error in this case. However, this change unintentionally left a path where md_autodetect_dev() could be called without confirming that part is a valid pointer. This commit separates the error handling logic by splitting the initial if-condition, improving code readability and handling specific error scenarios explicitly. The function now distinguishes the general error case from -ENXIO without altering the existing behavior of md_autodetect_dev() calls.(CVE-2024-47705)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: jfs: fix out-of-bounds in dbNextAG() and diAlloc() In dbNextAG() , there is no check for the case where bmp-\u0026gt;db_numag is greater or same than MAXAG due to a polluted image, which causes an out-of-bounds. Therefore, a bounds check should be added in dbMount(). And in dbNextAG(), a check for the case where agpref is greater than bmp-\u0026gt;db_numag should be added, so an out-of-bounds exception should be prevented. Additionally, a check for the case where agno is greater or same than MAXAG should be added in diAlloc() to prevent out-of-bounds.(CVE-2024-47723)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: padata: use integer wrap around to prevent deadlock on seq_nr overflow When submitting more than 2^32 padata objects to padata_do_serial, the current sorting implementation incorrectly sorts padata objects with overflowed seq_nr, causing them to be placed before existing objects in the reorder list. This leads to a deadlock in the serialization process as padata_find_next cannot match padata-\u0026gt;seq_nr and pd-\u0026gt;processed because the padata instance with overflowed seq_nr will be selected next. To fix this, we use an unsigned integer wrap around to correctly sort padata objects in scenarios with integer overflow.(CVE-2024-47739)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: firmware_loader: Block path traversal Most firmware names are hardcoded strings, or are constructed from fairly constrained format strings where the dynamic parts are just some hex numbers or such. However, there are a couple codepaths in the kernel where firmware file names contain string components that are passed through from a device or semi-privileged userspace; the ones I could find (not counting interfaces that require root privileges) are: - lpfc_sli4_request_firmware_update() seems to construct the firmware filename from \u0026quot;ModelName\u0026quot;, a string that was previously parsed out of some descriptor (\u0026quot;Vital Product Data\u0026quot;) in lpfc_fill_vpd() - nfp_net_fw_find() seems to construct a firmware filename from a model name coming from nfp_hwinfo_lookup(pf-\u0026gt;hwinfo, \u0026quot;nffw.partno\u0026quot;), which I think parses some descriptor that was read from the device. (But this case likely isn\u0026apos;t exploitable because the format string looks like \u0026quot;netronome/nic_%s\u0026quot;, and there shouldn\u0026apos;t be any *folders* starting with \u0026quot;netronome/nic_\u0026quot;. The previous case was different because there, the \u0026quot;%s\u0026quot; is *at the start* of the format string.) - module_flash_fw_schedule() is reachable from the ETHTOOL_MSG_MODULE_FW_FLASH_ACT netlink command, which is marked as GENL_UNS_ADMIN_PERM (meaning CAP_NET_ADMIN inside a user namespace is enough to pass the privilege check), and takes a userspace-provided firmware name. (But I think to reach this case, you need to have CAP_NET_ADMIN over a network namespace that a special kind of ethernet device is mapped into, so I think this is not a viable attack path in practice.) Fix it by rejecting any firmware names containing \u0026quot;..\u0026quot; path components. For what it\u0026apos;s worth, I went looking and haven\u0026apos;t found any USB device drivers that use the firmware loader dangerously.(CVE-2024-47742)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: vhost_vdpa: assign irq bypass producer token correctly We used to call irq_bypass_unregister_producer() in vhost_vdpa_setup_vq_irq() which is problematic as we don\u0026apos;t know if the token pointer is still valid or not. Actually, we use the eventfd_ctx as the token so the life cycle of the token should be bound to the VHOST_SET_VRING_CALL instead of vhost_vdpa_setup_vq_irq() which could be called by set_status(). Fixing this by setting up irq bypass producer\u0026apos;s token when handling VHOST_SET_VRING_CALL and un-registering the producer before calling vhost_vring_ioctl() to prevent a possible use after free as eventfd could have been released in vhost_vring_ioctl(). And such registering and unregistering will only be done if DRIVER_OK is set.(CVE-2024-47748)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: PCI: keystone: Fix if-statement expression in ks_pcie_quirk() This code accidentally uses \u0026amp;\u0026amp; where || was intended. It potentially results in a NULL dereference. Thus, fix the if-statement expression to use the correct condition. [kwilczynski: commit log](CVE-2024-47756)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: nbd: fix race between timeout and normal completion If request timetout is handled by nbd_requeue_cmd(), normal completion has to be stopped for avoiding to complete this requeued request, other use-after-free can be triggered. Fix the race by clearing NBD_CMD_INFLIGHT in nbd_requeue_cmd(), meantime make sure that cmd-\u0026gt;lock is grabbed for clearing the flag and the requeue.(CVE-2024-49855)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: efistub/tpm: Use ACPI reclaim memory for event log to avoid corruption The TPM event log table is a Linux specific construct, where the data produced by the GetEventLog() boot service is cached in memory, and passed on to the OS using an EFI configuration table. The use of EFI_LOADER_DATA here results in the region being left unreserved in the E820 memory map constructed by the EFI stub, and this is the memory description that is passed on to the incoming kernel by kexec, which is therefore unaware that the region should be reserved. Even though the utility of the TPM2 event log after a kexec is questionable, any corruption might send the parsing code off into the weeds and crash the kernel. So let\u0026apos;s use EFI_ACPI_RECLAIM_MEMORY instead, which is always treated as reserved by the E820 conversion logic.(CVE-2024-49858)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ACPI: sysfs: validate return type of _STR method Only buffer objects are valid return values of _STR. If something else is returned description_show() will access invalid memory.(CVE-2024-49860)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: vhost/scsi: null-ptr-dereference in vhost_scsi_get_req() Since commit 3f8ca2e115e5 (\u0026quot;vhost/scsi: Extract common handling code from control queue handler\u0026quot;) a null pointer dereference bug can be triggered when guest sends an SCSI AN request. In vhost_scsi_ctl_handle_vq(), `vc.target` is assigned with `\u0026amp;v_req.tmf.lun[1]` within a switch-case block and is then passed to vhost_scsi_get_req() which extracts `vc-\u0026gt;req` and `tpg`. However, for a `VIRTIO_SCSI_T_AN_*` request, tpg is not required, so `vc.target` is set to NULL in this branch. Later, in vhost_scsi_get_req(), `vc-\u0026gt;target` is dereferenced without being checked, leading to a null pointer dereference bug. This bug can be triggered from guest. When this bug occurs, the vhost_worker process is killed while holding `vq-\u0026gt;mutex` and the corresponding tpg will remain occupied indefinitely. Below is the KASAN report: Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] CPU: 1 PID: 840 Comm: poc Not tainted 6.10.0+ #1 Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:vhost_scsi_get_req+0x165/0x3a0 Code: 00 fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 2b 02 00 00 48 b8 00 00 00 00 00 fc ff df 4d 8b 65 30 4c 89 e2 48 c1 ea 03 \u0026lt;0f\u0026gt; b6 04 02 4c 89 e2 83 e2 07 38 d0 7f 08 84 c0 0f 85 be 01 00 00 RSP: 0018:ffff888017affb50 EFLAGS: 00010246 RAX: dffffc0000000000 RBX: ffff88801b000000 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff888017affcb8 RBP: ffff888017affb80 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 R13: ffff888017affc88 R14: ffff888017affd1c R15: ffff888017993000 FS: 000055556e076500(0000) GS:ffff88806b100000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000200027c0 CR3: 0000000010ed0004 CR4: 0000000000370ef0 Call Trace: \u0026lt;TASK\u0026gt; ? show_regs+0x86/0xa0 ? die_addr+0x4b/0xd0 ? exc_general_protection+0x163/0x260 ? asm_exc_general_protection+0x27/0x30 ? vhost_scsi_get_req+0x165/0x3a0 vhost_scsi_ctl_handle_vq+0x2a4/0xca0 ? __pfx_vhost_scsi_ctl_handle_vq+0x10/0x10 ? __switch_to+0x721/0xeb0 ? __schedule+0xda5/0x5710 ? __kasan_check_write+0x14/0x30 ? _raw_spin_lock+0x82/0xf0 vhost_scsi_ctl_handle_kick+0x52/0x90 vhost_run_work_list+0x134/0x1b0 vhost_task_fn+0x121/0x350 ... \u0026lt;/TASK\u0026gt; ---[ end trace 0000000000000000 ]--- Let\u0026apos;s add a check in vhost_scsi_get_req. [whitespace fixes](CVE-2024-49863)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ocfs2: fix possible null-ptr-deref in ocfs2_set_buffer_uptodate When doing cleanup, if flags without OCFS2_BH_READAHEAD, it may trigger NULL pointer dereference in the following ocfs2_set_buffer_uptodate() if bh is NULL.(CVE-2024-49877)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm: omapdrm: Add missing check for alloc_ordered_workqueue As it may return NULL pointer and cause NULL pointer dereference. Add check for the return value of alloc_ordered_workqueue.(CVE-2024-49879)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ext4: update orig_path in ext4_find_extent() In ext4_find_extent(), if the path is not big enough, we free it and set *orig_path to NULL. But after reallocating and successfully initializing the path, we don\u0026apos;t update *orig_path, in which case the caller gets a valid path but a NULL ppath, and this may cause a NULL pointer dereference or a path memory leak. For example: ext4_split_extent path = *ppath = 2000 ext4_find_extent if (depth \u0026gt; path[0].p_maxdepth) kfree(path = 2000); *orig_path = path = NULL; path = kcalloc() = 3000 ext4_split_extent_at(*ppath = NULL) path = *ppath; ex = path[depth].p_ext; // NULL pointer dereference! ================================================================== BUG: kernel NULL pointer dereference, address: 0000000000000010 CPU: 6 UID: 0 PID: 576 Comm: fsstress Not tainted 6.11.0-rc2-dirty #847 RIP: 0010:ext4_split_extent_at+0x6d/0x560 Call Trace: \u0026lt;TASK\u0026gt; ext4_split_extent.isra.0+0xcb/0x1b0 ext4_ext_convert_to_initialized+0x168/0x6c0 ext4_ext_handle_unwritten_extents+0x325/0x4d0 ext4_ext_map_blocks+0x520/0xdb0 ext4_map_blocks+0x2b0/0x690 ext4_iomap_begin+0x20e/0x2c0 [...] ================================================================== Therefore, *orig_path is updated when the extent lookup succeeds, so that the caller can safely use path or *ppath.(CVE-2024-49881)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ext4: fix double brelse() the buffer of the extents path In ext4_ext_try_to_merge_up(), set path[1].p_bh to NULL after it has been released, otherwise it may be released twice. An example of what triggers this is as follows: split2 map split1 |--------|-------|--------| ext4_ext_map_blocks ext4_ext_handle_unwritten_extents ext4_split_convert_extents // path-\u0026gt;p_depth == 0 ext4_split_extent // 1. do split1 ext4_split_extent_at |ext4_ext_insert_extent | ext4_ext_create_new_leaf | ext4_ext_grow_indepth | le16_add_cpu(\u0026amp;neh-\u0026gt;eh_depth, 1) | ext4_find_extent | // return -ENOMEM |// get error and try zeroout |path = ext4_find_extent | path-\u0026gt;p_depth = 1 |ext4_ext_try_to_merge | ext4_ext_try_to_merge_up | path-\u0026gt;p_depth = 0 | brelse(path[1].p_bh) ---\u0026gt; not set to NULL here |// zeroout success // 2. update path ext4_find_extent // 3. do split2 ext4_split_extent_at ext4_ext_insert_extent ext4_ext_create_new_leaf ext4_ext_grow_indepth le16_add_cpu(\u0026amp;neh-\u0026gt;eh_depth, 1) ext4_find_extent path[0].p_bh = NULL; path-\u0026gt;p_depth = 1 read_extent_tree_block ---\u0026gt; return err // path[1].p_bh is still the old value ext4_free_ext_path ext4_ext_drop_refs // path-\u0026gt;p_depth == 1 brelse(path[1].p_bh) ---\u0026gt; brelse a buffer twice Finally got the following WARRNING when removing the buffer from lru: ============================================ VFS: brelse: Trying to free free buffer WARNING: CPU: 2 PID: 72 at fs/buffer.c:1241 __brelse+0x58/0x90 CPU: 2 PID: 72 Comm: kworker/u19:1 Not tainted 6.9.0-dirty #716 RIP: 0010:__brelse+0x58/0x90 Call Trace: \u0026lt;TASK\u0026gt; __find_get_block+0x6e7/0x810 bdev_getblk+0x2b/0x480 __ext4_get_inode_loc+0x48a/0x1240 ext4_get_inode_loc+0xb2/0x150 ext4_reserve_inode_write+0xb7/0x230 __ext4_mark_inode_dirty+0x144/0x6a0 ext4_ext_insert_extent+0x9c8/0x3230 ext4_ext_map_blocks+0xf45/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] ============================================(CVE-2024-49882)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ext4: aovid use-after-free in ext4_ext_insert_extent() As Ojaswin mentioned in Link, in ext4_ext_insert_extent(), if the path is reallocated in ext4_ext_create_new_leaf(), we\u0026apos;ll use the stale path and cause UAF. Below is a sample trace with dummy values: ext4_ext_insert_extent path = *ppath = 2000 ext4_ext_create_new_leaf(ppath) ext4_find_extent(ppath) path = *ppath = 2000 if (depth \u0026gt; path[0].p_maxdepth) kfree(path = 2000); *ppath = path = NULL; path = kcalloc() = 3000 *ppath = 3000; return path; /* here path is still 2000, UAF! */ eh = path[depth].p_hdr ================================================================== BUG: KASAN: slab-use-after-free in ext4_ext_insert_extent+0x26d4/0x3330 Read of size 8 at addr ffff8881027bf7d0 by task kworker/u36:1/179 CPU: 3 UID: 0 PID: 179 Comm: kworker/u6:1 Not tainted 6.11.0-rc2-dirty #866 Call Trace: \u0026lt;TASK\u0026gt; ext4_ext_insert_extent+0x26d4/0x3330 ext4_ext_map_blocks+0xe22/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 [...] Allocated by task 179: ext4_find_extent+0x81c/0x1f70 ext4_ext_map_blocks+0x146/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 ext4_writepages+0x26d/0x4e0 do_writepages+0x175/0x700 [...] Freed by task 179: kfree+0xcb/0x240 ext4_find_extent+0x7c0/0x1f70 ext4_ext_insert_extent+0xa26/0x3330 ext4_ext_map_blocks+0xe22/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 ext4_writepages+0x26d/0x4e0 do_writepages+0x175/0x700 [...] ================================================================== So use *ppath to update the path to avoid the above problem.(CVE-2024-49883)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ext4: fix slab-use-after-free in ext4_split_extent_at() We hit the following use-after-free: ================================================================== BUG: KASAN: slab-use-after-free in ext4_split_extent_at+0xba8/0xcc0 Read of size 2 at addr ffff88810548ed08 by task kworker/u20:0/40 CPU: 0 PID: 40 Comm: kworker/u20:0 Not tainted 6.9.0-dirty #724 Call Trace: \u0026lt;TASK\u0026gt; kasan_report+0x93/0xc0 ext4_split_extent_at+0xba8/0xcc0 ext4_split_extent.isra.0+0x18f/0x500 ext4_split_convert_extents+0x275/0x750 ext4_ext_handle_unwritten_extents+0x73e/0x1580 ext4_ext_map_blocks+0xe20/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] Allocated by task 40: __kmalloc_noprof+0x1ac/0x480 ext4_find_extent+0xf3b/0x1e70 ext4_ext_map_blocks+0x188/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] Freed by task 40: kfree+0xf1/0x2b0 ext4_find_extent+0xa71/0x1e70 ext4_ext_insert_extent+0xa22/0x3260 ext4_split_extent_at+0x3ef/0xcc0 ext4_split_extent.isra.0+0x18f/0x500 ext4_split_convert_extents+0x275/0x750 ext4_ext_handle_unwritten_extents+0x73e/0x1580 ext4_ext_map_blocks+0xe20/0x2dc0 ext4_map_blocks+0x724/0x1700 ext4_do_writepages+0x12d6/0x2a70 [...] ================================================================== The flow of issue triggering is as follows: ext4_split_extent_at path = *ppath ext4_ext_insert_extent(ppath) ext4_ext_create_new_leaf(ppath) ext4_find_extent(orig_path) path = *orig_path read_extent_tree_block // return -ENOMEM or -EIO ext4_free_ext_path(path) kfree(path) *orig_path = NULL a. If err is -ENOMEM: ext4_ext_dirty(path + path-\u0026gt;p_depth) // path use-after-free !!! b. If err is -EIO and we have EXT_DEBUG defined: ext4_ext_show_leaf(path) eh = path[depth].p_hdr // path also use-after-free !!! So when trying to zeroout or fix the extent length, call ext4_find_extent() to update the path. In addition we use *ppath directly as an ext4_ext_show_leaf() input to avoid possible use-after-free when EXT_DEBUG is defined, and to avoid unnecessary path updates.(CVE-2024-49884)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: platform/x86: ISST: Fix the KASAN report slab-out-of-bounds bug Attaching SST PCI device to VM causes \u0026quot;BUG: KASAN: slab-out-of-bounds\u0026quot;. kasan report: [ 19.411889] ================================================================== [ 19.413702] BUG: KASAN: slab-out-of-bounds in _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.415634] Read of size 8 at addr ffff888829e65200 by task cpuhp/16/113 [ 19.417368] [ 19.418627] CPU: 16 PID: 113 Comm: cpuhp/16 Tainted: G E 6.9.0 #10 [ 19.420435] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference Platform, BIOS VMW201.00V.20192059.B64.2207280713 07/28/2022 [ 19.422687] Call Trace: [ 19.424091] \u0026lt;TASK\u0026gt; [ 19.425448] dump_stack_lvl+0x5d/0x80 [ 19.426963] ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.428694] print_report+0x19d/0x52e [ 19.430206] ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [ 19.431837] ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.433539] kasan_report+0xf0/0x170 [ 19.435019] ? _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.436709] _isst_if_get_pci_dev+0x3d5/0x400 [isst_if_common] [ 19.438379] ? __pfx_sched_clock_cpu+0x10/0x10 [ 19.439910] isst_if_cpu_online+0x406/0x58f [isst_if_common] [ 19.441573] ? __pfx_isst_if_cpu_online+0x10/0x10 [isst_if_common] [ 19.443263] ? ttwu_queue_wakelist+0x2c1/0x360 [ 19.444797] cpuhp_invoke_callback+0x221/0xec0 [ 19.446337] cpuhp_thread_fun+0x21b/0x610 [ 19.447814] ? __pfx_cpuhp_thread_fun+0x10/0x10 [ 19.449354] smpboot_thread_fn+0x2e7/0x6e0 [ 19.450859] ? __pfx_smpboot_thread_fn+0x10/0x10 [ 19.452405] kthread+0x29c/0x350 [ 19.453817] ? __pfx_kthread+0x10/0x10 [ 19.455253] ret_from_fork+0x31/0x70 [ 19.456685] ? __pfx_kthread+0x10/0x10 [ 19.458114] ret_from_fork_asm+0x1a/0x30 [ 19.459573] \u0026lt;/TASK\u0026gt; [ 19.460853] [ 19.462055] Allocated by task 1198: [ 19.463410] kasan_save_stack+0x30/0x50 [ 19.464788] kasan_save_track+0x14/0x30 [ 19.466139] __kasan_kmalloc+0xaa/0xb0 [ 19.467465] __kmalloc+0x1cd/0x470 [ 19.468748] isst_if_cdev_register+0x1da/0x350 [isst_if_common] [ 19.470233] isst_if_mbox_init+0x108/0xff0 [isst_if_mbox_msr] [ 19.471670] do_one_initcall+0xa4/0x380 [ 19.472903] do_init_module+0x238/0x760 [ 19.474105] load_module+0x5239/0x6f00 [ 19.475285] init_module_from_file+0xd1/0x130 [ 19.476506] idempotent_init_module+0x23b/0x650 [ 19.477725] __x64_sys_finit_module+0xbe/0x130 [ 19.476506] idempotent_init_module+0x23b/0x650 [ 19.477725] __x64_sys_finit_module+0xbe/0x130 [ 19.478920] do_syscall_64+0x82/0x160 [ 19.480036] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 19.481292] [ 19.482205] The buggy address belongs to the object at ffff888829e65000 which belongs to the cache kmalloc-512 of size 512 [ 19.484818] The buggy address is located 0 bytes to the right of allocated 512-byte region [ffff888829e65000, ffff888829e65200) [ 19.487447] [ 19.488328] The buggy address belongs to the physical page: [ 19.489569] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff888829e60c00 pfn:0x829e60 [ 19.491140] head: order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0 [ 19.492466] anon flags: 0x57ffffc0000840(slab|head|node=1|zone=2|lastcpupid=0x1fffff) [ 19.493914] page_type: 0xffffffff() [ 19.494988] raw: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [ 19.496451] raw: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [ 19.497906] head: 0057ffffc0000840 ffff88810004cc80 0000000000000000 0000000000000001 [ 19.499379] head: ffff888829e60c00 0000000080200018 00000001ffffffff 0000000000000000 [ 19.500844] head: 0057ffffc0000003 ffffea0020a79801 ffffea0020a79848 00000000ffffffff [ 19.502316] head: 0000000800000000 0000000000000000 00000000ffffffff 0000000000000000 [ 19.503784] page dumped because: k ---truncated---(CVE-2024-49886)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ext4: avoid use-after-free in ext4_ext_show_leaf() In ext4_find_extent(), path may be freed by error or be reallocated, so using a previously saved *ppath may have been freed and thus may trigger use-after-free, as follows: ext4_split_extent path = *ppath; ext4_split_extent_at(ppath) path = ext4_find_extent(ppath) ext4_split_extent_at(ppath) // ext4_find_extent fails to free path // but zeroout succeeds ext4_ext_show_leaf(inode, path) eh = path[depth].p_hdr // path use-after-free !!! Similar to ext4_split_extent_at(), we use *ppath directly as an input to ext4_ext_show_leaf(). Fix a spelling error by the way. Same problem in ext4_ext_handle_unwritten_extents(). Since \u0026apos;path\u0026apos; is only used in ext4_ext_show_leaf(), remove \u0026apos;path\u0026apos; and use *ppath directly. This issue is triggered only when EXT_DEBUG is defined and therefore does not affect functionality.(CVE-2024-49889)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add null check for top_pipe_to_program in commit_planes_for_stream This commit addresses a null pointer dereference issue in the `commit_planes_for_stream` function at line 4140. The issue could occur when `top_pipe_to_program` is null. The fix adds a check to ensure `top_pipe_to_program` is not null before accessing its stream_res. This prevents a null pointer dereference. Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.c:4140 commit_planes_for_stream() error: we previously assumed \u0026apos;top_pipe_to_program\u0026apos; could be null (see line 3906)(CVE-2024-49913)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add NULL check for clk_mgr and clk_mgr-\u0026gt;funcs in dcn30_init_hw This commit addresses a potential null pointer dereference issue in the `dcn30_init_hw` function. The issue could occur when `dc-\u0026gt;clk_mgr` or `dc-\u0026gt;clk_mgr-\u0026gt;funcs` is null. The fix adds a check to ensure `dc-\u0026gt;clk_mgr` and `dc-\u0026gt;clk_mgr-\u0026gt;funcs` is not null before accessing its functions. This prevents a potential null pointer dereference. Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn30/dcn30_hwseq.c:789 dcn30_init_hw() error: we previously assumed \u0026apos;dc-\u0026gt;clk_mgr\u0026apos; could be null (see line 628)(CVE-2024-49917)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check null pointers before using them [WHAT \u0026amp; HOW] These pointers are null checked previously in the same function, indicating they might be null as reported by Coverity. As a result, they need to be checked when used again. This fixes 3 FORWARD_NULL issue reported by Coverity.(CVE-2024-49922)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: fbdev: pxafb: Fix possible use after free in pxafb_task() In the pxafb_probe function, it calls the pxafb_init_fbinfo function, after which \u0026amp;fbi-\u0026gt;task is associated with pxafb_task. Moreover, within this pxafb_init_fbinfo function, the pxafb_blank function within the \u0026amp;pxafb_ops struct is capable of scheduling work. If we remove the module which will call pxafb_remove to make cleanup, it will call unregister_framebuffer function which can call do_unregister_framebuffer to free fbi-\u0026gt;fb through put_fb_info(fb_info), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows: CPU0 CPU1 | pxafb_task pxafb_remove | unregister_framebuffer(info) | do_unregister_framebuffer(fb_info) | put_fb_info(fb_info) | // free fbi-\u0026gt;fb | set_ctrlr_state(fbi, state) | __pxafb_lcd_power(fbi, 0) | fbi-\u0026gt;lcd_power(on, \u0026amp;fbi-\u0026gt;fb.var) | //use fbi-\u0026gt;fb Fix it by ensuring that the work is canceled before proceeding with the cleanup in pxafb_remove. Note that only root user can remove the driver at runtime.(CVE-2024-49924)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: blk_iocost: fix more out of bound shifts Recently running UBSAN caught few out of bound shifts in the ioc_forgive_debts() function: UBSAN: shift-out-of-bounds in block/blk-iocost.c:2142:38 shift exponent 80 is too large for 64-bit type \u0026apos;u64\u0026apos; (aka \u0026apos;unsigned long long\u0026apos;) ... UBSAN: shift-out-of-bounds in block/blk-iocost.c:2144:30 shift exponent 80 is too large for 64-bit type \u0026apos;u64\u0026apos; (aka \u0026apos;unsigned long long\u0026apos;) ... Call Trace: \u0026lt;IRQ\u0026gt; dump_stack_lvl+0xca/0x130 __ubsan_handle_shift_out_of_bounds+0x22c/0x280 ? __lock_acquire+0x6441/0x7c10 ioc_timer_fn+0x6cec/0x7750 ? blk_iocost_init+0x720/0x720 ? call_timer_fn+0x5d/0x470 call_timer_fn+0xfa/0x470 ? blk_iocost_init+0x720/0x720 __run_timer_base+0x519/0x700 ... Actual impact of this issue was not identified but I propose to fix the undefined behaviour. The proposed fix to prevent those out of bound shifts consist of precalculating exponent before using it the shift operations by taking min value from the actual exponent and maximum possible number of bits.(CVE-2024-49933)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: fs/inode: Prevent dump_mapping() accessing invalid dentry.d_name.name It\u0026apos;s observed that a crash occurs during hot-remove a memory device, in which user is accessing the hugetlb. See calltrace as following: ------------[ cut here ]------------ WARNING: CPU: 1 PID: 14045 at arch/x86/mm/fault.c:1278 do_user_addr_fault+0x2a0/0x790 Modules linked in: kmem device_dax cxl_mem cxl_pmem cxl_port cxl_pci dax_hmem dax_pmem nd_pmem cxl_acpi nd_btt cxl_core crc32c_intel nvme virtiofs fuse nvme_core nfit libnvdimm dm_multipath scsi_dh_rdac scsi_dh_emc s mirror dm_region_hash dm_log dm_mod CPU: 1 PID: 14045 Comm: daxctl Not tainted 6.10.0-rc2-lizhijian+ #492 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:do_user_addr_fault+0x2a0/0x790 Code: 48 8b 00 a8 04 0f 84 b5 fe ff ff e9 1c ff ff ff 4c 89 e9 4c 89 e2 be 01 00 00 00 bf 02 00 00 00 e8 b5 ef 24 00 e9 42 fe ff ff \u0026lt;0f\u0026gt; 0b 48 83 c4 08 4c 89 ea 48 89 ee 4c 89 e7 5b 5d 41 5c 41 5d 41 RSP: 0000:ffffc90000a575f0 EFLAGS: 00010046 RAX: ffff88800c303600 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000001000 RSI: ffffffff82504162 RDI: ffffffff824b2c36 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffffc90000a57658 R13: 0000000000001000 R14: ffff88800bc2e040 R15: 0000000000000000 FS: 00007f51cb57d880(0000) GS:ffff88807fd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000001000 CR3: 00000000072e2004 CR4: 00000000001706f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: \u0026lt;TASK\u0026gt; ? __warn+0x8d/0x190 ? do_user_addr_fault+0x2a0/0x790 ? report_bug+0x1c3/0x1d0 ? handle_bug+0x3c/0x70 ? exc_invalid_op+0x14/0x70 ? asm_exc_invalid_op+0x16/0x20 ? do_user_addr_fault+0x2a0/0x790 ? exc_page_fault+0x31/0x200 exc_page_fault+0x68/0x200 \u0026lt;...snip...\u0026gt; BUG: unable to handle page fault for address: 0000000000001000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0 Oops: Oops: 0000 [#1] PREEMPT SMP PTI ---[ end trace 0000000000000000 ]--- BUG: unable to handle page fault for address: 0000000000001000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0 Oops: Oops: 0000 [#1] PREEMPT SMP PTI CPU: 1 PID: 14045 Comm: daxctl Kdump: loaded Tainted: G W 6.10.0-rc2-lizhijian+ #492 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:dentry_name+0x1f4/0x440 \u0026lt;...snip...\u0026gt; ? dentry_name+0x2fa/0x440 vsnprintf+0x1f3/0x4f0 vprintk_store+0x23a/0x540 vprintk_emit+0x6d/0x330 _printk+0x58/0x80 dump_mapping+0x10b/0x1a0 ? __pfx_free_object_rcu+0x10/0x10 __dump_page+0x26b/0x3e0 ? vprintk_emit+0xe0/0x330 ? _printk+0x58/0x80 ? dump_page+0x17/0x50 dump_page+0x17/0x50 do_migrate_range+0x2f7/0x7f0 ? do_migrate_range+0x42/0x7f0 ? offline_pages+0x2f4/0x8c0 offline_pages+0x60a/0x8c0 memory_subsys_offline+0x9f/0x1c0 ? lockdep_hardirqs_on+0x77/0x100 ? _raw_spin_unlock_irqrestore+0x38/0x60 device_offline+0xe3/0x110 state_store+0x6e/0xc0 kernfs_fop_write_iter+0x143/0x200 vfs_write+0x39f/0x560 ksys_write+0x65/0xf0 do_syscall_64+0x62/0x130 Previously, some sanity check have been done in dump_mapping() before the print facility parsing \u0026apos;%pd\u0026apos; though, it\u0026apos;s still possible to run into an invalid dentry.d_name.name. Since dump_mapping() only needs to dump the filename only, retrieve it by itself in a safer way to prevent an unnecessary crash. Note that either retrieving the filename with \u0026apos;%pd\u0026apos; or strncpy_from_kernel_nofault(), the filename could be unreliable.(CVE-2024-49934)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: net/xen-netback: prevent UAF in xenvif_flush_hash() During the list_for_each_entry_rcu iteration call of xenvif_flush_hash, kfree_rcu does not exist inside the rcu read critical section, so if kfree_rcu is called when the rcu grace period ends during the iteration, UAF occurs when accessing head-\u0026gt;next after the entry becomes free. Therefore, to solve this, you need to change it to list_for_each_entry_safe.(CVE-2024-49936)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: l2tp: prevent possible tunnel refcount underflow When a session is created, it sets a backpointer to its tunnel. When the session refcount drops to 0, l2tp_session_free drops the tunnel refcount if session-\u0026gt;tunnel is non-NULL. However, session-\u0026gt;tunnel is set in l2tp_session_create, before the tunnel refcount is incremented by l2tp_session_register, which leaves a small window where session-\u0026gt;tunnel is non-NULL when the tunnel refcount hasn\u0026apos;t been bumped. Moving the assignment to l2tp_session_register is trivial but l2tp_session_create calls l2tp_session_set_header_len which uses session-\u0026gt;tunnel to get the tunnel\u0026apos;s encap. Add an encap arg to l2tp_session_set_header_len to avoid using session-\u0026gt;tunnel. If l2tpv3 sessions have colliding IDs, it is possible for l2tp_v3_session_get to race with l2tp_session_register and fetch a session which doesn\u0026apos;t yet have session-\u0026gt;tunnel set. Add a check for this case.(CVE-2024-49940)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix uaf in l2cap_connect [Syzbot reported] BUG: KASAN: slab-use-after-free in l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949 Read of size 8 at addr ffff8880241e9800 by task kworker/u9:0/54 CPU: 0 UID: 0 PID: 54 Comm: kworker/u9:0 Not tainted 6.11.0-rc6-syzkaller-00268-g788220eee30d #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 Workqueue: hci2 hci_rx_work Call Trace: \u0026lt;TASK\u0026gt; __dump_stack lib/dump_stack.c:93 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:119 print_address_description mm/kasan/report.c:377 [inline] print_report+0xc3/0x620 mm/kasan/report.c:488 kasan_report+0xd9/0x110 mm/kasan/report.c:601 l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949 l2cap_connect_req net/bluetooth/l2cap_core.c:4080 [inline] l2cap_bredr_sig_cmd net/bluetooth/l2cap_core.c:4772 [inline] l2cap_sig_channel net/bluetooth/l2cap_core.c:5543 [inline] l2cap_recv_frame+0xf0b/0x8eb0 net/bluetooth/l2cap_core.c:6825 l2cap_recv_acldata+0x9b4/0xb70 net/bluetooth/l2cap_core.c:7514 hci_acldata_packet net/bluetooth/hci_core.c:3791 [inline] hci_rx_work+0xaab/0x1610 net/bluetooth/hci_core.c:4028 process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231 process_scheduled_works kernel/workqueue.c:3312 [inline] worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389 kthread+0x2c1/0x3a0 kernel/kthread.c:389 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 ... Freed by task 5245: kasan_save_stack+0x33/0x60 mm/kasan/common.c:47 kasan_save_track+0x14/0x30 mm/kasan/common.c:68 kasan_save_free_info+0x3b/0x60 mm/kasan/generic.c:579 poison_slab_object+0xf7/0x160 mm/kasan/common.c:240 __kasan_slab_free+0x32/0x50 mm/kasan/common.c:256 kasan_slab_free include/linux/kasan.h:184 [inline] slab_free_hook mm/slub.c:2256 [inline] slab_free mm/slub.c:4477 [inline] kfree+0x12a/0x3b0 mm/slub.c:4598 l2cap_conn_free net/bluetooth/l2cap_core.c:1810 [inline] kref_put include/linux/kref.h:65 [inline] l2cap_conn_put net/bluetooth/l2cap_core.c:1822 [inline] l2cap_conn_del+0x59d/0x730 net/bluetooth/l2cap_core.c:1802 l2cap_connect_cfm+0x9e6/0xf80 net/bluetooth/l2cap_core.c:7241 hci_connect_cfm include/net/bluetooth/hci_core.h:1960 [inline] hci_conn_failed+0x1c3/0x370 net/bluetooth/hci_conn.c:1265 hci_abort_conn_sync+0x75a/0xb50 net/bluetooth/hci_sync.c:5583 abort_conn_sync+0x197/0x360 net/bluetooth/hci_conn.c:2917 hci_cmd_sync_work+0x1a4/0x410 net/bluetooth/hci_sync.c:328 process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231 process_scheduled_works kernel/workqueue.c:3312 [inline] worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389 kthread+0x2c1/0x3a0 kernel/kthread.c:389 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244(CVE-2024-49950)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: static_call: Replace pointless WARN_ON() in static_call_module_notify() static_call_module_notify() triggers a WARN_ON(), when memory allocation fails in __static_call_add_module(). That\u0026apos;s not really justified, because the failure case must be correctly handled by the well known call chain and the error code is passed through to the initiating userspace application. A memory allocation fail is not a fatal problem, but the WARN_ON() takes the machine out when panic_on_warn is set. Replace it with a pr_warn().(CVE-2024-49954)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ACPI: battery: Fix possible crash when unregistering a battery hook When a battery hook returns an error when adding a new battery, then the battery hook is automatically unregistered. However the battery hook provider cannot know that, so it will later call battery_hook_unregister() on the already unregistered battery hook, resulting in a crash. Fix this by using the list head to mark already unregistered battery hooks as already being unregistered so that they can be ignored by battery_hook_unregister().(CVE-2024-49955)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ocfs2: reserve space for inline xattr before attaching reflink tree One of our customers reported a crash and a corrupted ocfs2 filesystem. The crash was due to the detection of corruption. Upon troubleshooting, the fsck -fn output showed the below corruption [EXTENT_LIST_FREE] Extent list in owner 33080590 claims 230 as the next free chain record, but fsck believes the largest valid value is 227. Clamp the next record value? n The stat output from the debugfs.ocfs2 showed the following corruption where the \u0026quot;Next Free Rec:\u0026quot; had overshot the \u0026quot;Count:\u0026quot; in the root metadata block. Inode: 33080590 Mode: 0640 Generation: 2619713622 (0x9c25a856) FS Generation: 904309833 (0x35e6ac49) CRC32: 00000000 ECC: 0000 Type: Regular Attr: 0x0 Flags: Valid Dynamic Features: (0x16) HasXattr InlineXattr Refcounted Extended Attributes Block: 0 Extended Attributes Inline Size: 256 User: 0 (root) Group: 0 (root) Size: 281320357888 Links: 1 Clusters: 141738 ctime: 0x66911b56 0x316edcb8 -- Fri Jul 12 06:02:30.829349048 2024 atime: 0x66911d6b 0x7f7a28d -- Fri Jul 12 06:11:23.133669517 2024 mtime: 0x66911b56 0x12ed75d7 -- Fri Jul 12 06:02:30.317552087 2024 dtime: 0x0 -- Wed Dec 31 17:00:00 1969 Refcount Block: 2777346 Last Extblk: 2886943 Orphan Slot: 0 Sub Alloc Slot: 0 Sub Alloc Bit: 14 Tree Depth: 1 Count: 227 Next Free Rec: 230 ## Offset Clusters Block# 0 0 2310 2776351 1 2310 2139 2777375 2 4449 1221 2778399 3 5670 731 2779423 4 6401 566 2780447 ....... .... ....... ....... .... ....... The issue was in the reflink workfow while reserving space for inline xattr. The problematic function is ocfs2_reflink_xattr_inline(). By the time this function is called the reflink tree is already recreated at the destination inode from the source inode. At this point, this function reserves space for inline xattrs at the destination inode without even checking if there is space at the root metadata block. It simply reduces the l_count from 243 to 227 thereby making space of 256 bytes for inline xattr whereas the inode already has extents beyond this index (in this case up to 230), thereby causing corruption. The fix for this is to reserve space for inline metadata at the destination inode before the reflink tree gets recreated. The customer has verified the fix.(CVE-2024-49958)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ocfs2: remove unreasonable unlock in ocfs2_read_blocks Patch series \u0026quot;Misc fixes for ocfs2_read_blocks\u0026quot;, v5. This series contains 2 fixes for ocfs2_read_blocks(). The first patch fix the issue reported by syzbot, which detects bad unlock balance in ocfs2_read_blocks(). The second patch fixes an issue reported by Heming Zhao when reviewing above fix. This patch (of 2): There was a lock release before exiting, so remove the unreasonable unlock.(CVE-2024-49965)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: r8169: add tally counter fields added with RTL8125 RTL8125 added fields to the tally counter, what may result in the chip dma\u0026apos;ing these new fields to unallocated memory. Therefore make sure that the allocated memory area is big enough to hold all of the tally counter values, even if we use only parts of it.(CVE-2024-49973)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: uprobes: fix kernel info leak via \u0026quot;[uprobes]\u0026quot; vma xol_add_vma() maps the uninitialized page allocated by __create_xol_area() into userspace. On some architectures (x86) this memory is readable even without VM_READ, VM_EXEC results in the same pgprot_t as VM_EXEC|VM_READ, although this doesn\u0026apos;t really matter, debugger can read this memory anyway.(CVE-2024-49975)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: gso: fix udp gso fraglist segmentation after pull from frag_list Detect gso fraglist skbs with corrupted geometry (see below) and pass these to skb_segment instead of skb_segment_list, as the first can segment them correctly. Valid SKB_GSO_FRAGLIST skbs - consist of two or more segments - the head_skb holds the protocol headers plus first gso_size - one or more frag_list skbs hold exactly one segment - all but the last must be gso_size Optional datapath hooks such as NAT and BPF (bpf_skb_pull_data) can modify these skbs, breaking these invariants. In extreme cases they pull all data into skb linear. For UDP, this causes a NULL ptr deref in __udpv4_gso_segment_list_csum at udp_hdr(seg-\u0026gt;next)-\u0026gt;dest. Detect invalid geometry due to pull, by checking head_skb size. Don\u0026apos;t just drop, as this may blackhole a destination. Convert to be able to pass to regular skb_segment.(CVE-2024-49978)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: media: venus: fix use after free bug in venus_remove due to race condition in venus_probe, core-\u0026gt;work is bound with venus_sys_error_handler, which is used to handle error. The code use core-\u0026gt;sys_err_done to make sync work. The core-\u0026gt;work is started in venus_event_notify. If we call venus_remove, there might be an unfished work. The possible sequence is as follows: CPU0 CPU1 |venus_sys_error_handler venus_remove | hfi_destroy | venus_hfi_destroy | kfree(hdev); | |hfi_reinit |venus_hfi_queues_reinit |//use hdev Fix it by canceling the work in venus_remove.(CVE-2024-49981)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm/stm: Avoid use-after-free issues with crtc and plane ltdc_load() calls functions drm_crtc_init_with_planes(), drm_universal_plane_init() and drm_encoder_init(). These functions should not be called with parameters allocated with devm_kzalloc() to avoid use-after-free issues [1]. Use allocations managed by the DRM framework. Found by Linux Verification Center (linuxtesting.org). [1] https://lore.kernel.org/lkml/u366i76e3qhh3ra5oxrtngjtm2u5lterkekcz6y2jkndhuxzli@diujon4h7qwb/(CVE-2024-49992)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: tipc: guard against string buffer overrun Smatch reports that copying media_name and if_name to name_parts may overwrite the destination. .../bearer.c:166 bearer_name_validate() error: strcpy() \u0026apos;media_name\u0026apos; too large for \u0026apos;name_parts-\u0026gt;media_name\u0026apos; (32 vs 16) .../bearer.c:167 bearer_name_validate() error: strcpy() \u0026apos;if_name\u0026apos; too large for \u0026apos;name_parts-\u0026gt;if_name\u0026apos; (1010102 vs 16) This does seem to be the case so guard against this possibility by using strscpy() and failing if truncation occurs. Introduced by commit b97bf3fd8f6a (\u0026quot;[TIPC] Initial merge\u0026quot;) Compile tested only.(CVE-2024-49995)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: cifs: Fix buffer overflow when parsing NFS reparse points ReparseDataLength is sum of the InodeType size and DataBuffer size. So to get DataBuffer size it is needed to subtract InodeType\u0026apos;s size from ReparseDataLength. Function cifs_strndup_from_utf16() is currentlly accessing buf-\u0026gt;DataBuffer at position after the end of the buffer because it does not subtract InodeType size from the length. Fix this problem and correctly subtract variable len. Member InodeType is present only when reparse buffer is large enough. Check for ReparseDataLength before accessing InodeType to prevent another invalid memory access. Major and minor rdev values are present also only when reparse buffer is large enough. Check for reparse buffer size before calling reparse_mkdev().(CVE-2024-49996)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_cmd_802_11_scan_ext() Replace one-element array with a flexible-array member in `struct host_cmd_ds_802_11_scan_ext`. With this, fix the following warning: elo 16 17:51:58 surfacebook kernel: ------------[ cut here ]------------ elo 16 17:51:58 surfacebook kernel: memcpy: detected field-spanning write (size 243) of single field \u0026quot;ext_scan-\u0026gt;tlv_buffer\u0026quot; at drivers/net/wireless/marvell/mwifiex/scan.c:2239 (size 1) elo 16 17:51:58 surfacebook kernel: WARNING: CPU: 0 PID: 498 at drivers/net/wireless/marvell/mwifiex/scan.c:2239 mwifiex_cmd_802_11_scan_ext+0x83/0x90 [mwifiex](CVE-2024-50008)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ext4: dax: fix overflowing extents beyond inode size when partially writing The dax_iomap_rw() does two things in each iteration: map written blocks and copy user data to blocks. If the process is killed by user(See signal handling in dax_iomap_iter()), the copied data will be returned and added on inode size, which means that the length of written extents may exceed the inode size, then fsck will fail. An example is given as: dd if=/dev/urandom of=file bs=4M count=1 dax_iomap_rw iomap_iter // round 1 ext4_iomap_begin ext4_iomap_alloc // allocate 0~2M extents(written flag) dax_iomap_iter // copy 2M data iomap_iter // round 2 iomap_iter_advance iter-\u0026gt;pos += iter-\u0026gt;processed // iter-\u0026gt;pos = 2M ext4_iomap_begin ext4_iomap_alloc // allocate 2~4M extents(written flag) dax_iomap_iter fatal_signal_pending done = iter-\u0026gt;pos - iocb-\u0026gt;ki_pos // done = 2M ext4_handle_inode_extension ext4_update_inode_size // inode size = 2M fsck reports: Inode 13, i_size is 2097152, should be 4194304. Fix? Fix the problem by truncating extents if the written length is smaller than expected.(CVE-2024-50015)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Avoid overflow assignment in link_dp_cts sampling_rate is an uint8_t but is assigned an unsigned int, and thus it can overflow. As a result, sampling_rate is changed to uint32_t. Similarly, LINK_QUAL_PATTERN_SET has a size of 2 bits, and it should only be assigned to a value less or equal than 4. This fixes 2 INTEGER_OVERFLOW issues reported by Coverity.(CVE-2024-50016)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: thermal: core: Reference count the zone in thermal_zone_get_by_id() There are places in the thermal netlink code where nothing prevents the thermal zone object from going away while being accessed after it has been returned by thermal_zone_get_by_id(). To address this, make thermal_zone_get_by_id() get a reference on the thermal zone device object to be returned with the help of get_device(), under thermal_list_lock, and adjust all of its callers to this change with the help of the cleanup.h infrastructure.(CVE-2024-50028)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: slip: make slhc_remember() more robust against malicious packets syzbot found that slhc_remember() was missing checks against malicious packets [1]. slhc_remember() only checked the size of the packet was at least 20, which is not good enough. We need to make sure the packet includes the IPv4 and TCP header that are supposed to be carried. Add iph and th pointers to make the code more readable. [1] BUG: KMSAN: uninit-value in slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666 slhc_remember+0x2e8/0x7b0 drivers/net/slip/slhc.c:666 ppp_receive_nonmp_frame+0xe45/0x35e0 drivers/net/ppp/ppp_generic.c:2455 ppp_receive_frame drivers/net/ppp/ppp_generic.c:2372 [inline] ppp_do_recv+0x65f/0x40d0 drivers/net/ppp/ppp_generic.c:2212 ppp_input+0x7dc/0xe60 drivers/net/ppp/ppp_generic.c:2327 pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379 sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113 __release_sock+0x1da/0x330 net/core/sock.c:3072 release_sock+0x6b/0x250 net/core/sock.c:3626 pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 ____sys_sendmsg+0x903/0xb60 net/socket.c:2602 ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was created at: slab_post_alloc_hook mm/slub.c:4091 [inline] slab_alloc_node mm/slub.c:4134 [inline] kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4186 kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587 __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678 alloc_skb include/linux/skbuff.h:1322 [inline] sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732 pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 ____sys_sendmsg+0x903/0xb60 net/socket.c:2602 ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f CPU: 0 UID: 0 PID: 5460 Comm: syz.2.33 Not tainted 6.12.0-rc2-syzkaller-00006-g87d6aab2389e #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50033)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ppp: fix ppp_async_encode() illegal access syzbot reported an issue in ppp_async_encode() [1] In this case, pppoe_sendmsg() is called with a zero size. Then ppp_async_encode() is called with an empty skb. BUG: KMSAN: uninit-value in ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline] BUG: KMSAN: uninit-value in ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675 ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline] ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675 ppp_async_send+0x130/0x1b0 drivers/net/ppp/ppp_async.c:634 ppp_channel_bridge_input drivers/net/ppp/ppp_generic.c:2280 [inline] ppp_input+0x1f1/0xe60 drivers/net/ppp/ppp_generic.c:2304 pppoe_rcv_core+0x1d3/0x720 drivers/net/ppp/pppoe.c:379 sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1113 __release_sock+0x1da/0x330 net/core/sock.c:3072 release_sock+0x6b/0x250 net/core/sock.c:3626 pppoe_sendmsg+0x2b8/0xb90 drivers/net/ppp/pppoe.c:903 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 ____sys_sendmsg+0x903/0xb60 net/socket.c:2602 ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was created at: slab_post_alloc_hook mm/slub.c:4092 [inline] slab_alloc_node mm/slub.c:4135 [inline] kmem_cache_alloc_node_noprof+0x6bf/0xb80 mm/slub.c:4187 kmalloc_reserve+0x13d/0x4a0 net/core/skbuff.c:587 __alloc_skb+0x363/0x7b0 net/core/skbuff.c:678 alloc_skb include/linux/skbuff.h:1322 [inline] sock_wmalloc+0xfe/0x1a0 net/core/sock.c:2732 pppoe_sendmsg+0x3a7/0xb90 drivers/net/ppp/pppoe.c:867 sock_sendmsg_nosec net/socket.c:729 [inline] __sock_sendmsg+0x30f/0x380 net/socket.c:744 ____sys_sendmsg+0x903/0xb60 net/socket.c:2602 ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2656 __sys_sendmmsg+0x3c1/0x960 net/socket.c:2742 __do_sys_sendmmsg net/socket.c:2771 [inline] __se_sys_sendmmsg net/socket.c:2768 [inline] __x64_sys_sendmmsg+0xbc/0x120 net/socket.c:2768 x64_sys_call+0xb6e/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:308 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f CPU: 1 UID: 0 PID: 5411 Comm: syz.1.14 Not tainted 6.12.0-rc1-syzkaller-00165-g360c1f1f24c6 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024(CVE-2024-50035)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: NFSv4: Prevent NULL-pointer dereference in nfs42_complete_copies() On the node of an NFS client, some files saved in the mountpoint of the NFS server were copied to another location of the same NFS server. Accidentally, the nfs42_complete_copies() got a NULL-pointer dereference crash with the following syslog: [232064.838881] NFSv4: state recovery failed for open file nfs/pvc-12b5200d-cd0f-46a3-b9f0-af8f4fe0ef64.qcow2, error = -116 [232064.839360] NFSv4: state recovery failed for open file nfs/pvc-12b5200d-cd0f-46a3-b9f0-af8f4fe0ef64.qcow2, error = -116 [232066.588183] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000058 [232066.588586] Mem abort info: [232066.588701] ESR = 0x0000000096000007 [232066.588862] EC = 0x25: DABT (current EL), IL = 32 bits [232066.589084] SET = 0, FnV = 0 [232066.589216] EA = 0, S1PTW = 0 [232066.589340] FSC = 0x07: level 3 translation fault [232066.589559] Data abort info: [232066.589683] ISV = 0, ISS = 0x00000007 [232066.589842] CM = 0, WnR = 0 [232066.589967] user pgtable: 64k pages, 48-bit VAs, pgdp=00002000956ff400 [232066.590231] [0000000000000058] pgd=08001100ae100003, p4d=08001100ae100003, pud=08001100ae100003, pmd=08001100b3c00003, pte=0000000000000000 [232066.590757] Internal error: Oops: 96000007 [#1] SMP [232066.590958] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace fscache netfs ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm vhost_net vhost vhost_iotlb tap tun ipt_rpfilter xt_multiport ip_set_hash_ip ip_set_hash_net xfrm_interface xfrm6_tunnel tunnel4 tunnel6 esp4 ah4 wireguard libcurve25519_generic veth xt_addrtype xt_set nf_conntrack_netlink ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_bitmap_port ip_set_hash_ipport dummy ip_set ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs iptable_filter sch_ingress nfnetlink_cttimeout vport_gre ip_gre ip_tunnel gre vport_geneve geneve vport_vxlan vxlan ip6_udp_tunnel udp_tunnel openvswitch nf_conncount dm_round_robin dm_service_time dm_multipath xt_nat xt_MASQUERADE nft_chain_nat nf_nat xt_mark xt_conntrack xt_comment nft_compat nft_counter nf_tables nfnetlink ocfs2 ocfs2_nodemanager ocfs2_stackglue iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ipmi_ssif nbd overlay 8021q garp mrp bonding tls rfkill sunrpc ext4 mbcache jbd2 [232066.591052] vfat fat cas_cache cas_disk ses enclosure scsi_transport_sas sg acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler ip_tables vfio_pci vfio_pci_core vfio_virqfd vfio_iommu_type1 vfio dm_mirror dm_region_hash dm_log dm_mod nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter bridge stp llc fuse xfs libcrc32c ast drm_vram_helper qla2xxx drm_kms_helper syscopyarea crct10dif_ce sysfillrect ghash_ce sysimgblt sha2_ce fb_sys_fops cec sha256_arm64 sha1_ce drm_ttm_helper ttm nvme_fc igb sbsa_gwdt nvme_fabrics drm nvme_core i2c_algo_bit i40e scsi_transport_fc megaraid_sas aes_neon_bs [232066.596953] CPU: 6 PID: 4124696 Comm: 10.253.166.125- Kdump: loaded Not tainted 5.15.131-9.cl9_ocfs2.aarch64 #1 [232066.597356] Hardware name: Great Wall .\\x93\\x8e...RF6260 V5/GWMSSE2GL1T, BIOS T656FBE_V3.0.18 2024-01-06 [232066.597721] pstate: 20400009 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [232066.598034] pc : nfs4_reclaim_open_state+0x220/0x800 [nfsv4] [232066.598327] lr : nfs4_reclaim_open_state+0x12c/0x800 [nfsv4] [232066.598595] sp : ffff8000f568fc70 [232066.598731] x29: ffff8000f568fc70 x28: 0000000000001000 x27: ffff21003db33000 [232066.599030] x26: ffff800005521ae0 x25: ffff0100f98fa3f0 x24: 0000000000000001 [232066.599319] x23: ffff800009920008 x22: ffff21003db33040 x21: ffff21003db33050 [232066.599628] x20: ffff410172fe9e40 x19: ffff410172fe9e00 x18: 0000000000000000 [232066.599914] x17: 0000000000000000 x16: 0000000000000004 x15: 0000000000000000 [232066.600195] x14: 0000000000000000 x13: ffff800008e685a8 x12: 00000000eac0c6e6 [232066.600498] x11: 00000000000000 ---truncated---(CVE-2024-50046)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: smb: client: fix UAF in async decryption Doing an async decryption (large read) crashes with a slab-use-after-free way down in the crypto API. Reproducer: # mount.cifs -o ...,seal,esize=1 //srv/share /mnt # dd if=/mnt/largefile of=/dev/null ... [ 194.196391] ================================================================== [ 194.196844] BUG: KASAN: slab-use-after-free in gf128mul_4k_lle+0xc1/0x110 [ 194.197269] Read of size 8 at addr ffff888112bd0448 by task kworker/u77:2/899 [ 194.197707] [ 194.197818] CPU: 12 UID: 0 PID: 899 Comm: kworker/u77:2 Not tainted 6.11.0-lku-00028-gfca3ca14a17a-dirty #43 [ 194.198400] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.2-3-gd478f380-prebuilt.qemu.org 04/01/2014 [ 194.199046] Workqueue: smb3decryptd smb2_decrypt_offload [cifs] [ 194.200032] Call Trace: [ 194.200191] \u0026lt;TASK\u0026gt; [ 194.200327] dump_stack_lvl+0x4e/0x70 [ 194.200558] ? gf128mul_4k_lle+0xc1/0x110 [ 194.200809] print_report+0x174/0x505 [ 194.201040] ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [ 194.201352] ? srso_return_thunk+0x5/0x5f [ 194.201604] ? __virt_addr_valid+0xdf/0x1c0 [ 194.201868] ? gf128mul_4k_lle+0xc1/0x110 [ 194.202128] kasan_report+0xc8/0x150 [ 194.202361] ? gf128mul_4k_lle+0xc1/0x110 [ 194.202616] gf128mul_4k_lle+0xc1/0x110 [ 194.202863] ghash_update+0x184/0x210 [ 194.203103] shash_ahash_update+0x184/0x2a0 [ 194.203377] ? __pfx_shash_ahash_update+0x10/0x10 [ 194.203651] ? srso_return_thunk+0x5/0x5f [ 194.203877] ? crypto_gcm_init_common+0x1ba/0x340 [ 194.204142] gcm_hash_assoc_remain_continue+0x10a/0x140 [ 194.204434] crypt_message+0xec1/0x10a0 [cifs] [ 194.206489] ? __pfx_crypt_message+0x10/0x10 [cifs] [ 194.208507] ? srso_return_thunk+0x5/0x5f [ 194.209205] ? srso_return_thunk+0x5/0x5f [ 194.209925] ? srso_return_thunk+0x5/0x5f [ 194.210443] ? srso_return_thunk+0x5/0x5f [ 194.211037] decrypt_raw_data+0x15f/0x250 [cifs] [ 194.212906] ? __pfx_decrypt_raw_data+0x10/0x10 [cifs] [ 194.214670] ? srso_return_thunk+0x5/0x5f [ 194.215193] smb2_decrypt_offload+0x12a/0x6c0 [cifs] This is because TFM is being used in parallel. Fix this by allocating a new AEAD TFM for async decryption, but keep the existing one for synchronous READ cases (similar to what is done in smb3_calc_signature()). Also remove the calls to aead_request_set_callback() and crypto_wait_req() since it\u0026apos;s always going to be a synchronous operation.(CVE-2024-50047)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: serial: protect uart_port_dtr_rts() in uart_shutdown() too Commit af224ca2df29 (serial: core: Prevent unsafe uart port access, part 3) added few uport == NULL checks. It added one to uart_shutdown(), so the commit assumes, uport can be NULL in there. But right after that protection, there is an unprotected \u0026quot;uart_port_dtr_rts(uport, false);\u0026quot; call. That is invoked only if HUPCL is set, so I assume that is the reason why we do not see lots of these reports. Or it cannot be NULL at this point at all for some reason :P. Until the above is investigated, stay on the safe side and move this dereference to the if too. I got this inconsistency from Coverity under CID 1585130. Thanks.(CVE-2024-50058)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: ntb: ntb_hw_switchtec: Fix use after free vulnerability in switchtec_ntb_remove due to race condition In the switchtec_ntb_add function, it can call switchtec_ntb_init_sndev function, then \u0026amp;sndev-\u0026gt;check_link_status_work is bound with check_link_status_work. switchtec_ntb_link_notification may be called to start the work. If we remove the module which will call switchtec_ntb_remove to make cleanup, it will free sndev through kfree(sndev), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows: CPU0 CPU1 | check_link_status_work switchtec_ntb_remove | kfree(sndev); | | if (sndev-\u0026gt;link_force_down) | // use sndev Fix it by ensuring that the work is canceled before proceeding with the cleanup in switchtec_ntb_remove.(CVE-2024-50059)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: io_uring: check if we need to reschedule during overflow flush In terms of normal application usage, this list will always be empty. And if an application does overflow a bit, it\u0026apos;ll have a few entries. However, nothing obviously prevents syzbot from running a test case that generates a ton of overflow entries, and then flushing them can take quite a while. Check for needing to reschedule while flushing, and drop our locks and do so if necessary. There\u0026apos;s no state to maintain here as overflows always prune from head-of-list, hence it\u0026apos;s fine to drop and reacquire the locks at the end of the loop.(CVE-2024-50060)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: bpf: Prevent tail call between progs attached to different hooks bpf progs can be attached to kernel functions, and the attached functions can take different parameters or return different return values. If prog attached to one kernel function tail calls prog attached to another kernel function, the ctx access or return value verification could be bypassed. For example, if prog1 is attached to func1 which takes only 1 parameter and prog2 is attached to func2 which takes two parameters. Since verifier assumes the bpf ctx passed to prog2 is constructed based on func2\u0026apos;s prototype, verifier allows prog2 to access the second parameter from the bpf ctx passed to it. The problem is that verifier does not prevent prog1 from passing its bpf ctx to prog2 via tail call. In this case, the bpf ctx passed to prog2 is constructed from func1 instead of func2, that is, the assumption for ctx access verification is bypassed. Another example, if BPF LSM prog1 is attached to hook file_alloc_security, and BPF LSM prog2 is attached to hook bpf_lsm_audit_rule_known. Verifier knows the return value rules for these two hooks, e.g. it is legal for bpf_lsm_audit_rule_known to return positive number 1, and it is illegal for file_alloc_security to return positive number. So verifier allows prog2 to return positive number 1, but does not allow prog1 to return positive number. The problem is that verifier does not prevent prog1 from calling prog2 via tail call. In this case, prog2\u0026apos;s return value 1 will be used as the return value for prog1\u0026apos;s hook file_alloc_security. That is, the return value rule is bypassed. This patch adds restriction for tail call to prevent such bypasses.(CVE-2024-50063)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: uprobe: avoid out-of-bounds memory access of fetching args Uprobe needs to fetch args into a percpu buffer, and then copy to ring buffer to avoid non-atomic context problem. Sometimes user-space strings, arrays can be very large, but the size of percpu buffer is only page size. And store_trace_args() won\u0026apos;t check whether these data exceeds a single page or not, caused out-of-bounds memory access. It could be reproduced by following steps: 1. build kernel with CONFIG_KASAN enabled 2. save follow program as test.c ``` \\#include \u0026lt;stdio.h\u0026gt; \\#include \u0026lt;stdlib.h\u0026gt; \\#include \u0026lt;string.h\u0026gt; // If string length large than MAX_STRING_SIZE, the fetch_store_strlen() // will return 0, cause __get_data_size() return shorter size, and // store_trace_args() will not trigger out-of-bounds access. // So make string length less than 4096. \\#define STRLEN 4093 void generate_string(char *str, int n) { int i; for (i = 0; i \u0026lt; n; ++i) { char c = i % 26 + \u0026apos;a\u0026apos;; str[i] = c; } str[n-1] = \u0026apos;\\0\u0026apos;; } void print_string(char *str) { printf(\u0026quot;%s\\n\u0026quot;, str); } int main() { char tmp[STRLEN]; generate_string(tmp, STRLEN); print_string(tmp); return 0; } ``` 3. compile program `gcc -o test test.c` 4. get the offset of `print_string()` ``` objdump -t test | grep -w print_string 0000000000401199 g F .text 000000000000001b print_string ``` 5. configure uprobe with offset 0x1199 ``` off=0x1199 cd /sys/kernel/debug/tracing/ echo \u0026quot;p /root/test:${off} arg1=+0(%di):ustring arg2=\\$comm arg3=+0(%di):ustring\u0026quot; \u0026gt; uprobe_events echo 1 \u0026gt; events/uprobes/enable echo 1 \u0026gt; tracing_on ``` 6. run `test`, and kasan will report error. ================================================================== BUG: KASAN: use-after-free in strncpy_from_user+0x1d6/0x1f0 Write of size 8 at addr ffff88812311c004 by task test/499CPU: 0 UID: 0 PID: 499 Comm: test Not tainted 6.12.0-rc3+ #18 Hardware name: Red Hat KVM, BIOS 1.16.0-4.al8 04/01/2014 Call Trace: \u0026lt;TASK\u0026gt; dump_stack_lvl+0x55/0x70 print_address_description.constprop.0+0x27/0x310 kasan_report+0x10f/0x120 ? strncpy_from_user+0x1d6/0x1f0 strncpy_from_user+0x1d6/0x1f0 ? rmqueue.constprop.0+0x70d/0x2ad0 process_fetch_insn+0xb26/0x1470 ? __pfx_process_fetch_insn+0x10/0x10 ? _raw_spin_lock+0x85/0xe0 ? __pfx__raw_spin_lock+0x10/0x10 ? __pte_offset_map+0x1f/0x2d0 ? unwind_next_frame+0xc5f/0x1f80 ? arch_stack_walk+0x68/0xf0 ? is_bpf_text_address+0x23/0x30 ? kernel_text_address.part.0+0xbb/0xd0 ? __kernel_text_address+0x66/0xb0 ? unwind_get_return_address+0x5e/0xa0 ? __pfx_stack_trace_consume_entry+0x10/0x10 ? arch_stack_walk+0xa2/0xf0 ? _raw_spin_lock_irqsave+0x8b/0xf0 ? __pfx__raw_spin_lock_irqsave+0x10/0x10 ? depot_alloc_stack+0x4c/0x1f0 ? _raw_spin_unlock_irqrestore+0xe/0x30 ? stack_depot_save_flags+0x35d/0x4f0 ? kasan_save_stack+0x34/0x50 ? kasan_save_stack+0x24/0x50 ? mutex_lock+0x91/0xe0 ? __pfx_mutex_lock+0x10/0x10 prepare_uprobe_buffer.part.0+0x2cd/0x500 uprobe_dispatcher+0x2c3/0x6a0 ? __pfx_uprobe_dispatcher+0x10/0x10 ? __kasan_slab_alloc+0x4d/0x90 handler_chain+0xdd/0x3e0 handle_swbp+0x26e/0x3d0 ? __pfx_handle_swbp+0x10/0x10 ? uprobe_pre_sstep_notifier+0x151/0x1b0 irqentry_exit_to_user_mode+0xe2/0x1b0 asm_exc_int3+0x39/0x40 RIP: 0033:0x401199 Code: 01 c2 0f b6 45 fb 88 02 83 45 fc 01 8b 45 fc 3b 45 e4 7c b7 8b 45 e4 48 98 48 8d 50 ff 48 8b 45 e8 48 01 d0 ce RSP: 002b:00007ffdf00576a8 EFLAGS: 00000206 RAX: 00007ffdf00576b0 RBX: 0000000000000000 RCX: 0000000000000ff2 RDX: 0000000000000ffc RSI: 0000000000000ffd RDI: 00007ffdf00576b0 RBP: 00007ffdf00586b0 R08: 00007feb2f9c0d20 R09: 00007feb2f9c0d20 R10: 0000000000000001 R11: 0000000000000202 R12: 0000000000401040 R13: 00007ffdf0058780 R14: 0000000000000000 R15: 0000000000000000 \u0026lt;/TASK\u0026gt; This commit enforces the buffer\u0026apos;s maxlen less than a page-size to avoid store_trace_args() out-of-memory access.(CVE-2024-50067)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: parport: Proper fix for array out-of-bounds access The recent fix for array out-of-bounds accesses replaced sprintf() calls blindly with snprintf(). However, since snprintf() returns the would-be-printed size, not the actually output size, the length calculation can still go over the given limit. Use scnprintf() instead of snprintf(), which returns the actually output letters, for addressing the potential out-of-bounds access properly.(CVE-2024-50074)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: tcp: fix mptcp DSS corruption due to large pmtu xmit Syzkaller was able to trigger a DSS corruption: TCP: request_sock_subflow_v4: Possible SYN flooding on port [::]:20002. Sending cookies. ------------[ cut here ]------------ WARNING: CPU: 0 PID: 5227 at net/mptcp/protocol.c:695 __mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695 Modules linked in: CPU: 0 UID: 0 PID: 5227 Comm: syz-executor350 Not tainted 6.11.0-syzkaller-08829-gaf9c191ac2a0 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 RIP: 0010:__mptcp_move_skbs_from_subflow+0x20a9/0x21f0 net/mptcp/protocol.c:695 Code: 0f b6 dc 31 ff 89 de e8 b5 dd ea f5 89 d8 48 81 c4 50 01 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 98 da ea f5 90 \u0026lt;0f\u0026gt; 0b 90 e9 47 ff ff ff e8 8a da ea f5 90 0f 0b 90 e9 99 e0 ff ff RSP: 0018:ffffc90000006db8 EFLAGS: 00010246 RAX: ffffffff8ba9df18 RBX: 00000000000055f0 RCX: ffff888030023c00 RDX: 0000000000000100 RSI: 00000000000081e5 RDI: 00000000000055f0 RBP: 1ffff110062bf1ae R08: ffffffff8ba9cf12 R09: 1ffff110062bf1b8 R10: dffffc0000000000 R11: ffffed10062bf1b9 R12: 0000000000000000 R13: dffffc0000000000 R14: 00000000700cec61 R15: 00000000000081e5 FS: 000055556679c380(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020287000 CR3: 0000000077892000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: \u0026lt;IRQ\u0026gt; move_skbs_to_msk net/mptcp/protocol.c:811 [inline] mptcp_data_ready+0x29c/0xa90 net/mptcp/protocol.c:854 subflow_data_ready+0x34a/0x920 net/mptcp/subflow.c:1490 tcp_data_queue+0x20fd/0x76c0 net/ipv4/tcp_input.c:5283 tcp_rcv_established+0xfba/0x2020 net/ipv4/tcp_input.c:6237 tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915 tcp_v4_rcv+0x2dc0/0x37f0 net/ipv4/tcp_ipv4.c:2350 ip_protocol_deliver_rcu+0x22e/0x440 net/ipv4/ip_input.c:205 ip_local_deliver_finish+0x341/0x5f0 net/ipv4/ip_input.c:233 NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314 NF_HOOK+0x3a4/0x450 include/linux/netfilter.h:314 __netif_receive_skb_one_core net/core/dev.c:5662 [inline] __netif_receive_skb+0x2bf/0x650 net/core/dev.c:5775 process_backlog+0x662/0x15b0 net/core/dev.c:6107 __napi_poll+0xcb/0x490 net/core/dev.c:6771 napi_poll net/core/dev.c:6840 [inline] net_rx_action+0x89b/0x1240 net/core/dev.c:6962 handle_softirqs+0x2c5/0x980 kernel/softirq.c:554 do_softirq+0x11b/0x1e0 kernel/softirq.c:455 \u0026lt;/IRQ\u0026gt; \u0026lt;TASK\u0026gt; __local_bh_enable_ip+0x1bb/0x200 kernel/softirq.c:382 local_bh_enable include/linux/bottom_half.h:33 [inline] rcu_read_unlock_bh include/linux/rcupdate.h:919 [inline] __dev_queue_xmit+0x1764/0x3e80 net/core/dev.c:4451 dev_queue_xmit include/linux/netdevice.h:3094 [inline] neigh_hh_output include/net/neighbour.h:526 [inline] neigh_output include/net/neighbour.h:540 [inline] ip_finish_output2+0xd41/0x1390 net/ipv4/ip_output.c:236 ip_local_out net/ipv4/ip_output.c:130 [inline] __ip_queue_xmit+0x118c/0x1b80 net/ipv4/ip_output.c:536 __tcp_transmit_skb+0x2544/0x3b30 net/ipv4/tcp_output.c:1466 tcp_transmit_skb net/ipv4/tcp_output.c:1484 [inline] tcp_mtu_probe net/ipv4/tcp_output.c:2547 [inline] tcp_write_xmit+0x641d/0x6bf0 net/ipv4/tcp_output.c:2752 __tcp_push_pending_frames+0x9b/0x360 net/ipv4/tcp_output.c:3015 tcp_push_pending_frames include/net/tcp.h:2107 [inline] tcp_data_snd_check net/ipv4/tcp_input.c:5714 [inline] tcp_rcv_established+0x1026/0x2020 net/ipv4/tcp_input.c:6239 tcp_v4_do_rcv+0x96d/0xc70 net/ipv4/tcp_ipv4.c:1915 sk_backlog_rcv include/net/sock.h:1113 [inline] __release_sock+0x214/0x350 net/core/sock.c:3072 release_sock+0x61/0x1f0 net/core/sock.c:3626 mptcp_push_ ---truncated---(CVE-2024-50083)",
"id": "OESA-2024-2371",
"modified": "2026-08-06T11:07:51Z",
"published": "2024-11-08T11:07:51Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2371"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48956"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48958"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48960"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48961"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48962"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48966"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48972"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48975"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48981"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48982"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48992"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48995"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-49004"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-49005"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-49011"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-49017"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-49020"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-49021"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-49023"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-49031"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-49032"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-45021"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-46677"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-46809"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47659"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47660"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47668"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47673"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47690"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47691"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47692"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47693"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47696"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47699"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47701"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47703"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47705"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47723"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47739"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47742"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47748"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47756"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49855"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49858"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49860"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49863"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49877"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49879"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49881"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49882"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49883"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49884"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49886"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49889"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49913"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49917"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49922"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49924"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49933"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49934"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49936"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49940"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49950"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49954"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49955"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49958"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49965"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49973"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49975"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49978"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49981"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49992"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49995"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49996"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50008"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50015"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50016"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50028"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50033"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50035"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50046"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50047"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50058"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50059"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50060"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50063"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50067"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50074"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50083"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "kernel security update",
"upstream": [
"CVE-2022-48956",
"CVE-2022-48958",
"CVE-2022-48960",
"CVE-2022-48961",
"CVE-2022-48962",
"CVE-2022-48966",
"CVE-2022-48972",
"CVE-2022-48975",
"CVE-2022-48981",
"CVE-2022-48982",
"CVE-2022-48992",
"CVE-2022-48995",
"CVE-2022-49004",
"CVE-2022-49005",
"CVE-2022-49011",
"CVE-2022-49017",
"CVE-2022-49020",
"CVE-2022-49021",
"CVE-2022-49023",
"CVE-2022-49031",
"CVE-2022-49032",
"CVE-2024-45021",
"CVE-2024-46677",
"CVE-2024-46809",
"CVE-2024-47659",
"CVE-2024-47660",
"CVE-2024-47668",
"CVE-2024-47673",
"CVE-2024-47690",
"CVE-2024-47691",
"CVE-2024-47692",
"CVE-2024-47693",
"CVE-2024-47696",
"CVE-2024-47699",
"CVE-2024-47701",
"CVE-2024-47703",
"CVE-2024-47705",
"CVE-2024-47723",
"CVE-2024-47739",
"CVE-2024-47742",
"CVE-2024-47748",
"CVE-2024-47756",
"CVE-2024-49855",
"CVE-2024-49858",
"CVE-2024-49860",
"CVE-2024-49863",
"CVE-2024-49877",
"CVE-2024-49879",
"CVE-2024-49881",
"CVE-2024-49882",
"CVE-2024-49883",
"CVE-2024-49884",
"CVE-2024-49886",
"CVE-2024-49889",
"CVE-2024-49913",
"CVE-2024-49917",
"CVE-2024-49922",
"CVE-2024-49924",
"CVE-2024-49933",
"CVE-2024-49934",
"CVE-2024-49936",
"CVE-2024-49940",
"CVE-2024-49950",
"CVE-2024-49954",
"CVE-2024-49955",
"CVE-2024-49958",
"CVE-2024-49965",
"CVE-2024-49973",
"CVE-2024-49975",
"CVE-2024-49978",
"CVE-2024-49981",
"CVE-2024-49992",
"CVE-2024-49995",
"CVE-2024-49996",
"CVE-2024-50008",
"CVE-2024-50015",
"CVE-2024-50016",
"CVE-2024-50028",
"CVE-2024-50033",
"CVE-2024-50035",
"CVE-2024-50046",
"CVE-2024-50047",
"CVE-2024-50058",
"CVE-2024-50059",
"CVE-2024-50060",
"CVE-2024-50063",
"CVE-2024-50067",
"CVE-2024-50074",
"CVE-2024-50083"
]
}
SSA-355557
Vulnerability from csaf_siemens - Published: 2025-08-12 00:00 - Updated: 2026-02-24 00:00UBUNTU-CVE-2024-47659 (CVE-2024-47659)
Vulnerability from osv_ubuntu – Published: 2024-10-09 14:15 – Updated: 2026-09-17 16:24 – Source websiteIn the Linux kernel, the following vulnerability has been resolved: smack: tcp: ipv4, fix incorrect labeling Currently, Smack mirrors the label of incoming tcp/ipv4 connections: when a label 'foo' connects to a label 'bar' with tcp/ipv4, 'foo' always gets 'foo' in returned ipv4 packets. So, 1) returned packets are incorrectly labeled ('foo' instead of 'bar') 2) 'bar' can write to 'foo' without being authorized to write. Here is a scenario how to see this: * Take two machines, let's call them C and S, with active Smack in the default state (no settings, no rules, no labeled hosts, only builtin labels) * At S, add Smack rule 'foo bar w' (labels 'foo' and 'bar' are instantiated at S at this moment) * At S, at label 'bar', launch a program that listens for incoming tcp/ipv4 connections * From C, at label 'foo', connect to the listener at S. (label 'foo' is instantiated at C at this moment) Connection succeedes and works. * Send some data in both directions. * Collect network traffic of this connection. All packets in both directions are labeled with the CIPSO of the label 'foo'. Hence, label 'bar' writes to 'foo' without being authorized, and even without ever being known at C. If anybody cares: exactly the same happens with DCCP. This behavior 1st manifested in release 2.6.29.4 (see Fixes below) and it looks unintentional. At least, no explanation was provided. I changed returned packes label into the 'bar', to bring it into line with the Smack documentation claims.
| URL | Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "block-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "crypto-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "fat-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "fb-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "firewire-core-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "floppy-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "fs-core-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "fs-secondary-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "input-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "ipmi-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "irda-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "kernel-image-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-buildinfo-3.13.0-217-generic",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-buildinfo-3.13.0-217-lowlatency",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-cloud-tools-3.13.0-217",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-cloud-tools-3.13.0-217-generic",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-cloud-tools-3.13.0-217-lowlatency",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-cloud-tools-common",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-headers-3.13.0-217",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-headers-3.13.0-217-generic",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-headers-3.13.0-217-lowlatency",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-image-unsigned-3.13.0-217-generic",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-image-unsigned-3.13.0-217-lowlatency",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-modules-3.13.0-217-generic",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-modules-3.13.0-217-lowlatency",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-modules-extra-3.13.0-217-generic",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-source-3.13.0",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-tools-3.13.0-217",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-tools-3.13.0-217-generic",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-tools-3.13.0-217-lowlatency",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-tools-common",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-udebs-generic",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "md-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "message-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "mouse-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "multipath-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "nfs-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "nic-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "nic-pcmcia-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "nic-shared-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "nic-usb-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "parport-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "pata-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "pcmcia-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "pcmcia-storage-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "plip-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "ppp-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "sata-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "scsi-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "serial-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "speakup-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "squashfs-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "storage-core-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "usb-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "virtio-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "vlan-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:14.04:LTS",
"name": "linux",
"purl": "pkg:deb/ubuntu/linux@3.13.0-217.268?arch=source\u0026distro=esm-infra-legacy/trusty"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.11.0-12.19",
"3.12.0-1.3",
"3.12.0-2.5",
"3.12.0-2.7",
"3.12.0-3.8",
"3.12.0-3.9",
"3.12.0-4.10",
"3.12.0-4.12",
"3.12.0-5.13",
"3.12.0-7.15",
"3.13.0-1.16",
"3.13.0-2.17",
"3.13.0-3.18",
"3.13.0-4.19",
"3.13.0-5.20",
"3.13.0-6.23",
"3.13.0-7.25",
"3.13.0-7.26",
"3.13.0-8.27",
"3.13.0-8.28",
"3.13.0-10.30",
"3.13.0-11.31",
"3.13.0-12.32",
"3.13.0-13.33",
"3.13.0-14.34",
"3.13.0-15.35",
"3.13.0-16.36",
"3.13.0-17.37",
"3.13.0-18.38",
"3.13.0-19.39",
"3.13.0-19.40",
"3.13.0-20.42",
"3.13.0-21.43",
"3.13.0-22.44",
"3.13.0-23.45",
"3.13.0-24.46",
"3.13.0-24.47",
"3.13.0-27.50",
"3.13.0-29.53",
"3.13.0-30.54",
"3.13.0-30.55",
"3.13.0-32.57",
"3.13.0-33.58",
"3.13.0-34.60",
"3.13.0-35.62",
"3.13.0-36.63",
"3.13.0-37.64",
"3.13.0-39.66",
"3.13.0-40.69",
"3.13.0-41.70",
"3.13.0-43.72",
"3.13.0-44.73",
"3.13.0-45.74",
"3.13.0-46.75",
"3.13.0-46.76",
"3.13.0-46.77",
"3.13.0-46.79",
"3.13.0-48.80",
"3.13.0-49.81",
"3.13.0-49.83",
"3.13.0-51.84",
"3.13.0-52.85",
"3.13.0-52.86",
"3.13.0-53.88",
"3.13.0-53.89",
"3.13.0-54.91",
"3.13.0-55.92",
"3.13.0-55.94",
"3.13.0-57.95",
"3.13.0-58.97",
"3.13.0-59.98",
"3.13.0-61.100",
"3.13.0-62.102",
"3.13.0-63.103",
"3.13.0-65.105",
"3.13.0-65.106",
"3.13.0-66.108",
"3.13.0-67.110",
"3.13.0-68.111",
"3.13.0-70.113",
"3.13.0-71.114",
"3.13.0-73.116",
"3.13.0-74.118",
"3.13.0-76.120",
"3.13.0-77.121",
"3.13.0-79.123",
"3.13.0-83.127",
"3.13.0-85.129",
"3.13.0-86.130",
"3.13.0-86.131",
"3.13.0-87.133",
"3.13.0-88.135",
"3.13.0-91.138",
"3.13.0-92.139",
"3.13.0-93.140",
"3.13.0-95.142",
"3.13.0-96.143",
"3.13.0-98.145",
"3.13.0-100.147",
"3.13.0-101.148",
"3.13.0-103.150",
"3.13.0-105.152",
"3.13.0-106.153",
"3.13.0-107.154",
"3.13.0-108.155",
"3.13.0-109.156",
"3.13.0-110.157",
"3.13.0-111.158",
"3.13.0-112.159",
"3.13.0-113.160",
"3.13.0-115.162",
"3.13.0-116.163",
"3.13.0-117.164",
"3.13.0-119.166",
"3.13.0-121.170",
"3.13.0-123.172",
"3.13.0-125.174",
"3.13.0-126.175",
"3.13.0-128.177",
"3.13.0-129.178",
"3.13.0-132.181",
"3.13.0-133.182",
"3.13.0-135.184",
"3.13.0-137.186",
"3.13.0-139.188",
"3.13.0-141.190",
"3.13.0-142.191",
"3.13.0-143.192",
"3.13.0-144.193",
"3.13.0-145.194",
"3.13.0-147.196",
"3.13.0-149.199",
"3.13.0-151.201",
"3.13.0-153.203",
"3.13.0-155.205",
"3.13.0-156.206",
"3.13.0-157.207",
"3.13.0-158.208",
"3.13.0-160.210",
"3.13.0-161.211",
"3.13.0-162.212",
"3.13.0-163.213",
"3.13.0-164.214",
"3.13.0-165.215",
"3.13.0-166.216",
"3.13.0-167.217",
"3.13.0-168.218",
"3.13.0-169.219",
"3.13.0-170.220",
"3.13.0-171.222",
"3.13.0-172.223",
"3.13.0-173.224",
"3.13.0-174.225",
"3.13.0-175.226",
"3.13.0-176.227",
"3.13.0-180.231",
"3.13.0-181.232",
"3.13.0-182.233",
"3.13.0-183.234",
"3.13.0-184.235",
"3.13.0-185.236",
"3.13.0-186.237",
"3.13.0-187.238",
"3.13.0-188.239",
"3.13.0-189.240",
"3.13.0-190.241",
"3.13.0-191.242",
"3.13.0-192.243",
"3.13.0-193.244",
"3.13.0-194.245",
"3.13.0-195.246",
"3.13.0-196.247",
"3.13.0-197.248",
"3.13.0-198.249",
"3.13.0-199.250",
"3.13.0-200.251",
"3.13.0-201.252",
"3.13.0-202.253",
"3.13.0-203.254",
"3.13.0-204.255",
"3.13.0-205.256",
"3.13.0-206.257",
"3.13.0-207.258",
"3.13.0-208.259",
"3.13.0-209.260",
"3.13.0-210.261",
"3.13.0-211.262",
"3.13.0-212.263",
"3.13.0-214.265",
"3.13.0-215.266",
"3.13.0-217.268"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro with Legacy support add-on: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-aws-cloud-tools-4.4.0-1152",
"binary_version": "4.4.0-1152.158"
},
{
"binary_name": "linux-aws-headers-4.4.0-1152",
"binary_version": "4.4.0-1152.158"
},
{
"binary_name": "linux-aws-tools-4.4.0-1152",
"binary_version": "4.4.0-1152.158"
},
{
"binary_name": "linux-buildinfo-4.4.0-1152-aws",
"binary_version": "4.4.0-1152.158"
},
{
"binary_name": "linux-cloud-tools-4.4.0-1152-aws",
"binary_version": "4.4.0-1152.158"
},
{
"binary_name": "linux-headers-4.4.0-1152-aws",
"binary_version": "4.4.0-1152.158"
},
{
"binary_name": "linux-image-4.4.0-1152-aws",
"binary_version": "4.4.0-1152.158"
},
{
"binary_name": "linux-modules-4.4.0-1152-aws",
"binary_version": "4.4.0-1152.158"
},
{
"binary_name": "linux-tools-4.4.0-1152-aws",
"binary_version": "4.4.0-1152.158"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:14.04:LTS",
"name": "linux-aws",
"purl": "pkg:deb/ubuntu/linux-aws@4.4.0-1152.158?arch=source\u0026distro=esm-infra-legacy/trusty"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.4.0-1152.158"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.4.0-1002.2",
"4.4.0-1003.3",
"4.4.0-1005.5",
"4.4.0-1006.6",
"4.4.0-1009.9",
"4.4.0-1010.10",
"4.4.0-1011.11",
"4.4.0-1012.12",
"4.4.0-1014.14",
"4.4.0-1016.16",
"4.4.0-1017.17",
"4.4.0-1019.19",
"4.4.0-1022.22",
"4.4.0-1023.23",
"4.4.0-1024.25",
"4.4.0-1025.26",
"4.4.0-1027.30",
"4.4.0-1028.31",
"4.4.0-1029.32",
"4.4.0-1031.34",
"4.4.0-1032.35",
"4.4.0-1034.37",
"4.4.0-1036.39",
"4.4.0-1037.40",
"4.4.0-1038.41",
"4.4.0-1039.42",
"4.4.0-1040.43",
"4.4.0-1042.45",
"4.4.0-1044.47",
"4.4.0-1045.48",
"4.4.0-1046.50",
"4.4.0-1048.52",
"4.4.0-1050.54",
"4.4.0-1052.56",
"4.4.0-1054.58",
"4.4.0-1055.59",
"4.4.0-1056.60",
"4.4.0-1058.62",
"4.4.0-1059.63",
"4.4.0-1060.64",
"4.4.0-1061.65",
"4.4.0-1062.66",
"4.4.0-1064.68",
"4.4.0-1065.69",
"4.4.0-1066.70",
"4.4.0-1067.71",
"4.4.0-1073.77",
"4.4.0-1074.78",
"4.4.0-1075.79",
"4.4.0-1076.80",
"4.4.0-1077.81",
"4.4.0-1078.82",
"4.4.0-1081.85",
"4.4.0-1082.86",
"4.4.0-1083.87",
"4.4.0-1085.89",
"4.4.0-1086.90",
"4.4.0-1087.91",
"4.4.0-1088.92",
"4.4.0-1090.94",
"4.4.0-1091.95",
"4.4.0-1092.96",
"4.4.0-1093.97",
"4.4.0-1094.99",
"4.4.0-1095.100",
"4.4.0-1096.101",
"4.4.0-1097.102",
"4.4.0-1098.103",
"4.4.0-1099.104",
"4.4.0-1101.106",
"4.4.0-1102.107",
"4.4.0-1103.108",
"4.4.0-1104.109",
"4.4.0-1107.113",
"4.4.0-1109.115",
"4.4.0-1110.116",
"4.4.0-1111.117",
"4.4.0-1112.118",
"4.4.0-1113.119",
"4.4.0-1114.120",
"4.4.0-1115.121",
"4.4.0-1116.122",
"4.4.0-1117.123",
"4.4.0-1118.124",
"4.4.0-1119.125",
"4.4.0-1120.126",
"4.4.0-1121.127",
"4.4.0-1122.128",
"4.4.0-1123.129",
"4.4.0-1124.130",
"4.4.0-1125.131",
"4.4.0-1127.133",
"4.4.0-1128.134",
"4.4.0-1129.135",
"4.4.0-1130.136",
"4.4.0-1131.137",
"4.4.0-1133.139",
"4.4.0-1134.140",
"4.4.0-1135.141",
"4.4.0-1136.142",
"4.4.0-1137.143",
"4.4.0-1138.144",
"4.4.0-1139.145",
"4.4.0-1140.146",
"4.4.0-1141.147",
"4.4.0-1142.148",
"4.4.0-1143.149",
"4.4.0-1144.150",
"4.4.0-1145.151",
"4.4.0-1146.152",
"4.4.0-1147.153",
"4.4.0-1148.154",
"4.4.0-1149.155",
"4.4.0-1150.156",
"4.4.0-1151.157"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro with Legacy support add-on: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-azure-cloud-tools-4.15.0-1197",
"binary_version": "4.15.0-1197.212~14.04.1"
},
{
"binary_name": "linux-azure-headers-4.15.0-1197",
"binary_version": "4.15.0-1197.212~14.04.1"
},
{
"binary_name": "linux-azure-tools-4.15.0-1197",
"binary_version": "4.15.0-1197.212~14.04.1"
},
{
"binary_name": "linux-buildinfo-4.15.0-1197-azure",
"binary_version": "4.15.0-1197.212~14.04.1"
},
{
"binary_name": "linux-cloud-tools-4.15.0-1197-azure",
"binary_version": "4.15.0-1197.212~14.04.1"
},
{
"binary_name": "linux-headers-4.15.0-1197-azure",
"binary_version": "4.15.0-1197.212~14.04.1"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1197-azure",
"binary_version": "4.15.0-1197.212~14.04.1"
},
{
"binary_name": "linux-modules-4.15.0-1197-azure",
"binary_version": "4.15.0-1197.212~14.04.1"
},
{
"binary_name": "linux-modules-extra-4.15.0-1197-azure",
"binary_version": "4.15.0-1197.212~14.04.1"
},
{
"binary_name": "linux-tools-4.15.0-1197-azure",
"binary_version": "4.15.0-1197.212~14.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:14.04:LTS",
"name": "linux-azure",
"purl": "pkg:deb/ubuntu/linux-azure@4.15.0-1197.212~14.04.1?arch=source\u0026distro=esm-infra-legacy/trusty"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.15.0-1197.212~14.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1023.24~14.04.1",
"4.15.0-1030.31~14.04.1",
"4.15.0-1031.32~14.04.1",
"4.15.0-1032.33~14.04.2",
"4.15.0-1035.36~14.04.2",
"4.15.0-1036.38~14.04.2",
"4.15.0-1037.39~14.04.2",
"4.15.0-1039.41~14.04.2",
"4.15.0-1040.44~14.04.1",
"4.15.0-1041.45~14.04.1",
"4.15.0-1042.46~14.04.1",
"4.15.0-1045.49~14.04.1",
"4.15.0-1046.50~14.04.1",
"4.15.0-1047.51~14.04.1",
"4.15.0-1049.54~14.04.1",
"4.15.0-1050.55~14.04.1",
"4.15.0-1051.56~14.04.1",
"4.15.0-1052.57~14.04.1",
"4.15.0-1055.60~14.04.1",
"4.15.0-1056.61~14.04.1",
"4.15.0-1057.62~14.04.1",
"4.15.0-1059.64~14.04.1",
"4.15.0-1060.65~14.04.1",
"4.15.0-1061.66~14.04.1",
"4.15.0-1063.68~14.04.1",
"4.15.0-1064.69~14.04.1",
"4.15.0-1066.71~14.04.1",
"4.15.0-1067.72~14.04.1",
"4.15.0-1069.74~14.04.1",
"4.15.0-1071.76~14.04.1",
"4.15.0-1074.79~14.04.1",
"4.15.0-1077.82~14.04.1",
"4.15.0-1082.92~14.04.1",
"4.15.0-1083.93~14.04.1",
"4.15.0-1089.99~14.04.1",
"4.15.0-1091.101~14.04.1",
"4.15.0-1092.102~14.04.1",
"4.15.0-1093.103~14.04.1",
"4.15.0-1095.105~14.04.1",
"4.15.0-1096.106~14.04.1",
"4.15.0-1098.109~14.04.1",
"4.15.0-1100.111~14.04.1",
"4.15.0-1102.113~14.04.1",
"4.15.0-1103.114~14.04.1",
"4.15.0-1106.118~14.04.1",
"4.15.0-1108.120~14.04.1",
"4.15.0-1109.121~14.04.1",
"4.15.0-1110.122~14.04.1",
"4.15.0-1111.123~14.04.1",
"4.15.0-1112.124~14.04.1",
"4.15.0-1113.126~14.04.1",
"4.15.0-1114.127~14.04.1",
"4.15.0-1115.128~14.04.1",
"4.15.0-1118.131~14.04.1",
"4.15.0-1121.134~14.04.1",
"4.15.0-1122.135~14.04.1",
"4.15.0-1123.136~14.04.1",
"4.15.0-1124.137~14.04.1",
"4.15.0-1125.138~14.04.1",
"4.15.0-1126.139~14.04.1",
"4.15.0-1127.140~14.04.1",
"4.15.0-1129.142~14.04.1",
"4.15.0-1130.143~14.04.1",
"4.15.0-1131.144~14.04.1",
"4.15.0-1133.146~14.04.1",
"4.15.0-1134.147~14.04.1",
"4.15.0-1136.149~14.04.1",
"4.15.0-1137.150~14.04.1",
"4.15.0-1138.151~14.04.1",
"4.15.0-1139.152~14.04.1",
"4.15.0-1142.156~14.04.1",
"4.15.0-1145.160~14.04.1",
"4.15.0-1146.161~14.04.1",
"4.15.0-1149.164~14.04.1",
"4.15.0-1150.165~14.04.1",
"4.15.0-1151.166~14.04.1",
"4.15.0-1153.168~14.04.1",
"4.15.0-1157.172~14.04.2",
"4.15.0-1158.173~14.04.1",
"4.15.0-1159.174~14.04.1",
"4.15.0-1162.177~14.04.1",
"4.15.0-1163.178~14.04.1",
"4.15.0-1164.179~14.04.1",
"4.15.0-1165.180~14.04.1",
"4.15.0-1166.181~14.04.1",
"4.15.0-1167.182~14.04.1",
"4.15.0-1168.183~14.04.1",
"4.15.0-1169.184~14.04.1",
"4.15.0-1170.185~14.04.1",
"4.15.0-1171.186~14.04.1",
"4.15.0-1172.187~14.04.1",
"4.15.0-1173.188~14.04.1",
"4.15.0-1174.189~14.04.1",
"4.15.0-1175.190~14.04.1",
"4.15.0-1176.191~14.04.1",
"4.15.0-1177.192~14.04.1",
"4.15.0-1178.193~14.04.1",
"4.15.0-1179.194~14.04.1",
"4.15.0-1180.195~14.04.1",
"4.15.0-1181.196~14.04.1",
"4.15.0-1182.197~14.04.1",
"4.15.0-1183.198~14.04.1",
"4.15.0-1184.199~14.04.1",
"4.15.0-1185.200~14.04.1",
"4.15.0-1186.201~14.04.1",
"4.15.0-1187.202~14.04.1",
"4.15.0-1188.203~14.04.1",
"4.15.0-1189.204~14.04.1",
"4.15.0-1190.205~14.04.1",
"4.15.0-1191.206~14.04.1",
"4.15.0-1192.207~14.04.1",
"4.15.0-1193.208~14.04.1",
"4.15.0-1194.209~14.04.1",
"4.15.0-1195.210~14.04.1",
"4.15.0-1196.211~14.04.1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro with Legacy support add-on: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "block-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "crypto-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "fat-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "fb-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "firewire-core-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "floppy-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "fs-core-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "fs-secondary-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "input-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "ipmi-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "irda-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "kernel-image-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "linux-buildinfo-4.4.0-278-generic",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "linux-buildinfo-4.4.0-278-lowlatency",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "linux-cloud-tools-4.4.0-278-generic",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "linux-cloud-tools-4.4.0-278-lowlatency",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "linux-headers-4.4.0-278",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "linux-headers-4.4.0-278-generic",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "linux-headers-4.4.0-278-lowlatency",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "linux-image-4.4.0-278-generic",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "linux-image-unsigned-4.4.0-278-generic",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "linux-image-unsigned-4.4.0-278-lowlatency",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "linux-lts-xenial-cloud-tools-4.4.0-278",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "linux-lts-xenial-tools-4.4.0-278",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "linux-lts-xenial-udebs-generic",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "linux-modules-4.4.0-278-generic",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "linux-modules-4.4.0-278-lowlatency",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "linux-modules-extra-4.4.0-278-generic",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "linux-tools-4.4.0-278-generic",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "linux-tools-4.4.0-278-lowlatency",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "md-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "message-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "mouse-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "multipath-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "nfs-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "nic-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "nic-pcmcia-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "nic-shared-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "nic-usb-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "parport-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "pata-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "pcmcia-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "pcmcia-storage-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "plip-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "ppp-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "sata-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "scsi-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "serial-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "speakup-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "storage-core-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "usb-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "virtio-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
},
{
"binary_name": "vlan-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312~14.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:14.04:LTS",
"name": "linux-lts-xenial",
"purl": "pkg:deb/ubuntu/linux-lts-xenial@4.4.0-278.312~14.04.1?arch=source\u0026distro=esm-infra-legacy/trusty"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.4.0-278.312~14.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.4.0-13.29~14.04.1",
"4.4.0-14.30~14.04.2",
"4.4.0-15.31~14.04.1",
"4.4.0-18.34~14.04.1",
"4.4.0-21.37~14.04.1",
"4.4.0-22.39~14.04.1",
"4.4.0-22.40~14.04.1",
"4.4.0-24.43~14.04.1",
"4.4.0-28.47~14.04.1",
"4.4.0-31.50~14.04.1",
"4.4.0-34.53~14.04.1",
"4.4.0-36.55~14.04.1",
"4.4.0-38.57~14.04.1",
"4.4.0-42.62~14.04.1",
"4.4.0-45.66~14.04.1",
"4.4.0-47.68~14.04.1",
"4.4.0-51.72~14.04.1",
"4.4.0-53.74~14.04.1",
"4.4.0-57.78~14.04.1",
"4.4.0-59.80~14.04.1",
"4.4.0-62.83~14.04.1",
"4.4.0-63.84~14.04.2",
"4.4.0-64.85~14.04.1",
"4.4.0-66.87~14.04.1",
"4.4.0-67.88~14.04.1",
"4.4.0-70.91~14.04.1",
"4.4.0-71.92~14.04.1",
"4.4.0-72.93~14.04.1",
"4.4.0-75.96~14.04.1",
"4.4.0-78.99~14.04.2",
"4.4.0-79.100~14.04.1",
"4.4.0-81.104~14.04.1",
"4.4.0-83.106~14.04.1",
"4.4.0-87.110~14.04.1",
"4.4.0-89.112~14.04.1",
"4.4.0-91.114~14.04.1",
"4.4.0-92.115~14.04.1",
"4.4.0-93.116~14.04.1",
"4.4.0-96.119~14.04.1",
"4.4.0-97.120~14.04.1",
"4.4.0-98.121~14.04.1",
"4.4.0-101.124~14.04.1",
"4.4.0-103.126~14.04.1",
"4.4.0-104.127~14.04.1",
"4.4.0-108.131~14.04.1",
"4.4.0-109.132~14.04.1",
"4.4.0-111.134~14.04.1",
"4.4.0-112.135~14.04.1",
"4.4.0-116.140~14.04.1",
"4.4.0-119.143~14.04.1",
"4.4.0-121.145~14.04.1",
"4.4.0-124.148~14.04.1",
"4.4.0-127.153~14.04.1",
"4.4.0-128.154~14.04.1",
"4.4.0-130.156~14.04.1",
"4.4.0-131.157~14.04.1",
"4.4.0-133.159~14.04.1",
"4.4.0-134.160~14.04.1",
"4.4.0-135.161~14.04.1",
"4.4.0-137.163~14.04.1",
"4.4.0-138.164~14.04.1",
"4.4.0-139.165~14.04.1",
"4.4.0-140.166~14.04.1",
"4.4.0-141.167~14.04.1",
"4.4.0-142.168~14.04.1",
"4.4.0-143.169~14.04.2",
"4.4.0-144.170~14.04.1",
"4.4.0-146.172~14.04.1",
"4.4.0-148.174~14.04.1",
"4.4.0-150.176~14.04.1",
"4.4.0-151.178~14.04.1",
"4.4.0-154.181~14.04.1",
"4.4.0-157.185~14.04.1",
"4.4.0-159.187~14.04.1",
"4.4.0-161.189~14.04.1",
"4.4.0-164.192~14.04.1",
"4.4.0-165.193~14.04.1",
"4.4.0-166.195~14.04.1",
"4.4.0-168.197~14.04.1",
"4.4.0-169.198~14.04.1",
"4.4.0-170.199~14.04.1",
"4.4.0-171.200~14.04.1",
"4.4.0-173.203~14.04.1",
"4.4.0-174.204~14.04.1",
"4.4.0-176.206~14.04.1",
"4.4.0-177.207~14.04.1",
"4.4.0-178.208~14.04.1",
"4.4.0-179.209~14.04.1",
"4.4.0-184.214~14.04.1",
"4.4.0-185.215~14.04.1",
"4.4.0-186.216~14.04.1",
"4.4.0-187.217~14.04.1",
"4.4.0-189.219~14.04.1",
"4.4.0-190.220~14.04.1",
"4.4.0-193.224~14.04.1",
"4.4.0-194.226~14.04.1",
"4.4.0-197.229~14.04.1",
"4.4.0-198.230~14.04.1",
"4.4.0-200.232~14.04.1",
"4.4.0-201.233~14.04.1",
"4.4.0-203.235~14.04.1",
"4.4.0-204.236~14.04.1",
"4.4.0-206.238~14.04.1",
"4.4.0-208.240~14.04.1",
"4.4.0-209.241~14.04.1",
"4.4.0-210.242~14.04.1",
"4.4.0-211.243~14.04.1",
"4.4.0-212.244~14.04.1",
"4.4.0-213.245~14.04.1",
"4.4.0-214.246~14.04.1",
"4.4.0-215.247~14.04.1",
"4.4.0-218.251~14.04.1",
"4.4.0-219.252~14.04.1",
"4.4.0-221.254~14.04.1",
"4.4.0-222.255~14.04.1",
"4.4.0-223.256~14.04.1",
"4.4.0-224.257~14.04.1",
"4.4.0-227.261~14.04.1",
"4.4.0-229.263~14.04.1",
"4.4.0-230.264~14.04.1",
"4.4.0-231.265~14.04.1",
"4.4.0-233.267~14.04.1",
"4.4.0-234.268~14.04.1",
"4.4.0-235.269~14.04.1",
"4.4.0-236.270~14.04.1",
"4.4.0-237.271~14.04.1",
"4.4.0-239.273~14.04.1",
"4.4.0-240.274~14.04.1",
"4.4.0-241.275~14.04.1",
"4.4.0-242.276~14.04.1",
"4.4.0-243.277~14.04.1",
"4.4.0-244.278~14.04.1",
"4.4.0-245.279~14.04.1",
"4.4.0-246.280~14.04.1",
"4.4.0-248.282~14.04.1",
"4.4.0-250.284~14.04.1",
"4.4.0-251.285~14.04.1",
"4.4.0-252.286~14.04.1",
"4.4.0-253.287~14.04.1",
"4.4.0-254.288~14.04.1",
"4.4.0-256.290~14.04.1",
"4.4.0-257.291~14.04.1",
"4.4.0-258.292~14.04.2",
"4.4.0-259.293~14.04.1",
"4.4.0-260.294~14.04.1",
"4.4.0-261.295~14.04.1",
"4.4.0-262.296~14.04.1",
"4.4.0-263.297~14.04.1",
"4.4.0-264.298~14.04.1",
"4.4.0-266.300~14.04.1",
"4.4.0-267.301~14.04.1",
"4.4.0-268.302~14.04.1",
"4.4.0-269.303~14.04.1",
"4.4.0-270.304~14.04.1",
"4.4.0-271.305~14.04.1",
"4.4.0-272.306~14.04.1",
"4.4.0-273.307~14.04.1",
"4.4.0-274.308~14.04.1",
"4.4.0-276.310~14.04.1",
"4.4.0-277.311~14.04.1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "block-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "crypto-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "dasd-extra-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "dasd-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "fat-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "fb-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "firewire-core-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "floppy-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "fs-core-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "fs-secondary-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "input-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "ipmi-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "irda-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "kernel-image-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "linux-buildinfo-4.4.0-278-generic",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "linux-buildinfo-4.4.0-278-lowlatency",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "linux-cloud-tools-4.4.0-278",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "linux-cloud-tools-4.4.0-278-generic",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "linux-cloud-tools-4.4.0-278-lowlatency",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "linux-cloud-tools-common",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "linux-headers-4.4.0-278",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "linux-headers-4.4.0-278-generic",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "linux-headers-4.4.0-278-lowlatency",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "linux-image-4.4.0-278-generic",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "linux-image-unsigned-4.4.0-278-generic",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "linux-image-unsigned-4.4.0-278-lowlatency",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "linux-modules-4.4.0-278-generic",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "linux-modules-4.4.0-278-lowlatency",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "linux-modules-extra-4.4.0-278-generic",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "linux-source-4.4.0",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "linux-tools-4.4.0-278",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "linux-tools-4.4.0-278-generic",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "linux-tools-4.4.0-278-lowlatency",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "linux-tools-common",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "linux-tools-host",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "linux-udebs-generic",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "md-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "message-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "mouse-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "multipath-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "nfs-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "nic-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "nic-pcmcia-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "nic-shared-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "nic-usb-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "parport-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "pata-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "pcmcia-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "pcmcia-storage-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "plip-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "ppp-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "sata-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "scsi-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "serial-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "speakup-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "storage-core-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "usb-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "virtio-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
},
{
"binary_name": "vlan-modules-4.4.0-278-generic-di",
"binary_version": "4.4.0-278.312"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "linux",
"purl": "pkg:deb/ubuntu/linux@4.4.0-278.312?arch=source\u0026distro=esm-infra/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.4.0-278.312"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.2.0-16.19",
"4.2.0-17.21",
"4.2.0-19.23",
"4.3.0-1.10",
"4.3.0-2.11",
"4.3.0-5.16",
"4.3.0-6.17",
"4.3.0-7.18",
"4.4.0-2.16",
"4.4.0-4.19",
"4.4.0-6.21",
"4.4.0-7.22",
"4.4.0-8.23",
"4.4.0-9.24",
"4.4.0-10.25",
"4.4.0-11.26",
"4.4.0-12.28",
"4.4.0-13.29",
"4.4.0-14.30",
"4.4.0-15.31",
"4.4.0-16.32",
"4.4.0-17.33",
"4.4.0-18.34",
"4.4.0-21.37",
"4.4.0-22.39",
"4.4.0-22.40",
"4.4.0-24.43",
"4.4.0-28.47",
"4.4.0-31.50",
"4.4.0-34.53",
"4.4.0-36.55",
"4.4.0-38.57",
"4.4.0-42.62",
"4.4.0-43.63",
"4.4.0-45.66",
"4.4.0-47.68",
"4.4.0-51.72",
"4.4.0-53.74",
"4.4.0-57.78",
"4.4.0-59.80",
"4.4.0-62.83",
"4.4.0-63.84",
"4.4.0-64.85",
"4.4.0-65.86",
"4.4.0-66.87",
"4.4.0-67.88",
"4.4.0-70.91",
"4.4.0-71.92",
"4.4.0-72.93",
"4.4.0-75.96",
"4.4.0-77.98",
"4.4.0-78.99",
"4.4.0-79.100",
"4.4.0-81.104",
"4.4.0-83.106",
"4.4.0-87.110",
"4.4.0-89.112",
"4.4.0-91.114",
"4.4.0-92.115",
"4.4.0-93.116",
"4.4.0-96.119",
"4.4.0-97.120",
"4.4.0-98.121",
"4.4.0-101.124",
"4.4.0-103.126",
"4.4.0-104.127",
"4.4.0-108.131",
"4.4.0-109.132",
"4.4.0-112.135",
"4.4.0-116.140",
"4.4.0-119.143",
"4.4.0-121.145",
"4.4.0-122.146",
"4.4.0-124.148",
"4.4.0-127.153",
"4.4.0-128.154",
"4.4.0-130.156",
"4.4.0-131.157",
"4.4.0-133.159",
"4.4.0-134.160",
"4.4.0-135.161",
"4.4.0-137.163",
"4.4.0-138.164",
"4.4.0-139.165",
"4.4.0-140.166",
"4.4.0-141.167",
"4.4.0-142.168",
"4.4.0-143.169",
"4.4.0-145.171",
"4.4.0-146.172",
"4.4.0-148.174",
"4.4.0-150.176",
"4.4.0-151.178",
"4.4.0-154.181",
"4.4.0-157.185",
"4.4.0-159.187",
"4.4.0-161.189",
"4.4.0-164.192",
"4.4.0-165.193",
"4.4.0-166.195",
"4.4.0-168.197",
"4.4.0-169.198",
"4.4.0-170.199",
"4.4.0-171.200",
"4.4.0-173.203",
"4.4.0-174.204",
"4.4.0-176.206",
"4.4.0-177.207",
"4.4.0-178.208",
"4.4.0-179.209",
"4.4.0-184.214",
"4.4.0-185.215",
"4.4.0-186.216",
"4.4.0-187.217",
"4.4.0-189.219",
"4.4.0-190.220",
"4.4.0-193.224",
"4.4.0-194.226",
"4.4.0-197.229",
"4.4.0-198.230",
"4.4.0-200.232",
"4.4.0-201.233",
"4.4.0-203.235",
"4.4.0-204.236",
"4.4.0-206.238",
"4.4.0-208.240",
"4.4.0-209.241",
"4.4.0-210.242",
"4.4.0-211.243",
"4.4.0-212.244",
"4.4.0-213.245",
"4.4.0-214.246",
"4.4.0-216.249",
"4.4.0-217.250",
"4.4.0-218.251",
"4.4.0-219.252",
"4.4.0-221.254",
"4.4.0-222.255",
"4.4.0-223.256",
"4.4.0-224.257",
"4.4.0-227.261",
"4.4.0-229.263",
"4.4.0-230.264",
"4.4.0-231.265",
"4.4.0-233.267",
"4.4.0-234.268",
"4.4.0-235.269",
"4.4.0-236.270",
"4.4.0-237.271",
"4.4.0-239.273",
"4.4.0-240.274",
"4.4.0-241.275",
"4.4.0-242.276",
"4.4.0-243.277",
"4.4.0-244.278",
"4.4.0-245.279",
"4.4.0-246.280",
"4.4.0-248.282",
"4.4.0-250.284",
"4.4.0-251.285",
"4.4.0-252.286",
"4.4.0-253.287",
"4.4.0-254.288",
"4.4.0-256.290",
"4.4.0-257.291",
"4.4.0-258.292",
"4.4.0-259.293",
"4.4.0-260.294",
"4.4.0-261.295",
"4.4.0-262.296",
"4.4.0-263.297",
"4.4.0-264.298",
"4.4.0-266.300",
"4.4.0-267.301",
"4.4.0-268.302",
"4.4.0-269.303",
"4.4.0-270.304",
"4.4.0-271.305",
"4.4.0-272.306",
"4.4.0-273.307",
"4.4.0-274.308",
"4.4.0-276.310",
"4.4.0-277.311"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-aws-cloud-tools-4.4.0-1190",
"binary_version": "4.4.0-1190.205"
},
{
"binary_name": "linux-aws-headers-4.4.0-1190",
"binary_version": "4.4.0-1190.205"
},
{
"binary_name": "linux-aws-tools-4.4.0-1190",
"binary_version": "4.4.0-1190.205"
},
{
"binary_name": "linux-buildinfo-4.4.0-1190-aws",
"binary_version": "4.4.0-1190.205"
},
{
"binary_name": "linux-cloud-tools-4.4.0-1190-aws",
"binary_version": "4.4.0-1190.205"
},
{
"binary_name": "linux-headers-4.4.0-1190-aws",
"binary_version": "4.4.0-1190.205"
},
{
"binary_name": "linux-image-4.4.0-1190-aws",
"binary_version": "4.4.0-1190.205"
},
{
"binary_name": "linux-modules-4.4.0-1190-aws",
"binary_version": "4.4.0-1190.205"
},
{
"binary_name": "linux-modules-extra-4.4.0-1190-aws",
"binary_version": "4.4.0-1190.205"
},
{
"binary_name": "linux-tools-4.4.0-1190-aws",
"binary_version": "4.4.0-1190.205"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "linux-aws",
"purl": "pkg:deb/ubuntu/linux-aws@4.4.0-1190.205?arch=source\u0026distro=esm-infra/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.4.0-1190.205"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.4.0-1001.10",
"4.4.0-1003.12",
"4.4.0-1004.13",
"4.4.0-1007.16",
"4.4.0-1009.18",
"4.4.0-1011.20",
"4.4.0-1012.21",
"4.4.0-1013.22",
"4.4.0-1016.25",
"4.4.0-1017.26",
"4.4.0-1018.27",
"4.4.0-1020.29",
"4.4.0-1022.31",
"4.4.0-1026.35",
"4.4.0-1028.37",
"4.4.0-1030.39",
"4.4.0-1031.40",
"4.4.0-1032.41",
"4.4.0-1035.44",
"4.4.0-1037.46",
"4.4.0-1038.47",
"4.4.0-1039.48",
"4.4.0-1041.50",
"4.4.0-1043.52",
"4.4.0-1044.53",
"4.4.0-1047.56",
"4.4.0-1048.57",
"4.4.0-1049.58",
"4.4.0-1050.59",
"4.4.0-1052.61",
"4.4.0-1054.63",
"4.4.0-1055.64",
"4.4.0-1057.66",
"4.4.0-1060.69",
"4.4.0-1061.70",
"4.4.0-1062.71",
"4.4.0-1063.72",
"4.4.0-1065.75",
"4.4.0-1066.76",
"4.4.0-1067.77",
"4.4.0-1069.79",
"4.4.0-1070.80",
"4.4.0-1072.82",
"4.4.0-1073.83",
"4.4.0-1074.84",
"4.4.0-1075.85",
"4.4.0-1077.87",
"4.4.0-1079.89",
"4.4.0-1081.91",
"4.4.0-1083.93",
"4.4.0-1084.94",
"4.4.0-1085.96",
"4.4.0-1087.98",
"4.4.0-1088.99",
"4.4.0-1090.101",
"4.4.0-1092.103",
"4.4.0-1094.105",
"4.4.0-1095.106",
"4.4.0-1096.107",
"4.4.0-1098.109",
"4.4.0-1099.110",
"4.4.0-1100.111",
"4.4.0-1101.112",
"4.4.0-1102.113",
"4.4.0-1104.115",
"4.4.0-1105.116",
"4.4.0-1106.117",
"4.4.0-1107.118",
"4.4.0-1109.120",
"4.4.0-1110.121",
"4.4.0-1111.123",
"4.4.0-1112.124",
"4.4.0-1113.126",
"4.4.0-1114.127",
"4.4.0-1117.131",
"4.4.0-1118.132",
"4.4.0-1119.133",
"4.4.0-1121.135",
"4.4.0-1122.136",
"4.4.0-1123.137",
"4.4.0-1124.138",
"4.4.0-1126.140",
"4.4.0-1127.141",
"4.4.0-1128.142",
"4.4.0-1129.143",
"4.4.0-1130.144",
"4.4.0-1131.145",
"4.4.0-1132.146",
"4.4.0-1133.147",
"4.4.0-1134.148",
"4.4.0-1135.149",
"4.4.0-1137.151",
"4.4.0-1138.152",
"4.4.0-1139.153",
"4.4.0-1140.154",
"4.4.0-1143.158",
"4.4.0-1145.160",
"4.4.0-1146.161",
"4.4.0-1147.162",
"4.4.0-1148.163",
"4.4.0-1150.165",
"4.4.0-1151.166",
"4.4.0-1152.167",
"4.4.0-1153.168",
"4.4.0-1154.169",
"4.4.0-1155.170",
"4.4.0-1156.171",
"4.4.0-1157.172",
"4.4.0-1158.173",
"4.4.0-1159.174",
"4.4.0-1160.175",
"4.4.0-1161.176",
"4.4.0-1162.177",
"4.4.0-1163.178",
"4.4.0-1164.179",
"4.4.0-1165.180",
"4.4.0-1166.181",
"4.4.0-1167.182",
"4.4.0-1168.183",
"4.4.0-1169.184",
"4.4.0-1171.186",
"4.4.0-1172.187",
"4.4.0-1173.188",
"4.4.0-1174.189",
"4.4.0-1175.190",
"4.4.0-1176.191",
"4.4.0-1177.192",
"4.4.0-1178.193",
"4.4.0-1179.194",
"4.4.0-1180.195",
"4.4.0-1181.196",
"4.4.0-1182.197",
"4.4.0-1183.198",
"4.4.0-1184.199",
"4.4.0-1185.200",
"4.4.0-1186.201",
"4.4.0-1187.202",
"4.4.0-1188.203",
"4.4.0-1189.204"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-aws-headers-4.15.0-1189",
"binary_version": "4.15.0-1189.202~16.04.1"
},
{
"binary_name": "linux-aws-hwe-cloud-tools-4.15.0-1189",
"binary_version": "4.15.0-1189.202~16.04.1"
},
{
"binary_name": "linux-aws-hwe-tools-4.15.0-1189",
"binary_version": "4.15.0-1189.202~16.04.1"
},
{
"binary_name": "linux-buildinfo-4.15.0-1189-aws",
"binary_version": "4.15.0-1189.202~16.04.1"
},
{
"binary_name": "linux-cloud-tools-4.15.0-1189-aws",
"binary_version": "4.15.0-1189.202~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-1189-aws",
"binary_version": "4.15.0-1189.202~16.04.1"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1189-aws",
"binary_version": "4.15.0-1189.202~16.04.1"
},
{
"binary_name": "linux-modules-4.15.0-1189-aws",
"binary_version": "4.15.0-1189.202~16.04.1"
},
{
"binary_name": "linux-modules-extra-4.15.0-1189-aws",
"binary_version": "4.15.0-1189.202~16.04.1"
},
{
"binary_name": "linux-tools-4.15.0-1189-aws",
"binary_version": "4.15.0-1189.202~16.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "linux-aws-hwe",
"purl": "pkg:deb/ubuntu/linux-aws-hwe@4.15.0-1189.202~16.04.1?arch=source\u0026distro=esm-infra/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.15.0-1189.202~16.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1030.31~16.04.1",
"4.15.0-1031.33~16.04.1",
"4.15.0-1032.34~16.04.1",
"4.15.0-1033.35~16.04.1",
"4.15.0-1035.37~16.04.1",
"4.15.0-1036.38~16.04.1",
"4.15.0-1039.41~16.04.1",
"4.15.0-1040.42~16.04.1",
"4.15.0-1041.43~16.04.1",
"4.15.0-1043.45~16.04.1",
"4.15.0-1044.46~16.04.1",
"4.15.0-1045.47~16.04.1",
"4.15.0-1047.49~16.04.1",
"4.15.0-1048.50~16.04.1",
"4.15.0-1050.52~16.04.1",
"4.15.0-1051.53~16.04.1",
"4.15.0-1052.54~16.04.1",
"4.15.0-1054.56~16.04.1",
"4.15.0-1056.58~16.04.1",
"4.15.0-1057.59~16.04.1",
"4.15.0-1058.60~16.04.1",
"4.15.0-1060.62~16.04.1",
"4.15.0-1063.67~16.04.1",
"4.15.0-1065.69~16.04.1",
"4.15.0-1066.70~16.04.1",
"4.15.0-1067.71~16.04.1",
"4.15.0-1073.77~16.04.1",
"4.15.0-1074.78~16.04.1",
"4.15.0-1079.83~16.04.1",
"4.15.0-1080.84~16.04.1",
"4.15.0-1082.86~16.04.1",
"4.15.0-1083.87~16.04.1",
"4.15.0-1085.90~16.04.1",
"4.15.0-1088.93~16.04.1",
"4.15.0-1090.95~16.04.1",
"4.15.0-1091.96~16.04.1",
"4.15.0-1093.99~16.04.1",
"4.15.0-1094.101~16.04.1",
"4.15.0-1095.102~16.04.1",
"4.15.0-1096.103~16.04.1",
"4.15.0-1097.104~16.04.1",
"4.15.0-1098.105~16.04.1",
"4.15.0-1099.106~16.04.1",
"4.15.0-1102.109~16.04.1",
"4.15.0-1103.110~16.04.1",
"4.15.0-1106.113~16.04.1",
"4.15.0-1109.116~16.04.1",
"4.15.0-1110.117~16.04.1",
"4.15.0-1111.118~16.04.1",
"4.15.0-1112.119~16.04.1",
"4.15.0-1113.120~16.04.1",
"4.15.0-1115.122~16.04.1",
"4.15.0-1116.123~16.04.1",
"4.15.0-1118.125~16.04.1",
"4.15.0-1119.126~16.04.2",
"4.15.0-1120.128~16.04.1",
"4.15.0-1123.132~16.04.1",
"4.15.0-1124.133~16.04.1",
"4.15.0-1126.135~16.04.2",
"4.15.0-1127.136~16.04.1",
"4.15.0-1128.137~16.04.1",
"4.15.0-1130.139~16.04.1",
"4.15.0-1133.143~16.04.1",
"4.15.0-1136.147~16.04.1",
"4.15.0-1137.148~16.04.1",
"4.15.0-1139.150~16.04.1",
"4.15.0-1140.151~16.04.1",
"4.15.0-1141.152~16.04.1",
"4.15.0-1142.154~16.04.1",
"4.15.0-1143.155~16.04.1",
"4.15.0-1146.158~16.04.2",
"4.15.0-1147.159~16.04.1",
"4.15.0-1148.160~16.04.1",
"4.15.0-1151.164~16.04.1",
"4.15.0-1153.166~16.04.1",
"4.15.0-1154.167~16.04.1",
"4.15.0-1155.168~16.04.1",
"4.15.0-1156.169~16.04.1",
"4.15.0-1157.170~16.04.1",
"4.15.0-1158.171~16.04.1",
"4.15.0-1159.172~16.04.1",
"4.15.0-1160.173~16.04.1",
"4.15.0-1161.174~16.04.1",
"4.15.0-1162.175~16.04.1",
"4.15.0-1163.176~16.04.1",
"4.15.0-1164.177~16.04.1",
"4.15.0-1165.178~16.04.1",
"4.15.0-1166.179~16.04.1",
"4.15.0-1167.180~16.04.1",
"4.15.0-1168.181~16.04.1",
"4.15.0-1169.182~16.04.1",
"4.15.0-1170.183~16.04.1",
"4.15.0-1172.185~16.04.1",
"4.15.0-1173.186~16.04.1",
"4.15.0-1174.187~16.04.1",
"4.15.0-1175.188~16.04.1",
"4.15.0-1176.189~16.04.1",
"4.15.0-1177.190~16.04.1",
"4.15.0-1178.191~16.04.1",
"4.15.0-1179.192~16.04.1",
"4.15.0-1180.193~16.04.1",
"4.15.0-1181.194~16.04.1",
"4.15.0-1182.195~16.04.1",
"4.15.0-1183.196~16.04.1",
"4.15.0-1184.197~16.04.1",
"4.15.0-1185.198~16.04.1",
"4.15.0-1186.199~16.04.1",
"4.15.0-1187.200~16.04.1",
"4.15.0-1188.201~16.04.1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-azure-cloud-tools-4.15.0-1197",
"binary_version": "4.15.0-1197.212~16.04.1"
},
{
"binary_name": "linux-azure-headers-4.15.0-1197",
"binary_version": "4.15.0-1197.212~16.04.1"
},
{
"binary_name": "linux-azure-tools-4.15.0-1197",
"binary_version": "4.15.0-1197.212~16.04.1"
},
{
"binary_name": "linux-buildinfo-4.15.0-1197-azure",
"binary_version": "4.15.0-1197.212~16.04.1"
},
{
"binary_name": "linux-cloud-tools-4.15.0-1197-azure",
"binary_version": "4.15.0-1197.212~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-1197-azure",
"binary_version": "4.15.0-1197.212~16.04.1"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1197-azure",
"binary_version": "4.15.0-1197.212~16.04.1"
},
{
"binary_name": "linux-modules-4.15.0-1197-azure",
"binary_version": "4.15.0-1197.212~16.04.1"
},
{
"binary_name": "linux-modules-extra-4.15.0-1197-azure",
"binary_version": "4.15.0-1197.212~16.04.1"
},
{
"binary_name": "linux-tools-4.15.0-1197-azure",
"binary_version": "4.15.0-1197.212~16.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "linux-azure",
"purl": "pkg:deb/ubuntu/linux-azure@4.15.0-1197.212~16.04.1?arch=source\u0026distro=esm-infra/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.15.0-1197.212~16.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.11.0-1009.9",
"4.11.0-1011.11",
"4.11.0-1013.13",
"4.11.0-1014.14",
"4.11.0-1015.15",
"4.11.0-1016.16",
"4.13.0-1005.7",
"4.13.0-1006.8",
"4.13.0-1007.9",
"4.13.0-1009.12",
"4.13.0-1011.14",
"4.13.0-1012.15",
"4.13.0-1014.17",
"4.13.0-1016.19",
"4.13.0-1018.21",
"4.15.0-1013.13~16.04.2",
"4.15.0-1014.14~16.04.1",
"4.15.0-1018.18~16.04.1",
"4.15.0-1019.19~16.04.1",
"4.15.0-1021.21~16.04.1",
"4.15.0-1022.22~16.04.1",
"4.15.0-1023.24~16.04.1",
"4.15.0-1025.26~16.04.1",
"4.15.0-1028.29~16.04.1",
"4.15.0-1030.31~16.04.1",
"4.15.0-1031.32~16.04.1",
"4.15.0-1032.33~16.04.1",
"4.15.0-1035.36~16.04.1",
"4.15.0-1036.38~16.04.1",
"4.15.0-1037.39~16.04.1",
"4.15.0-1039.43",
"4.15.0-1040.44",
"4.15.0-1041.45",
"4.15.0-1042.46",
"4.15.0-1045.49",
"4.15.0-1046.50",
"4.15.0-1047.51",
"4.15.0-1049.54",
"4.15.0-1050.55",
"4.15.0-1051.56",
"4.15.0-1052.57",
"4.15.0-1055.60",
"4.15.0-1056.61",
"4.15.0-1057.62",
"4.15.0-1059.64",
"4.15.0-1060.65",
"4.15.0-1061.66",
"4.15.0-1063.68",
"4.15.0-1064.69",
"4.15.0-1066.71",
"4.15.0-1067.72",
"4.15.0-1069.74",
"4.15.0-1071.76",
"4.15.0-1075.80",
"4.15.0-1077.82",
"4.15.0-1082.92~16.04.1",
"4.15.0-1083.93~16.04.1",
"4.15.0-1089.99~16.04.1",
"4.15.0-1091.101~16.04.1",
"4.15.0-1092.102~16.04.1",
"4.15.0-1093.103~16.04.1",
"4.15.0-1095.105~16.04.1",
"4.15.0-1096.106~16.04.1",
"4.15.0-1098.109~16.04.1",
"4.15.0-1100.111~16.04.1",
"4.15.0-1102.113~16.04.1",
"4.15.0-1103.114~16.04.1",
"4.15.0-1106.118~16.04.1",
"4.15.0-1108.120~16.04.1",
"4.15.0-1109.121~16.04.1",
"4.15.0-1110.122~16.04.1",
"4.15.0-1111.123~16.04.1",
"4.15.0-1112.124~16.04.1",
"4.15.0-1113.126~16.04.1",
"4.15.0-1114.127~16.04.1",
"4.15.0-1115.128~16.04.1",
"4.15.0-1118.131~16.04.1",
"4.15.0-1121.134~16.04.1",
"4.15.0-1122.135~16.04.1",
"4.15.0-1123.136~16.04.1",
"4.15.0-1124.137~16.04.1",
"4.15.0-1125.138~16.04.1",
"4.15.0-1126.139~16.04.1",
"4.15.0-1127.140~16.04.1",
"4.15.0-1129.142~16.04.1",
"4.15.0-1130.143~16.04.1",
"4.15.0-1131.144~16.04.1",
"4.15.0-1133.146~16.04.1",
"4.15.0-1134.147~16.04.1",
"4.15.0-1136.149~16.04.1",
"4.15.0-1137.150~16.04.1",
"4.15.0-1138.151~16.04.1",
"4.15.0-1139.152~16.04.1",
"4.15.0-1142.156~16.04.1",
"4.15.0-1145.160~16.04.1",
"4.15.0-1146.161~16.04.1",
"4.15.0-1149.164~16.04.1",
"4.15.0-1150.165~16.04.1",
"4.15.0-1151.166~16.04.1",
"4.15.0-1153.168~16.04.1",
"4.15.0-1159.174~16.04.1",
"4.15.0-1162.177~16.04.1",
"4.15.0-1163.178~16.04.1",
"4.15.0-1164.179~16.04.1",
"4.15.0-1165.180~16.04.1",
"4.15.0-1166.181~16.04.1",
"4.15.0-1167.182~16.04.1",
"4.15.0-1168.183~16.04.1",
"4.15.0-1169.184~16.04.1",
"4.15.0-1170.185~16.04.1",
"4.15.0-1171.186~16.04.1",
"4.15.0-1172.187~16.04.1",
"4.15.0-1173.188~16.04.1",
"4.15.0-1174.189~16.04.1",
"4.15.0-1175.190~16.04.1",
"4.15.0-1176.191~16.04.1",
"4.15.0-1177.192~16.04.1",
"4.15.0-1178.193~16.04.1",
"4.15.0-1179.194~16.04.1",
"4.15.0-1180.195~16.04.1",
"4.15.0-1181.196~16.04.1",
"4.15.0-1182.197~16.04.1",
"4.15.0-1183.198~16.04.1",
"4.15.0-1184.199~16.04.1",
"4.15.0-1185.200~16.04.1",
"4.15.0-1186.201~16.04.1",
"4.15.0-1187.202~16.04.1",
"4.15.0-1188.203~16.04.1",
"4.15.0-1189.204~16.04.1",
"4.15.0-1190.205~16.04.1",
"4.15.0-1191.206~16.04.1",
"4.15.0-1192.207~16.04.1",
"4.15.0-1193.208~16.04.1",
"4.15.0-1194.209~16.04.1",
"4.15.0-1195.210~16.04.1",
"4.15.0-1196.211~16.04.1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-1182-gcp",
"binary_version": "4.15.0-1182.199~16.04.1"
},
{
"binary_name": "linux-gcp-headers-4.15.0-1182",
"binary_version": "4.15.0-1182.199~16.04.1"
},
{
"binary_name": "linux-gcp-tools-4.15.0-1182",
"binary_version": "4.15.0-1182.199~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-1182-gcp",
"binary_version": "4.15.0-1182.199~16.04.1"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1182-gcp",
"binary_version": "4.15.0-1182.199~16.04.1"
},
{
"binary_name": "linux-modules-4.15.0-1182-gcp",
"binary_version": "4.15.0-1182.199~16.04.1"
},
{
"binary_name": "linux-modules-extra-4.15.0-1182-gcp",
"binary_version": "4.15.0-1182.199~16.04.1"
},
{
"binary_name": "linux-tools-4.15.0-1182-gcp",
"binary_version": "4.15.0-1182.199~16.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "linux-gcp",
"purl": "pkg:deb/ubuntu/linux-gcp@4.15.0-1182.199~16.04.1?arch=source\u0026distro=esm-infra/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.15.0-1182.199~16.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.10.0-1004.4",
"4.10.0-1006.6",
"4.10.0-1007.7",
"4.10.0-1008.8",
"4.10.0-1009.9",
"4.13.0-1002.5",
"4.13.0-1006.9",
"4.13.0-1007.10",
"4.13.0-1008.11",
"4.13.0-1011.15",
"4.13.0-1012.16",
"4.13.0-1013.17",
"4.13.0-1015.19",
"4.13.0-1017.21",
"4.13.0-1019.23",
"4.15.0-1014.14~16.04.1",
"4.15.0-1015.15~16.04.1",
"4.15.0-1017.18~16.04.1",
"4.15.0-1018.19~16.04.2",
"4.15.0-1019.20~16.04.1",
"4.15.0-1021.22~16.04.1",
"4.15.0-1023.24~16.04.1",
"4.15.0-1024.25~16.04.2",
"4.15.0-1025.26~16.04.1",
"4.15.0-1026.27~16.04.1",
"4.15.0-1027.28~16.04.1",
"4.15.0-1028.29~16.04.1",
"4.15.0-1029.31~16.04.1",
"4.15.0-1030.32~16.04.1",
"4.15.0-1032.34~16.04.1",
"4.15.0-1033.35~16.04.1",
"4.15.0-1034.36~16.04.1",
"4.15.0-1036.38~16.04.1",
"4.15.0-1037.39~16.04.1",
"4.15.0-1040.42~16.04.1",
"4.15.0-1041.43",
"4.15.0-1042.44",
"4.15.0-1044.46",
"4.15.0-1046.49",
"4.15.0-1047.50",
"4.15.0-1049.52",
"4.15.0-1050.53",
"4.15.0-1052.56",
"4.15.0-1055.59",
"4.15.0-1058.62",
"4.15.0-1060.64",
"4.15.0-1061.65",
"4.15.0-1071.81~16.04.1",
"4.15.0-1077.87~16.04.1",
"4.15.0-1078.88~16.04.1",
"4.15.0-1080.90~16.04.1",
"4.15.0-1081.92~16.04.1",
"4.15.0-1083.94~16.04.1",
"4.15.0-1084.95~16.04.1",
"4.15.0-1086.98~16.04.1",
"4.15.0-1087.100~16.04.1",
"4.15.0-1088.101~16.04.1",
"4.15.0-1090.103~16.04.1",
"4.15.0-1091.104~16.04.1",
"4.15.0-1092.105~16.04.1",
"4.15.0-1093.106~16.04.1",
"4.15.0-1094.107~16.04.1",
"4.15.0-1095.108~16.04.1",
"4.15.0-1096.109~16.04.1",
"4.15.0-1097.110~16.04.1",
"4.15.0-1098.111~16.04.1",
"4.15.0-1099.112~16.04.1",
"4.15.0-1100.113~16.04.1",
"4.15.0-1103.116~16.04.1",
"4.15.0-1106.120~16.04.1",
"4.15.0-1107.121~16.04.1",
"4.15.0-1108.122~16.04.1",
"4.15.0-1109.123~16.04.1",
"4.15.0-1110.124~16.04.1",
"4.15.0-1111.125~16.04.1",
"4.15.0-1112.126~16.04.1",
"4.15.0-1114.128~16.04.1",
"4.15.0-1115.129~16.04.1",
"4.15.0-1116.130~16.04.1",
"4.15.0-1118.132~16.04.1",
"4.15.0-1119.133~16.04.1",
"4.15.0-1120.134~16.04.1",
"4.15.0-1121.135~16.04.1",
"4.15.0-1122.136~16.04.1",
"4.15.0-1124.138~16.04.1",
"4.15.0-1127.142~16.04.1",
"4.15.0-1130.146~16.04.1",
"4.15.0-1131.147~16.04.1",
"4.15.0-1134.150~16.04.2",
"4.15.0-1135.151~16.04.2",
"4.15.0-1136.152~16.04.1",
"4.15.0-1137.153~16.04.1",
"4.15.0-1138.154~16.04.1",
"4.15.0-1141.157~16.04.2",
"4.15.0-1142.158~16.04.1",
"4.15.0-1143.159~16.04.1",
"4.15.0-1146.162~16.04.1",
"4.15.0-1147.163~16.04.1",
"4.15.0-1148.164~16.04.1",
"4.15.0-1149.165~16.04.1",
"4.15.0-1150.166~16.04.1",
"4.15.0-1151.167~16.04.1",
"4.15.0-1152.168~16.04.1",
"4.15.0-1153.170~16.04.1",
"4.15.0-1154.171~16.04.1",
"4.15.0-1155.172~16.04.1",
"4.15.0-1156.173~16.04.1",
"4.15.0-1157.174~16.04.1",
"4.15.0-1158.175~16.04.1",
"4.15.0-1159.176~16.04.1",
"4.15.0-1160.177~16.04.1",
"4.15.0-1161.178~16.04.1",
"4.15.0-1162.179~16.04.1",
"4.15.0-1163.180~16.04.1",
"4.15.0-1164.181~16.04.1",
"4.15.0-1165.182~16.04.1",
"4.15.0-1166.183~16.04.1",
"4.15.0-1167.184~16.04.2",
"4.15.0-1168.185~16.04.1",
"4.15.0-1169.186~16.04.1",
"4.15.0-1170.187~16.04.1",
"4.15.0-1171.188~16.04.1",
"4.15.0-1172.189~16.04.1",
"4.15.0-1173.190~16.04.1",
"4.15.0-1174.191~16.04.1",
"4.15.0-1175.192~16.04.1",
"4.15.0-1176.193~16.04.1",
"4.15.0-1177.194~16.04.1",
"4.15.0-1178.195~16.04.1",
"4.15.0-1179.196~16.04.1",
"4.15.0-1180.197~16.04.1",
"4.15.0-1181.198~16.04.1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "block-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "crypto-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "dasd-extra-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "dasd-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "fat-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "fb-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "firewire-core-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "floppy-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "fs-core-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "fs-secondary-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "input-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "ipmi-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "irda-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "kernel-image-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "linux-buildinfo-4.15.0-247-generic",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "linux-buildinfo-4.15.0-247-lowlatency",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "linux-cloud-tools-4.15.0-247-generic",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "linux-cloud-tools-4.15.0-247-lowlatency",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-247",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-247-generic",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-247-lowlatency",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "linux-hwe-cloud-tools-4.15.0-247",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "linux-hwe-tools-4.15.0-247",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "linux-hwe-udebs-generic",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "linux-image-4.15.0-247-generic",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "linux-image-unsigned-4.15.0-247-generic",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "linux-image-unsigned-4.15.0-247-lowlatency",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "linux-modules-4.15.0-247-generic",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "linux-modules-4.15.0-247-lowlatency",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "linux-modules-extra-4.15.0-247-generic",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "linux-tools-4.15.0-247-generic",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "linux-tools-4.15.0-247-lowlatency",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "md-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "message-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "mouse-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "multipath-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "nfs-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "nic-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "nic-pcmcia-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "nic-shared-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "nic-usb-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "parport-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "pata-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "pcmcia-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "pcmcia-storage-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "plip-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "ppp-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "sata-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "scsi-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "serial-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "storage-core-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "usb-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "virtio-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
},
{
"binary_name": "vlan-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259~16.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "linux-hwe",
"purl": "pkg:deb/ubuntu/linux-hwe@4.15.0-247.259~16.04.1?arch=source\u0026distro=esm-infra/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.15.0-247.259~16.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.8.0-36.36~16.04.1",
"4.8.0-39.42~16.04.1",
"4.8.0-41.44~16.04.1",
"4.8.0-42.45~16.04.1",
"4.8.0-44.47~16.04.1",
"4.8.0-45.48~16.04.1",
"4.8.0-46.49~16.04.1",
"4.8.0-49.52~16.04.1",
"4.8.0-51.54~16.04.1",
"4.8.0-52.55~16.04.1",
"4.8.0-53.56~16.04.1",
"4.8.0-54.57~16.04.1",
"4.8.0-56.61~16.04.1",
"4.8.0-58.63~16.04.1",
"4.10.0-27.30~16.04.2",
"4.10.0-28.32~16.04.2",
"4.10.0-30.34~16.04.1",
"4.10.0-32.36~16.04.1",
"4.10.0-33.37~16.04.1",
"4.10.0-35.39~16.04.1",
"4.10.0-37.41~16.04.1",
"4.10.0-38.42~16.04.1",
"4.10.0-40.44~16.04.1",
"4.10.0-42.46~16.04.1",
"4.13.0-26.29~16.04.2",
"4.13.0-31.34~16.04.1",
"4.13.0-32.35~16.04.1",
"4.13.0-36.40~16.04.1",
"4.13.0-37.42~16.04.1",
"4.13.0-38.43~16.04.1",
"4.13.0-39.44~16.04.1",
"4.13.0-41.46~16.04.1",
"4.13.0-43.48~16.04.1",
"4.13.0-45.50~16.04.1",
"4.15.0-24.26~16.04.1",
"4.15.0-29.31~16.04.1",
"4.15.0-30.32~16.04.1",
"4.15.0-32.35~16.04.1",
"4.15.0-33.36~16.04.1",
"4.15.0-34.37~16.04.1",
"4.15.0-36.39~16.04.1",
"4.15.0-38.41~16.04.1",
"4.15.0-39.42~16.04.1",
"4.15.0-42.45~16.04.1",
"4.15.0-43.46~16.04.1",
"4.15.0-45.48~16.04.1",
"4.15.0-46.49~16.04.1",
"4.15.0-47.50~16.04.1",
"4.15.0-48.51~16.04.1",
"4.15.0-50.54~16.04.1",
"4.15.0-51.55~16.04.1",
"4.15.0-52.56~16.04.1",
"4.15.0-54.58~16.04.1",
"4.15.0-55.60~16.04.2",
"4.15.0-58.64~16.04.1",
"4.15.0-60.67~16.04.1",
"4.15.0-62.69~16.04.1",
"4.15.0-64.73~16.04.1",
"4.15.0-65.74~16.04.1",
"4.15.0-66.75~16.04.1",
"4.15.0-69.78~16.04.1",
"4.15.0-70.79~16.04.1",
"4.15.0-72.81~16.04.1",
"4.15.0-74.83~16.04.1",
"4.15.0-76.86~16.04.1",
"4.15.0-88.88~16.04.1",
"4.15.0-91.92~16.04.1",
"4.15.0-96.97~16.04.1",
"4.15.0-99.100~16.04.1",
"4.15.0-101.102~16.04.1",
"4.15.0-106.107~16.04.1",
"4.15.0-107.108~16.04.1",
"4.15.0-112.113~16.04.1",
"4.15.0-115.116~16.04.1",
"4.15.0-117.118~16.04.1",
"4.15.0-118.119~16.04.1",
"4.15.0-120.122~16.04.1",
"4.15.0-122.124~16.04.1",
"4.15.0-123.126~16.04.1",
"4.15.0-126.129~16.04.1",
"4.15.0-128.131~16.04.1",
"4.15.0-129.132~16.04.1",
"4.15.0-132.136~16.04.1",
"4.15.0-133.137~16.04.1",
"4.15.0-136.140~16.04.1",
"4.15.0-137.141~16.04.1",
"4.15.0-139.143~16.04.1",
"4.15.0-140.144~16.04.1",
"4.15.0-142.146~16.04.1",
"4.15.0-143.147~16.04.3",
"4.15.0-144.148~16.04.1",
"4.15.0-147.151~16.04.1",
"4.15.0-151.157~16.04.1",
"4.15.0-153.160~16.04.1",
"4.15.0-154.161~16.04.1",
"4.15.0-156.163~16.04.1",
"4.15.0-158.166~16.04.1",
"4.15.0-159.167~16.04.1",
"4.15.0-161.169~16.04.1",
"4.15.0-162.170~16.04.1",
"4.15.0-163.171~16.04.1",
"4.15.0-166.174~16.04.1",
"4.15.0-167.175~16.04.1",
"4.15.0-169.177~16.04.1",
"4.15.0-171.180~16.04.1",
"4.15.0-173.182~16.04.1",
"4.15.0-175.184~16.04.1",
"4.15.0-176.185~16.04.1",
"4.15.0-177.186~16.04.1",
"4.15.0-180.189~16.04.1",
"4.15.0-184.194~16.04.1",
"4.15.0-187.198~16.04.1",
"4.15.0-188.199~16.04.1",
"4.15.0-189.200~16.04.1",
"4.15.0-191.202~16.04.1",
"4.15.0-192.203~16.04.1",
"4.15.0-193.204~16.04.1",
"4.15.0-194.205~16.04.1",
"4.15.0-196.207~16.04.1",
"4.15.0-197.208~16.04.1",
"4.15.0-200.211~16.04.2",
"4.15.0-201.212~16.04.1",
"4.15.0-202.213~16.04.1",
"4.15.0-206.217~16.04.1",
"4.15.0-208.219~16.04.1",
"4.15.0-209.220~16.04.1",
"4.15.0-210.221~16.04.1",
"4.15.0-211.222~16.04.1",
"4.15.0-212.223~16.04.1",
"4.15.0-213.224~16.04.1",
"4.15.0-214.225~16.04.1",
"4.15.0-216.227~16.04.1",
"4.15.0-218.229~16.04.1",
"4.15.0-219.230~16.04.1",
"4.15.0-220.231~16.04.1",
"4.15.0-221.232~16.04.1",
"4.15.0-222.233~16.04.1",
"4.15.0-223.235~16.04.1",
"4.15.0-224.236~16.04.1",
"4.15.0-225.237~16.04.1",
"4.15.0-226.238~16.04.1",
"4.15.0-227.239~16.04.1",
"4.15.0-228.240~16.04.1",
"4.15.0-229.241~16.04.1",
"4.15.0-230.242~16.04.1",
"4.15.0-231.243~16.04.1",
"4.15.0-232.244~16.04.1",
"4.15.0-233.245~16.04.1",
"4.15.0-234.246~16.04.1",
"4.15.0-235.247~16.04.1",
"4.15.0-236.248~16.04.1",
"4.15.0-237.249~16.04.1",
"4.15.0-238.250~16.04.1",
"4.15.0-239.251~16.04.1",
"4.15.0-240.252~16.04.1",
"4.15.0-241.253~16.04.1",
"4.15.0-242.254~16.04.1",
"4.15.0-243.255~16.04.1",
"4.15.0-245.257~16.04.1",
"4.15.0-246.258~16.04.1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-4.4.0-1153-kvm",
"binary_version": "4.4.0-1153.164"
},
{
"binary_name": "linux-cloud-tools-4.4.0-1153-kvm",
"binary_version": "4.4.0-1153.164"
},
{
"binary_name": "linux-headers-4.4.0-1153-kvm",
"binary_version": "4.4.0-1153.164"
},
{
"binary_name": "linux-image-4.4.0-1153-kvm",
"binary_version": "4.4.0-1153.164"
},
{
"binary_name": "linux-kvm-cloud-tools-4.4.0-1153",
"binary_version": "4.4.0-1153.164"
},
{
"binary_name": "linux-kvm-headers-4.4.0-1153",
"binary_version": "4.4.0-1153.164"
},
{
"binary_name": "linux-kvm-tools-4.4.0-1153",
"binary_version": "4.4.0-1153.164"
},
{
"binary_name": "linux-modules-4.4.0-1153-kvm",
"binary_version": "4.4.0-1153.164"
},
{
"binary_name": "linux-tools-4.4.0-1153-kvm",
"binary_version": "4.4.0-1153.164"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "linux-kvm",
"purl": "pkg:deb/ubuntu/linux-kvm@4.4.0-1153.164?arch=source\u0026distro=esm-infra/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.4.0-1153.164"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.4.0-1004.9",
"4.4.0-1007.12",
"4.4.0-1008.13",
"4.4.0-1009.14",
"4.4.0-1010.15",
"4.4.0-1012.17",
"4.4.0-1013.18",
"4.4.0-1015.20",
"4.4.0-1017.22",
"4.4.0-1019.24",
"4.4.0-1020.25",
"4.4.0-1021.26",
"4.4.0-1023.28",
"4.4.0-1026.31",
"4.4.0-1027.32",
"4.4.0-1029.34",
"4.4.0-1031.37",
"4.4.0-1032.38",
"4.4.0-1033.39",
"4.4.0-1035.41",
"4.4.0-1036.42",
"4.4.0-1037.43",
"4.4.0-1038.44",
"4.4.0-1039.45",
"4.4.0-1040.46",
"4.4.0-1041.47",
"4.4.0-1043.49",
"4.4.0-1044.50",
"4.4.0-1046.52",
"4.4.0-1047.53",
"4.4.0-1048.55",
"4.4.0-1051.58",
"4.4.0-1052.59",
"4.4.0-1054.61",
"4.4.0-1056.63",
"4.4.0-1058.65",
"4.4.0-1059.66",
"4.4.0-1060.67",
"4.4.0-1062.69",
"4.4.0-1063.70",
"4.4.0-1064.71",
"4.4.0-1065.72",
"4.4.0-1066.73",
"4.4.0-1068.75",
"4.4.0-1069.76",
"4.4.0-1070.77",
"4.4.0-1071.78",
"4.4.0-1075.82",
"4.4.0-1076.83",
"4.4.0-1077.84",
"4.4.0-1078.85",
"4.4.0-1079.86",
"4.4.0-1080.87",
"4.4.0-1082.91",
"4.4.0-1084.93",
"4.4.0-1085.94",
"4.4.0-1087.96",
"4.4.0-1088.97",
"4.4.0-1089.98",
"4.4.0-1090.99",
"4.4.0-1091.100",
"4.4.0-1092.101",
"4.4.0-1093.102",
"4.4.0-1094.103",
"4.4.0-1095.104",
"4.4.0-1096.105",
"4.4.0-1097.106",
"4.4.0-1098.107",
"4.4.0-1099.108",
"4.4.0-1100.109",
"4.4.0-1102.111",
"4.4.0-1103.112",
"4.4.0-1104.113",
"4.4.0-1105.114",
"4.4.0-1108.118",
"4.4.0-1110.120",
"4.4.0-1111.121",
"4.4.0-1112.122",
"4.4.0-1113.123",
"4.4.0-1114.124",
"4.4.0-1115.125",
"4.4.0-1116.126",
"4.4.0-1117.127",
"4.4.0-1118.128",
"4.4.0-1119.129",
"4.4.0-1120.130",
"4.4.0-1121.131",
"4.4.0-1122.132",
"4.4.0-1123.133",
"4.4.0-1124.134",
"4.4.0-1125.135",
"4.4.0-1126.136",
"4.4.0-1128.138",
"4.4.0-1129.139",
"4.4.0-1130.140",
"4.4.0-1131.141",
"4.4.0-1132.142",
"4.4.0-1134.144",
"4.4.0-1135.145",
"4.4.0-1136.146",
"4.4.0-1137.147",
"4.4.0-1138.148",
"4.4.0-1139.149",
"4.4.0-1140.151",
"4.4.0-1141.152",
"4.4.0-1142.153",
"4.4.0-1143.154",
"4.4.0-1144.155",
"4.4.0-1145.156",
"4.4.0-1146.157",
"4.4.0-1147.158",
"4.4.0-1148.159",
"4.4.0-1149.160",
"4.4.0-1150.161",
"4.4.0-1151.162",
"4.4.0-1152.163"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-1151-oracle",
"binary_version": "4.15.0-1151.162~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-1151-oracle",
"binary_version": "4.15.0-1151.162~16.04.1"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1151-oracle",
"binary_version": "4.15.0-1151.162~16.04.1"
},
{
"binary_name": "linux-modules-4.15.0-1151-oracle",
"binary_version": "4.15.0-1151.162~16.04.1"
},
{
"binary_name": "linux-modules-extra-4.15.0-1151-oracle",
"binary_version": "4.15.0-1151.162~16.04.1"
},
{
"binary_name": "linux-oracle-headers-4.15.0-1151",
"binary_version": "4.15.0-1151.162~16.04.1"
},
{
"binary_name": "linux-oracle-tools-4.15.0-1151",
"binary_version": "4.15.0-1151.162~16.04.1"
},
{
"binary_name": "linux-tools-4.15.0-1151-oracle",
"binary_version": "4.15.0-1151.162~16.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "linux-oracle",
"purl": "pkg:deb/ubuntu/linux-oracle@4.15.0-1151.162~16.04.1?arch=source\u0026distro=esm-infra/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.15.0-1151.162~16.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1007.9~16.04.1",
"4.15.0-1008.10~16.04.1",
"4.15.0-1009.11~16.04.1",
"4.15.0-1010.12~16.04.1",
"4.15.0-1011.13~16.04.1",
"4.15.0-1013.15~16.04.1",
"4.15.0-1014.16~16.04.1",
"4.15.0-1015.17~16.04.1",
"4.15.0-1017.19~16.04.2",
"4.15.0-1018.20~16.04.1",
"4.15.0-1021.23~16.04.1",
"4.15.0-1022.25~16.04.1",
"4.15.0-1023.26~16.04.1",
"4.15.0-1025.28~16.04.1",
"4.15.0-1026.29~16.04.1",
"4.15.0-1027.30~16.04.1",
"4.15.0-1029.32~16.04.1",
"4.15.0-1030.33~16.04.1",
"4.15.0-1031.34~16.04.1",
"4.15.0-1033.36~16.04.1",
"4.15.0-1035.38~16.04.1",
"4.15.0-1037.41~16.04.1",
"4.15.0-1038.42~16.04.1",
"4.15.0-1039.43~16.04.1",
"4.15.0-1045.49~16.04.1",
"4.15.0-1046.50~16.04.1",
"4.15.0-1050.54~16.04.1",
"4.15.0-1051.55~16.04.1",
"4.15.0-1053.57~16.04.1",
"4.15.0-1054.58~16.04.1",
"4.15.0-1056.61~16.04.1",
"4.15.0-1058.64~16.04.1",
"4.15.0-1059.65~16.04.1",
"4.15.0-1061.67~16.04.1",
"4.15.0-1062.68~16.04.1",
"4.15.0-1064.71~16.04.1",
"4.15.0-1065.73~16.04.1",
"4.15.0-1066.74~16.04.1",
"4.15.0-1067.75~16.04.1",
"4.15.0-1068.76~16.04.1",
"4.15.0-1069.77~16.04.1",
"4.15.0-1070.78~16.04.1",
"4.15.0-1071.79~16.04.1",
"4.15.0-1072.80~16.04.1",
"4.15.0-1075.83~16.04.1",
"4.15.0-1078.86~16.04.1",
"4.15.0-1079.87~16.04.1",
"4.15.0-1080.88~16.04.1",
"4.15.0-1081.89~16.04.1",
"4.15.0-1082.90~16.04.1",
"4.15.0-1083.91~16.04.1",
"4.15.0-1084.92~16.04.1",
"4.15.0-1085.93~16.04.1",
"4.15.0-1086.94~16.04.1",
"4.15.0-1087.95~16.04.1",
"4.15.0-1089.98~16.04.1",
"4.15.0-1090.99~16.04.1",
"4.15.0-1091.100~16.04.1",
"4.15.0-1092.101~16.04.1",
"4.15.0-1093.102~16.04.1",
"4.15.0-1095.104~16.04.1",
"4.15.0-1098.108~16.04.1",
"4.15.0-1101.112~16.04.1",
"4.15.0-1102.113~16.04.1",
"4.15.0-1104.115~16.04.1",
"4.15.0-1105.116~16.04.1",
"4.15.0-1106.117~16.04.1",
"4.15.0-1107.118~16.04.1",
"4.15.0-1108.119~16.04.1",
"4.15.0-1111.122~16.04.2",
"4.15.0-1112.123~16.04.1",
"4.15.0-1113.124~16.04.1",
"4.15.0-1115.126~16.04.1",
"4.15.0-1116.127~16.04.1",
"4.15.0-1117.128~16.04.1",
"4.15.0-1118.129~16.04.1",
"4.15.0-1119.130~16.04.1",
"4.15.0-1120.131~16.04.1",
"4.15.0-1121.132~16.04.1",
"4.15.0-1122.133~16.04.1",
"4.15.0-1123.134~16.04.1",
"4.15.0-1124.135~16.04.1",
"4.15.0-1125.136~16.04.1",
"4.15.0-1126.137~16.04.1",
"4.15.0-1127.138~16.04.1",
"4.15.0-1128.139~16.04.1",
"4.15.0-1129.140~16.04.1",
"4.15.0-1130.141~16.04.1",
"4.15.0-1131.142~16.04.1",
"4.15.0-1132.143~16.04.1",
"4.15.0-1133.144~16.04.1",
"4.15.0-1134.145~16.04.1",
"4.15.0-1135.146~16.04.1",
"4.15.0-1136.147~16.04.1",
"4.15.0-1137.148~16.04.1",
"4.15.0-1138.149~16.04.1",
"4.15.0-1139.150~16.04.1",
"4.15.0-1140.151~16.04.1",
"4.15.0-1141.152~16.04.1",
"4.15.0-1142.153~16.04.1",
"4.15.0-1143.154~16.04.1",
"4.15.0-1144.155~16.04.1",
"4.15.0-1145.156~16.04.1",
"4.15.0-1148.159~16.04.1",
"4.15.0-1149.160~16.04.1",
"4.15.0-1150.161~16.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "block-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "block-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "crypto-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "crypto-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "dasd-extra-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "dasd-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "fat-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "fat-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "fb-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "firewire-core-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "floppy-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "fs-core-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "fs-core-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "fs-secondary-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "fs-secondary-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "input-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "input-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "ipmi-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "ipmi-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "irda-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "irda-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "kernel-image-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "kernel-image-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-cloud-tools-4.15.0-23-generic",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-cloud-tools-4.15.0-23-lowlatency",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-23",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-23-generic",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-23-generic-lpae",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-23-lowlatency",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-hwe-edge-cloud-tools-4.15.0-23",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-hwe-edge-tools-4.15.0-23",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-hwe-edge-udebs-generic",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-hwe-edge-udebs-generic-lpae",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-image-4.15.0-23-generic",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-image-4.15.0-23-generic-lpae",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-image-4.15.0-23-lowlatency",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-image-unsigned-4.15.0-23-generic",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-image-unsigned-4.15.0-23-lowlatency",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-modules-4.15.0-23-generic",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-modules-4.15.0-23-generic-lpae",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-modules-4.15.0-23-lowlatency",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-modules-extra-4.15.0-23-generic",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-source-4.15.0",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-tools-4.15.0-23-generic",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-tools-4.15.0-23-generic-lpae",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-tools-4.15.0-23-lowlatency",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "md-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "md-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "message-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "mouse-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "mouse-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "multipath-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "multipath-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "nfs-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "nfs-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "nic-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "nic-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "nic-pcmcia-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "nic-shared-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "nic-shared-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "nic-usb-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "nic-usb-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "parport-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "parport-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "pata-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "pcmcia-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "pcmcia-storage-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "plip-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "plip-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "ppp-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "ppp-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "sata-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "sata-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "scsi-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "scsi-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "serial-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "storage-core-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "storage-core-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "usb-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "usb-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "virtio-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "vlan-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "vlan-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:16.04:LTS",
"name": "linux-hwe-edge",
"purl": "pkg:deb/ubuntu/linux-hwe-edge@4.15.0-23.25~16.04.1?arch=source\u0026distro=xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.8.0-28.30~16.04.1",
"4.8.0-30.32~16.04.1",
"4.8.0-32.34~16.04.1",
"4.8.0-34.36~16.04.1",
"4.10.0-14.16~16.04.1",
"4.10.0-19.21~16.04.1",
"4.10.0-20.22~16.04.1",
"4.10.0-21.23~16.04.1",
"4.10.0-22.24~16.04.1",
"4.10.0-24.28~16.04.1",
"4.10.0-26.30~16.04.1",
"4.11.0-13.19~16.04.1",
"4.11.0-14.20~16.04.1",
"4.13.0-16.19~16.04.3",
"4.13.0-17.20~16.04.1",
"4.13.0-19.22~16.04.1",
"4.13.0-21.24~16.04.1",
"4.13.0-25.29~16.04.2",
"4.15.0-13.14~16.04.1",
"4.15.0-15.16~16.04.1",
"4.15.0-20.21~16.04.1",
"4.15.0-22.24~16.04.1",
"4.15.0-23.25~16.04.1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "block-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "crypto-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "dasd-extra-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "dasd-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "fat-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "fb-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "firewire-core-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "floppy-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "fs-core-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "fs-secondary-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "input-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "ipmi-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "irda-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "kernel-image-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "linux-buildinfo-4.4.0-1122-fips",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "linux-fips-cloud-tools-common",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "linux-fips-headers-4.4.0-1122",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "linux-fips-source-4.4.0",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "linux-fips-tools-4.4.0-1122",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "linux-headers-4.4.0-1122-fips",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "linux-image-4.4.0-1122-fips",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "linux-image-hmac-4.4.0-1122-fips",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "linux-image-unsigned-4.4.0-1122-fips",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "linux-image-unsigned-hmac-4.4.0-1122-fips",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "linux-modules-4.4.0-1122-fips",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "linux-modules-extra-4.4.0-1122-fips",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "linux-tools-4.4.0-1122-fips",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "linux-udebs-fips",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "md-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "message-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "mouse-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "multipath-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "nfs-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "nic-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "nic-pcmcia-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "nic-shared-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "nic-usb-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "parport-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "pata-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "pcmcia-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "pcmcia-storage-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "plip-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "ppp-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "sata-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "scsi-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "serial-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "speakup-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "storage-core-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "usb-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "virtio-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
},
{
"binary_name": "vlan-modules-4.4.0-1122-fips-di",
"binary_version": "4.4.0-1122.129"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS:16.04:LTS",
"name": "linux-fips",
"purl": "pkg:deb/ubuntu/linux-fips@4.4.0-1122.129?arch=source\u0026distro=fips-updates/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.4.0-1122.129"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.4.0-1003.3",
"4.4.0-1005.5",
"4.4.0-1006.6",
"4.4.0-1008.10",
"4.4.0-1010.13",
"4.4.0-1011.14",
"4.4.0-1012.16",
"4.4.0-1013.17",
"4.4.0-1015.20",
"4.4.0-1017.22",
"4.4.0-1019.24",
"4.4.0-1021.26",
"4.4.0-1022.27",
"4.4.0-1023.28",
"4.4.0-1025.30",
"4.4.0-1026.31",
"4.4.0-1027.32",
"4.4.0-1028.33",
"4.4.0-1029.34",
"4.4.0-1031.36",
"4.4.0-1032.37",
"4.4.0-1033.38",
"4.4.0-1034.39",
"4.4.0-1041.46",
"4.4.0-1042.47",
"4.4.0-1043.48",
"4.4.0-1044.49",
"4.4.0-1045.50",
"4.4.0-1046.51",
"4.4.0-1048.53",
"4.4.0-1049.55",
"4.4.0-1051.57",
"4.4.0-1052.58",
"4.4.0-1054.60",
"4.4.0-1055.61",
"4.4.0-1056.62",
"4.4.0-1057.63",
"4.4.0-1058.64",
"4.4.0-1060.66",
"4.4.0-1061.67",
"4.4.0-1062.68",
"4.4.0-1063.69",
"4.4.0-1064.70",
"4.4.0-1065.71",
"4.4.0-1066.72",
"4.4.0-1067.73",
"4.4.0-1068.74",
"4.4.0-1069.75",
"4.4.0-1071.77",
"4.4.0-1072.78",
"4.4.0-1073.79",
"4.4.0-1074.80",
"4.4.0-1077.84",
"4.4.0-1079.86",
"4.4.0-1080.87",
"4.4.0-1081.88",
"4.4.0-1082.89",
"4.4.0-1083.90",
"4.4.0-1084.91",
"4.4.0-1085.92",
"4.4.0-1086.93",
"4.4.0-1088.95",
"4.4.0-1089.96",
"4.4.0-1090.97",
"4.4.0-1091.98",
"4.4.0-1092.99",
"4.4.0-1093.100",
"4.4.0-1094.101",
"4.4.0-1095.102",
"4.4.0-1097.104",
"4.4.0-1099.106",
"4.4.0-1100.107",
"4.4.0-1101.108",
"4.4.0-1102.109",
"4.4.0-1103.110",
"4.4.0-1104.111",
"4.4.0-1105.112",
"4.4.0-1106.113",
"4.4.0-1107.114",
"4.4.0-1108.115",
"4.4.0-1109.116",
"4.4.0-1110.117",
"4.4.0-1111.118",
"4.4.0-1112.119",
"4.4.0-1113.120",
"4.4.0-1114.121",
"4.4.0-1115.122",
"4.4.0-1116.123",
"4.4.0-1117.124",
"4.4.0-1119.126",
"4.4.0-1120.127",
"4.4.0-1121.128"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "block-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "crypto-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "dasd-extra-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "dasd-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "fat-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "fb-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "firewire-core-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "floppy-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "fs-core-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "fs-secondary-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "input-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "ipmi-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "irda-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "kernel-image-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "linux-fips-headers-4.4.0-1002",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "linux-fips-source-4.4.0",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "linux-fips-tools-4.4.0-1002",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "linux-headers-4.4.0-1002-fips",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "linux-image-4.4.0-1002-fips",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "linux-image-extra-4.4.0-1002-fips",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "linux-image-hmac-4.4.0-1002-fips",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "linux-tools-4.4.0-1002-fips",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "linux-udebs-fips",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "md-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "message-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "mouse-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "multipath-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "nfs-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "nic-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "nic-pcmcia-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "nic-shared-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "nic-usb-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "parport-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "pata-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "pcmcia-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "pcmcia-storage-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "plip-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "ppp-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "sata-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "scsi-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "serial-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "speakup-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "storage-core-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "usb-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "virtio-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "vlan-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS:16.04:LTS",
"name": "linux-fips",
"purl": "pkg:deb/ubuntu/linux-fips@4.4.0-1002.2?arch=source\u0026distro=fips/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.4.0-1001.1",
"4.4.0-1002.2"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "block-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "crypto-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "dasd-extra-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "dasd-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "fat-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "fb-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "firewire-core-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "floppy-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "fs-core-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "fs-secondary-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "input-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "ipmi-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "irda-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "kernel-image-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "linux-buildinfo-4.15.0-247-generic",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "linux-buildinfo-4.15.0-247-lowlatency",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "linux-cloud-tools-4.15.0-247",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "linux-cloud-tools-4.15.0-247-generic",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "linux-cloud-tools-4.15.0-247-lowlatency",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "linux-cloud-tools-common",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "linux-headers-4.15.0-247",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "linux-headers-4.15.0-247-generic",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "linux-headers-4.15.0-247-lowlatency",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "linux-image-4.15.0-247-generic",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "linux-image-unsigned-4.15.0-247-generic",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "linux-image-unsigned-4.15.0-247-lowlatency",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "linux-modules-4.15.0-247-generic",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "linux-modules-4.15.0-247-lowlatency",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "linux-modules-extra-4.15.0-247-generic",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "linux-source-4.15.0",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "linux-tools-4.15.0-247",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "linux-tools-4.15.0-247-generic",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "linux-tools-4.15.0-247-lowlatency",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "linux-tools-common",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "linux-tools-host",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "linux-udebs-generic",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "md-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "message-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "mouse-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "multipath-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "nfs-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "nic-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "nic-pcmcia-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "nic-shared-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "nic-usb-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "parport-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "pata-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "pcmcia-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "pcmcia-storage-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "plip-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "ppp-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "sata-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "scsi-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "serial-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "storage-core-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "usb-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "virtio-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
},
{
"binary_name": "vlan-modules-4.15.0-247-generic-di",
"binary_version": "4.15.0-247.259"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "linux",
"purl": "pkg:deb/ubuntu/linux@4.15.0-247.259?arch=source\u0026distro=esm-infra/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.15.0-247.259"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.13.0-16.19",
"4.13.0-17.20",
"4.13.0-25.29",
"4.13.0-32.35",
"4.15.0-10.11",
"4.15.0-12.13",
"4.15.0-13.14",
"4.15.0-15.16",
"4.15.0-19.20",
"4.15.0-20.21",
"4.15.0-22.24",
"4.15.0-23.25",
"4.15.0-24.26",
"4.15.0-29.31",
"4.15.0-30.32",
"4.15.0-32.35",
"4.15.0-33.36",
"4.15.0-34.37",
"4.15.0-36.39",
"4.15.0-38.41",
"4.15.0-39.42",
"4.15.0-42.45",
"4.15.0-43.46",
"4.15.0-44.47",
"4.15.0-45.48",
"4.15.0-46.49",
"4.15.0-47.50",
"4.15.0-48.51",
"4.15.0-50.54",
"4.15.0-51.55",
"4.15.0-52.56",
"4.15.0-54.58",
"4.15.0-55.60",
"4.15.0-58.64",
"4.15.0-60.67",
"4.15.0-62.69",
"4.15.0-64.73",
"4.15.0-65.74",
"4.15.0-66.75",
"4.15.0-69.78",
"4.15.0-70.79",
"4.15.0-72.81",
"4.15.0-74.84",
"4.15.0-76.86",
"4.15.0-88.88",
"4.15.0-91.92",
"4.15.0-96.97",
"4.15.0-99.100",
"4.15.0-101.102",
"4.15.0-106.107",
"4.15.0-108.109",
"4.15.0-109.110",
"4.15.0-111.112",
"4.15.0-112.113",
"4.15.0-115.116",
"4.15.0-117.118",
"4.15.0-118.119",
"4.15.0-121.123",
"4.15.0-122.124",
"4.15.0-123.126",
"4.15.0-124.127",
"4.15.0-126.129",
"4.15.0-128.131",
"4.15.0-129.132",
"4.15.0-130.134",
"4.15.0-132.136",
"4.15.0-134.138",
"4.15.0-135.139",
"4.15.0-136.140",
"4.15.0-137.141",
"4.15.0-139.143",
"4.15.0-140.144",
"4.15.0-141.145",
"4.15.0-142.146",
"4.15.0-143.147",
"4.15.0-144.148",
"4.15.0-147.151",
"4.15.0-151.157",
"4.15.0-153.160",
"4.15.0-154.161",
"4.15.0-156.163",
"4.15.0-158.166",
"4.15.0-159.167",
"4.15.0-161.169",
"4.15.0-162.170",
"4.15.0-163.171",
"4.15.0-166.174",
"4.15.0-167.175",
"4.15.0-169.177",
"4.15.0-171.180",
"4.15.0-173.182",
"4.15.0-175.184",
"4.15.0-176.185",
"4.15.0-177.186",
"4.15.0-180.189",
"4.15.0-184.194",
"4.15.0-187.198",
"4.15.0-188.199",
"4.15.0-189.200",
"4.15.0-191.202",
"4.15.0-192.203",
"4.15.0-193.204",
"4.15.0-194.205",
"4.15.0-196.207",
"4.15.0-197.208",
"4.15.0-200.211",
"4.15.0-201.212",
"4.15.0-202.213",
"4.15.0-204.215",
"4.15.0-206.217",
"4.15.0-208.220",
"4.15.0-209.220",
"4.15.0-210.221",
"4.15.0-211.222",
"4.15.0-212.223",
"4.15.0-213.224",
"4.15.0-214.225",
"4.15.0-216.227",
"4.15.0-218.229",
"4.15.0-219.230",
"4.15.0-220.231",
"4.15.0-221.232",
"4.15.0-222.233",
"4.15.0-223.235",
"4.15.0-224.236",
"4.15.0-225.237",
"4.15.0-226.238",
"4.15.0-227.239",
"4.15.0-228.240",
"4.15.0-229.241",
"4.15.0-230.242",
"4.15.0-231.243",
"4.15.0-232.244",
"4.15.0-233.245",
"4.15.0-234.246",
"4.15.0-235.247",
"4.15.0-236.248",
"4.15.0-237.249",
"4.15.0-238.250",
"4.15.0-239.251",
"4.15.0-240.252",
"4.15.0-241.253",
"4.15.0-242.254",
"4.15.0-243.255",
"4.15.0-245.257",
"4.15.0-246.258"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-aws-cloud-tools-4.15.0-1189",
"binary_version": "4.15.0-1189.202"
},
{
"binary_name": "linux-aws-headers-4.15.0-1189",
"binary_version": "4.15.0-1189.202"
},
{
"binary_name": "linux-aws-tools-4.15.0-1189",
"binary_version": "4.15.0-1189.202"
},
{
"binary_name": "linux-buildinfo-4.15.0-1189-aws",
"binary_version": "4.15.0-1189.202"
},
{
"binary_name": "linux-cloud-tools-4.15.0-1189-aws",
"binary_version": "4.15.0-1189.202"
},
{
"binary_name": "linux-headers-4.15.0-1189-aws",
"binary_version": "4.15.0-1189.202"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1189-aws",
"binary_version": "4.15.0-1189.202"
},
{
"binary_name": "linux-modules-4.15.0-1189-aws",
"binary_version": "4.15.0-1189.202"
},
{
"binary_name": "linux-modules-extra-4.15.0-1189-aws",
"binary_version": "4.15.0-1189.202"
},
{
"binary_name": "linux-tools-4.15.0-1189-aws",
"binary_version": "4.15.0-1189.202"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "linux-aws",
"purl": "pkg:deb/ubuntu/linux-aws@4.15.0-1189.202?arch=source\u0026distro=esm-infra/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.15.0-1189.202"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1001.1",
"4.15.0-1003.3",
"4.15.0-1005.5",
"4.15.0-1006.6",
"4.15.0-1007.7",
"4.15.0-1009.9",
"4.15.0-1010.10",
"4.15.0-1011.11",
"4.15.0-1016.16",
"4.15.0-1017.17",
"4.15.0-1019.19",
"4.15.0-1020.20",
"4.15.0-1021.21",
"4.15.0-1023.23",
"4.15.0-1025.25",
"4.15.0-1027.27",
"4.15.0-1029.30",
"4.15.0-1031.33",
"4.15.0-1032.34",
"4.15.0-1033.35",
"4.15.0-1034.36",
"4.15.0-1035.37",
"4.15.0-1037.39",
"4.15.0-1039.41",
"4.15.0-1040.42",
"4.15.0-1041.43",
"4.15.0-1043.45",
"4.15.0-1044.46",
"4.15.0-1045.47",
"4.15.0-1047.49",
"4.15.0-1048.50",
"4.15.0-1050.52",
"4.15.0-1051.53",
"4.15.0-1052.54",
"4.15.0-1054.56",
"4.15.0-1056.58",
"4.15.0-1057.59",
"4.15.0-1058.60",
"4.15.0-1060.62",
"4.15.0-1063.67",
"4.15.0-1065.69",
"4.15.0-1066.70",
"4.15.0-1067.71",
"4.15.0-1073.77",
"4.15.0-1076.80",
"4.15.0-1077.81",
"4.15.0-1079.83",
"4.15.0-1080.84",
"4.15.0-1082.86",
"4.15.0-1083.87",
"4.15.0-1086.91",
"4.15.0-1087.92",
"4.15.0-1088.93",
"4.15.0-1090.95",
"4.15.0-1091.96",
"4.15.0-1092.98",
"4.15.0-1093.99",
"4.15.0-1094.101",
"4.15.0-1095.102",
"4.15.0-1096.103",
"4.15.0-1097.104",
"4.15.0-1098.105",
"4.15.0-1099.106",
"4.15.0-1101.108",
"4.15.0-1102.109",
"4.15.0-1103.110",
"4.15.0-1106.113",
"4.15.0-1109.116",
"4.15.0-1110.117",
"4.15.0-1111.118",
"4.15.0-1112.119",
"4.15.0-1114.121",
"4.15.0-1115.122",
"4.15.0-1116.123",
"4.15.0-1118.125",
"4.15.0-1119.127",
"4.15.0-1121.129",
"4.15.0-1123.132",
"4.15.0-1124.133",
"4.15.0-1126.135",
"4.15.0-1127.136",
"4.15.0-1128.137",
"4.15.0-1130.139",
"4.15.0-1133.143",
"4.15.0-1136.147",
"4.15.0-1137.148",
"4.15.0-1139.150",
"4.15.0-1140.151",
"4.15.0-1141.152",
"4.15.0-1142.154",
"4.15.0-1143.155",
"4.15.0-1144.156",
"4.15.0-1146.158",
"4.15.0-1147.159",
"4.15.0-1148.160",
"4.15.0-1150.163",
"4.15.0-1151.164",
"4.15.0-1153.166",
"4.15.0-1154.167",
"4.15.0-1155.168",
"4.15.0-1156.169",
"4.15.0-1157.170",
"4.15.0-1158.171",
"4.15.0-1159.172",
"4.15.0-1160.173",
"4.15.0-1161.174",
"4.15.0-1162.175",
"4.15.0-1163.176",
"4.15.0-1164.177",
"4.15.0-1165.178",
"4.15.0-1166.179",
"4.15.0-1167.180",
"4.15.0-1168.181",
"4.15.0-1169.182",
"4.15.0-1170.183",
"4.15.0-1172.185",
"4.15.0-1173.186",
"4.15.0-1174.187",
"4.15.0-1175.188",
"4.15.0-1176.189",
"4.15.0-1177.190",
"4.15.0-1178.191",
"4.15.0-1179.192",
"4.15.0-1180.193",
"4.15.0-1181.194",
"4.15.0-1182.195",
"4.15.0-1183.196",
"4.15.0-1184.197",
"4.15.0-1185.198",
"4.15.0-1186.199",
"4.15.0-1187.200",
"4.15.0-1188.201"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-aws-5.0-tools-5.0.0-1027",
"binary_version": "5.0.0-1027.30"
},
{
"binary_name": "linux-aws-headers-5.0.0-1027",
"binary_version": "5.0.0-1027.30"
},
{
"binary_name": "linux-buildinfo-5.0.0-1027-aws",
"binary_version": "5.0.0-1027.30"
},
{
"binary_name": "linux-cloud-tools-5.0.0-1027-aws",
"binary_version": "5.0.0-1027.30"
},
{
"binary_name": "linux-headers-5.0.0-1027-aws",
"binary_version": "5.0.0-1027.30"
},
{
"binary_name": "linux-image-5.0.0-1027-aws",
"binary_version": "5.0.0-1027.30"
},
{
"binary_name": "linux-modules-5.0.0-1027-aws",
"binary_version": "5.0.0-1027.30"
},
{
"binary_name": "linux-modules-extra-5.0.0-1027-aws",
"binary_version": "5.0.0-1027.30"
},
{
"binary_name": "linux-tools-5.0.0-1027-aws",
"binary_version": "5.0.0-1027.30"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-aws-5.0",
"purl": "pkg:deb/ubuntu/linux-aws-5.0@5.0.0-1027.30?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.0.0-1021.24~18.04.1",
"5.0.0-1022.25~18.04.1",
"5.0.0-1023.26~18.04.1",
"5.0.0-1024.27~18.04.1",
"5.0.0-1025.28",
"5.0.0-1027.30"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-aws-5.3-cloud-tools-5.3.0-1035",
"binary_version": "5.3.0-1035.37"
},
{
"binary_name": "linux-aws-5.3-headers-5.3.0-1035",
"binary_version": "5.3.0-1035.37"
},
{
"binary_name": "linux-aws-5.3-tools-5.3.0-1035",
"binary_version": "5.3.0-1035.37"
},
{
"binary_name": "linux-buildinfo-5.3.0-1035-aws",
"binary_version": "5.3.0-1035.37"
},
{
"binary_name": "linux-cloud-tools-5.3.0-1035-aws",
"binary_version": "5.3.0-1035.37"
},
{
"binary_name": "linux-headers-5.3.0-1035-aws",
"binary_version": "5.3.0-1035.37"
},
{
"binary_name": "linux-image-5.3.0-1035-aws",
"binary_version": "5.3.0-1035.37"
},
{
"binary_name": "linux-modules-5.3.0-1035-aws",
"binary_version": "5.3.0-1035.37"
},
{
"binary_name": "linux-modules-extra-5.3.0-1035-aws",
"binary_version": "5.3.0-1035.37"
},
{
"binary_name": "linux-tools-5.3.0-1035-aws",
"binary_version": "5.3.0-1035.37"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-aws-5.3",
"purl": "pkg:deb/ubuntu/linux-aws-5.3@5.3.0-1035.37?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.3.0-1016.17~18.04.1",
"5.3.0-1017.18~18.04.1",
"5.3.0-1019.21~18.04.1",
"5.3.0-1023.25~18.04.1",
"5.3.0-1028.30~18.04.1",
"5.3.0-1030.32~18.04.1",
"5.3.0-1032.34~18.04.2",
"5.3.0-1033.35",
"5.3.0-1034.36",
"5.3.0-1035.37"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-aws-5.4-cloud-tools-5.4.0-1135",
"binary_version": "5.4.0-1135.145~18.04.1"
},
{
"binary_name": "linux-aws-5.4-headers-5.4.0-1135",
"binary_version": "5.4.0-1135.145~18.04.1"
},
{
"binary_name": "linux-aws-5.4-tools-5.4.0-1135",
"binary_version": "5.4.0-1135.145~18.04.1"
},
{
"binary_name": "linux-buildinfo-5.4.0-1135-aws",
"binary_version": "5.4.0-1135.145~18.04.1"
},
{
"binary_name": "linux-cloud-tools-5.4.0-1135-aws",
"binary_version": "5.4.0-1135.145~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-1135-aws",
"binary_version": "5.4.0-1135.145~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1135-aws",
"binary_version": "5.4.0-1135.145~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-1135-aws",
"binary_version": "5.4.0-1135.145~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1135-aws",
"binary_version": "5.4.0-1135.145~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-1135-aws",
"binary_version": "5.4.0-1135.145~18.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "linux-aws-5.4",
"purl": "pkg:deb/ubuntu/linux-aws-5.4@5.4.0-1135.145~18.04.1?arch=source\u0026distro=esm-infra/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1135.145~18.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1018.18~18.04.1",
"5.4.0-1020.20~18.04.2",
"5.4.0-1022.22~18.04.1",
"5.4.0-1024.24~18.04.1",
"5.4.0-1025.25~18.04.1",
"5.4.0-1028.29~18.04.1",
"5.4.0-1029.30~18.04.1",
"5.4.0-1030.31~18.04.1",
"5.4.0-1032.33~18.04.1",
"5.4.0-1034.35~18.04.1",
"5.4.0-1035.37~18.04.1",
"5.4.0-1037.39~18.04.1",
"5.4.0-1038.40~18.04.1",
"5.4.0-1039.41~18.04.1",
"5.4.0-1041.43~18.04.1",
"5.4.0-1043.45~18.04.1",
"5.4.0-1045.47~18.04.1",
"5.4.0-1047.49~18.04.1",
"5.4.0-1048.50~18.04.1",
"5.4.0-1049.51~18.04.1",
"5.4.0-1051.53~18.04.1",
"5.4.0-1054.57~18.04.1",
"5.4.0-1055.58~18.04.1",
"5.4.0-1056.59~18.04.1",
"5.4.0-1057.60~18.04.1",
"5.4.0-1058.61~18.04.3",
"5.4.0-1059.62~18.04.1",
"5.4.0-1060.63~18.04.1",
"5.4.0-1061.64~18.04.1",
"5.4.0-1063.66~18.04.1",
"5.4.0-1064.67~18.04.1",
"5.4.0-1065.68~18.04.1",
"5.4.0-1066.69~18.04.1",
"5.4.0-1068.72~18.04.1",
"5.4.0-1069.73~18.04.1",
"5.4.0-1071.76~18.04.1",
"5.4.0-1072.77~18.04.1",
"5.4.0-1075.80~18.04.1",
"5.4.0-1078.84~18.04.1",
"5.4.0-1080.87~18.04.1",
"5.4.0-1081.88~18.04.1",
"5.4.0-1083.90~18.04.1",
"5.4.0-1084.91~18.04.1",
"5.4.0-1085.92~18.04.1",
"5.4.0-1086.93~18.04.1",
"5.4.0-1088.96~18.04.1",
"5.4.0-1089.97~18.04.1",
"5.4.0-1090.98~18.04.1",
"5.4.0-1092.100~18.04.2",
"5.4.0-1093.102~18.04.2",
"5.4.0-1094.102~18.04.1",
"5.4.0-1096.104~18.04.1",
"5.4.0-1097.105~18.04.1",
"5.4.0-1099.107~18.04.1",
"5.4.0-1100.108~18.04.1",
"5.4.0-1101.109~18.04.1",
"5.4.0-1103.111~18.04.1",
"5.4.0-1104.112~18.04.1",
"5.4.0-1105.113~18.04.1",
"5.4.0-1106.114~18.04.1",
"5.4.0-1107.115~18.04.1",
"5.4.0-1108.116~18.04.1",
"5.4.0-1109.118~18.04.1",
"5.4.0-1110.119~18.04.1",
"5.4.0-1111.120~18.04.1",
"5.4.0-1112.121~18.04.2",
"5.4.0-1113.123~18.04.1",
"5.4.0-1114.124~18.04.1",
"5.4.0-1116.126~18.04.1",
"5.4.0-1117.127~18.04.1",
"5.4.0-1118.128~18.04.1",
"5.4.0-1119.129~18.04.1",
"5.4.0-1120.130~18.04.1",
"5.4.0-1121.131~18.04.1",
"5.4.0-1122.132~18.04.1",
"5.4.0-1123.133~18.04.1",
"5.4.0-1124.134~18.04.1",
"5.4.0-1125.135~18.04.1",
"5.4.0-1126.136~18.04.1",
"5.4.0-1127.137~18.04.2",
"5.4.0-1128.138~18.04.1",
"5.4.0-1129.139~18.04.1",
"5.4.0-1130.140~18.04.1",
"5.4.0-1131.141~18.04.1",
"5.4.0-1132.142~18.04.1",
"5.4.0-1133.143~18.04.1",
"5.4.0-1134.144~18.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-azure-cloud-tools-5.0.0-1036",
"binary_version": "5.0.0-1036.38"
},
{
"binary_name": "linux-azure-headers-5.0.0-1036",
"binary_version": "5.0.0-1036.38"
},
{
"binary_name": "linux-azure-tools-5.0.0-1036",
"binary_version": "5.0.0-1036.38"
},
{
"binary_name": "linux-buildinfo-5.0.0-1036-azure",
"binary_version": "5.0.0-1036.38"
},
{
"binary_name": "linux-cloud-tools-5.0.0-1036-azure",
"binary_version": "5.0.0-1036.38"
},
{
"binary_name": "linux-headers-5.0.0-1036-azure",
"binary_version": "5.0.0-1036.38"
},
{
"binary_name": "linux-image-unsigned-5.0.0-1036-azure",
"binary_version": "5.0.0-1036.38"
},
{
"binary_name": "linux-modules-5.0.0-1036-azure",
"binary_version": "5.0.0-1036.38"
},
{
"binary_name": "linux-modules-extra-5.0.0-1036-azure",
"binary_version": "5.0.0-1036.38"
},
{
"binary_name": "linux-tools-5.0.0-1036-azure",
"binary_version": "5.0.0-1036.38"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-azure",
"purl": "pkg:deb/ubuntu/linux-azure@5.0.0-1036.38?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1002.2",
"4.15.0-1003.3",
"4.15.0-1004.4",
"4.15.0-1008.8",
"4.15.0-1009.9",
"4.15.0-1012.12",
"4.15.0-1013.13",
"4.15.0-1014.14",
"4.15.0-1018.18",
"4.15.0-1019.19",
"4.15.0-1021.21",
"4.15.0-1022.23",
"4.15.0-1023.24",
"4.15.0-1025.26",
"4.15.0-1028.29",
"4.15.0-1030.31",
"4.15.0-1031.32",
"4.15.0-1032.33",
"4.15.0-1035.36",
"4.15.0-1036.38",
"4.15.0-1037.39",
"4.18.0-1011.11~18.04.1",
"4.18.0-1013.13~18.04.1",
"4.18.0-1014.14~18.04.1",
"4.18.0-1018.18~18.04.1",
"4.18.0-1019.19~18.04.1",
"4.18.0-1020.20~18.04.1",
"4.18.0-1023.24~18.04.1",
"4.18.0-1024.25~18.04.1",
"4.18.0-1025.27~18.04.1",
"5.0.0-1014.14~18.04.1",
"5.0.0-1016.17~18.04.1",
"5.0.0-1018.19~18.04.1",
"5.0.0-1020.21~18.04.1",
"5.0.0-1022.23~18.04.1",
"5.0.0-1023.24~18.04.1",
"5.0.0-1025.27~18.04.1",
"5.0.0-1027.29~18.04.1",
"5.0.0-1028.30~18.04.1",
"5.0.0-1029.31~18.04.1",
"5.0.0-1031.33",
"5.0.0-1032.34",
"5.0.0-1035.37",
"5.0.0-1036.38"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-azure-4.15-cloud-tools-4.15.0-1197",
"binary_version": "4.15.0-1197.212"
},
{
"binary_name": "linux-azure-4.15-headers-4.15.0-1197",
"binary_version": "4.15.0-1197.212"
},
{
"binary_name": "linux-azure-4.15-tools-4.15.0-1197",
"binary_version": "4.15.0-1197.212"
},
{
"binary_name": "linux-buildinfo-4.15.0-1197-azure",
"binary_version": "4.15.0-1197.212"
},
{
"binary_name": "linux-cloud-tools-4.15.0-1197-azure",
"binary_version": "4.15.0-1197.212"
},
{
"binary_name": "linux-headers-4.15.0-1197-azure",
"binary_version": "4.15.0-1197.212"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1197-azure",
"binary_version": "4.15.0-1197.212"
},
{
"binary_name": "linux-modules-4.15.0-1197-azure",
"binary_version": "4.15.0-1197.212"
},
{
"binary_name": "linux-modules-extra-4.15.0-1197-azure",
"binary_version": "4.15.0-1197.212"
},
{
"binary_name": "linux-tools-4.15.0-1197-azure",
"binary_version": "4.15.0-1197.212"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "linux-azure-4.15",
"purl": "pkg:deb/ubuntu/linux-azure-4.15@4.15.0-1197.212?arch=source\u0026distro=esm-infra/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.15.0-1197.212"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1082.92",
"4.15.0-1083.93",
"4.15.0-1089.99",
"4.15.0-1091.101",
"4.15.0-1092.102",
"4.15.0-1093.103",
"4.15.0-1095.105",
"4.15.0-1096.106",
"4.15.0-1099.110",
"4.15.0-1100.111",
"4.15.0-1102.113",
"4.15.0-1103.114",
"4.15.0-1104.116",
"4.15.0-1106.118",
"4.15.0-1108.120",
"4.15.0-1109.121",
"4.15.0-1110.122",
"4.15.0-1111.123",
"4.15.0-1112.125",
"4.15.0-1113.126",
"4.15.0-1114.127",
"4.15.0-1115.128",
"4.15.0-1118.131",
"4.15.0-1121.134",
"4.15.0-1122.135",
"4.15.0-1123.136",
"4.15.0-1124.137",
"4.15.0-1125.138",
"4.15.0-1126.139",
"4.15.0-1127.140",
"4.15.0-1129.142",
"4.15.0-1130.143",
"4.15.0-1131.144",
"4.15.0-1133.146",
"4.15.0-1134.147",
"4.15.0-1136.149",
"4.15.0-1137.150",
"4.15.0-1138.151",
"4.15.0-1139.152",
"4.15.0-1142.156",
"4.15.0-1145.160",
"4.15.0-1146.161",
"4.15.0-1149.164",
"4.15.0-1150.165",
"4.15.0-1151.166",
"4.15.0-1153.168",
"4.15.0-1157.172",
"4.15.0-1158.173",
"4.15.0-1159.174",
"4.15.0-1161.176",
"4.15.0-1162.177",
"4.15.0-1163.178",
"4.15.0-1164.179",
"4.15.0-1165.180",
"4.15.0-1166.181",
"4.15.0-1167.182",
"4.15.0-1168.183",
"4.15.0-1169.184",
"4.15.0-1170.185",
"4.15.0-1171.186",
"4.15.0-1172.187",
"4.15.0-1173.188",
"4.15.0-1174.189",
"4.15.0-1175.190",
"4.15.0-1176.191",
"4.15.0-1177.192",
"4.15.0-1178.193",
"4.15.0-1179.194",
"4.15.0-1180.195",
"4.15.0-1181.196",
"4.15.0-1182.197",
"4.15.0-1183.198",
"4.15.0-1184.199",
"4.15.0-1185.200",
"4.15.0-1186.201",
"4.15.0-1187.202",
"4.15.0-1188.203",
"4.15.0-1189.204",
"4.15.0-1190.205",
"4.15.0-1191.206",
"4.15.0-1192.207",
"4.15.0-1193.208",
"4.15.0-1194.209",
"4.15.0-1195.210",
"4.15.0-1196.211"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-azure-5.3-cloud-tools-5.3.0-1035",
"binary_version": "5.3.0-1035.36"
},
{
"binary_name": "linux-azure-5.3-headers-5.3.0-1035",
"binary_version": "5.3.0-1035.36"
},
{
"binary_name": "linux-azure-5.3-tools-5.3.0-1035",
"binary_version": "5.3.0-1035.36"
},
{
"binary_name": "linux-buildinfo-5.3.0-1035-azure",
"binary_version": "5.3.0-1035.36"
},
{
"binary_name": "linux-cloud-tools-5.3.0-1035-azure",
"binary_version": "5.3.0-1035.36"
},
{
"binary_name": "linux-headers-5.3.0-1035-azure",
"binary_version": "5.3.0-1035.36"
},
{
"binary_name": "linux-image-unsigned-5.3.0-1035-azure",
"binary_version": "5.3.0-1035.36"
},
{
"binary_name": "linux-modules-5.3.0-1035-azure",
"binary_version": "5.3.0-1035.36"
},
{
"binary_name": "linux-modules-extra-5.3.0-1035-azure",
"binary_version": "5.3.0-1035.36"
},
{
"binary_name": "linux-tools-5.3.0-1035-azure",
"binary_version": "5.3.0-1035.36"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-azure-5.3",
"purl": "pkg:deb/ubuntu/linux-azure-5.3@5.3.0-1035.36?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.3.0-1007.8~18.04.1",
"5.3.0-1008.9~18.04.1",
"5.3.0-1009.10~18.04.1",
"5.3.0-1010.11~18.04.1",
"5.3.0-1012.13~18.04.1",
"5.3.0-1013.14~18.04.1",
"5.3.0-1016.17~18.04.1",
"5.3.0-1018.19~18.04.1",
"5.3.0-1019.20~18.04.1",
"5.3.0-1020.21~18.04.1",
"5.3.0-1022.23~18.04.1",
"5.3.0-1028.29~18.04.1",
"5.3.0-1031.32~18.04.1",
"5.3.0-1032.33~18.04.1",
"5.3.0-1034.35~18.04.1",
"5.3.0-1035.36"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-azure-5.4-cloud-tools-5.4.0-1140",
"binary_version": "5.4.0-1140.147~18.04.1"
},
{
"binary_name": "linux-azure-5.4-headers-5.4.0-1140",
"binary_version": "5.4.0-1140.147~18.04.1"
},
{
"binary_name": "linux-azure-5.4-tools-5.4.0-1140",
"binary_version": "5.4.0-1140.147~18.04.1"
},
{
"binary_name": "linux-buildinfo-5.4.0-1140-azure",
"binary_version": "5.4.0-1140.147~18.04.1"
},
{
"binary_name": "linux-cloud-tools-5.4.0-1140-azure",
"binary_version": "5.4.0-1140.147~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-1140-azure",
"binary_version": "5.4.0-1140.147~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1140-azure",
"binary_version": "5.4.0-1140.147~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-1140-azure",
"binary_version": "5.4.0-1140.147~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1140-azure",
"binary_version": "5.4.0-1140.147~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-1140-azure",
"binary_version": "5.4.0-1140.147~18.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "linux-azure-5.4",
"purl": "pkg:deb/ubuntu/linux-azure-5.4@5.4.0-1140.147~18.04.1?arch=source\u0026distro=esm-infra/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1140.147~18.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1020.20~18.04.1",
"5.4.0-1022.22~18.04.1",
"5.4.0-1023.23~18.04.1",
"5.4.0-1025.25~18.04.1",
"5.4.0-1026.26~18.04.1",
"5.4.0-1031.32~18.04.1",
"5.4.0-1032.33~18.04.1",
"5.4.0-1034.35~18.04.1",
"5.4.0-1035.36~18.04.1",
"5.4.0-1036.38~18.04.1",
"5.4.0-1039.41~18.04.1",
"5.4.0-1040.42~18.04.1",
"5.4.0-1041.43~18.04.1",
"5.4.0-1043.45~18.04.1",
"5.4.0-1044.46~18.04.1",
"5.4.0-1046.48~18.04.1",
"5.4.0-1047.49~18.04.1",
"5.4.0-1048.50~18.04.1",
"5.4.0-1049.51~18.04.1",
"5.4.0-1051.53~18.04.1",
"5.4.0-1055.57~18.04.1",
"5.4.0-1056.58~18.04.1",
"5.4.0-1058.60~18.04.1",
"5.4.0-1059.62~18.04.1",
"5.4.0-1061.64~18.04.1",
"5.4.0-1062.65~18.04.1",
"5.4.0-1063.66~18.04.1",
"5.4.0-1064.67~18.04.1",
"5.4.0-1065.68~18.04.1",
"5.4.0-1067.70~18.04.1",
"5.4.0-1068.71~18.04.1",
"5.4.0-1069.72~18.04.1",
"5.4.0-1070.73~18.04.1",
"5.4.0-1072.75~18.04.1",
"5.4.0-1073.76~18.04.1",
"5.4.0-1074.77~18.04.1",
"5.4.0-1077.80~18.04.1",
"5.4.0-1078.81~18.04.1",
"5.4.0-1080.83~18.04.2",
"5.4.0-1083.87~18.04.1",
"5.4.0-1085.90~18.04.1",
"5.4.0-1086.91~18.04.1",
"5.4.0-1089.94~18.04.1",
"5.4.0-1090.95~18.04.1",
"5.4.0-1091.96~18.04.1",
"5.4.0-1094.100~18.04.1",
"5.4.0-1095.101~18.04.1",
"5.4.0-1098.104~18.04.2",
"5.4.0-1100.106~18.04.1",
"5.4.0-1101.107~18.04.1",
"5.4.0-1103.109~18.04.1",
"5.4.0-1104.110~18.04.1",
"5.4.0-1105.111~18.04.1",
"5.4.0-1106.112~18.04.1",
"5.4.0-1107.113~18.04.1",
"5.4.0-1108.114~18.04.1",
"5.4.0-1109.115~18.04.1",
"5.4.0-1110.116~18.04.1",
"5.4.0-1111.117~18.04.1",
"5.4.0-1112.118~18.04.1",
"5.4.0-1113.119~18.04.1",
"5.4.0-1115.122~18.04.1",
"5.4.0-1116.123~18.04.1",
"5.4.0-1117.124~18.04.1",
"5.4.0-1118.125~18.04.1",
"5.4.0-1119.126~18.04.2",
"5.4.0-1120.127~18.04.1",
"5.4.0-1121.128~18.04.1",
"5.4.0-1122.129~18.04.1",
"5.4.0-1123.130~18.04.1",
"5.4.0-1124.131~18.04.1",
"5.4.0-1126.133~18.04.1",
"5.4.0-1127.134~18.04.1",
"5.4.0-1128.135~18.04.1",
"5.4.0-1129.136~18.04.1",
"5.4.0-1130.137~18.04.1",
"5.4.0-1131.138~18.04.1",
"5.4.0-1132.139~18.04.1",
"5.4.0-1133.140~18.04.1",
"5.4.0-1134.141~18.04.1",
"5.4.0-1135.142~18.04.1",
"5.4.0-1136.143~18.04.1",
"5.4.0-1137.144~18.04.1",
"5.4.0-1138.145~18.04.1",
"5.4.0-1139.146~18.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-azure-edge-cloud-tools-5.0.0-1012",
"binary_version": "5.0.0-1012.12~18.04.2"
},
{
"binary_name": "linux-azure-edge-tools-5.0.0-1012",
"binary_version": "5.0.0-1012.12~18.04.2"
},
{
"binary_name": "linux-azure-headers-5.0.0-1012",
"binary_version": "5.0.0-1012.12~18.04.2"
},
{
"binary_name": "linux-buildinfo-5.0.0-1012-azure",
"binary_version": "5.0.0-1012.12~18.04.2"
},
{
"binary_name": "linux-cloud-tools-5.0.0-1012-azure",
"binary_version": "5.0.0-1012.12~18.04.2"
},
{
"binary_name": "linux-headers-5.0.0-1012-azure",
"binary_version": "5.0.0-1012.12~18.04.2"
},
{
"binary_name": "linux-image-unsigned-5.0.0-1012-azure",
"binary_version": "5.0.0-1012.12~18.04.2"
},
{
"binary_name": "linux-modules-5.0.0-1012-azure",
"binary_version": "5.0.0-1012.12~18.04.2"
},
{
"binary_name": "linux-modules-extra-5.0.0-1012-azure",
"binary_version": "5.0.0-1012.12~18.04.2"
},
{
"binary_name": "linux-tools-5.0.0-1012-azure",
"binary_version": "5.0.0-1012.12~18.04.2"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-azure-edge",
"purl": "pkg:deb/ubuntu/linux-azure-edge@5.0.0-1012.12~18.04.2?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.18.0-1006.6~18.04.1",
"4.18.0-1007.7~18.04.1",
"4.18.0-1008.8~18.04.1",
"5.0.0-1012.12~18.04.2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.0.0-1034-gcp",
"binary_version": "5.0.0-1034.35"
},
{
"binary_name": "linux-gcp-headers-5.0.0-1034",
"binary_version": "5.0.0-1034.35"
},
{
"binary_name": "linux-gcp-tools-5.0.0-1034",
"binary_version": "5.0.0-1034.35"
},
{
"binary_name": "linux-headers-5.0.0-1034-gcp",
"binary_version": "5.0.0-1034.35"
},
{
"binary_name": "linux-image-unsigned-5.0.0-1034-gcp",
"binary_version": "5.0.0-1034.35"
},
{
"binary_name": "linux-modules-5.0.0-1034-gcp",
"binary_version": "5.0.0-1034.35"
},
{
"binary_name": "linux-modules-extra-5.0.0-1034-gcp",
"binary_version": "5.0.0-1034.35"
},
{
"binary_name": "linux-tools-5.0.0-1034-gcp",
"binary_version": "5.0.0-1034.35"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-gcp",
"purl": "pkg:deb/ubuntu/linux-gcp@5.0.0-1034.35?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1001.1",
"4.15.0-1003.3",
"4.15.0-1005.5",
"4.15.0-1006.6",
"4.15.0-1008.8",
"4.15.0-1009.9",
"4.15.0-1010.10",
"4.15.0-1014.14",
"4.15.0-1015.15",
"4.15.0-1017.18",
"4.15.0-1018.19",
"4.15.0-1019.20",
"4.15.0-1021.22",
"4.15.0-1023.24",
"4.15.0-1024.25",
"4.15.0-1025.26",
"4.15.0-1026.27",
"4.15.0-1027.28",
"4.15.0-1028.29",
"4.15.0-1029.31",
"4.15.0-1030.32",
"4.15.0-1032.34",
"4.15.0-1033.35",
"4.15.0-1034.36",
"4.15.0-1036.38",
"4.15.0-1037.39",
"4.15.0-1040.42",
"4.15.0-1042.45",
"4.15.0-1044.70",
"5.0.0-1020.20~18.04.1",
"5.0.0-1021.21~18.04.1",
"5.0.0-1025.26~18.04.1",
"5.0.0-1026.27~18.04.1",
"5.0.0-1028.29~18.04.1",
"5.0.0-1029.30~18.04.1",
"5.0.0-1031.32",
"5.0.0-1033.34",
"5.0.0-1034.35"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-1182-gcp",
"binary_version": "4.15.0-1182.199"
},
{
"binary_name": "linux-gcp-4.15-headers-4.15.0-1182",
"binary_version": "4.15.0-1182.199"
},
{
"binary_name": "linux-gcp-4.15-tools-4.15.0-1182",
"binary_version": "4.15.0-1182.199"
},
{
"binary_name": "linux-headers-4.15.0-1182-gcp",
"binary_version": "4.15.0-1182.199"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1182-gcp",
"binary_version": "4.15.0-1182.199"
},
{
"binary_name": "linux-modules-4.15.0-1182-gcp",
"binary_version": "4.15.0-1182.199"
},
{
"binary_name": "linux-modules-extra-4.15.0-1182-gcp",
"binary_version": "4.15.0-1182.199"
},
{
"binary_name": "linux-tools-4.15.0-1182-gcp",
"binary_version": "4.15.0-1182.199"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "linux-gcp-4.15",
"purl": "pkg:deb/ubuntu/linux-gcp-4.15@4.15.0-1182.199?arch=source\u0026distro=esm-infra/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.15.0-1182.199"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1071.81",
"4.15.0-1077.87",
"4.15.0-1078.88",
"4.15.0-1080.90",
"4.15.0-1081.92",
"4.15.0-1083.94",
"4.15.0-1084.95",
"4.15.0-1086.98",
"4.15.0-1087.100",
"4.15.0-1088.101",
"4.15.0-1090.103",
"4.15.0-1091.104",
"4.15.0-1092.105",
"4.15.0-1093.106",
"4.15.0-1094.107",
"4.15.0-1095.108",
"4.15.0-1096.109",
"4.15.0-1097.110",
"4.15.0-1098.111",
"4.15.0-1099.112",
"4.15.0-1100.113",
"4.15.0-1103.116",
"4.15.0-1106.120",
"4.15.0-1107.121",
"4.15.0-1108.122",
"4.15.0-1109.123",
"4.15.0-1110.124",
"4.15.0-1111.125",
"4.15.0-1112.126",
"4.15.0-1114.128",
"4.15.0-1115.129",
"4.15.0-1116.130",
"4.15.0-1118.132",
"4.15.0-1119.133",
"4.15.0-1120.134",
"4.15.0-1121.135",
"4.15.0-1122.136",
"4.15.0-1124.138",
"4.15.0-1127.142",
"4.15.0-1130.146",
"4.15.0-1131.147",
"4.15.0-1134.150",
"4.15.0-1135.151",
"4.15.0-1136.152",
"4.15.0-1137.153",
"4.15.0-1138.154",
"4.15.0-1141.157",
"4.15.0-1142.158",
"4.15.0-1143.159",
"4.15.0-1145.161",
"4.15.0-1146.162",
"4.15.0-1147.163",
"4.15.0-1148.164",
"4.15.0-1149.165",
"4.15.0-1150.166",
"4.15.0-1151.167",
"4.15.0-1152.168",
"4.15.0-1153.170",
"4.15.0-1154.171",
"4.15.0-1155.172",
"4.15.0-1156.173",
"4.15.0-1157.174",
"4.15.0-1158.175",
"4.15.0-1159.176",
"4.15.0-1160.177",
"4.15.0-1161.178",
"4.15.0-1162.179",
"4.15.0-1163.180",
"4.15.0-1164.181",
"4.15.0-1165.182",
"4.15.0-1166.183",
"4.15.0-1167.184",
"4.15.0-1168.185",
"4.15.0-1169.186",
"4.15.0-1170.187",
"4.15.0-1171.188",
"4.15.0-1172.189",
"4.15.0-1173.190",
"4.15.0-1174.191",
"4.15.0-1175.192",
"4.15.0-1176.193",
"4.15.0-1177.194",
"4.15.0-1178.195",
"4.15.0-1179.196",
"4.15.0-1180.197",
"4.15.0-1181.198"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.3.0-1032-gcp",
"binary_version": "5.3.0-1032.34~18.04.1"
},
{
"binary_name": "linux-gcp-5.3-headers-5.3.0-1032",
"binary_version": "5.3.0-1032.34~18.04.1"
},
{
"binary_name": "linux-gcp-5.3-tools-5.3.0-1032",
"binary_version": "5.3.0-1032.34~18.04.1"
},
{
"binary_name": "linux-headers-5.3.0-1032-gcp",
"binary_version": "5.3.0-1032.34~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.3.0-1032-gcp",
"binary_version": "5.3.0-1032.34~18.04.1"
},
{
"binary_name": "linux-modules-5.3.0-1032-gcp",
"binary_version": "5.3.0-1032.34~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.3.0-1032-gcp",
"binary_version": "5.3.0-1032.34~18.04.1"
},
{
"binary_name": "linux-tools-5.3.0-1032-gcp",
"binary_version": "5.3.0-1032.34~18.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-gcp-5.3",
"purl": "pkg:deb/ubuntu/linux-gcp-5.3@5.3.0-1032.34~18.04.1?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.3.0-1008.9~18.04.1",
"5.3.0-1009.10~18.04.1",
"5.3.0-1010.11~18.04.1",
"5.3.0-1012.13~18.04.1",
"5.3.0-1014.15~18.04.1",
"5.3.0-1016.17~18.04.1",
"5.3.0-1017.18~18.04.1",
"5.3.0-1018.19~18.04.1",
"5.3.0-1020.22~18.04.1",
"5.3.0-1026.28~18.04.1",
"5.3.0-1029.31~18.04.1",
"5.3.0-1030.32~18.04.1",
"5.3.0-1032.34~18.04.1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1139-gcp",
"binary_version": "5.4.0-1139.148~18.04.1"
},
{
"binary_name": "linux-gcp-5.4-headers-5.4.0-1139",
"binary_version": "5.4.0-1139.148~18.04.1"
},
{
"binary_name": "linux-gcp-5.4-tools-5.4.0-1139",
"binary_version": "5.4.0-1139.148~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-1139-gcp",
"binary_version": "5.4.0-1139.148~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1139-gcp",
"binary_version": "5.4.0-1139.148~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-1139-gcp",
"binary_version": "5.4.0-1139.148~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1139-gcp",
"binary_version": "5.4.0-1139.148~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-1139-gcp",
"binary_version": "5.4.0-1139.148~18.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "linux-gcp-5.4",
"purl": "pkg:deb/ubuntu/linux-gcp-5.4@5.4.0-1139.148~18.04.1?arch=source\u0026distro=esm-infra/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1139.148~18.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1019.19~18.04.2",
"5.4.0-1021.21~18.04.1",
"5.4.0-1022.22~18.04.1",
"5.4.0-1024.24~18.04.1",
"5.4.0-1025.25~18.04.1",
"5.4.0-1028.29~18.04.1",
"5.4.0-1029.31~18.04.1",
"5.4.0-1030.32~18.04.1",
"5.4.0-1032.34~18.04.1",
"5.4.0-1033.35~18.04.1",
"5.4.0-1034.37~18.04.1",
"5.4.0-1036.39~18.04.1",
"5.4.0-1037.40~18.04.1",
"5.4.0-1038.41~18.04.1",
"5.4.0-1040.43~18.04.1",
"5.4.0-1041.44~18.04.1",
"5.4.0-1042.45~18.04.1",
"5.4.0-1043.46~18.04.1",
"5.4.0-1044.47~18.04.2",
"5.4.0-1046.49~18.04.1",
"5.4.0-1049.53~18.04.1",
"5.4.0-1051.55~18.04.1",
"5.4.0-1052.56~18.04.1",
"5.4.0-1053.57~18.04.1",
"5.4.0-1055.59~18.04.1",
"5.4.0-1056.60~18.04.1",
"5.4.0-1057.61~18.04.1",
"5.4.0-1058.62~18.04.1",
"5.4.0-1059.63~18.04.1",
"5.4.0-1060.64~18.04.1",
"5.4.0-1062.66~18.04.1",
"5.4.0-1063.67~18.04.1",
"5.4.0-1064.68~18.04.1",
"5.4.0-1065.69~18.04.1",
"5.4.0-1067.71~18.04.1",
"5.4.0-1068.72~18.04.1",
"5.4.0-1069.73~18.04.1",
"5.4.0-1072.77~18.04.1",
"5.4.0-1073.78~18.04.1",
"5.4.0-1075.80~18.04.1",
"5.4.0-1078.84~18.04.1",
"5.4.0-1080.87~18.04.1",
"5.4.0-1083.91~18.04.1",
"5.4.0-1084.92~18.04.1",
"5.4.0-1086.94~18.04.1",
"5.4.0-1087.95~18.04.1",
"5.4.0-1089.97~18.04.1",
"5.4.0-1092.101~18.04.1",
"5.4.0-1093.102~18.04.1",
"5.4.0-1096.105~18.04.2",
"5.4.0-1097.106~18.04.1",
"5.4.0-1098.107~18.04.1",
"5.4.0-1100.109~18.04.1",
"5.4.0-1101.110~18.04.1",
"5.4.0-1102.111~18.04.2",
"5.4.0-1103.112~18.04.1",
"5.4.0-1104.113~18.04.1",
"5.4.0-1105.114~18.04.1",
"5.4.0-1106.115~18.04.1",
"5.4.0-1107.116~18.04.1",
"5.4.0-1108.117~18.04.1",
"5.4.0-1109.118~18.04.1",
"5.4.0-1110.119~18.04.1",
"5.4.0-1111.120~18.04.1",
"5.4.0-1112.121~18.04.1",
"5.4.0-1113.122~18.04.1",
"5.4.0-1115.124~18.04.1",
"5.4.0-1116.125~18.04.1",
"5.4.0-1117.126~18.04.1",
"5.4.0-1118.127~18.04.1",
"5.4.0-1120.129~18.04.1",
"5.4.0-1121.130~18.04.1",
"5.4.0-1122.131~18.04.1",
"5.4.0-1123.132~18.04.1",
"5.4.0-1124.133~18.04.1",
"5.4.0-1125.134~18.04.1",
"5.4.0-1126.135~18.04.1",
"5.4.0-1127.136~18.04.1",
"5.4.0-1128.137~18.04.1",
"5.4.0-1129.138~18.04.1",
"5.4.0-1130.139~18.04.1",
"5.4.0-1132.141~18.04.1",
"5.4.0-1133.142~18.04.1",
"5.4.0-1134.143~18.04.1",
"5.4.0-1135.144~18.04.1",
"5.4.0-1136.145~18.04.1",
"5.4.0-1137.146~18.04.1",
"5.4.0-1138.147~18.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-1079-gke",
"binary_version": "4.15.0-1079.84"
},
{
"binary_name": "linux-gke-4.15-headers-4.15.0-1079",
"binary_version": "4.15.0-1079.84"
},
{
"binary_name": "linux-gke-4.15-tools-4.15.0-1079",
"binary_version": "4.15.0-1079.84"
},
{
"binary_name": "linux-headers-4.15.0-1079-gke",
"binary_version": "4.15.0-1079.84"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1079-gke",
"binary_version": "4.15.0-1079.84"
},
{
"binary_name": "linux-modules-4.15.0-1079-gke",
"binary_version": "4.15.0-1079.84"
},
{
"binary_name": "linux-modules-extra-4.15.0-1079-gke",
"binary_version": "4.15.0-1079.84"
},
{
"binary_name": "linux-tools-4.15.0-1079-gke",
"binary_version": "4.15.0-1079.84"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-gke-4.15",
"purl": "pkg:deb/ubuntu/linux-gke-4.15@4.15.0-1079.84?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1030.32",
"4.15.0-1032.34",
"4.15.0-1033.35",
"4.15.0-1034.36",
"4.15.0-1036.38",
"4.15.0-1037.39",
"4.15.0-1040.42",
"4.15.0-1041.43",
"4.15.0-1042.44",
"4.15.0-1044.46",
"4.15.0-1045.48",
"4.15.0-1046.49",
"4.15.0-1048.51",
"4.15.0-1049.52",
"4.15.0-1050.53",
"4.15.0-1052.55",
"4.15.0-1055.58",
"4.15.0-1057.60",
"4.15.0-1058.61",
"4.15.0-1059.62",
"4.15.0-1063.66",
"4.15.0-1064.67",
"4.15.0-1066.69",
"4.15.0-1067.70",
"4.15.0-1069.72",
"4.15.0-1070.73",
"4.15.0-1072.76",
"4.15.0-1073.78",
"4.15.0-1074.79",
"4.15.0-1076.81",
"4.15.0-1077.82",
"4.15.0-1078.83",
"4.15.0-1079.84"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1080-gke",
"binary_version": "5.4.0-1080.86~18.04.1"
},
{
"binary_name": "linux-gke-5.4-headers-5.4.0-1080",
"binary_version": "5.4.0-1080.86~18.04.1"
},
{
"binary_name": "linux-gke-5.4-tools-5.4.0-1080",
"binary_version": "5.4.0-1080.86~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-1080-gke",
"binary_version": "5.4.0-1080.86~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1080-gke",
"binary_version": "5.4.0-1080.86~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-1080-gke",
"binary_version": "5.4.0-1080.86~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1080-gke",
"binary_version": "5.4.0-1080.86~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-1080-gke",
"binary_version": "5.4.0-1080.86~18.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-gke-5.4",
"purl": "pkg:deb/ubuntu/linux-gke-5.4@5.4.0-1080.86~18.04.1?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1025.25~18.04.1",
"5.4.0-1027.28~18.04.1",
"5.4.0-1029.31~18.04.1",
"5.4.0-1030.32~18.04.1",
"5.4.0-1032.34~18.04.1",
"5.4.0-1033.35~18.04.1",
"5.4.0-1035.37~18.04.1",
"5.4.0-1036.38~18.04.1",
"5.4.0-1037.39~18.04.1",
"5.4.0-1039.41~18.04.1",
"5.4.0-1040.42~18.04.1",
"5.4.0-1042.44~18.04.1",
"5.4.0-1043.45~18.04.1",
"5.4.0-1044.46~18.04.1",
"5.4.0-1046.48~18.04.1",
"5.4.0-1049.52~18.04.1",
"5.4.0-1051.54~18.04.1",
"5.4.0-1052.55~18.04.1",
"5.4.0-1053.56~18.04.1",
"5.4.0-1054.57~18.04.1",
"5.4.0-1055.58~18.04.1",
"5.4.0-1056.59~18.04.1",
"5.4.0-1057.60~18.04.1",
"5.4.0-1059.62~18.04.1",
"5.4.0-1061.64~18.04.1",
"5.4.0-1062.65~18.04.1",
"5.4.0-1063.66~18.04.1",
"5.4.0-1065.68~18.04.1",
"5.4.0-1066.69~18.04.1",
"5.4.0-1067.70~18.04.1",
"5.4.0-1068.71~18.04.1",
"5.4.0-1071.76~18.04.3",
"5.4.0-1072.77~18.04.1",
"5.4.0-1074.79~18.04.1",
"5.4.0-1076.82~18.04.1",
"5.4.0-1078.84~18.04.1",
"5.4.0-1080.86~18.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1051-gkeop",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-cloud-tools-5.4.0-1051-gkeop",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-gkeop-5.4-cloud-tools-5.4.0-1051",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-gkeop-5.4-headers-5.4.0-1051",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-gkeop-5.4-source-5.4.0",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-gkeop-5.4-tools-5.4.0-1051",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-1051-gkeop",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1051-gkeop",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-1051-gkeop",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1051-gkeop",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-1051-gkeop",
"binary_version": "5.4.0-1051.54~18.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-gkeop-5.4",
"purl": "pkg:deb/ubuntu/linux-gkeop-5.4@5.4.0-1051.54~18.04.1?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1001.1",
"5.4.0-1003.3",
"5.4.0-1004.5",
"5.4.0-1005.6",
"5.4.0-1007.8~18.04.1",
"5.4.0-1008.9~18.04.1",
"5.4.0-1009.10~18.04.1",
"5.4.0-1010.11~18.04.1",
"5.4.0-1011.12~18.04.2",
"5.4.0-1012.13~18.04.1",
"5.4.0-1013.14~18.04.1",
"5.4.0-1014.15~18.04.1",
"5.4.0-1015.16~18.04.1",
"5.4.0-1016.17~18.04.1",
"5.4.0-1018.19~18.04.1",
"5.4.0-1021.22~18.04.1",
"5.4.0-1022.23~18.04.1",
"5.4.0-1023.24~18.04.1",
"5.4.0-1024.25~18.04.1",
"5.4.0-1025.26~18.04.1",
"5.4.0-1026.27~18.04.1",
"5.4.0-1027.28~18.04.1",
"5.4.0-1029.30~18.04.2",
"5.4.0-1031.32~18.04.1",
"5.4.0-1032.33~18.04.1",
"5.4.0-1033.34~18.04.1",
"5.4.0-1034.35~18.04.1",
"5.4.0-1036.37~18.04.1",
"5.4.0-1037.38~18.04.1",
"5.4.0-1038.39~18.04.1",
"5.4.0-1039.40~18.04.1",
"5.4.0-1040.41~18.04.1",
"5.4.0-1043.44~18.04.1",
"5.4.0-1046.48~18.04.1",
"5.4.0-1048.51~18.04.1",
"5.4.0-1049.52~18.04.1",
"5.4.0-1051.54~18.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "block-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "crypto-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "fat-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "fb-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "firewire-core-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "floppy-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "fs-core-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "fs-secondary-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "input-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "ipmi-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "kernel-image-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-buildinfo-5.3.0-76-generic",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-buildinfo-5.3.0-76-lowlatency",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-cloud-tools-5.3.0-76-generic",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-cloud-tools-5.3.0-76-lowlatency",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-headers-5.3.0-76-generic",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-headers-5.3.0-76-lowlatency",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-hwe-cloud-tools-5.3.0-76",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-hwe-headers-5.3.0-76",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-hwe-tools-5.3.0-76",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-hwe-udebs-generic",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-image-5.3.0-76-generic",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-image-5.3.0-76-lowlatency",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-image-unsigned-5.3.0-76-generic",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-image-unsigned-5.3.0-76-lowlatency",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-modules-5.3.0-76-generic",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-modules-5.3.0-76-lowlatency",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-modules-extra-5.3.0-76-generic",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-source-5.3.0",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-tools-5.3.0-76-generic",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-tools-5.3.0-76-lowlatency",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "md-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "message-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "mouse-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "multipath-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "nfs-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "nic-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "nic-pcmcia-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "nic-shared-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "nic-usb-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "parport-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "pata-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "pcmcia-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "pcmcia-storage-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "plip-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "ppp-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "sata-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "scsi-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "serial-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "storage-core-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "usb-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "virtio-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "vlan-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-hwe",
"purl": "pkg:deb/ubuntu/linux-hwe@5.3.0-76.72?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.18.0-13.14~18.04.1",
"4.18.0-14.15~18.04.1",
"4.18.0-15.16~18.04.1",
"4.18.0-16.17~18.04.1",
"4.18.0-17.18~18.04.1",
"4.18.0-18.19~18.04.1",
"4.18.0-20.21~18.04.1",
"4.18.0-21.22~18.04.1",
"4.18.0-22.23~18.04.1",
"4.18.0-24.25~18.04.1",
"4.18.0-25.26~18.04.1",
"5.0.0-23.24~18.04.1",
"5.0.0-25.26~18.04.1",
"5.0.0-27.28~18.04.1",
"5.0.0-29.31~18.04.1",
"5.0.0-31.33~18.04.1",
"5.0.0-32.34~18.04.2",
"5.0.0-35.38~18.04.1",
"5.0.0-36.39~18.04.1",
"5.0.0-37.40~18.04.1",
"5.3.0-26.28~18.04.1",
"5.3.0-28.30~18.04.1",
"5.3.0-40.32~18.04.1",
"5.3.0-42.34~18.04.1",
"5.3.0-45.37~18.04.1",
"5.3.0-46.38~18.04.1",
"5.3.0-51.44~18.04.2",
"5.3.0-53.47~18.04.1",
"5.3.0-59.53~18.04.1",
"5.3.0-61.55~18.04.1",
"5.3.0-62.56~18.04.1",
"5.3.0-64.58~18.04.1",
"5.3.0-65.59",
"5.3.0-66.60",
"5.3.0-67.61",
"5.3.0-68.63",
"5.3.0-69.65",
"5.3.0-70.66",
"5.3.0-72.68",
"5.3.0-73.69",
"5.3.0-74.70",
"5.3.0-75.71",
"5.3.0-76.72"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "block-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "crypto-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "dasd-extra-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "dasd-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "fat-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "fb-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "firewire-core-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "floppy-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "fs-core-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "fs-secondary-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "input-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "ipmi-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "kernel-image-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-buildinfo-5.4.0-200-generic",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-buildinfo-5.4.0-200-lowlatency",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-cloud-tools-5.4.0-200-generic",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-cloud-tools-5.4.0-200-lowlatency",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-200-generic",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-200-lowlatency",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-hwe-5.4-cloud-tools-5.4.0-200",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-hwe-5.4-cloud-tools-common",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-hwe-5.4-headers-5.4.0-200",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-hwe-5.4-source-5.4.0",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-hwe-5.4-tools-5.4.0-200",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-hwe-5.4-tools-common",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-hwe-5.4-udebs-generic",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-200-generic",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-200-lowlatency",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-200-generic",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-200-lowlatency",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.4.0-200-generic",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-200-generic",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-200-lowlatency",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "md-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "message-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "mouse-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "multipath-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "nfs-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "nic-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "nic-pcmcia-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "nic-shared-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "nic-usb-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "parport-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "pata-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "pcmcia-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "pcmcia-storage-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "plip-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "ppp-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "sata-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "scsi-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "serial-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "storage-core-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "usb-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "virtio-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "vlan-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "linux-hwe-5.4",
"purl": "pkg:deb/ubuntu/linux-hwe-5.4@5.4.0-200.220~18.04.1?arch=source\u0026distro=esm-infra/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-200.220~18.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-37.41~18.04.1",
"5.4.0-39.43~18.04.1",
"5.4.0-40.44~18.04.1",
"5.4.0-42.46~18.04.1",
"5.4.0-45.49~18.04.2",
"5.4.0-47.51~18.04.1",
"5.4.0-48.52~18.04.1",
"5.4.0-51.56~18.04.1",
"5.4.0-52.57~18.04.1",
"5.4.0-53.59~18.04.1",
"5.4.0-54.60~18.04.1",
"5.4.0-56.62~18.04.1",
"5.4.0-58.64~18.04.1",
"5.4.0-59.65~18.04.1",
"5.4.0-60.67~18.04.1",
"5.4.0-62.70~18.04.1",
"5.4.0-64.72~18.04.1",
"5.4.0-65.73~18.04.1",
"5.4.0-66.74~18.04.2",
"5.4.0-67.75~18.04.1",
"5.4.0-70.78~18.04.1",
"5.4.0-71.79~18.04.1",
"5.4.0-72.80~18.04.1",
"5.4.0-73.82~18.04.1",
"5.4.0-74.83~18.04.1",
"5.4.0-77.86~18.04.1",
"5.4.0-80.90~18.04.1",
"5.4.0-81.91~18.04.1",
"5.4.0-84.94~18.04.1",
"5.4.0-86.97~18.04.1",
"5.4.0-87.98~18.04.1",
"5.4.0-89.100~18.04.1",
"5.4.0-90.101~18.04.1",
"5.4.0-91.102~18.04.1",
"5.4.0-92.103~18.04.2",
"5.4.0-94.106~18.04.1",
"5.4.0-96.109~18.04.1",
"5.4.0-97.110~18.04.1",
"5.4.0-99.112~18.04.1",
"5.4.0-100.113~18.04.1",
"5.4.0-104.118~18.04.1",
"5.4.0-105.119~18.04.1",
"5.4.0-107.121~18.04.1",
"5.4.0-109.123~18.04.1",
"5.4.0-110.124~18.04.1",
"5.4.0-113.127~18.04.1",
"5.4.0-117.132~18.04.1",
"5.4.0-120.136~18.04.1",
"5.4.0-121.137~18.04.1",
"5.4.0-122.138~18.04.1",
"5.4.0-124.140~18.04.1",
"5.4.0-125.141~18.04.1",
"5.4.0-126.142~18.04.1",
"5.4.0-128.144~18.04.1",
"5.4.0-131.147~18.04.1",
"5.4.0-132.148~18.04.1",
"5.4.0-133.149~18.04.1",
"5.4.0-135.152~18.04.2",
"5.4.0-136.153~18.04.1",
"5.4.0-137.154~18.04.1",
"5.4.0-139.156~18.04.1",
"5.4.0-144.161~18.04.1",
"5.4.0-146.163~18.04.1",
"5.4.0-147.164~18.04.1",
"5.4.0-148.165~18.04.1",
"5.4.0-149.166~18.04.1",
"5.4.0-150.167~18.04.1",
"5.4.0-152.169~18.04.1",
"5.4.0-153.170~18.04.1",
"5.4.0-155.172~18.04.1",
"5.4.0-156.173~18.04.1",
"5.4.0-159.176~18.04.1",
"5.4.0-162.179~18.04.1",
"5.4.0-163.180~18.04.1",
"5.4.0-164.181~18.04.1",
"5.4.0-165.182~18.04.1",
"5.4.0-166.183~18.04.2",
"5.4.0-167.184~18.04.1",
"5.4.0-169.187~18.04.1",
"5.4.0-170.188~18.04.1",
"5.4.0-171.189~18.04.1",
"5.4.0-172.190~18.04.1",
"5.4.0-173.191~18.04.1",
"5.4.0-174.193~18.04.1",
"5.4.0-175.195~18.04.1",
"5.4.0-177.197~18.04.1",
"5.4.0-181.201~18.04.1",
"5.4.0-182.202~18.04.1",
"5.4.0-186.206~18.04.1",
"5.4.0-187.207~18.04.1",
"5.4.0-189.209~18.04.1",
"5.4.0-190.210~18.04.1",
"5.4.0-192.212~18.04.1",
"5.4.0-193.213~18.04.1",
"5.4.0-195.215~18.04.1",
"5.4.0-196.216~18.04.1",
"5.4.0-198.218~18.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "block-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "block-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "crypto-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "crypto-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "dasd-extra-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "dasd-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "fat-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "fat-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "fb-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "firewire-core-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "floppy-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "fs-core-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "fs-core-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "fs-secondary-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "fs-secondary-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "input-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "input-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "ipmi-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "ipmi-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "kernel-image-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "kernel-image-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-buildinfo-5.3.0-24-generic",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-buildinfo-5.3.0-24-generic-lpae",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-buildinfo-5.3.0-24-lowlatency",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-cloud-tools-5.3.0-24-generic",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-cloud-tools-5.3.0-24-lowlatency",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-headers-5.3.0-24",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-headers-5.3.0-24-generic",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-headers-5.3.0-24-generic-lpae",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-headers-5.3.0-24-lowlatency",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-hwe-edge-cloud-tools-5.3.0-24",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-hwe-edge-tools-5.3.0-24",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-hwe-edge-udebs-generic",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-hwe-edge-udebs-generic-lpae",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-image-5.3.0-24-generic",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-image-5.3.0-24-generic-lpae",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-image-5.3.0-24-lowlatency",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-image-unsigned-5.3.0-24-generic",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-image-unsigned-5.3.0-24-lowlatency",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-modules-5.3.0-24-generic",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-modules-5.3.0-24-generic-lpae",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-modules-5.3.0-24-lowlatency",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-modules-extra-5.3.0-24-generic",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-source-5.3.0",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-tools-5.3.0-24-generic",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-tools-5.3.0-24-generic-lpae",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-tools-5.3.0-24-lowlatency",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "md-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "md-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "message-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "mouse-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "mouse-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "multipath-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "multipath-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "nfs-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "nfs-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "nic-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "nic-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "nic-pcmcia-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "nic-shared-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "nic-shared-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "nic-usb-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "nic-usb-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "parport-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "parport-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "pata-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "pcmcia-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "pcmcia-storage-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "plip-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "plip-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "ppp-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "ppp-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "sata-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "sata-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "scsi-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "scsi-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "serial-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "storage-core-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "storage-core-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "usb-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "usb-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "virtio-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "vlan-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "vlan-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-hwe-edge",
"purl": "pkg:deb/ubuntu/linux-hwe-edge@5.3.0-24.26~18.04.2?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.0.0-15.16~18.04.1",
"5.0.0-16.17~18.04.1",
"5.0.0-17.18~18.04.1",
"5.0.0-19.20~18.04.1",
"5.0.0-20.21~18.04.1",
"5.3.0-19.20~18.04.2",
"5.3.0-22.24~18.04.1",
"5.3.0-23.25~18.04.1",
"5.3.0-23.25~18.04.2",
"5.3.0-24.26~18.04.2"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1082-ibm",
"binary_version": "5.4.0-1082.87~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-1082-ibm",
"binary_version": "5.4.0-1082.87~18.04.1"
},
{
"binary_name": "linux-ibm-5.4-cloud-tools-common",
"binary_version": "5.4.0-1082.87~18.04.1"
},
{
"binary_name": "linux-ibm-5.4-headers-5.4.0-1082",
"binary_version": "5.4.0-1082.87~18.04.1"
},
{
"binary_name": "linux-ibm-5.4-source-5.4.0",
"binary_version": "5.4.0-1082.87~18.04.1"
},
{
"binary_name": "linux-ibm-5.4-tools-5.4.0-1082",
"binary_version": "5.4.0-1082.87~18.04.1"
},
{
"binary_name": "linux-ibm-5.4-tools-common",
"binary_version": "5.4.0-1082.87~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1082-ibm",
"binary_version": "5.4.0-1082.87~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-1082-ibm",
"binary_version": "5.4.0-1082.87~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1082-ibm",
"binary_version": "5.4.0-1082.87~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-1082-ibm",
"binary_version": "5.4.0-1082.87~18.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "linux-ibm-5.4",
"purl": "pkg:deb/ubuntu/linux-ibm-5.4@5.4.0-1082.87~18.04.1?arch=source\u0026distro=esm-infra/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1082.87~18.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1010.11~18.04.2",
"5.4.0-1012.13~18.04.1",
"5.4.0-1014.15~18.04.1",
"5.4.0-1015.16~18.04.1",
"5.4.0-1017.19~18.04.1",
"5.4.0-1018.20~18.04.1",
"5.4.0-1019.21~18.04.1",
"5.4.0-1020.22~18.04.1",
"5.4.0-1021.23~18.04.1",
"5.4.0-1023.25~18.04.1",
"5.4.0-1026.29~18.04.1",
"5.4.0-1028.32~18.04.1",
"5.4.0-1029.33~18.04.1",
"5.4.0-1031.35~18.04.1",
"5.4.0-1032.36~18.04.1",
"5.4.0-1033.37~18.04.1",
"5.4.0-1034.38~18.04.1",
"5.4.0-1036.41~18.04.1",
"5.4.0-1037.42~18.04.1",
"5.4.0-1040.45~18.04.2",
"5.4.0-1041.46~18.04.1",
"5.4.0-1042.47~18.04.1",
"5.4.0-1044.49~18.04.1",
"5.4.0-1045.50~18.04.1",
"5.4.0-1046.51~18.04.1",
"5.4.0-1047.52~18.04.1",
"5.4.0-1048.53~18.04.1",
"5.4.0-1049.54~18.04.1",
"5.4.0-1050.55~18.04.1",
"5.4.0-1051.56~18.04.1",
"5.4.0-1052.57~18.04.1",
"5.4.0-1053.58~18.04.1",
"5.4.0-1054.59~18.04.1",
"5.4.0-1056.61~18.04.1",
"5.4.0-1057.62~18.04.1",
"5.4.0-1058.63~18.04.1",
"5.4.0-1059.64~18.04.1",
"5.4.0-1060.65~18.04.1",
"5.4.0-1061.66~18.04.1",
"5.4.0-1063.68~18.04.1",
"5.4.0-1064.69~18.04.1",
"5.4.0-1065.70~18.04.1",
"5.4.0-1066.71~18.04.1",
"5.4.0-1067.72~18.04.1",
"5.4.0-1068.73~18.04.1",
"5.4.0-1069.74~18.04.1",
"5.4.0-1070.75~18.04.1",
"5.4.0-1071.76~18.04.1",
"5.4.0-1072.77~18.04.1",
"5.4.0-1073.78~18.04.1",
"5.4.0-1074.79~18.04.1",
"5.4.0-1075.80~18.04.1",
"5.4.0-1076.81~18.04.1",
"5.4.0-1077.82~18.04.1",
"5.4.0-1078.83~18.04.1",
"5.4.0-1079.84~18.04.1",
"5.4.0-1080.85~18.04.1",
"5.4.0-1081.86~18.04.1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-1171-kvm",
"binary_version": "4.15.0-1171.176"
},
{
"binary_name": "linux-headers-4.15.0-1171-kvm",
"binary_version": "4.15.0-1171.176"
},
{
"binary_name": "linux-image-4.15.0-1171-kvm",
"binary_version": "4.15.0-1171.176"
},
{
"binary_name": "linux-kvm-headers-4.15.0-1171",
"binary_version": "4.15.0-1171.176"
},
{
"binary_name": "linux-kvm-tools-4.15.0-1171",
"binary_version": "4.15.0-1171.176"
},
{
"binary_name": "linux-modules-4.15.0-1171-kvm",
"binary_version": "4.15.0-1171.176"
},
{
"binary_name": "linux-tools-4.15.0-1171-kvm",
"binary_version": "4.15.0-1171.176"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "linux-kvm",
"purl": "pkg:deb/ubuntu/linux-kvm@4.15.0-1171.176?arch=source\u0026distro=esm-infra/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.15.0-1171.176"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1002.2",
"4.15.0-1003.3",
"4.15.0-1004.4",
"4.15.0-1006.6",
"4.15.0-1008.8",
"4.15.0-1010.10",
"4.15.0-1011.11",
"4.15.0-1012.12",
"4.15.0-1016.16",
"4.15.0-1017.17",
"4.15.0-1019.19",
"4.15.0-1020.20",
"4.15.0-1021.21",
"4.15.0-1023.23",
"4.15.0-1025.25",
"4.15.0-1026.26",
"4.15.0-1027.27",
"4.15.0-1028.28",
"4.15.0-1029.29",
"4.15.0-1030.30",
"4.15.0-1031.31",
"4.15.0-1032.32",
"4.15.0-1034.34",
"4.15.0-1035.35",
"4.15.0-1036.36",
"4.15.0-1038.38",
"4.15.0-1039.39",
"4.15.0-1042.42",
"4.15.0-1043.43",
"4.15.0-1044.44",
"4.15.0-1046.46",
"4.15.0-1047.47",
"4.15.0-1048.48",
"4.15.0-1050.50",
"4.15.0-1051.51",
"4.15.0-1052.52",
"4.15.0-1053.53",
"4.15.0-1056.57",
"4.15.0-1058.59",
"4.15.0-1059.60",
"4.15.0-1060.61",
"4.15.0-1067.68",
"4.15.0-1069.70",
"4.15.0-1071.72",
"4.15.0-1072.73",
"4.15.0-1074.75",
"4.15.0-1075.76",
"4.15.0-1077.79",
"4.15.0-1079.81",
"4.15.0-1081.83",
"4.15.0-1082.84",
"4.15.0-1084.86",
"4.15.0-1085.87",
"4.15.0-1086.88",
"4.15.0-1087.89",
"4.15.0-1088.90",
"4.15.0-1089.91",
"4.15.0-1090.92",
"4.15.0-1091.93",
"4.15.0-1092.94",
"4.15.0-1094.96",
"4.15.0-1097.99",
"4.15.0-1098.100",
"4.15.0-1099.101",
"4.15.0-1100.102",
"4.15.0-1101.103",
"4.15.0-1102.104",
"4.15.0-1103.105",
"4.15.0-1105.107",
"4.15.0-1106.108",
"4.15.0-1107.109",
"4.15.0-1109.112",
"4.15.0-1110.113",
"4.15.0-1112.115",
"4.15.0-1113.116",
"4.15.0-1114.117",
"4.15.0-1116.119",
"4.15.0-1119.123",
"4.15.0-1122.127",
"4.15.0-1123.128",
"4.15.0-1125.130",
"4.15.0-1126.131",
"4.15.0-1127.132",
"4.15.0-1128.133",
"4.15.0-1129.134",
"4.15.0-1132.137",
"4.15.0-1133.138",
"4.15.0-1134.139",
"4.15.0-1135.140",
"4.15.0-1136.141",
"4.15.0-1137.142",
"4.15.0-1138.143",
"4.15.0-1139.144",
"4.15.0-1140.145",
"4.15.0-1141.146",
"4.15.0-1142.147",
"4.15.0-1143.148",
"4.15.0-1144.149",
"4.15.0-1145.150",
"4.15.0-1146.151",
"4.15.0-1147.152",
"4.15.0-1148.153",
"4.15.0-1149.154",
"4.15.0-1150.155",
"4.15.0-1151.156",
"4.15.0-1152.157",
"4.15.0-1153.158",
"4.15.0-1154.159",
"4.15.0-1155.160",
"4.15.0-1156.161",
"4.15.0-1157.162",
"4.15.0-1158.163",
"4.15.0-1159.164",
"4.15.0-1160.165",
"4.15.0-1161.166",
"4.15.0-1162.167",
"4.15.0-1163.168",
"4.15.0-1164.169",
"4.15.0-1165.170",
"4.15.0-1166.171",
"4.15.0-1167.172",
"4.15.0-1168.173",
"4.15.0-1169.174",
"4.15.0-1170.175"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "block-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "crypto-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "fat-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "fb-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "firewire-core-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "floppy-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "fs-core-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "fs-secondary-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "input-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "ipmi-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "irda-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "kernel-image-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "linux-buildinfo-4.15.0-1103-oem",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "linux-headers-4.15.0-1103-oem",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1103-oem",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "linux-modules-4.15.0-1103-oem",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "linux-oem-headers-4.15.0-1103",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "linux-oem-tools-4.15.0-1103",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "linux-tools-4.15.0-1103-oem",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "linux-udebs-oem",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "md-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "message-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "mouse-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "multipath-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "nfs-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "nic-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "nic-pcmcia-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "nic-shared-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "nic-usb-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "parport-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "pata-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "pcmcia-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "pcmcia-storage-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "plip-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "ppp-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "sata-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "scsi-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "serial-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "storage-core-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "usb-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "virtio-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "vlan-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-oem",
"purl": "pkg:deb/ubuntu/linux-oem@4.15.0-1103.114?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1002.3",
"4.15.0-1004.5",
"4.15.0-1006.9",
"4.15.0-1008.11",
"4.15.0-1009.12",
"4.15.0-1012.15",
"4.15.0-1013.16",
"4.15.0-1015.18",
"4.15.0-1017.20",
"4.15.0-1018.21",
"4.15.0-1021.24",
"4.15.0-1024.29",
"4.15.0-1026.31",
"4.15.0-1028.33",
"4.15.0-1030.35",
"4.15.0-1033.38",
"4.15.0-1034.39",
"4.15.0-1035.40",
"4.15.0-1036.41",
"4.15.0-1038.43",
"4.15.0-1039.44",
"4.15.0-1043.48",
"4.15.0-1045.50",
"4.15.0-1050.57",
"4.15.0-1056.65",
"4.15.0-1057.66",
"4.15.0-1059.68",
"4.15.0-1063.72",
"4.15.0-1064.73",
"4.15.0-1065.75",
"4.15.0-1066.76",
"4.15.0-1067.77",
"4.15.0-1069.79",
"4.15.0-1073.83",
"4.15.0-1076.86",
"4.15.0-1079.89",
"4.15.0-1080.90",
"4.15.0-1081.91",
"4.15.0-1087.97",
"4.15.0-1090.100",
"4.15.0-1091.101",
"4.15.0-1093.103",
"4.15.0-1094.104",
"4.15.0-1096.106",
"4.15.0-1097.107",
"4.15.0-1099.109",
"4.15.0-1100.110",
"4.15.0-1101.112",
"4.15.0-1102.113",
"4.15.0-1103.114"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-1151-oracle",
"binary_version": "4.15.0-1151.162"
},
{
"binary_name": "linux-headers-4.15.0-1151-oracle",
"binary_version": "4.15.0-1151.162"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1151-oracle",
"binary_version": "4.15.0-1151.162"
},
{
"binary_name": "linux-modules-4.15.0-1151-oracle",
"binary_version": "4.15.0-1151.162"
},
{
"binary_name": "linux-modules-extra-4.15.0-1151-oracle",
"binary_version": "4.15.0-1151.162"
},
{
"binary_name": "linux-oracle-headers-4.15.0-1151",
"binary_version": "4.15.0-1151.162"
},
{
"binary_name": "linux-oracle-tools-4.15.0-1151",
"binary_version": "4.15.0-1151.162"
},
{
"binary_name": "linux-tools-4.15.0-1151-oracle",
"binary_version": "4.15.0-1151.162"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "linux-oracle",
"purl": "pkg:deb/ubuntu/linux-oracle@4.15.0-1151.162?arch=source\u0026distro=esm-infra/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.15.0-1151.162"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1007.9",
"4.15.0-1008.10",
"4.15.0-1009.11",
"4.15.0-1010.12",
"4.15.0-1011.13",
"4.15.0-1013.15",
"4.15.0-1014.16",
"4.15.0-1015.17",
"4.15.0-1017.19",
"4.15.0-1018.20",
"4.15.0-1021.23",
"4.15.0-1022.25",
"4.15.0-1023.26",
"4.15.0-1025.28",
"4.15.0-1026.29",
"4.15.0-1027.30",
"4.15.0-1029.32",
"4.15.0-1030.33",
"4.15.0-1031.34",
"4.15.0-1033.36",
"4.15.0-1035.39",
"4.15.0-1037.41",
"4.15.0-1038.42",
"4.15.0-1039.43",
"4.15.0-1045.49",
"4.15.0-1047.51",
"4.15.0-1048.52",
"4.15.0-1050.54",
"4.15.0-1051.55",
"4.15.0-1053.57",
"4.15.0-1054.58",
"4.15.0-1057.62",
"4.15.0-1058.64",
"4.15.0-1059.65",
"4.15.0-1061.67",
"4.15.0-1062.68",
"4.15.0-1063.70",
"4.15.0-1064.71",
"4.15.0-1065.73",
"4.15.0-1066.74",
"4.15.0-1067.75",
"4.15.0-1068.76",
"4.15.0-1069.77",
"4.15.0-1070.78",
"4.15.0-1071.79",
"4.15.0-1072.80",
"4.15.0-1075.83",
"4.15.0-1078.86",
"4.15.0-1079.87",
"4.15.0-1080.88",
"4.15.0-1081.89",
"4.15.0-1082.90",
"4.15.0-1083.91",
"4.15.0-1084.92",
"4.15.0-1085.93",
"4.15.0-1086.94",
"4.15.0-1087.95",
"4.15.0-1089.98",
"4.15.0-1090.99",
"4.15.0-1091.100",
"4.15.0-1092.101",
"4.15.0-1093.102",
"4.15.0-1095.104",
"4.15.0-1098.108",
"4.15.0-1101.112",
"4.15.0-1102.113",
"4.15.0-1104.115",
"4.15.0-1105.116",
"4.15.0-1106.117",
"4.15.0-1107.118",
"4.15.0-1108.119",
"4.15.0-1111.122",
"4.15.0-1112.123",
"4.15.0-1113.124",
"4.15.0-1114.125",
"4.15.0-1115.126",
"4.15.0-1116.127",
"4.15.0-1117.128",
"4.15.0-1118.129",
"4.15.0-1119.130",
"4.15.0-1120.131",
"4.15.0-1121.132",
"4.15.0-1122.133",
"4.15.0-1123.134",
"4.15.0-1124.135",
"4.15.0-1125.136",
"4.15.0-1126.137",
"4.15.0-1127.138",
"4.15.0-1128.139",
"4.15.0-1129.140",
"4.15.0-1130.141",
"4.15.0-1131.142",
"4.15.0-1132.143",
"4.15.0-1133.144",
"4.15.0-1134.145",
"4.15.0-1135.146",
"4.15.0-1136.147",
"4.15.0-1137.148",
"4.15.0-1138.149",
"4.15.0-1139.150",
"4.15.0-1140.151",
"4.15.0-1141.152",
"4.15.0-1142.153",
"4.15.0-1143.154",
"4.15.0-1144.155",
"4.15.0-1145.156",
"4.15.0-1146.157",
"4.15.0-1147.158",
"4.15.0-1148.159",
"4.15.0-1149.160",
"4.15.0-1150.161"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.0.0-1014-oracle",
"binary_version": "5.0.0-1014.19"
},
{
"binary_name": "linux-headers-5.0.0-1014-oracle",
"binary_version": "5.0.0-1014.19"
},
{
"binary_name": "linux-image-unsigned-5.0.0-1014-oracle",
"binary_version": "5.0.0-1014.19"
},
{
"binary_name": "linux-modules-5.0.0-1014-oracle",
"binary_version": "5.0.0-1014.19"
},
{
"binary_name": "linux-modules-extra-5.0.0-1014-oracle",
"binary_version": "5.0.0-1014.19"
},
{
"binary_name": "linux-oracle-5.0-headers-5.0.0-1014",
"binary_version": "5.0.0-1014.19"
},
{
"binary_name": "linux-oracle-5.0-tools-5.0.0-1014",
"binary_version": "5.0.0-1014.19"
},
{
"binary_name": "linux-tools-5.0.0-1014-oracle",
"binary_version": "5.0.0-1014.19"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-oracle-5.0",
"purl": "pkg:deb/ubuntu/linux-oracle-5.0@5.0.0-1014.19?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.0.0-1007.12~18.04.1",
"5.0.0-1008.13~18.04.1",
"5.0.0-1009.14~18.04.1",
"5.0.0-1010.15~18.04.1",
"5.0.0-1011.16",
"5.0.0-1013.18",
"5.0.0-1014.19"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.3.0-1030-oracle",
"binary_version": "5.3.0-1030.32~18.04.1"
},
{
"binary_name": "linux-headers-5.3.0-1030-oracle",
"binary_version": "5.3.0-1030.32~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.3.0-1030-oracle",
"binary_version": "5.3.0-1030.32~18.04.1"
},
{
"binary_name": "linux-modules-5.3.0-1030-oracle",
"binary_version": "5.3.0-1030.32~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.3.0-1030-oracle",
"binary_version": "5.3.0-1030.32~18.04.1"
},
{
"binary_name": "linux-oracle-5.3-headers-5.3.0-1030",
"binary_version": "5.3.0-1030.32~18.04.1"
},
{
"binary_name": "linux-oracle-5.3-tools-5.3.0-1030",
"binary_version": "5.3.0-1030.32~18.04.1"
},
{
"binary_name": "linux-tools-5.3.0-1030-oracle",
"binary_version": "5.3.0-1030.32~18.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-oracle-5.3",
"purl": "pkg:deb/ubuntu/linux-oracle-5.3@5.3.0-1030.32~18.04.1?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.3.0-1011.12~18.04.1",
"5.3.0-1013.14~18.04.1",
"5.3.0-1014.15~18.04.1",
"5.3.0-1016.18~18.04.1",
"5.3.0-1018.20~18.04.1",
"5.3.0-1024.26~18.04.1",
"5.3.0-1027.29~18.04.1",
"5.3.0-1028.30~18.04.1",
"5.3.0-1030.32~18.04.1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1134-oracle",
"binary_version": "5.4.0-1134.143~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-1134-oracle",
"binary_version": "5.4.0-1134.143~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1134-oracle",
"binary_version": "5.4.0-1134.143~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-1134-oracle",
"binary_version": "5.4.0-1134.143~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1134-oracle",
"binary_version": "5.4.0-1134.143~18.04.1"
},
{
"binary_name": "linux-oracle-5.4-headers-5.4.0-1134",
"binary_version": "5.4.0-1134.143~18.04.1"
},
{
"binary_name": "linux-oracle-5.4-tools-5.4.0-1134",
"binary_version": "5.4.0-1134.143~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-1134-oracle",
"binary_version": "5.4.0-1134.143~18.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "linux-oracle-5.4",
"purl": "pkg:deb/ubuntu/linux-oracle-5.4@5.4.0-1134.143~18.04.1?arch=source\u0026distro=esm-infra/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1134.143~18.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1019.19~18.04.1",
"5.4.0-1021.21~18.04.1",
"5.4.0-1022.22~18.04.1",
"5.4.0-1024.24~18.04.1",
"5.4.0-1025.25~18.04.1",
"5.4.0-1028.29~18.04.1",
"5.4.0-1029.31~18.04.1",
"5.4.0-1030.32~18.04.1",
"5.4.0-1033.35",
"5.4.0-1034.36~18.04.1",
"5.4.0-1035.38~18.04.1",
"5.4.0-1037.40~18.04.1",
"5.4.0-1038.41~18.04.1",
"5.4.0-1039.42~18.04.1",
"5.4.0-1041.44~18.04.1",
"5.4.0-1042.45~18.04.1",
"5.4.0-1043.46~18.04.1",
"5.4.0-1044.47~18.04.1",
"5.4.0-1046.50~18.04.2",
"5.4.0-1048.52~18.04.1",
"5.4.0-1049.53~18.04.1",
"5.4.0-1052.56~18.04.1",
"5.4.0-1053.57~18.04.1",
"5.4.0-1054.58~18.04.1",
"5.4.0-1055.59~18.04.1",
"5.4.0-1056.60~18.04.1",
"5.4.0-1057.61~18.04.1",
"5.4.0-1058.62~18.04.1",
"5.4.0-1059.63~18.04.1",
"5.4.0-1061.65~18.04.1",
"5.4.0-1062.66~18.04.1",
"5.4.0-1063.67~18.04.1",
"5.4.0-1064.68~18.04.1",
"5.4.0-1066.71~18.04.1",
"5.4.0-1067.72~18.04.1",
"5.4.0-1069.75~18.04.1",
"5.4.0-1070.76~18.04.1",
"5.4.0-1071.77~18.04.1",
"5.4.0-1073.79~18.04.1",
"5.4.0-1076.83~18.04.1",
"5.4.0-1078.86~18.04.1",
"5.4.0-1079.87~18.04.1",
"5.4.0-1081.89~18.04.1",
"5.4.0-1082.90~18.04.1",
"5.4.0-1083.91~18.04.1",
"5.4.0-1084.92~18.04.1",
"5.4.0-1086.95~18.04.1",
"5.4.0-1087.96~18.04.1",
"5.4.0-1090.99~18.04.2",
"5.4.0-1091.100~18.04.1",
"5.4.0-1092.101~18.04.1",
"5.4.0-1093.102~18.04.1",
"5.4.0-1094.103~18.04.1",
"5.4.0-1098.107~18.04.1",
"5.4.0-1099.108~18.04.1",
"5.4.0-1100.109~18.04.1",
"5.4.0-1101.110~18.04.1",
"5.4.0-1102.111~18.04.1",
"5.4.0-1103.112~18.04.1",
"5.4.0-1104.113~18.04.1",
"5.4.0-1105.114~18.04.1",
"5.4.0-1106.115~18.04.1",
"5.4.0-1107.116~18.04.1",
"5.4.0-1108.117~18.04.1",
"5.4.0-1109.118~18.04.1",
"5.4.0-1110.119~18.04.1",
"5.4.0-1111.120~18.04.1",
"5.4.0-1112.121~18.04.4",
"5.4.0-1113.122~18.04.1",
"5.4.0-1115.124~18.04.1",
"5.4.0-1116.125~18.04.1",
"5.4.0-1117.126~18.04.1",
"5.4.0-1118.127~18.04.1",
"5.4.0-1119.128~18.04.1",
"5.4.0-1120.129~18.04.1",
"5.4.0-1121.130~18.04.1",
"5.4.0-1122.131~18.04.1",
"5.4.0-1123.132~18.04.1",
"5.4.0-1124.133~18.04.1",
"5.4.0-1125.134~18.04.1",
"5.4.0-1126.135~18.04.1",
"5.4.0-1127.136~18.04.1",
"5.4.0-1129.138~18.04.1",
"5.4.0-1130.139~18.04.1",
"5.4.0-1131.140~18.04.1",
"5.4.0-1132.141~18.04.1",
"5.4.0-1133.142~18.04.1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1119-raspi",
"binary_version": "5.4.0-1119.131~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-1119-raspi",
"binary_version": "5.4.0-1119.131~18.04.1"
},
{
"binary_name": "linux-image-5.4.0-1119-raspi",
"binary_version": "5.4.0-1119.131~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-1119-raspi",
"binary_version": "5.4.0-1119.131~18.04.1"
},
{
"binary_name": "linux-raspi-5.4-headers-5.4.0-1119",
"binary_version": "5.4.0-1119.131~18.04.1"
},
{
"binary_name": "linux-raspi-5.4-tools-5.4.0-1119",
"binary_version": "5.4.0-1119.131~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-1119-raspi",
"binary_version": "5.4.0-1119.131~18.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "linux-raspi-5.4",
"purl": "pkg:deb/ubuntu/linux-raspi-5.4@5.4.0-1119.131~18.04.1?arch=source\u0026distro=esm-infra/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1119.131~18.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1013.13~18.04.1",
"5.4.0-1015.15~18.04.1",
"5.4.0-1016.17~18.04.1",
"5.4.0-1018.20~18.04.1",
"5.4.0-1019.21~18.04.1",
"5.4.0-1021.24~18.04.1",
"5.4.0-1022.25~18.04.1",
"5.4.0-1023.26~18.04.1",
"5.4.0-1025.28~18.04.1",
"5.4.0-1026.29~18.04.1",
"5.4.0-1028.31~18.04.1",
"5.4.0-1029.32~18.04.1",
"5.4.0-1030.33~18.04.1",
"5.4.0-1032.35~18.04.1",
"5.4.0-1033.36~18.04.1",
"5.4.0-1034.37~18.04.1",
"5.4.0-1035.38~18.04.1",
"5.4.0-1036.39~18.04.1",
"5.4.0-1038.41~18.04.1",
"5.4.0-1041.45~18.04.1",
"5.4.0-1042.46~18.04.3",
"5.4.0-1043.47~18.04.1",
"5.4.0-1044.48~18.04.1",
"5.4.0-1045.49~18.04.1",
"5.4.0-1046.50~18.04.1",
"5.4.0-1047.52~18.04.1",
"5.4.0-1048.53~18.04.1",
"5.4.0-1050.56~18.04.1",
"5.4.0-1052.58~18.04.1",
"5.4.0-1053.60~18.04.1",
"5.4.0-1055.62~18.04.1",
"5.4.0-1056.63~18.04.1",
"5.4.0-1058.65~18.04.1",
"5.4.0-1059.66~18.04.1",
"5.4.0-1060.68~18.04.1",
"5.4.0-1062.70~18.04.1",
"5.4.0-1065.75~18.04.1",
"5.4.0-1066.76~18.04.1",
"5.4.0-1068.78~18.04.1",
"5.4.0-1069.79~18.04.1",
"5.4.0-1070.80~18.04.1",
"5.4.0-1071.81~18.04.1",
"5.4.0-1073.84~18.04.1",
"5.4.0-1074.85~18.04.1",
"5.4.0-1077.88~18.04.2",
"5.4.0-1078.89~18.04.1",
"5.4.0-1079.90~18.04.1",
"5.4.0-1080.91~18.04.1",
"5.4.0-1081.92~18.04.1",
"5.4.0-1082.93~18.04.1",
"5.4.0-1083.94~18.04.1",
"5.4.0-1084.95~18.04.1",
"5.4.0-1085.96~18.04.1",
"5.4.0-1086.97~18.04.1",
"5.4.0-1088.99~18.04.1",
"5.4.0-1089.100~18.04.1",
"5.4.0-1090.101~18.04.1",
"5.4.0-1091.102~18.04.1",
"5.4.0-1092.103~18.04.1",
"5.4.0-1093.104~18.04.1",
"5.4.0-1094.105~18.04.1",
"5.4.0-1095.106~18.04.1",
"5.4.0-1096.107~18.04.1",
"5.4.0-1097.109~18.04.2",
"5.4.0-1098.110~18.04.2",
"5.4.0-1100.112~18.04.1",
"5.4.0-1101.113~18.04.1",
"5.4.0-1102.114~18.04.1",
"5.4.0-1103.115~18.04.1",
"5.4.0-1104.116~18.04.1",
"5.4.0-1105.117~18.04.1",
"5.4.0-1106.118~18.04.1",
"5.4.0-1107.119~18.04.1",
"5.4.0-1108.120~18.04.1",
"5.4.0-1109.121~18.04.1",
"5.4.0-1110.122~18.04.1",
"5.4.0-1111.123~18.04.1",
"5.4.0-1112.124~18.04.1",
"5.4.0-1114.126~18.04.1",
"5.4.0-1115.127~18.04.1",
"5.4.0-1116.128~18.04.1",
"5.4.0-1117.129~18.04.1",
"5.4.0-1118.130~18.04.1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-aws-fips-headers-4.15.0-2127",
"binary_version": "4.15.0-2127.133"
},
{
"binary_name": "linux-aws-fips-tools-4.15.0-2127",
"binary_version": "4.15.0-2127.133"
},
{
"binary_name": "linux-buildinfo-4.15.0-2127-aws-fips",
"binary_version": "4.15.0-2127.133"
},
{
"binary_name": "linux-headers-4.15.0-2127-aws-fips",
"binary_version": "4.15.0-2127.133"
},
{
"binary_name": "linux-image-unsigned-4.15.0-2127-aws-fips",
"binary_version": "4.15.0-2127.133"
},
{
"binary_name": "linux-image-unsigned-hmac-4.15.0-2127-aws-fips",
"binary_version": "4.15.0-2127.133"
},
{
"binary_name": "linux-modules-4.15.0-2127-aws-fips",
"binary_version": "4.15.0-2127.133"
},
{
"binary_name": "linux-modules-extra-4.15.0-2127-aws-fips",
"binary_version": "4.15.0-2127.133"
},
{
"binary_name": "linux-tools-4.15.0-2127-aws-fips",
"binary_version": "4.15.0-2127.133"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:18.04:LTS",
"name": "linux-aws-fips",
"purl": "pkg:deb/ubuntu/linux-aws-fips@4.15.0-2127.133?arch=source\u0026distro=fips-updates/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.15.0-2127.133"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-2000.4",
"4.15.0-2018.18",
"4.15.0-2021.21",
"4.15.0-2022.22",
"4.15.0-2024.24",
"4.15.0-2025.25",
"4.15.0-2026.26",
"4.15.0-2027.27",
"4.15.0-2030.31",
"4.15.0-2031.32",
"4.15.0-2033.34",
"4.15.0-2034.35",
"4.15.0-2035.37",
"4.15.0-2036.38",
"4.15.0-2037.39",
"4.15.0-2038.40",
"4.15.0-2039.41",
"4.15.0-2040.42",
"4.15.0-2041.43",
"4.15.0-2042.44",
"4.15.0-2044.46",
"4.15.0-2045.47",
"4.15.0-2048.50",
"4.15.0-2051.53",
"4.15.0-2052.54",
"4.15.0-2053.55",
"4.15.0-2054.56",
"4.15.0-2055.57",
"4.15.0-2056.58",
"4.15.0-2057.59",
"4.15.0-2059.61",
"4.15.0-2060.62",
"4.15.0-2061.63",
"4.15.0-2063.66",
"4.15.0-2064.67",
"4.15.0-2065.68",
"4.15.0-2066.69",
"4.15.0-2067.70",
"4.15.0-2069.72",
"4.15.0-2072.76",
"4.15.0-2075.80",
"4.15.0-2076.81",
"4.15.0-2078.83",
"4.15.0-2079.84",
"4.15.0-2080.85",
"4.15.0-2081.87",
"4.15.0-2082.88",
"4.15.0-2083.89",
"4.15.0-2085.91",
"4.15.0-2087.93",
"4.15.0-2089.95",
"4.15.0-2090.96",
"4.15.0-2092.98",
"4.15.0-2093.99",
"4.15.0-2094.100",
"4.15.0-2095.101",
"4.15.0-2096.102",
"4.15.0-2097.103",
"4.15.0-2098.104",
"4.15.0-2099.105",
"4.15.0-2100.106",
"4.15.0-2101.107",
"4.15.0-2102.108",
"4.15.0-2103.109",
"4.15.0-2104.110",
"4.15.0-2105.111",
"4.15.0-2106.112",
"4.15.0-2107.113",
"4.15.0-2108.114",
"4.15.0-2109.115",
"4.15.0-2110.116",
"4.15.0-2111.117",
"4.15.0-2112.118",
"4.15.0-2113.119",
"4.15.0-2114.120",
"4.15.0-2115.121",
"4.15.0-2116.122",
"4.15.0-2117.123",
"4.15.0-2118.124",
"4.15.0-2119.125",
"4.15.0-2120.126",
"4.15.0-2121.127",
"4.15.0-2122.128",
"4.15.0-2123.129",
"4.15.0-2124.130",
"4.15.0-2125.131",
"4.15.0-2126.132"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-azure-fips-cloud-tools-4.15.0-2106",
"binary_version": "4.15.0-2106.112"
},
{
"binary_name": "linux-azure-fips-headers-4.15.0-2106",
"binary_version": "4.15.0-2106.112"
},
{
"binary_name": "linux-azure-fips-tools-4.15.0-2106",
"binary_version": "4.15.0-2106.112"
},
{
"binary_name": "linux-buildinfo-4.15.0-2106-azure-fips",
"binary_version": "4.15.0-2106.112"
},
{
"binary_name": "linux-cloud-tools-4.15.0-2106-azure-fips",
"binary_version": "4.15.0-2106.112"
},
{
"binary_name": "linux-headers-4.15.0-2106-azure-fips",
"binary_version": "4.15.0-2106.112"
},
{
"binary_name": "linux-image-unsigned-4.15.0-2106-azure-fips",
"binary_version": "4.15.0-2106.112"
},
{
"binary_name": "linux-image-unsigned-hmac-4.15.0-2106-azure-fips",
"binary_version": "4.15.0-2106.112"
},
{
"binary_name": "linux-modules-4.15.0-2106-azure-fips",
"binary_version": "4.15.0-2106.112"
},
{
"binary_name": "linux-modules-extra-4.15.0-2106-azure-fips",
"binary_version": "4.15.0-2106.112"
},
{
"binary_name": "linux-tools-4.15.0-2106-azure-fips",
"binary_version": "4.15.0-2106.112"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:18.04:LTS",
"name": "linux-azure-fips",
"purl": "pkg:deb/ubuntu/linux-azure-fips@4.15.0-2106.112?arch=source\u0026distro=fips-updates/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.15.0-2106.112"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1002.2",
"4.15.0-2006.7",
"4.15.0-2007.8",
"4.15.0-2008.9",
"4.15.0-2009.10",
"4.15.0-2012.14",
"4.15.0-2013.15",
"4.15.0-2015.17",
"4.15.0-2016.18",
"4.15.0-2017.20",
"4.15.0-2018.21",
"4.15.0-2020.23",
"4.15.0-2021.24",
"4.15.0-2022.25",
"4.15.0-2023.26",
"4.15.0-2024.27",
"4.15.0-2025.28",
"4.15.0-2026.29",
"4.15.0-2027.30",
"4.15.0-2030.33",
"4.15.0-2033.37",
"4.15.0-2034.38",
"4.15.0-2035.39",
"4.15.0-2036.40",
"4.15.0-2037.41",
"4.15.0-2038.42",
"4.15.0-2039.43",
"4.15.0-2041.45",
"4.15.0-2042.46",
"4.15.0-2043.47",
"4.15.0-2045.49",
"4.15.0-2046.50",
"4.15.0-2047.51",
"4.15.0-2048.52",
"4.15.0-2049.53",
"4.15.0-2050.54",
"4.15.0-2053.58",
"4.15.0-2056.62",
"4.15.0-2057.63",
"4.15.0-2059.65",
"4.15.0-2060.66",
"4.15.0-2062.68",
"4.15.0-2066.72",
"4.15.0-2067.73",
"4.15.0-2068.74",
"4.15.0-2070.76",
"4.15.0-2071.77",
"4.15.0-2072.78",
"4.15.0-2073.79",
"4.15.0-2074.80",
"4.15.0-2075.81",
"4.15.0-2076.82",
"4.15.0-2077.83",
"4.15.0-2078.84",
"4.15.0-2079.85",
"4.15.0-2080.86",
"4.15.0-2081.87",
"4.15.0-2082.88",
"4.15.0-2084.90",
"4.15.0-2085.91",
"4.15.0-2086.92",
"4.15.0-2087.93",
"4.15.0-2088.94",
"4.15.0-2089.95",
"4.15.0-2090.96",
"4.15.0-2091.97",
"4.15.0-2092.98",
"4.15.0-2093.99",
"4.15.0-2094.100",
"4.15.0-2095.101",
"4.15.0-2096.102",
"4.15.0-2097.103",
"4.15.0-2098.104",
"4.15.0-2099.105",
"4.15.0-2100.106",
"4.15.0-2101.107",
"4.15.0-2102.108",
"4.15.0-2104.110",
"4.15.0-2105.111"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-1144-fips",
"binary_version": "4.15.0-1144.156"
},
{
"binary_name": "linux-fips-headers-4.15.0-1144",
"binary_version": "4.15.0-1144.156"
},
{
"binary_name": "linux-fips-tools-4.15.0-1144",
"binary_version": "4.15.0-1144.156"
},
{
"binary_name": "linux-fips-tools-host",
"binary_version": "4.15.0-1144.156"
},
{
"binary_name": "linux-headers-4.15.0-1144-fips",
"binary_version": "4.15.0-1144.156"
},
{
"binary_name": "linux-image-4.15.0-1144-fips",
"binary_version": "4.15.0-1144.156"
},
{
"binary_name": "linux-image-hmac-4.15.0-1144-fips",
"binary_version": "4.15.0-1144.156"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1144-fips",
"binary_version": "4.15.0-1144.156"
},
{
"binary_name": "linux-image-unsigned-hmac-4.15.0-1144-fips",
"binary_version": "4.15.0-1144.156"
},
{
"binary_name": "linux-modules-4.15.0-1144-fips",
"binary_version": "4.15.0-1144.156"
},
{
"binary_name": "linux-modules-extra-4.15.0-1144-fips",
"binary_version": "4.15.0-1144.156"
},
{
"binary_name": "linux-tools-4.15.0-1144-fips",
"binary_version": "4.15.0-1144.156"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:18.04:LTS",
"name": "linux-fips",
"purl": "pkg:deb/ubuntu/linux-fips@4.15.0-1144.156?arch=source\u0026distro=fips-updates/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.15.0-1144.156"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1027.32",
"4.15.0-1029.34",
"4.15.0-1034.39",
"4.15.0-1035.40",
"4.15.0-1037.42",
"4.15.0-1038.43",
"4.15.0-1039.44",
"4.15.0-1040.45",
"4.15.0-1041.46",
"4.15.0-1044.50",
"4.15.0-1045.52",
"4.15.0-1046.53",
"4.15.0-1048.55",
"4.15.0-1049.56",
"4.15.0-1050.58",
"4.15.0-1051.59",
"4.15.0-1052.60",
"4.15.0-1053.61",
"4.15.0-1054.62",
"4.15.0-1055.63",
"4.15.0-1056.64",
"4.15.0-1057.65",
"4.15.0-1058.66",
"4.15.0-1059.67",
"4.15.0-1060.68",
"4.15.0-1063.71",
"4.15.0-1066.75",
"4.15.0-1067.76",
"4.15.0-1068.77",
"4.15.0-1069.78",
"4.15.0-1070.79",
"4.15.0-1071.80",
"4.15.0-1072.81",
"4.15.0-1073.82",
"4.15.0-1075.84",
"4.15.0-1076.85",
"4.15.0-1078.87",
"4.15.0-1080.89",
"4.15.0-1081.90",
"4.15.0-1083.92",
"4.15.0-1084.93",
"4.15.0-1085.94",
"4.15.0-1087.96",
"4.15.0-1090.100",
"4.15.0-1093.104",
"4.15.0-1094.105",
"4.15.0-1096.107",
"4.15.0-1097.108",
"4.15.0-1098.109",
"4.15.0-1099.110",
"4.15.0-1100.111",
"4.15.0-1103.114",
"4.15.0-1104.115",
"4.15.0-1105.116",
"4.15.0-1107.118",
"4.15.0-1108.119",
"4.15.0-1109.120",
"4.15.0-1110.121",
"4.15.0-1111.122",
"4.15.0-1112.123",
"4.15.0-1113.124",
"4.15.0-1114.125",
"4.15.0-1115.126",
"4.15.0-1116.127",
"4.15.0-1117.128",
"4.15.0-1118.129",
"4.15.0-1119.130",
"4.15.0-1121.132",
"4.15.0-1122.133",
"4.15.0-1123.134",
"4.15.0-1124.135",
"4.15.0-1125.136",
"4.15.0-1126.137",
"4.15.0-1127.138",
"4.15.0-1128.139",
"4.15.0-1129.140",
"4.15.0-1130.141",
"4.15.0-1131.142",
"4.15.0-1132.143",
"4.15.0-1133.144",
"4.15.0-1134.145",
"4.15.0-1135.146",
"4.15.0-1136.147",
"4.15.0-1137.148",
"4.15.0-1138.149",
"4.15.0-1139.150",
"4.15.0-1140.151",
"4.15.0-1141.153",
"4.15.0-1142.154",
"4.15.0-1143.155"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-2090-gcp-fips",
"binary_version": "4.15.0-2090.96"
},
{
"binary_name": "linux-gcp-fips-headers-4.15.0-2090",
"binary_version": "4.15.0-2090.96"
},
{
"binary_name": "linux-gcp-fips-tools-4.15.0-2090",
"binary_version": "4.15.0-2090.96"
},
{
"binary_name": "linux-headers-4.15.0-2090-gcp-fips",
"binary_version": "4.15.0-2090.96"
},
{
"binary_name": "linux-image-unsigned-4.15.0-2090-gcp-fips",
"binary_version": "4.15.0-2090.96"
},
{
"binary_name": "linux-image-unsigned-hmac-4.15.0-2090-gcp-fips",
"binary_version": "4.15.0-2090.96"
},
{
"binary_name": "linux-modules-4.15.0-2090-gcp-fips",
"binary_version": "4.15.0-2090.96"
},
{
"binary_name": "linux-modules-extra-4.15.0-2090-gcp-fips",
"binary_version": "4.15.0-2090.96"
},
{
"binary_name": "linux-tools-4.15.0-2090-gcp-fips",
"binary_version": "4.15.0-2090.96"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:18.04:LTS",
"name": "linux-gcp-fips",
"purl": "pkg:deb/ubuntu/linux-gcp-fips@4.15.0-2090.96?arch=source\u0026distro=fips-updates/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.15.0-2090.96"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-2013.14",
"4.15.0-2016.18",
"4.15.0-2017.19",
"4.15.0-2018.20",
"4.15.0-2019.21",
"4.15.0-2020.22",
"4.15.0-2021.23",
"4.15.0-2022.24",
"4.15.0-2024.26",
"4.15.0-2025.27",
"4.15.0-2026.28",
"4.15.0-2028.31",
"4.15.0-2029.32",
"4.15.0-2030.33",
"4.15.0-2031.34",
"4.15.0-2032.35",
"4.15.0-2034.37",
"4.15.0-2037.41",
"4.15.0-2040.45",
"4.15.0-2041.46",
"4.15.0-2043.48",
"4.15.0-2044.49",
"4.15.0-2045.50",
"4.15.0-2047.52",
"4.15.0-2050.55",
"4.15.0-2052.57",
"4.15.0-2054.59",
"4.15.0-2055.60",
"4.15.0-2056.61",
"4.15.0-2057.62",
"4.15.0-2058.63",
"4.15.0-2059.64",
"4.15.0-2060.65",
"4.15.0-2061.66",
"4.15.0-2062.67",
"4.15.0-2063.68",
"4.15.0-2064.69",
"4.15.0-2065.70",
"4.15.0-2066.71",
"4.15.0-2067.72",
"4.15.0-2068.73",
"4.15.0-2069.74",
"4.15.0-2070.75",
"4.15.0-2071.76",
"4.15.0-2072.77",
"4.15.0-2073.78",
"4.15.0-2074.79",
"4.15.0-2075.80",
"4.15.0-2076.81",
"4.15.0-2077.83",
"4.15.0-2078.84",
"4.15.0-2079.85",
"4.15.0-2080.86",
"4.15.0-2081.87",
"4.15.0-2082.88",
"4.15.0-2083.89",
"4.15.0-2084.90",
"4.15.0-2085.91",
"4.15.0-2086.92",
"4.15.0-2087.93",
"4.15.0-2088.94",
"4.15.0-2089.95"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-aws-fips-headers-4.15.0-2000",
"binary_version": "4.15.0-2000.4"
},
{
"binary_name": "linux-aws-fips-tools-4.15.0-2000",
"binary_version": "4.15.0-2000.4"
},
{
"binary_name": "linux-buildinfo-4.15.0-2000-aws-fips",
"binary_version": "4.15.0-2000.4"
},
{
"binary_name": "linux-headers-4.15.0-2000-aws-fips",
"binary_version": "4.15.0-2000.4"
},
{
"binary_name": "linux-image-unsigned-4.15.0-2000-aws-fips",
"binary_version": "4.15.0-2000.4"
},
{
"binary_name": "linux-image-unsigned-hmac-4.15.0-2000-aws-fips",
"binary_version": "4.15.0-2000.4"
},
{
"binary_name": "linux-modules-4.15.0-2000-aws-fips",
"binary_version": "4.15.0-2000.4"
},
{
"binary_name": "linux-modules-extra-4.15.0-2000-aws-fips",
"binary_version": "4.15.0-2000.4"
},
{
"binary_name": "linux-tools-4.15.0-2000-aws-fips",
"binary_version": "4.15.0-2000.4"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS:18.04:LTS",
"name": "linux-aws-fips",
"purl": "pkg:deb/ubuntu/linux-aws-fips@4.15.0-2000.4?arch=source\u0026distro=fips/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-2000.4"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-azure-fips-cloud-tools-4.15.0-1002",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-azure-fips-headers-4.15.0-1002",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-azure-fips-tools-4.15.0-1002",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-buildinfo-4.15.0-1002-azure-fips",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-cloud-tools-4.15.0-1002-azure-fips",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-headers-4.15.0-1002-azure-fips",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1002-azure-fips",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-image-unsigned-hmac-4.15.0-1002-azure-fips",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-modules-4.15.0-1002-azure-fips",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-modules-extra-4.15.0-1002-azure-fips",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-tools-4.15.0-1002-azure-fips",
"binary_version": "4.15.0-1002.2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS:18.04:LTS",
"name": "linux-azure-fips",
"purl": "pkg:deb/ubuntu/linux-azure-fips@4.15.0-1002.2?arch=source\u0026distro=fips/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1002.2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-1011-fips",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-fips-headers-4.15.0-1011",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-fips-tools-4.15.0-1011",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-fips-tools-host",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-headers-4.15.0-1011-fips",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-image-4.15.0-1011-fips",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-image-hmac-4.15.0-1011-fips",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1011-fips",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-image-unsigned-hmac-4.15.0-1011-fips",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-modules-4.15.0-1011-fips",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-modules-extra-4.15.0-1011-fips",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-tools-4.15.0-1011-fips",
"binary_version": "4.15.0-1011.12"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS:18.04:LTS",
"name": "linux-fips",
"purl": "pkg:deb/ubuntu/linux-fips@4.15.0-1011.12?arch=source\u0026distro=fips/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1011.12"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-1001-gcp-fips",
"binary_version": "4.15.0-1001.1"
},
{
"binary_name": "linux-gcp-fips-headers-4.15.0-1001",
"binary_version": "4.15.0-1001.1"
},
{
"binary_name": "linux-gcp-fips-tools-4.15.0-1001",
"binary_version": "4.15.0-1001.1"
},
{
"binary_name": "linux-headers-4.15.0-1001-gcp-fips",
"binary_version": "4.15.0-1001.1"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1001-gcp-fips",
"binary_version": "4.15.0-1001.1"
},
{
"binary_name": "linux-image-unsigned-hmac-4.15.0-1001-gcp-fips",
"binary_version": "4.15.0-1001.1"
},
{
"binary_name": "linux-modules-4.15.0-1001-gcp-fips",
"binary_version": "4.15.0-1001.1"
},
{
"binary_name": "linux-modules-extra-4.15.0-1001-gcp-fips",
"binary_version": "4.15.0-1001.1"
},
{
"binary_name": "linux-tools-4.15.0-1001-gcp-fips",
"binary_version": "4.15.0-1001.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS:18.04:LTS",
"name": "linux-gcp-fips",
"purl": "pkg:deb/ubuntu/linux-gcp-fips@4.15.0-1001.1?arch=source\u0026distro=fips/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1001.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "block-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "block-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "crypto-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "crypto-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "dasd-extra-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "dasd-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "fat-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "fat-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "fb-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "firewire-core-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "floppy-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "fs-core-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "fs-core-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "fs-secondary-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "fs-secondary-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "input-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "input-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "ipmi-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "ipmi-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "kernel-image-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "kernel-image-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-buildinfo-5.4.0-200-generic",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-buildinfo-5.4.0-200-generic-lpae",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-buildinfo-5.4.0-200-lowlatency",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-cloud-tools-5.4.0-200",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-cloud-tools-5.4.0-200-generic",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-cloud-tools-5.4.0-200-lowlatency",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-cloud-tools-common",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-headers-5.4.0-200",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-headers-5.4.0-200-generic",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-headers-5.4.0-200-generic-lpae",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-headers-5.4.0-200-lowlatency",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-image-5.4.0-200-generic",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-image-5.4.0-200-generic-lpae",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-image-unsigned-5.4.0-200-generic",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-image-unsigned-5.4.0-200-lowlatency",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-modules-5.4.0-200-generic",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-modules-5.4.0-200-generic-lpae",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-modules-5.4.0-200-lowlatency",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-modules-extra-5.4.0-200-generic",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-source-5.4.0",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-tools-5.4.0-200",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-tools-5.4.0-200-generic",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-tools-5.4.0-200-generic-lpae",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-tools-5.4.0-200-lowlatency",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-tools-common",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-tools-host",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-udebs-generic",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-udebs-generic-lpae",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "md-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "md-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "message-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "mouse-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "mouse-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "multipath-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "multipath-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "nfs-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "nfs-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "nic-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "nic-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "nic-pcmcia-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "nic-shared-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "nic-shared-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "nic-usb-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "nic-usb-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "parport-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "parport-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "pata-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "pcmcia-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "pcmcia-storage-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "plip-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "plip-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "ppp-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "ppp-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "sata-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "sata-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "scsi-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "scsi-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "serial-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "storage-core-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "storage-core-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "usb-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "usb-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "virtio-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "vlan-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "vlan-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux",
"purl": "pkg:deb/ubuntu/linux@5.4.0-200.220?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-200.220"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.3.0-18.19",
"5.3.0-24.26",
"5.4.0-9.12",
"5.4.0-18.22",
"5.4.0-21.25",
"5.4.0-24.28",
"5.4.0-25.29",
"5.4.0-26.30",
"5.4.0-28.32",
"5.4.0-29.33",
"5.4.0-31.35",
"5.4.0-33.37",
"5.4.0-37.41",
"5.4.0-39.43",
"5.4.0-40.44",
"5.4.0-42.46",
"5.4.0-45.49",
"5.4.0-47.51",
"5.4.0-48.52",
"5.4.0-51.56",
"5.4.0-52.57",
"5.4.0-53.59",
"5.4.0-54.60",
"5.4.0-56.62",
"5.4.0-58.64",
"5.4.0-59.65",
"5.4.0-60.67",
"5.4.0-62.70",
"5.4.0-64.72",
"5.4.0-65.73",
"5.4.0-66.74",
"5.4.0-67.75",
"5.4.0-70.78",
"5.4.0-71.79",
"5.4.0-72.80",
"5.4.0-73.82",
"5.4.0-74.83",
"5.4.0-77.86",
"5.4.0-80.90",
"5.4.0-81.91",
"5.4.0-84.94",
"5.4.0-86.97",
"5.4.0-88.99",
"5.4.0-89.100",
"5.4.0-90.101",
"5.4.0-91.102",
"5.4.0-92.103",
"5.4.0-94.106",
"5.4.0-96.109",
"5.4.0-97.110",
"5.4.0-99.112",
"5.4.0-100.113",
"5.4.0-104.118",
"5.4.0-105.119",
"5.4.0-107.121",
"5.4.0-109.123",
"5.4.0-110.124",
"5.4.0-113.127",
"5.4.0-117.132",
"5.4.0-120.136",
"5.4.0-121.137",
"5.4.0-122.138",
"5.4.0-124.140",
"5.4.0-125.141",
"5.4.0-126.142",
"5.4.0-128.144",
"5.4.0-131.147",
"5.4.0-132.148",
"5.4.0-135.152",
"5.4.0-136.153",
"5.4.0-137.154",
"5.4.0-139.156",
"5.4.0-144.161",
"5.4.0-146.163",
"5.4.0-147.164",
"5.4.0-148.165",
"5.4.0-149.166",
"5.4.0-150.167",
"5.4.0-152.169",
"5.4.0-153.170",
"5.4.0-155.172",
"5.4.0-156.173",
"5.4.0-159.176",
"5.4.0-162.179",
"5.4.0-163.180",
"5.4.0-164.181",
"5.4.0-165.182",
"5.4.0-166.183",
"5.4.0-167.184",
"5.4.0-169.187",
"5.4.0-170.188",
"5.4.0-171.189",
"5.4.0-172.190",
"5.4.0-173.191",
"5.4.0-174.193",
"5.4.0-176.196",
"5.4.0-177.197",
"5.4.0-181.201",
"5.4.0-182.202",
"5.4.0-186.206",
"5.4.0-187.207",
"5.4.0-189.209",
"5.4.0-190.210",
"5.4.0-192.212",
"5.4.0-193.213",
"5.4.0-195.215",
"5.4.0-196.216",
"5.4.0-198.218"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-aws-cloud-tools-5.4.0-1135",
"binary_version": "5.4.0-1135.145"
},
{
"binary_name": "linux-aws-headers-5.4.0-1135",
"binary_version": "5.4.0-1135.145"
},
{
"binary_name": "linux-aws-tools-5.4.0-1135",
"binary_version": "5.4.0-1135.145"
},
{
"binary_name": "linux-buildinfo-5.4.0-1135-aws",
"binary_version": "5.4.0-1135.145"
},
{
"binary_name": "linux-cloud-tools-5.4.0-1135-aws",
"binary_version": "5.4.0-1135.145"
},
{
"binary_name": "linux-headers-5.4.0-1135-aws",
"binary_version": "5.4.0-1135.145"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1135-aws",
"binary_version": "5.4.0-1135.145"
},
{
"binary_name": "linux-modules-5.4.0-1135-aws",
"binary_version": "5.4.0-1135.145"
},
{
"binary_name": "linux-modules-extra-5.4.0-1135-aws",
"binary_version": "5.4.0-1135.145"
},
{
"binary_name": "linux-tools-5.4.0-1135-aws",
"binary_version": "5.4.0-1135.145"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-aws",
"purl": "pkg:deb/ubuntu/linux-aws@5.4.0-1135.145?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1135.145"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.3.0-1003.3",
"5.3.0-1008.9",
"5.3.0-1009.10",
"5.3.0-1010.11",
"5.4.0-1005.5",
"5.4.0-1007.7",
"5.4.0-1008.8",
"5.4.0-1009.9",
"5.4.0-1011.11",
"5.4.0-1015.15",
"5.4.0-1017.17",
"5.4.0-1018.18",
"5.4.0-1020.20",
"5.4.0-1021.21",
"5.4.0-1022.22",
"5.4.0-1024.24",
"5.4.0-1025.25",
"5.4.0-1028.29",
"5.4.0-1029.30",
"5.4.0-1030.31",
"5.4.0-1032.33",
"5.4.0-1034.35",
"5.4.0-1035.37",
"5.4.0-1037.39",
"5.4.0-1038.40",
"5.4.0-1039.41",
"5.4.0-1041.43",
"5.4.0-1043.45",
"5.4.0-1045.47",
"5.4.0-1047.49",
"5.4.0-1048.50",
"5.4.0-1049.51",
"5.4.0-1051.53",
"5.4.0-1054.57",
"5.4.0-1055.58",
"5.4.0-1056.59",
"5.4.0-1057.60",
"5.4.0-1058.61",
"5.4.0-1059.62",
"5.4.0-1060.63",
"5.4.0-1061.64",
"5.4.0-1063.66",
"5.4.0-1064.67",
"5.4.0-1065.68",
"5.4.0-1066.69",
"5.4.0-1068.72",
"5.4.0-1069.73",
"5.4.0-1071.76",
"5.4.0-1072.77",
"5.4.0-1073.78",
"5.4.0-1075.80",
"5.4.0-1078.84",
"5.4.0-1080.87",
"5.4.0-1081.88",
"5.4.0-1083.90",
"5.4.0-1084.91",
"5.4.0-1085.92",
"5.4.0-1086.93",
"5.4.0-1088.96",
"5.4.0-1089.97",
"5.4.0-1092.100",
"5.4.0-1093.101",
"5.4.0-1094.102",
"5.4.0-1096.104",
"5.4.0-1097.105",
"5.4.0-1099.107",
"5.4.0-1100.108",
"5.4.0-1101.109",
"5.4.0-1102.110",
"5.4.0-1103.111",
"5.4.0-1104.112",
"5.4.0-1105.113",
"5.4.0-1106.114",
"5.4.0-1107.115",
"5.4.0-1108.116",
"5.4.0-1109.118",
"5.4.0-1110.119",
"5.4.0-1111.120",
"5.4.0-1112.121",
"5.4.0-1113.123",
"5.4.0-1114.124",
"5.4.0-1116.126",
"5.4.0-1117.127",
"5.4.0-1118.128",
"5.4.0-1119.129",
"5.4.0-1120.130",
"5.4.0-1121.131",
"5.4.0-1122.132",
"5.4.0-1123.133",
"5.4.0-1124.134",
"5.4.0-1125.135",
"5.4.0-1126.136",
"5.4.0-1127.137",
"5.4.0-1128.138",
"5.4.0-1129.139",
"5.4.0-1130.140",
"5.4.0-1131.141",
"5.4.0-1132.142",
"5.4.0-1133.143",
"5.4.0-1134.144"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-aws-5.15-cloud-tools-5.15.0-1072",
"binary_version": "5.15.0-1072.78~20.04.1"
},
{
"binary_name": "linux-aws-5.15-headers-5.15.0-1072",
"binary_version": "5.15.0-1072.78~20.04.1"
},
{
"binary_name": "linux-aws-5.15-tools-5.15.0-1072",
"binary_version": "5.15.0-1072.78~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.15.0-1072-aws",
"binary_version": "5.15.0-1072.78~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1072-aws",
"binary_version": "5.15.0-1072.78~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1072-aws",
"binary_version": "5.15.0-1072.78~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1072-aws",
"binary_version": "5.15.0-1072.78~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1072-aws",
"binary_version": "5.15.0-1072.78~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1072-aws",
"binary_version": "5.15.0-1072.78~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1072-aws",
"binary_version": "5.15.0-1072.78~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-aws-5.15",
"purl": "pkg:deb/ubuntu/linux-aws-5.15@5.15.0-1072.78~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1072.78~20.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1014.18~20.04.1",
"5.15.0-1015.19~20.04.1",
"5.15.0-1017.21~20.04.1",
"5.15.0-1019.23~20.04.1",
"5.15.0-1020.24~20.04.1",
"5.15.0-1021.25~20.04.1",
"5.15.0-1022.26~20.04.1",
"5.15.0-1023.27~20.04.1",
"5.15.0-1026.30~20.04.2",
"5.15.0-1027.31~20.04.1",
"5.15.0-1028.32~20.04.1",
"5.15.0-1030.34~20.04.1",
"5.15.0-1031.35~20.04.1",
"5.15.0-1033.37~20.04.1",
"5.15.0-1034.38~20.04.1",
"5.15.0-1035.39~20.04.1",
"5.15.0-1036.40~20.04.1",
"5.15.0-1037.41~20.04.1",
"5.15.0-1038.43~20.04.1",
"5.15.0-1039.44~20.04.1",
"5.15.0-1040.45~20.04.1",
"5.15.0-1041.46~20.04.1",
"5.15.0-1043.48~20.04.1",
"5.15.0-1044.49~20.04.1",
"5.15.0-1045.50~20.04.1",
"5.15.0-1047.52~20.04.1",
"5.15.0-1048.53~20.04.1",
"5.15.0-1049.54~20.04.1",
"5.15.0-1050.55~20.04.1",
"5.15.0-1051.56~20.04.1",
"5.15.0-1052.57~20.04.1",
"5.15.0-1053.58~20.04.1",
"5.15.0-1055.60~20.04.1",
"5.15.0-1056.61~20.04.1",
"5.15.0-1057.63~20.04.1",
"5.15.0-1058.64~20.04.1",
"5.15.0-1061.67~20.04.1",
"5.15.0-1062.68~20.04.1",
"5.15.0-1063.69~20.04.1",
"5.15.0-1064.70~20.04.1",
"5.15.0-1065.71~20.04.1",
"5.15.0-1066.72~20.04.1",
"5.15.0-1067.73~20.04.1",
"5.15.0-1068.74~20.04.1",
"5.15.0-1069.75~20.04.1",
"5.15.0-1070.76~20.04.1",
"5.15.0-1071.77~20.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-azure-cloud-tools-5.4.0-1140",
"binary_version": "5.4.0-1140.147"
},
{
"binary_name": "linux-azure-headers-5.4.0-1140",
"binary_version": "5.4.0-1140.147"
},
{
"binary_name": "linux-azure-tools-5.4.0-1140",
"binary_version": "5.4.0-1140.147"
},
{
"binary_name": "linux-buildinfo-5.4.0-1140-azure",
"binary_version": "5.4.0-1140.147"
},
{
"binary_name": "linux-cloud-tools-5.4.0-1140-azure",
"binary_version": "5.4.0-1140.147"
},
{
"binary_name": "linux-headers-5.4.0-1140-azure",
"binary_version": "5.4.0-1140.147"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1140-azure",
"binary_version": "5.4.0-1140.147"
},
{
"binary_name": "linux-modules-5.4.0-1140-azure",
"binary_version": "5.4.0-1140.147"
},
{
"binary_name": "linux-modules-extra-5.4.0-1140-azure",
"binary_version": "5.4.0-1140.147"
},
{
"binary_name": "linux-tools-5.4.0-1140-azure",
"binary_version": "5.4.0-1140.147"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-azure",
"purl": "pkg:deb/ubuntu/linux-azure@5.4.0-1140.147?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1140.147"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.3.0-1003.3",
"5.3.0-1008.9",
"5.3.0-1009.10",
"5.4.0-1006.6",
"5.4.0-1008.8",
"5.4.0-1009.9",
"5.4.0-1010.10",
"5.4.0-1012.12",
"5.4.0-1016.16",
"5.4.0-1019.19",
"5.4.0-1020.20",
"5.4.0-1022.22",
"5.4.0-1023.23",
"5.4.0-1025.25",
"5.4.0-1026.26",
"5.4.0-1031.32",
"5.4.0-1032.33",
"5.4.0-1034.35",
"5.4.0-1035.36",
"5.4.0-1036.38",
"5.4.0-1039.41",
"5.4.0-1040.42",
"5.4.0-1041.43",
"5.4.0-1043.45",
"5.4.0-1044.46",
"5.4.0-1046.48",
"5.4.0-1047.49",
"5.4.0-1048.50",
"5.4.0-1049.51",
"5.4.0-1051.53",
"5.4.0-1055.57",
"5.4.0-1056.58",
"5.4.0-1058.60",
"5.4.0-1059.62",
"5.4.0-1061.64",
"5.4.0-1062.65",
"5.4.0-1063.66",
"5.4.0-1064.67",
"5.4.0-1065.68",
"5.4.0-1067.70",
"5.4.0-1068.71",
"5.4.0-1069.72",
"5.4.0-1070.73",
"5.4.0-1072.75",
"5.4.0-1073.76",
"5.4.0-1074.77",
"5.4.0-1077.80",
"5.4.0-1078.81",
"5.4.0-1080.83",
"5.4.0-1083.87",
"5.4.0-1085.90",
"5.4.0-1086.91",
"5.4.0-1089.94",
"5.4.0-1090.95",
"5.4.0-1091.96",
"5.4.0-1094.100",
"5.4.0-1095.101",
"5.4.0-1098.104",
"5.4.0-1100.106",
"5.4.0-1101.107",
"5.4.0-1103.109",
"5.4.0-1104.110",
"5.4.0-1105.111",
"5.4.0-1106.112",
"5.4.0-1107.113",
"5.4.0-1108.114",
"5.4.0-1109.115",
"5.4.0-1110.116",
"5.4.0-1111.117",
"5.4.0-1112.118",
"5.4.0-1113.119",
"5.4.0-1114.120",
"5.4.0-1115.122",
"5.4.0-1116.123",
"5.4.0-1117.124",
"5.4.0-1118.125",
"5.4.0-1119.126",
"5.4.0-1120.127",
"5.4.0-1121.128",
"5.4.0-1122.129",
"5.4.0-1123.130",
"5.4.0-1124.131",
"5.4.0-1126.133",
"5.4.0-1127.134",
"5.4.0-1128.135",
"5.4.0-1129.136",
"5.4.0-1130.137",
"5.4.0-1131.138",
"5.4.0-1132.139",
"5.4.0-1133.140",
"5.4.0-1134.141",
"5.4.0-1135.142",
"5.4.0-1136.143",
"5.4.0-1137.144",
"5.4.0-1138.145",
"5.4.0-1139.146"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-azure-5.15-cloud-tools-5.15.0-1078",
"binary_version": "5.15.0-1078.87~20.04.1"
},
{
"binary_name": "linux-azure-5.15-headers-5.15.0-1078",
"binary_version": "5.15.0-1078.87~20.04.1"
},
{
"binary_name": "linux-azure-5.15-tools-5.15.0-1078",
"binary_version": "5.15.0-1078.87~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.15.0-1078-azure",
"binary_version": "5.15.0-1078.87~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1078-azure",
"binary_version": "5.15.0-1078.87~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1078-azure",
"binary_version": "5.15.0-1078.87~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1078-azure",
"binary_version": "5.15.0-1078.87~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1078-azure",
"binary_version": "5.15.0-1078.87~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1078-azure",
"binary_version": "5.15.0-1078.87~20.04.1"
},
{
"binary_name": "linux-modules-involflt-5.15.0-1078-azure",
"binary_version": "5.15.0-1078.87~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1078-azure",
"binary_version": "5.15.0-1078.87~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-azure-5.15",
"purl": "pkg:deb/ubuntu/linux-azure-5.15@5.15.0-1078.87~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1078.87~20.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1007.8~20.04.1",
"5.15.0-1008.9~20.04.1",
"5.15.0-1013.16~20.04.1",
"5.15.0-1014.17~20.04.1",
"5.15.0-1017.20~20.04.1",
"5.15.0-1019.24~20.04.1",
"5.15.0-1020.25~20.04.1",
"5.15.0-1021.26~20.04.1",
"5.15.0-1022.27~20.04.1",
"5.15.0-1023.29~20.04.1",
"5.15.0-1029.36~20.04.1",
"5.15.0-1030.37~20.04.1",
"5.15.0-1031.38~20.04.1",
"5.15.0-1033.40~20.04.1",
"5.15.0-1034.41~20.04.1",
"5.15.0-1035.42~20.04.1",
"5.15.0-1036.43~20.04.1",
"5.15.0-1037.44~20.04.1",
"5.15.0-1038.45~20.04.1",
"5.15.0-1039.46~20.04.1",
"5.15.0-1040.47~20.04.1",
"5.15.0-1041.48~20.04.1",
"5.15.0-1042.49~20.04.1",
"5.15.0-1043.50~20.04.1",
"5.15.0-1045.52~20.04.1",
"5.15.0-1046.53~20.04.1",
"5.15.0-1047.54~20.04.1",
"5.15.0-1049.56~20.04.1",
"5.15.0-1050.57~20.04.1",
"5.15.0-1051.59~20.04.1",
"5.15.0-1052.60~20.04.1",
"5.15.0-1053.61~20.04.1",
"5.15.0-1054.62~20.04.1",
"5.15.0-1056.64~20.04.1",
"5.15.0-1057.65~20.04.1",
"5.15.0-1058.66~20.04.2",
"5.15.0-1059.67~20.04.1",
"5.15.0-1060.69~20.04.1",
"5.15.0-1061.70~20.04.1",
"5.15.0-1063.72~20.04.1",
"5.15.0-1064.73~20.04.1",
"5.15.0-1065.74~20.04.1",
"5.15.0-1067.76~20.04.1",
"5.15.0-1068.77~20.04.1",
"5.15.0-1070.79~20.04.1",
"5.15.0-1071.80~20.04.1",
"5.15.0-1072.81~20.04.1",
"5.15.0-1073.82~20.04.1",
"5.15.0-1074.83~20.04.1",
"5.15.0-1075.84~20.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-bluefield-headers-5.4.0-1095",
"binary_version": "5.4.0-1095.102"
},
{
"binary_name": "linux-bluefield-tools-5.4.0-1095",
"binary_version": "5.4.0-1095.102"
},
{
"binary_name": "linux-buildinfo-5.4.0-1095-bluefield",
"binary_version": "5.4.0-1095.102"
},
{
"binary_name": "linux-headers-5.4.0-1095-bluefield",
"binary_version": "5.4.0-1095.102"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1095-bluefield",
"binary_version": "5.4.0-1095.102"
},
{
"binary_name": "linux-modules-5.4.0-1095-bluefield",
"binary_version": "5.4.0-1095.102"
},
{
"binary_name": "linux-tools-5.4.0-1095-bluefield",
"binary_version": "5.4.0-1095.102"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-bluefield",
"purl": "pkg:deb/ubuntu/linux-bluefield@5.4.0-1095.102?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1095.102"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1007.10",
"5.4.0-1011.14",
"5.4.0-1012.15",
"5.4.0-1013.16",
"5.4.0-1016.19",
"5.4.0-1019.22",
"5.4.0-1020.23",
"5.4.0-1021.24",
"5.4.0-1022.25",
"5.4.0-1023.26",
"5.4.0-1025.28",
"5.4.0-1026.29",
"5.4.0-1028.31",
"5.4.0-1030.33",
"5.4.0-1032.35",
"5.4.0-1035.38",
"5.4.0-1036.39",
"5.4.0-1040.44",
"5.4.0-1042.47",
"5.4.0-1044.49",
"5.4.0-1045.50",
"5.4.0-1046.51",
"5.4.0-1047.52",
"5.4.0-1049.55",
"5.4.0-1050.56",
"5.4.0-1054.60",
"5.4.0-1058.64",
"5.4.0-1059.65",
"5.4.0-1060.66",
"5.4.0-1062.68",
"5.4.0-1064.70",
"5.4.0-1065.71",
"5.4.0-1066.72",
"5.4.0-1068.74",
"5.4.0-1070.76",
"5.4.0-1071.77",
"5.4.0-1072.78",
"5.4.0-1073.79",
"5.4.0-1074.80",
"5.4.0-1075.81",
"5.4.0-1076.82",
"5.4.0-1077.83",
"5.4.0-1078.84",
"5.4.0-1079.85",
"5.4.0-1080.87",
"5.4.0-1081.88",
"5.4.0-1082.89",
"5.4.0-1083.90",
"5.4.0-1084.91",
"5.4.0-1085.92",
"5.4.0-1086.93",
"5.4.0-1087.94",
"5.4.0-1088.95",
"5.4.0-1089.96",
"5.4.0-1090.97",
"5.4.0-1091.98",
"5.4.0-1092.99",
"5.4.0-1093.100",
"5.4.0-1094.101"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1139-gcp",
"binary_version": "5.4.0-1139.148"
},
{
"binary_name": "linux-gcp-headers-5.4.0-1139",
"binary_version": "5.4.0-1139.148"
},
{
"binary_name": "linux-gcp-tools-5.4.0-1139",
"binary_version": "5.4.0-1139.148"
},
{
"binary_name": "linux-headers-5.4.0-1139-gcp",
"binary_version": "5.4.0-1139.148"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1139-gcp",
"binary_version": "5.4.0-1139.148"
},
{
"binary_name": "linux-modules-5.4.0-1139-gcp",
"binary_version": "5.4.0-1139.148"
},
{
"binary_name": "linux-modules-extra-5.4.0-1139-gcp",
"binary_version": "5.4.0-1139.148"
},
{
"binary_name": "linux-tools-5.4.0-1139-gcp",
"binary_version": "5.4.0-1139.148"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-gcp",
"purl": "pkg:deb/ubuntu/linux-gcp@5.4.0-1139.148?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1139.148"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.3.0-1004.4",
"5.3.0-1009.10",
"5.3.0-1011.12",
"5.4.0-1005.5",
"5.4.0-1007.7",
"5.4.0-1008.8",
"5.4.0-1009.9",
"5.4.0-1011.11",
"5.4.0-1015.15",
"5.4.0-1018.18",
"5.4.0-1019.19",
"5.4.0-1021.21",
"5.4.0-1022.22",
"5.4.0-1024.24",
"5.4.0-1025.25",
"5.4.0-1028.29",
"5.4.0-1029.31",
"5.4.0-1030.32",
"5.4.0-1032.34",
"5.4.0-1033.35",
"5.4.0-1034.37",
"5.4.0-1036.39",
"5.4.0-1037.40",
"5.4.0-1038.41",
"5.4.0-1040.43",
"5.4.0-1041.44",
"5.4.0-1042.45",
"5.4.0-1043.46",
"5.4.0-1044.47",
"5.4.0-1046.49",
"5.4.0-1049.53",
"5.4.0-1051.55",
"5.4.0-1052.56",
"5.4.0-1053.57",
"5.4.0-1055.59",
"5.4.0-1056.60",
"5.4.0-1057.61",
"5.4.0-1058.62",
"5.4.0-1059.63",
"5.4.0-1060.64",
"5.4.0-1062.66",
"5.4.0-1063.67",
"5.4.0-1064.68",
"5.4.0-1065.69",
"5.4.0-1067.71",
"5.4.0-1068.72",
"5.4.0-1069.73",
"5.4.0-1072.77",
"5.4.0-1073.78",
"5.4.0-1075.80",
"5.4.0-1078.84",
"5.4.0-1080.87",
"5.4.0-1083.91",
"5.4.0-1084.92",
"5.4.0-1086.94",
"5.4.0-1087.95",
"5.4.0-1089.97",
"5.4.0-1090.98",
"5.4.0-1092.101",
"5.4.0-1093.102",
"5.4.0-1096.105",
"5.4.0-1097.106",
"5.4.0-1098.107",
"5.4.0-1100.109",
"5.4.0-1101.110",
"5.4.0-1102.111",
"5.4.0-1103.112",
"5.4.0-1104.113",
"5.4.0-1105.114",
"5.4.0-1106.115",
"5.4.0-1107.116",
"5.4.0-1108.117",
"5.4.0-1109.118",
"5.4.0-1110.119",
"5.4.0-1111.120",
"5.4.0-1112.121",
"5.4.0-1113.122",
"5.4.0-1115.124",
"5.4.0-1116.125",
"5.4.0-1117.126",
"5.4.0-1118.127",
"5.4.0-1120.129",
"5.4.0-1121.130",
"5.4.0-1122.131",
"5.4.0-1123.132",
"5.4.0-1124.133",
"5.4.0-1125.134",
"5.4.0-1126.135",
"5.4.0-1127.136",
"5.4.0-1128.137",
"5.4.0-1129.138",
"5.4.0-1130.139",
"5.4.0-1131.140",
"5.4.0-1132.141",
"5.4.0-1133.142",
"5.4.0-1134.143",
"5.4.0-1135.144",
"5.4.0-1136.145",
"5.4.0-1137.146",
"5.4.0-1138.147"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1071-gcp",
"binary_version": "5.15.0-1071.79~20.04.1"
},
{
"binary_name": "linux-gcp-5.15-headers-5.15.0-1071",
"binary_version": "5.15.0-1071.79~20.04.1"
},
{
"binary_name": "linux-gcp-5.15-tools-5.15.0-1071",
"binary_version": "5.15.0-1071.79~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1071-gcp",
"binary_version": "5.15.0-1071.79~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1071-gcp",
"binary_version": "5.15.0-1071.79~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1071-gcp",
"binary_version": "5.15.0-1071.79~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1071-gcp",
"binary_version": "5.15.0-1071.79~20.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-1071-gcp",
"binary_version": "5.15.0-1071.79~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1071-gcp",
"binary_version": "5.15.0-1071.79~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-gcp-5.15",
"purl": "pkg:deb/ubuntu/linux-gcp-5.15@5.15.0-1071.79~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1071.79~20.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1006.9~20.04.1",
"5.15.0-1012.17~20.04.1",
"5.15.0-1013.18~20.04.1",
"5.15.0-1016.21~20.04.1",
"5.15.0-1017.23~20.04.2",
"5.15.0-1018.24~20.04.1",
"5.15.0-1021.28~20.04.1",
"5.15.0-1022.29~20.04.1",
"5.15.0-1025.32~20.04.2",
"5.15.0-1026.33~20.04.1",
"5.15.0-1027.34~20.04.1",
"5.15.0-1029.36~20.04.1",
"5.15.0-1030.37~20.04.1",
"5.15.0-1031.38~20.04.1",
"5.15.0-1032.40~20.04.1",
"5.15.0-1033.41~20.04.1",
"5.15.0-1034.42~20.04.1",
"5.15.0-1035.43~20.04.1",
"5.15.0-1036.44~20.04.1",
"5.15.0-1037.45~20.04.1",
"5.15.0-1038.46~20.04.1",
"5.15.0-1039.47~20.04.1",
"5.15.0-1040.48~20.04.1",
"5.15.0-1041.49~20.04.1",
"5.15.0-1042.50~20.04.1",
"5.15.0-1044.52~20.04.1",
"5.15.0-1045.53~20.04.2",
"5.15.0-1046.54~20.04.1",
"5.15.0-1047.55~20.04.1",
"5.15.0-1048.56~20.04.1",
"5.15.0-1049.57~20.04.1",
"5.15.0-1051.59~20.04.1",
"5.15.0-1052.60~20.04.1",
"5.15.0-1053.61~20.04.1",
"5.15.0-1054.62~20.04.1",
"5.15.0-1055.63~20.04.1",
"5.15.0-1058.66~20.04.1",
"5.15.0-1059.67~20.04.1",
"5.15.0-1060.68~20.04.1",
"5.15.0-1062.70~20.04.1",
"5.15.0-1065.73~20.04.1",
"5.15.0-1066.74~20.04.1",
"5.15.0-1067.75~20.04.1",
"5.15.0-1068.76~20.04.1",
"5.15.0-1069.77~20.04.1",
"5.15.0-1070.78~20.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1102-gkeop",
"binary_version": "5.4.0-1102.106"
},
{
"binary_name": "linux-cloud-tools-5.4.0-1102-gkeop",
"binary_version": "5.4.0-1102.106"
},
{
"binary_name": "linux-gkeop-cloud-tools-5.4.0-1102",
"binary_version": "5.4.0-1102.106"
},
{
"binary_name": "linux-gkeop-headers-5.4.0-1102",
"binary_version": "5.4.0-1102.106"
},
{
"binary_name": "linux-gkeop-source-5.4.0",
"binary_version": "5.4.0-1102.106"
},
{
"binary_name": "linux-gkeop-tools-5.4.0-1102",
"binary_version": "5.4.0-1102.106"
},
{
"binary_name": "linux-headers-5.4.0-1102-gkeop",
"binary_version": "5.4.0-1102.106"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1102-gkeop",
"binary_version": "5.4.0-1102.106"
},
{
"binary_name": "linux-modules-5.4.0-1102-gkeop",
"binary_version": "5.4.0-1102.106"
},
{
"binary_name": "linux-modules-extra-5.4.0-1102-gkeop",
"binary_version": "5.4.0-1102.106"
},
{
"binary_name": "linux-tools-5.4.0-1102-gkeop",
"binary_version": "5.4.0-1102.106"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-gkeop",
"purl": "pkg:deb/ubuntu/linux-gkeop@5.4.0-1102.106?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1102.106"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1008.9",
"5.4.0-1009.10",
"5.4.0-1010.11",
"5.4.0-1011.12",
"5.4.0-1012.13",
"5.4.0-1013.14",
"5.4.0-1014.15",
"5.4.0-1015.16",
"5.4.0-1016.17",
"5.4.0-1018.19",
"5.4.0-1021.22",
"5.4.0-1022.23",
"5.4.0-1023.24",
"5.4.0-1024.25",
"5.4.0-1025.26",
"5.4.0-1026.27",
"5.4.0-1027.28",
"5.4.0-1029.30",
"5.4.0-1031.32",
"5.4.0-1032.33",
"5.4.0-1033.34",
"5.4.0-1034.35",
"5.4.0-1036.37",
"5.4.0-1037.38",
"5.4.0-1038.39",
"5.4.0-1039.40",
"5.4.0-1040.41",
"5.4.0-1043.44",
"5.4.0-1046.48",
"5.4.0-1048.51",
"5.4.0-1049.52",
"5.4.0-1051.54",
"5.4.0-1052.55",
"5.4.0-1053.56",
"5.4.0-1054.57",
"5.4.0-1056.60",
"5.4.0-1057.61",
"5.4.0-1060.64",
"5.4.0-1061.65",
"5.4.0-1062.66",
"5.4.0-1064.68",
"5.4.0-1065.69",
"5.4.0-1066.70",
"5.4.0-1067.71",
"5.4.0-1068.72",
"5.4.0-1069.73",
"5.4.0-1070.74",
"5.4.0-1071.75",
"5.4.0-1072.76",
"5.4.0-1073.77",
"5.4.0-1074.78",
"5.4.0-1075.79",
"5.4.0-1076.80",
"5.4.0-1077.81",
"5.4.0-1078.82",
"5.4.0-1079.83",
"5.4.0-1080.84",
"5.4.0-1081.85",
"5.4.0-1083.87",
"5.4.0-1084.88",
"5.4.0-1085.89",
"5.4.0-1086.90",
"5.4.0-1087.91",
"5.4.0-1088.92",
"5.4.0-1089.93",
"5.4.0-1090.94",
"5.4.0-1091.95",
"5.4.0-1092.96",
"5.4.0-1093.97",
"5.4.0-1094.98",
"5.4.0-1095.99",
"5.4.0-1096.100",
"5.4.0-1097.101",
"5.4.0-1098.102",
"5.4.0-1099.103",
"5.4.0-1100.104",
"5.4.0-1101.105"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1055-gkeop",
"binary_version": "5.15.0-1055.62~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1055-gkeop",
"binary_version": "5.15.0-1055.62~20.04.1"
},
{
"binary_name": "linux-gkeop-5.15-cloud-tools-5.15.0-1055",
"binary_version": "5.15.0-1055.62~20.04.1"
},
{
"binary_name": "linux-gkeop-5.15-headers-5.15.0-1055",
"binary_version": "5.15.0-1055.62~20.04.1"
},
{
"binary_name": "linux-gkeop-5.15-tools-5.15.0-1055",
"binary_version": "5.15.0-1055.62~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1055-gkeop",
"binary_version": "5.15.0-1055.62~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1055-gkeop",
"binary_version": "5.15.0-1055.62~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1055-gkeop",
"binary_version": "5.15.0-1055.62~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1055-gkeop",
"binary_version": "5.15.0-1055.62~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1055-gkeop",
"binary_version": "5.15.0-1055.62~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-gkeop-5.15",
"purl": "pkg:deb/ubuntu/linux-gkeop-5.15@5.15.0-1055.62~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1055.62~20.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1003.5~20.04.2",
"5.15.0-1005.7~20.04.1",
"5.15.0-1007.10~20.04.1",
"5.15.0-1008.12~20.04.1",
"5.15.0-1011.15~20.04.2",
"5.15.0-1012.16~20.04.1",
"5.15.0-1013.17~20.04.1",
"5.15.0-1015.19~20.04.1",
"5.15.0-1016.21~20.04.1",
"5.15.0-1017.22~20.04.1",
"5.15.0-1018.23~20.04.1",
"5.15.0-1019.24~20.04.1",
"5.15.0-1020.25~20.04.1",
"5.15.0-1021.26~20.04.1",
"5.15.0-1022.27~20.04.1",
"5.15.0-1023.28~20.04.1",
"5.15.0-1024.29~20.04.1",
"5.15.0-1025.30~20.04.1",
"5.15.0-1026.31~20.04.1",
"5.15.0-1027.32~20.04.1",
"5.15.0-1028.33~20.04.1",
"5.15.0-1030.35~20.04.1",
"5.15.0-1031.37~20.04.1",
"5.15.0-1032.38~20.04.1",
"5.15.0-1033.39~20.04.1",
"5.15.0-1034.40~20.04.1",
"5.15.0-1035.41~20.04.1",
"5.15.0-1036.42~20.04.1",
"5.15.0-1037.43~20.04.1",
"5.15.0-1038.44~20.04.1",
"5.15.0-1039.45~20.04.1",
"5.15.0-1040.46~20.04.1",
"5.15.0-1043.50~20.04.1",
"5.15.0-1044.51~20.04.1",
"5.15.0-1045.52~20.04.1",
"5.15.0-1046.53~20.04.1",
"5.15.0-1047.54~20.04.1",
"5.15.0-1048.55~20.04.1",
"5.15.0-1049.56~20.04.1",
"5.15.0-1050.57~20.04.1",
"5.15.0-1051.58~20.04.1",
"5.15.0-1052.59~20.04.1",
"5.15.0-1053.60~20.04.1",
"5.15.0-1054.61~20.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-125-generic",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.15.0-125-generic-64k",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.15.0-125-generic-lpae",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-125-generic",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-125-generic",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-125-generic-64k",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-125-generic-lpae",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-hwe-5.15-cloud-tools-5.15.0-125",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-hwe-5.15-cloud-tools-common",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-hwe-5.15-headers-5.15.0-125",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-hwe-5.15-source-5.15.0",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-hwe-5.15-tools-5.15.0-125",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-hwe-5.15-tools-common",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-hwe-5.15-tools-host",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-image-5.15.0-125-generic",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-image-5.15.0-125-generic-lpae",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-125-generic",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-125-generic-64k",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-125-generic",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-125-generic-64k",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-125-generic-lpae",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-125-generic",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-125-generic",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-125-generic",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-125-generic-64k",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-125-generic-lpae",
"binary_version": "5.15.0-125.135~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-hwe-5.15",
"purl": "pkg:deb/ubuntu/linux-hwe-5.15@5.15.0-125.135~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-125.135~20.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-33.34~20.04.1",
"5.15.0-41.44~20.04.1",
"5.15.0-43.46~20.04.1",
"5.15.0-46.49~20.04.1",
"5.15.0-48.54~20.04.1",
"5.15.0-50.56~20.04.1",
"5.15.0-52.58~20.04.1",
"5.15.0-53.59~20.04.1",
"5.15.0-56.62~20.04.1",
"5.15.0-57.63~20.04.1",
"5.15.0-58.64~20.04.1",
"5.15.0-60.66~20.04.1",
"5.15.0-67.74~20.04.1",
"5.15.0-69.76~20.04.1",
"5.15.0-70.77~20.04.1",
"5.15.0-71.78~20.04.1",
"5.15.0-72.79~20.04.1",
"5.15.0-73.80~20.04.1",
"5.15.0-75.82~20.04.1",
"5.15.0-76.83~20.04.1",
"5.15.0-78.85~20.04.1",
"5.15.0-79.86~20.04.2",
"5.15.0-82.91~20.04.1",
"5.15.0-83.92~20.04.1",
"5.15.0-84.93~20.04.1",
"5.15.0-86.96~20.04.1",
"5.15.0-87.97~20.04.1",
"5.15.0-88.98~20.04.1",
"5.15.0-89.99~20.04.1",
"5.15.0-91.101~20.04.1",
"5.15.0-92.102~20.04.1",
"5.15.0-94.104~20.04.1",
"5.15.0-97.107~20.04.1",
"5.15.0-100.110~20.04.1",
"5.15.0-101.111~20.04.1",
"5.15.0-102.112~20.04.1",
"5.15.0-105.115~20.04.1",
"5.15.0-106.116~20.04.1",
"5.15.0-107.117~20.04.1",
"5.15.0-113.123~20.04.1",
"5.15.0-116.126~20.04.1",
"5.15.0-117.127~20.04.1",
"5.15.0-118.128~20.04.1",
"5.15.0-119.129~20.04.1",
"5.15.0-121.131~20.04.1",
"5.15.0-122.132~20.04.1",
"5.15.0-124.134~20.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1082-ibm",
"binary_version": "5.4.0-1082.87"
},
{
"binary_name": "linux-headers-5.4.0-1082-ibm",
"binary_version": "5.4.0-1082.87"
},
{
"binary_name": "linux-ibm-cloud-tools-common",
"binary_version": "5.4.0-1082.87"
},
{
"binary_name": "linux-ibm-headers-5.4.0-1082",
"binary_version": "5.4.0-1082.87"
},
{
"binary_name": "linux-ibm-source-5.4.0",
"binary_version": "5.4.0-1082.87"
},
{
"binary_name": "linux-ibm-tools-5.4.0-1082",
"binary_version": "5.4.0-1082.87"
},
{
"binary_name": "linux-ibm-tools-common",
"binary_version": "5.4.0-1082.87"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1082-ibm",
"binary_version": "5.4.0-1082.87"
},
{
"binary_name": "linux-modules-5.4.0-1082-ibm",
"binary_version": "5.4.0-1082.87"
},
{
"binary_name": "linux-modules-extra-5.4.0-1082-ibm",
"binary_version": "5.4.0-1082.87"
},
{
"binary_name": "linux-tools-5.4.0-1082-ibm",
"binary_version": "5.4.0-1082.87"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-ibm",
"purl": "pkg:deb/ubuntu/linux-ibm@5.4.0-1082.87?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1082.87"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1003.4",
"5.4.0-1004.5",
"5.4.0-1005.6",
"5.4.0-1006.7",
"5.4.0-1007.8",
"5.4.0-1008.9",
"5.4.0-1010.11",
"5.4.0-1012.13",
"5.4.0-1013.14",
"5.4.0-1014.15",
"5.4.0-1015.16",
"5.4.0-1017.19",
"5.4.0-1018.20",
"5.4.0-1019.21",
"5.4.0-1020.22",
"5.4.0-1021.23",
"5.4.0-1023.25",
"5.4.0-1026.29",
"5.4.0-1028.32",
"5.4.0-1029.33",
"5.4.0-1031.35",
"5.4.0-1032.36",
"5.4.0-1033.37",
"5.4.0-1034.38",
"5.4.0-1036.41",
"5.4.0-1037.42",
"5.4.0-1040.45",
"5.4.0-1041.46",
"5.4.0-1042.47",
"5.4.0-1044.49",
"5.4.0-1045.50",
"5.4.0-1046.51",
"5.4.0-1047.52",
"5.4.0-1048.53",
"5.4.0-1049.54",
"5.4.0-1050.55",
"5.4.0-1051.56",
"5.4.0-1052.57",
"5.4.0-1053.58",
"5.4.0-1054.59",
"5.4.0-1056.61",
"5.4.0-1057.62",
"5.4.0-1058.63",
"5.4.0-1059.64",
"5.4.0-1060.65",
"5.4.0-1061.66",
"5.4.0-1063.68",
"5.4.0-1064.69",
"5.4.0-1065.70",
"5.4.0-1066.71",
"5.4.0-1067.72",
"5.4.0-1068.73",
"5.4.0-1069.74",
"5.4.0-1070.75",
"5.4.0-1071.76",
"5.4.0-1072.77",
"5.4.0-1073.78",
"5.4.0-1074.79",
"5.4.0-1075.80",
"5.4.0-1076.81",
"5.4.0-1077.82",
"5.4.0-1078.83",
"5.4.0-1079.84",
"5.4.0-1080.85",
"5.4.0-1081.86"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1065-ibm",
"binary_version": "5.15.0-1065.68~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1065-ibm",
"binary_version": "5.15.0-1065.68~20.04.1"
},
{
"binary_name": "linux-ibm-5.15-headers-5.15.0-1065",
"binary_version": "5.15.0-1065.68~20.04.1"
},
{
"binary_name": "linux-ibm-5.15-source-5.15.0",
"binary_version": "5.15.0-1065.68~20.04.1"
},
{
"binary_name": "linux-ibm-5.15-tools-5.15.0-1065",
"binary_version": "5.15.0-1065.68~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1065-ibm",
"binary_version": "5.15.0-1065.68~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1065-ibm",
"binary_version": "5.15.0-1065.68~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1065-ibm",
"binary_version": "5.15.0-1065.68~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1065-ibm",
"binary_version": "5.15.0-1065.68~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-ibm-5.15",
"purl": "pkg:deb/ubuntu/linux-ibm-5.15@5.15.0-1065.68~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1065.68~20.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1033.36~20.04.1",
"5.15.0-1034.37~20.04.1",
"5.15.0-1035.38~20.04.1",
"5.15.0-1036.39~20.04.1",
"5.15.0-1037.40~20.04.1",
"5.15.0-1038.41~20.04.1",
"5.15.0-1040.43~20.04.1",
"5.15.0-1041.44~20.04.1",
"5.15.0-1042.45~20.04.1",
"5.15.0-1043.46~20.04.1",
"5.15.0-1044.47~20.04.1",
"5.15.0-1045.48~20.04.1",
"5.15.0-1046.49~20.04.1",
"5.15.0-1047.50~20.04.1",
"5.15.0-1048.51~20.04.1",
"5.15.0-1049.52~20.04.1",
"5.15.0-1050.53~20.04.1",
"5.15.0-1053.56~20.04.1",
"5.15.0-1054.57~20.04.1",
"5.15.0-1055.58~20.04.1",
"5.15.0-1057.60~20.04.1",
"5.15.0-1058.61~20.04.1",
"5.15.0-1059.62~20.04.1",
"5.15.0-1060.63~20.04.1",
"5.15.0-1061.64~20.04.1",
"5.15.0-1062.65~20.04.1",
"5.15.0-1063.66~20.04.1",
"5.15.0-1064.67~20.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-intel-iotg-5.15-cloud-tools-5.15.0-1067",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-intel-iotg-5.15-cloud-tools-common",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-intel-iotg-5.15-headers-5.15.0-1067",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-intel-iotg-5.15-tools-5.15.0-1067",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-intel-iotg-5.15-tools-common",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-intel-iotg-5.15-tools-host",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-intel-iotg-5.15",
"purl": "pkg:deb/ubuntu/linux-intel-iotg-5.15@5.15.0-1067.73~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1067.73~20.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1003.5~20.04.1",
"5.15.0-1008.11~20.04.1",
"5.15.0-1010.14~20.04.1",
"5.15.0-1015.20~20.04.2",
"5.15.0-1016.21~20.04.1",
"5.15.0-1017.22~20.04.1",
"5.15.0-1018.23~20.04.1",
"5.15.0-1021.26~20.04.1",
"5.15.0-1023.28~20.04.1",
"5.15.0-1025.30~20.04.1",
"5.15.0-1026.31~20.04.1",
"5.15.0-1027.32~20.04.1",
"5.15.0-1030.35~20.04.1",
"5.15.0-1031.36~20.04.1",
"5.15.0-1033.38~20.04.1",
"5.15.0-1034.39~20.04.1",
"5.15.0-1036.41~20.04.1",
"5.15.0-1037.42~20.04.1",
"5.15.0-1038.43~20.04.1",
"5.15.0-1040.46~20.04.1",
"5.15.0-1043.49~20.04.1",
"5.15.0-1045.51~20.04.1",
"5.15.0-1046.52~20.04.1",
"5.15.0-1048.54~20.04.1",
"5.15.0-1049.55~20.04.1",
"5.15.0-1050.56~20.04.1",
"5.15.0-1051.57~20.04.1",
"5.15.0-1052.58~20.04.1",
"5.15.0-1055.61~20.04.1",
"5.15.0-1058.64~20.04.1",
"5.15.0-1059.65~20.04.1",
"5.15.0-1060.66~20.04.1",
"5.15.0-1061.67~20.04.1",
"5.15.0-1062.68~20.04.1",
"5.15.0-1063.69~20.04.1",
"5.15.0-1064.70~20.04.1",
"5.15.0-1065.71~20.04.1",
"5.15.0-1066.72~20.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1044-iot",
"binary_version": "5.4.0-1044.45"
},
{
"binary_name": "linux-headers-5.4.0-1044-iot",
"binary_version": "5.4.0-1044.45"
},
{
"binary_name": "linux-image-5.4.0-1044-iot",
"binary_version": "5.4.0-1044.45"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1044-iot",
"binary_version": "5.4.0-1044.45"
},
{
"binary_name": "linux-iot-headers-5.4.0-1044",
"binary_version": "5.4.0-1044.45"
},
{
"binary_name": "linux-iot-tools-5.4.0-1044",
"binary_version": "5.4.0-1044.45"
},
{
"binary_name": "linux-modules-5.4.0-1044-iot",
"binary_version": "5.4.0-1044.45"
},
{
"binary_name": "linux-tools-5.4.0-1044-iot",
"binary_version": "5.4.0-1044.45"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-iot",
"purl": "pkg:deb/ubuntu/linux-iot@5.4.0-1044.45?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1044.45"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1001.3",
"5.4.0-1004.6",
"5.4.0-1005.7",
"5.4.0-1006.8",
"5.4.0-1009.11",
"5.4.0-1010.12",
"5.4.0-1011.13",
"5.4.0-1012.14",
"5.4.0-1013.15",
"5.4.0-1014.16",
"5.4.0-1017.18",
"5.4.0-1018.19",
"5.4.0-1019.20",
"5.4.0-1021.22",
"5.4.0-1022.23",
"5.4.0-1023.24",
"5.4.0-1024.25",
"5.4.0-1025.26",
"5.4.0-1026.27",
"5.4.0-1028.29",
"5.4.0-1029.30",
"5.4.0-1030.31",
"5.4.0-1031.32",
"5.4.0-1032.33",
"5.4.0-1033.34",
"5.4.0-1034.35",
"5.4.0-1035.36",
"5.4.0-1036.37",
"5.4.0-1037.38",
"5.4.0-1038.39",
"5.4.0-1039.40",
"5.4.0-1040.41",
"5.4.0-1041.42",
"5.4.0-1042.43",
"5.4.0-1043.44"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1123-kvm",
"binary_version": "5.4.0-1123.131"
},
{
"binary_name": "linux-headers-5.4.0-1123-kvm",
"binary_version": "5.4.0-1123.131"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1123-kvm",
"binary_version": "5.4.0-1123.131"
},
{
"binary_name": "linux-kvm-headers-5.4.0-1123",
"binary_version": "5.4.0-1123.131"
},
{
"binary_name": "linux-kvm-tools-5.4.0-1123",
"binary_version": "5.4.0-1123.131"
},
{
"binary_name": "linux-modules-5.4.0-1123-kvm",
"binary_version": "5.4.0-1123.131"
},
{
"binary_name": "linux-tools-5.4.0-1123-kvm",
"binary_version": "5.4.0-1123.131"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-kvm",
"purl": "pkg:deb/ubuntu/linux-kvm@5.4.0-1123.131?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1123.131"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.3.0-1003.3",
"5.3.0-1008.9",
"5.3.0-1009.10",
"5.4.0-1004.4",
"5.4.0-1006.6",
"5.4.0-1007.7",
"5.4.0-1008.8",
"5.4.0-1009.9",
"5.4.0-1011.11",
"5.4.0-1015.15",
"5.4.0-1018.18",
"5.4.0-1020.20",
"5.4.0-1021.21",
"5.4.0-1023.23",
"5.4.0-1024.24",
"5.4.0-1026.27",
"5.4.0-1028.29",
"5.4.0-1030.31",
"5.4.0-1031.32",
"5.4.0-1032.33",
"5.4.0-1033.34",
"5.4.0-1034.35",
"5.4.0-1036.37",
"5.4.0-1037.38",
"5.4.0-1038.39",
"5.4.0-1039.40",
"5.4.0-1040.41",
"5.4.0-1041.42",
"5.4.0-1044.46",
"5.4.0-1045.47",
"5.4.0-1046.48",
"5.4.0-1047.49",
"5.4.0-1048.50",
"5.4.0-1049.51",
"5.4.0-1050.52",
"5.4.0-1051.53",
"5.4.0-1053.55",
"5.4.0-1054.56",
"5.4.0-1055.57",
"5.4.0-1056.58",
"5.4.0-1058.61",
"5.4.0-1059.62",
"5.4.0-1061.64",
"5.4.0-1062.65",
"5.4.0-1063.66",
"5.4.0-1065.68",
"5.4.0-1068.72",
"5.4.0-1070.75",
"5.4.0-1071.76",
"5.4.0-1073.78",
"5.4.0-1074.79",
"5.4.0-1075.80",
"5.4.0-1076.81",
"5.4.0-1078.84",
"5.4.0-1079.85",
"5.4.0-1082.88",
"5.4.0-1083.89",
"5.4.0-1084.90",
"5.4.0-1086.92",
"5.4.0-1087.93",
"5.4.0-1088.94",
"5.4.0-1089.95",
"5.4.0-1090.96",
"5.4.0-1091.97",
"5.4.0-1092.98",
"5.4.0-1093.99",
"5.4.0-1094.100",
"5.4.0-1095.101",
"5.4.0-1096.102",
"5.4.0-1097.103",
"5.4.0-1098.104",
"5.4.0-1099.105",
"5.4.0-1100.106",
"5.4.0-1101.107",
"5.4.0-1102.108",
"5.4.0-1103.110",
"5.4.0-1104.111",
"5.4.0-1105.112",
"5.4.0-1106.113",
"5.4.0-1107.114",
"5.4.0-1108.115",
"5.4.0-1109.116",
"5.4.0-1110.117",
"5.4.0-1111.118",
"5.4.0-1112.119",
"5.4.0-1113.120",
"5.4.0-1114.121",
"5.4.0-1115.122",
"5.4.0-1116.123",
"5.4.0-1117.124",
"5.4.0-1118.125",
"5.4.0-1119.127",
"5.4.0-1120.128",
"5.4.0-1121.129",
"5.4.0-1122.130"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-125-lowlatency",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.15.0-125-lowlatency-64k",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-125-lowlatency",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-125-lowlatency",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-125-lowlatency-64k",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-125-lowlatency",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-125-lowlatency-64k",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-5.15-cloud-tools-5.15.0-125",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-5.15-cloud-tools-common",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-5.15-headers-5.15.0-125",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-5.15-tools-5.15.0-125",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-5.15-tools-common",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-5.15-tools-host",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-125-lowlatency",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-125-lowlatency-64k",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-125-lowlatency",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-125-lowlatency",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-125-lowlatency-64k",
"binary_version": "5.15.0-125.135~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-lowlatency-hwe-5.15",
"purl": "pkg:deb/ubuntu/linux-lowlatency-hwe-5.15@5.15.0-125.135~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-125.135~20.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-33.34~20.04.1",
"5.15.0-42.45~20.04.1",
"5.15.0-43.46~20.04.1",
"5.15.0-46.49~20.04.1",
"5.15.0-48.54~20.04.1",
"5.15.0-50.56~20.04.1",
"5.15.0-52.58~20.04.1",
"5.15.0-53.59~20.04.1",
"5.15.0-56.62~20.04.1",
"5.15.0-58.64~20.04.1",
"5.15.0-60.66~20.04.1",
"5.15.0-67.74~20.04.1",
"5.15.0-69.76~20.04.1",
"5.15.0-70.77~20.04.1",
"5.15.0-71.78~20.04.1",
"5.15.0-72.79~20.04.1",
"5.15.0-73.80~20.04.1",
"5.15.0-75.82~20.04.1",
"5.15.0-76.83~20.04.1",
"5.15.0-78.85~20.04.1",
"5.15.0-79.88~20.04.1",
"5.15.0-82.91~20.04.1",
"5.15.0-83.92~20.04.1",
"5.15.0-84.93~20.04.1",
"5.15.0-86.95~20.04.1",
"5.15.0-87.96~20.04.1",
"5.15.0-88.98~20.04.1",
"5.15.0-89.99~20.04.1",
"5.15.0-91.101~20.04.1",
"5.15.0-92.102~20.04.1",
"5.15.0-94.104~20.04.1",
"5.15.0-97.107~20.04.1",
"5.15.0-100.110~20.04.1",
"5.15.0-101.111~20.04.1",
"5.15.0-102.112~20.04.1",
"5.15.0-105.115~20.04.1",
"5.15.0-106.116~20.04.1",
"5.15.0-107.117~20.04.1",
"5.15.0-110.120~20.04.1",
"5.15.0-113.123~20.04.1",
"5.15.0-116.126~20.04.1",
"5.15.0-117.127~20.04.1",
"5.15.0-118.128~20.04.1",
"5.15.0-119.129~20.04.1",
"5.15.0-121.131~20.04.1",
"5.15.0-122.132~20.04.1",
"5.15.0-124.134~20.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1032-nvidia-tegra",
"binary_version": "5.15.0-1032.32~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.15.0-1032-nvidia-tegra-rt",
"binary_version": "5.15.0-1032.32~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1032-nvidia-tegra",
"binary_version": "5.15.0-1032.32~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1032-nvidia-tegra-rt",
"binary_version": "5.15.0-1032.32~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1032-nvidia-tegra",
"binary_version": "5.15.0-1032.32~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1032-nvidia-tegra-rt",
"binary_version": "5.15.0-1032.32~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1032-nvidia-tegra",
"binary_version": "5.15.0-1032.32~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1032-nvidia-tegra-rt",
"binary_version": "5.15.0-1032.32~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1032-nvidia-tegra",
"binary_version": "5.15.0-1032.32~20.04.1"
},
{
"binary_name": "linux-nvidia-tegra-5.15-headers-5.15.0-1032",
"binary_version": "5.15.0-1032.32~20.04.1"
},
{
"binary_name": "linux-nvidia-tegra-5.15-tools-5.15.0-1032",
"binary_version": "5.15.0-1032.32~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1032-nvidia-tegra",
"binary_version": "5.15.0-1032.32~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1032-nvidia-tegra-rt",
"binary_version": "5.15.0-1032.32~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-nvidia-tegra-5.15",
"purl": "pkg:deb/ubuntu/linux-nvidia-tegra-5.15@5.15.0-1032.32~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1032.32~20.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1009.9~20.04.1",
"5.15.0-1010.10~20.04.1",
"5.15.0-1012.12~20.04.1",
"5.15.0-1014.14~20.04.1",
"5.15.0-1015.15~20.04.1",
"5.15.0-1016.16~20.04.1",
"5.15.0-1017.17~20.04.1",
"5.15.0-1018.18~20.04.1",
"5.15.0-1019.19~20.04.1",
"5.15.0-1020.20~20.04.1",
"5.15.0-1022.22~20.04.1",
"5.15.0-1025.25~20.04.1",
"5.15.0-1027.27~20.04.1",
"5.15.0-1030.30~20.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1134-oracle",
"binary_version": "5.4.0-1134.143"
},
{
"binary_name": "linux-headers-5.4.0-1134-oracle",
"binary_version": "5.4.0-1134.143"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1134-oracle",
"binary_version": "5.4.0-1134.143"
},
{
"binary_name": "linux-modules-5.4.0-1134-oracle",
"binary_version": "5.4.0-1134.143"
},
{
"binary_name": "linux-modules-extra-5.4.0-1134-oracle",
"binary_version": "5.4.0-1134.143"
},
{
"binary_name": "linux-oracle-headers-5.4.0-1134",
"binary_version": "5.4.0-1134.143"
},
{
"binary_name": "linux-oracle-tools-5.4.0-1134",
"binary_version": "5.4.0-1134.143"
},
{
"binary_name": "linux-tools-5.4.0-1134-oracle",
"binary_version": "5.4.0-1134.143"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-oracle",
"purl": "pkg:deb/ubuntu/linux-oracle@5.4.0-1134.143?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1134.143"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.3.0-1002.2",
"5.3.0-1007.8",
"5.3.0-1008.9",
"5.4.0-1005.5",
"5.4.0-1007.7",
"5.4.0-1008.8",
"5.4.0-1009.9",
"5.4.0-1011.11",
"5.4.0-1015.15",
"5.4.0-1018.18",
"5.4.0-1019.19",
"5.4.0-1021.21",
"5.4.0-1022.22",
"5.4.0-1024.24",
"5.4.0-1025.25",
"5.4.0-1028.29",
"5.4.0-1029.31",
"5.4.0-1030.32",
"5.4.0-1032.34",
"5.4.0-1034.36",
"5.4.0-1035.38",
"5.4.0-1037.40",
"5.4.0-1038.41",
"5.4.0-1039.42",
"5.4.0-1041.44",
"5.4.0-1042.45",
"5.4.0-1043.46",
"5.4.0-1045.49",
"5.4.0-1046.50",
"5.4.0-1048.52",
"5.4.0-1049.53",
"5.4.0-1052.56",
"5.4.0-1053.57",
"5.4.0-1054.58",
"5.4.0-1055.59",
"5.4.0-1056.60",
"5.4.0-1057.61",
"5.4.0-1058.62",
"5.4.0-1059.63",
"5.4.0-1061.65",
"5.4.0-1062.66",
"5.4.0-1063.67",
"5.4.0-1064.68",
"5.4.0-1066.71",
"5.4.0-1067.72",
"5.4.0-1069.75",
"5.4.0-1070.76",
"5.4.0-1071.77",
"5.4.0-1073.79",
"5.4.0-1076.83",
"5.4.0-1078.86",
"5.4.0-1079.87",
"5.4.0-1081.89",
"5.4.0-1082.90",
"5.4.0-1083.91",
"5.4.0-1084.92",
"5.4.0-1086.95",
"5.4.0-1087.96",
"5.4.0-1090.99",
"5.4.0-1091.100",
"5.4.0-1092.101",
"5.4.0-1093.102",
"5.4.0-1094.103",
"5.4.0-1097.106",
"5.4.0-1098.107",
"5.4.0-1099.108",
"5.4.0-1100.109",
"5.4.0-1101.110",
"5.4.0-1102.111",
"5.4.0-1103.112",
"5.4.0-1104.113",
"5.4.0-1105.114",
"5.4.0-1106.115",
"5.4.0-1107.116",
"5.4.0-1108.117",
"5.4.0-1109.118",
"5.4.0-1110.119",
"5.4.0-1111.120",
"5.4.0-1112.121",
"5.4.0-1113.122",
"5.4.0-1115.124",
"5.4.0-1116.125",
"5.4.0-1117.126",
"5.4.0-1118.127",
"5.4.0-1119.128",
"5.4.0-1120.129",
"5.4.0-1121.130",
"5.4.0-1122.131",
"5.4.0-1123.132",
"5.4.0-1124.133",
"5.4.0-1125.134",
"5.4.0-1126.135",
"5.4.0-1127.136",
"5.4.0-1129.138",
"5.4.0-1130.139",
"5.4.0-1131.140",
"5.4.0-1132.141",
"5.4.0-1133.142"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1070-oracle",
"binary_version": "5.15.0-1070.76~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1070-oracle",
"binary_version": "5.15.0-1070.76~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1070-oracle",
"binary_version": "5.15.0-1070.76~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1070-oracle",
"binary_version": "5.15.0-1070.76~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1070-oracle",
"binary_version": "5.15.0-1070.76~20.04.1"
},
{
"binary_name": "linux-oracle-5.15-headers-5.15.0-1070",
"binary_version": "5.15.0-1070.76~20.04.1"
},
{
"binary_name": "linux-oracle-5.15-tools-5.15.0-1070",
"binary_version": "5.15.0-1070.76~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1070-oracle",
"binary_version": "5.15.0-1070.76~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-oracle-5.15",
"purl": "pkg:deb/ubuntu/linux-oracle-5.15@5.15.0-1070.76~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1070.76~20.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1007.9~20.04.1",
"5.15.0-1013.17~20.04.1",
"5.15.0-1016.20~20.04.1",
"5.15.0-1017.22~20.04.1",
"5.15.0-1018.23~20.04.1",
"5.15.0-1019.24~20.04.1",
"5.15.0-1021.27~20.04.1",
"5.15.0-1022.28~20.04.1",
"5.15.0-1025.31~20.04.2",
"5.15.0-1027.33~20.04.1",
"5.15.0-1029.35~20.04.1",
"5.15.0-1030.36~20.04.1",
"5.15.0-1032.38~20.04.1",
"5.15.0-1033.39~20.04.1",
"5.15.0-1034.40~20.04.1",
"5.15.0-1035.41~20.04.1",
"5.15.0-1036.42~20.04.1",
"5.15.0-1037.43~20.04.1",
"5.15.0-1038.44~20.04.1",
"5.15.0-1039.45~20.04.1",
"5.15.0-1040.46~20.04.1",
"5.15.0-1041.47~20.04.1",
"5.15.0-1042.48~20.04.1",
"5.15.0-1044.50~20.04.1",
"5.15.0-1045.51~20.04.1",
"5.15.0-1046.52~20.04.1",
"5.15.0-1047.53~20.04.1",
"5.15.0-1048.54~20.04.1",
"5.15.0-1049.55~20.04.1",
"5.15.0-1050.56~20.04.1",
"5.15.0-1051.57~20.04.1",
"5.15.0-1052.58~20.04.1",
"5.15.0-1053.59~20.04.1",
"5.15.0-1054.60~20.04.1",
"5.15.0-1055.61~20.04.1",
"5.15.0-1058.64~20.04.1",
"5.15.0-1059.65~20.04.1",
"5.15.0-1061.67~20.04.1",
"5.15.0-1062.68~20.04.1",
"5.15.0-1063.69~20.04.1",
"5.15.0-1065.71~20.04.1",
"5.15.0-1066.72~20.04.1",
"5.15.0-1067.73~20.04.1",
"5.15.0-1068.74~20.04.1",
"5.15.0-1069.75~20.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1119-raspi",
"binary_version": "5.4.0-1119.131"
},
{
"binary_name": "linux-headers-5.4.0-1119-raspi",
"binary_version": "5.4.0-1119.131"
},
{
"binary_name": "linux-image-5.4.0-1119-raspi",
"binary_version": "5.4.0-1119.131"
},
{
"binary_name": "linux-modules-5.4.0-1119-raspi",
"binary_version": "5.4.0-1119.131"
},
{
"binary_name": "linux-raspi-headers-5.4.0-1119",
"binary_version": "5.4.0-1119.131"
},
{
"binary_name": "linux-raspi-tools-5.4.0-1119",
"binary_version": "5.4.0-1119.131"
},
{
"binary_name": "linux-tools-5.4.0-1119-raspi",
"binary_version": "5.4.0-1119.131"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-raspi",
"purl": "pkg:deb/ubuntu/linux-raspi@5.4.0-1119.131?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1119.131"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1007.7",
"5.4.0-1008.8",
"5.4.0-1011.11",
"5.4.0-1012.12",
"5.4.0-1013.13",
"5.4.0-1015.15",
"5.4.0-1016.17",
"5.4.0-1018.20",
"5.4.0-1019.21",
"5.4.0-1021.24",
"5.4.0-1022.25",
"5.4.0-1023.26",
"5.4.0-1025.28",
"5.4.0-1026.29",
"5.4.0-1028.31",
"5.4.0-1029.32",
"5.4.0-1030.33",
"5.4.0-1032.35",
"5.4.0-1033.36",
"5.4.0-1034.37",
"5.4.0-1035.38",
"5.4.0-1036.39",
"5.4.0-1038.41",
"5.4.0-1041.45",
"5.4.0-1042.46",
"5.4.0-1043.47",
"5.4.0-1044.48",
"5.4.0-1045.49",
"5.4.0-1046.50",
"5.4.0-1047.52",
"5.4.0-1048.53",
"5.4.0-1050.56",
"5.4.0-1052.58",
"5.4.0-1053.60",
"5.4.0-1055.62",
"5.4.0-1056.63",
"5.4.0-1058.65",
"5.4.0-1059.67",
"5.4.0-1060.68",
"5.4.0-1062.70",
"5.4.0-1065.75",
"5.4.0-1066.76",
"5.4.0-1068.78",
"5.4.0-1069.79",
"5.4.0-1070.80",
"5.4.0-1071.81",
"5.4.0-1073.84",
"5.4.0-1074.85",
"5.4.0-1077.88",
"5.4.0-1078.89",
"5.4.0-1079.90",
"5.4.0-1080.91",
"5.4.0-1081.92",
"5.4.0-1082.93",
"5.4.0-1083.94",
"5.4.0-1084.95",
"5.4.0-1085.96",
"5.4.0-1086.97",
"5.4.0-1088.99",
"5.4.0-1089.100",
"5.4.0-1090.101",
"5.4.0-1091.102",
"5.4.0-1092.103",
"5.4.0-1093.104",
"5.4.0-1094.105",
"5.4.0-1095.106",
"5.4.0-1096.107",
"5.4.0-1097.109",
"5.4.0-1098.110",
"5.4.0-1100.112",
"5.4.0-1101.113",
"5.4.0-1102.114",
"5.4.0-1103.115",
"5.4.0-1104.116",
"5.4.0-1105.117",
"5.4.0-1106.118",
"5.4.0-1107.119",
"5.4.0-1108.120",
"5.4.0-1109.121",
"5.4.0-1110.122",
"5.4.0-1111.123",
"5.4.0-1112.124",
"5.4.0-1113.125",
"5.4.0-1114.126",
"5.4.0-1115.127",
"5.4.0-1116.128",
"5.4.0-1117.129",
"5.4.0-1118.130"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1068-generic",
"binary_version": "5.15.0-1068.72~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1068-generic",
"binary_version": "5.15.0-1068.72~20.04.1"
},
{
"binary_name": "linux-image-5.15.0-1068-generic",
"binary_version": "5.15.0-1068.72~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1068-generic",
"binary_version": "5.15.0-1068.72~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1068-generic",
"binary_version": "5.15.0-1068.72~20.04.1"
},
{
"binary_name": "linux-riscv-5.15-headers-5.15.0-1068",
"binary_version": "5.15.0-1068.72~20.04.1"
},
{
"binary_name": "linux-riscv-5.15-tools-5.15.0-1068",
"binary_version": "5.15.0-1068.72~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1068-generic",
"binary_version": "5.15.0-1068.72~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-riscv-5.15",
"purl": "pkg:deb/ubuntu/linux-riscv-5.15@5.15.0-1068.72~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1068.72~20.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1015.17~20.04.1",
"5.15.0-1017.19~20.04.1",
"5.15.0-1018.21~20.04.1",
"5.15.0-1019.22~20.04.1",
"5.15.0-1022.26~20.04.1",
"5.15.0-1023.27~20.04.1",
"5.15.0-1026.30~20.04.2",
"5.15.0-1027.31~20.04.1",
"5.15.0-1028.32~20.04.1",
"5.15.0-1029.33~20.04.1",
"5.15.0-1030.34~20.04.1",
"5.15.0-1031.35~20.04.1",
"5.15.0-1032.36~20.04.1",
"5.15.0-1033.37~20.04.1",
"5.15.0-1034.38~20.04.1",
"5.15.0-1035.39~20.04.1",
"5.15.0-1036.40~20.04.2",
"5.15.0-1037.41~20.04.2",
"5.15.0-1038.42~20.04.2",
"5.15.0-1039.43~20.04.2",
"5.15.0-1040.44~20.04.3",
"5.15.0-1041.45~20.04.1",
"5.15.0-1043.47~20.04.1",
"5.15.0-1044.48~20.04.1",
"5.15.0-1045.49~20.04.1",
"5.15.0-1046.50~20.04.1",
"5.15.0-1047.51~20.04.1",
"5.15.0-1048.52~20.04.1",
"5.15.0-1049.53~20.04.2",
"5.15.0-1050.54~20.04.1",
"5.15.0-1051.55~20.04.1",
"5.15.0-1052.56~20.04.1",
"5.15.0-1053.57~20.04.1",
"5.15.0-1056.60~20.04.1",
"5.15.0-1057.61~20.04.1",
"5.15.0-1058.62~20.04.1",
"5.15.0-1059.63~20.04.1",
"5.15.0-1060.64~20.04.1",
"5.15.0-1061.65~20.04.1",
"5.15.0-1062.66~20.04.1",
"5.15.0-1063.67~20.04.1",
"5.15.0-1064.68~20.04.1",
"5.15.0-1065.69~20.04.1",
"5.15.0-1066.70~20.04.1",
"5.15.0-1067.71~20.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1054-xilinx-zynqmp",
"binary_version": "5.4.0-1054.58"
},
{
"binary_name": "linux-headers-5.4.0-1054-xilinx-zynqmp",
"binary_version": "5.4.0-1054.58"
},
{
"binary_name": "linux-image-5.4.0-1054-xilinx-zynqmp",
"binary_version": "5.4.0-1054.58"
},
{
"binary_name": "linux-modules-5.4.0-1054-xilinx-zynqmp",
"binary_version": "5.4.0-1054.58"
},
{
"binary_name": "linux-tools-5.4.0-1054-xilinx-zynqmp",
"binary_version": "5.4.0-1054.58"
},
{
"binary_name": "linux-xilinx-zynqmp-headers-5.4.0-1054",
"binary_version": "5.4.0-1054.58"
},
{
"binary_name": "linux-xilinx-zynqmp-tools-5.4.0-1054",
"binary_version": "5.4.0-1054.58"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-xilinx-zynqmp",
"purl": "pkg:deb/ubuntu/linux-xilinx-zynqmp@5.4.0-1054.58?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1054.58"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1020.24",
"5.4.0-1021.25",
"5.4.0-1022.26",
"5.4.0-1023.27",
"5.4.0-1024.28",
"5.4.0-1025.29",
"5.4.0-1026.30",
"5.4.0-1027.31",
"5.4.0-1028.32",
"5.4.0-1029.33",
"5.4.0-1030.34",
"5.4.0-1031.35",
"5.4.0-1032.36",
"5.4.0-1033.37",
"5.4.0-1034.38",
"5.4.0-1035.39",
"5.4.0-1036.40",
"5.4.0-1037.41",
"5.4.0-1038.42",
"5.4.0-1039.43",
"5.4.0-1040.44",
"5.4.0-1041.45",
"5.4.0-1042.46",
"5.4.0-1043.47",
"5.4.0-1044.48",
"5.4.0-1045.49",
"5.4.0-1046.50",
"5.4.0-1047.51",
"5.4.0-1048.52",
"5.4.0-1049.53",
"5.4.0-1050.54",
"5.4.0-1051.55",
"5.4.0-1052.56",
"5.4.0-1053.57"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-aws-5.11-cloud-tools-5.11.0-1028",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-aws-5.11-headers-5.11.0-1028",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-aws-5.11-tools-5.11.0-1028",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.11.0-1028-aws",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.11.0-1028-aws",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-headers-5.11.0-1028-aws",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.11.0-1028-aws",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-modules-5.11.0-1028-aws",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.11.0-1028-aws",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-tools-5.11.0-1028-aws",
"binary_version": "5.11.0-1028.31~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-aws-5.11",
"purl": "pkg:deb/ubuntu/linux-aws-5.11@5.11.0-1028.31~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.11.0-1009.9~20.04.2",
"5.11.0-1014.15~20.04.1",
"5.11.0-1016.17~20.04.1",
"5.11.0-1017.18~20.04.1",
"5.11.0-1019.20~20.04.1",
"5.11.0-1020.21~20.04.2",
"5.11.0-1021.22~20.04.2",
"5.11.0-1022.23~20.04.1",
"5.11.0-1023.24~20.04.1",
"5.11.0-1025.27~20.04.1",
"5.11.0-1027.30~20.04.1",
"5.11.0-1028.31~20.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-aws-5.13-cloud-tools-5.13.0-1031",
"binary_version": "5.13.0-1031.35~20.04.1"
},
{
"binary_name": "linux-aws-5.13-headers-5.13.0-1031",
"binary_version": "5.13.0-1031.35~20.04.1"
},
{
"binary_name": "linux-aws-5.13-tools-5.13.0-1031",
"binary_version": "5.13.0-1031.35~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.13.0-1031-aws",
"binary_version": "5.13.0-1031.35~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.13.0-1031-aws",
"binary_version": "5.13.0-1031.35~20.04.1"
},
{
"binary_name": "linux-headers-5.13.0-1031-aws",
"binary_version": "5.13.0-1031.35~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.13.0-1031-aws",
"binary_version": "5.13.0-1031.35~20.04.1"
},
{
"binary_name": "linux-modules-5.13.0-1031-aws",
"binary_version": "5.13.0-1031.35~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.13.0-1031-aws",
"binary_version": "5.13.0-1031.35~20.04.1"
},
{
"binary_name": "linux-tools-5.13.0-1031-aws",
"binary_version": "5.13.0-1031.35~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-aws-5.13",
"purl": "pkg:deb/ubuntu/linux-aws-5.13@5.13.0-1031.35~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-1008.9~20.04.2",
"5.13.0-1011.12~20.04.1",
"5.13.0-1012.13~20.04.1",
"5.13.0-1014.15~20.04.1",
"5.13.0-1017.19~20.04.1",
"5.13.0-1019.21~20.04.1",
"5.13.0-1021.23~20.04.2",
"5.13.0-1022.24~20.04.1",
"5.13.0-1023.25~20.04.1",
"5.13.0-1025.27~20.04.1",
"5.13.0-1028.31~20.04.1",
"5.13.0-1029.32~20.04.1",
"5.13.0-1031.35~20.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-aws-5.8-cloud-tools-5.8.0-1042",
"binary_version": "5.8.0-1042.44~20.04.1"
},
{
"binary_name": "linux-aws-5.8-headers-5.8.0-1042",
"binary_version": "5.8.0-1042.44~20.04.1"
},
{
"binary_name": "linux-aws-5.8-tools-5.8.0-1042",
"binary_version": "5.8.0-1042.44~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.8.0-1042-aws",
"binary_version": "5.8.0-1042.44~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.8.0-1042-aws",
"binary_version": "5.8.0-1042.44~20.04.1"
},
{
"binary_name": "linux-headers-5.8.0-1042-aws",
"binary_version": "5.8.0-1042.44~20.04.1"
},
{
"binary_name": "linux-image-5.8.0-1042-aws",
"binary_version": "5.8.0-1042.44~20.04.1"
},
{
"binary_name": "linux-modules-5.8.0-1042-aws",
"binary_version": "5.8.0-1042.44~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.8.0-1042-aws",
"binary_version": "5.8.0-1042.44~20.04.1"
},
{
"binary_name": "linux-tools-5.8.0-1042-aws",
"binary_version": "5.8.0-1042.44~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-aws-5.8",
"purl": "pkg:deb/ubuntu/linux-aws-5.8@5.8.0-1042.44~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.8.0-1035.37~20.04.1",
"5.8.0-1038.40~20.04.1",
"5.8.0-1041.43~20.04.1",
"5.8.0-1042.44~20.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-azure-5.11-cloud-tools-5.11.0-1028",
"binary_version": "5.11.0-1028.31~20.04.2"
},
{
"binary_name": "linux-azure-5.11-headers-5.11.0-1028",
"binary_version": "5.11.0-1028.31~20.04.2"
},
{
"binary_name": "linux-azure-5.11-tools-5.11.0-1028",
"binary_version": "5.11.0-1028.31~20.04.2"
},
{
"binary_name": "linux-buildinfo-5.11.0-1028-azure",
"binary_version": "5.11.0-1028.31~20.04.2"
},
{
"binary_name": "linux-cloud-tools-5.11.0-1028-azure",
"binary_version": "5.11.0-1028.31~20.04.2"
},
{
"binary_name": "linux-headers-5.11.0-1028-azure",
"binary_version": "5.11.0-1028.31~20.04.2"
},
{
"binary_name": "linux-image-unsigned-5.11.0-1028-azure",
"binary_version": "5.11.0-1028.31~20.04.2"
},
{
"binary_name": "linux-modules-5.11.0-1028-azure",
"binary_version": "5.11.0-1028.31~20.04.2"
},
{
"binary_name": "linux-modules-extra-5.11.0-1028-azure",
"binary_version": "5.11.0-1028.31~20.04.2"
},
{
"binary_name": "linux-tools-5.11.0-1028-azure",
"binary_version": "5.11.0-1028.31~20.04.2"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-azure-5.11",
"purl": "pkg:deb/ubuntu/linux-azure-5.11@5.11.0-1028.31~20.04.2?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.11.0-1007.7~20.04.2",
"5.11.0-1012.13~20.04.1",
"5.11.0-1013.14~20.04.1",
"5.11.0-1015.16~20.04.1",
"5.11.0-1017.18~20.04.1",
"5.11.0-1019.20~20.04.1",
"5.11.0-1020.21~20.04.1",
"5.11.0-1021.22~20.04.1",
"5.11.0-1022.23~20.04.1",
"5.11.0-1023.24~20.04.1",
"5.11.0-1025.27~20.04.1",
"5.11.0-1027.30~20.04.1",
"5.11.0-1028.31~20.04.2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-azure-5.13-cloud-tools-5.13.0-1031",
"binary_version": "5.13.0-1031.37~20.04.1"
},
{
"binary_name": "linux-azure-5.13-headers-5.13.0-1031",
"binary_version": "5.13.0-1031.37~20.04.1"
},
{
"binary_name": "linux-azure-5.13-tools-5.13.0-1031",
"binary_version": "5.13.0-1031.37~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.13.0-1031-azure",
"binary_version": "5.13.0-1031.37~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.13.0-1031-azure",
"binary_version": "5.13.0-1031.37~20.04.1"
},
{
"binary_name": "linux-headers-5.13.0-1031-azure",
"binary_version": "5.13.0-1031.37~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.13.0-1031-azure",
"binary_version": "5.13.0-1031.37~20.04.1"
},
{
"binary_name": "linux-modules-5.13.0-1031-azure",
"binary_version": "5.13.0-1031.37~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.13.0-1031-azure",
"binary_version": "5.13.0-1031.37~20.04.1"
},
{
"binary_name": "linux-tools-5.13.0-1031-azure",
"binary_version": "5.13.0-1031.37~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-azure-5.13",
"purl": "pkg:deb/ubuntu/linux-azure-5.13@5.13.0-1031.37~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-1009.10~20.04.2",
"5.13.0-1012.14~20.04.1",
"5.13.0-1013.15~20.04.1",
"5.13.0-1014.16~20.04.1",
"5.13.0-1017.19~20.04.1",
"5.13.0-1021.24~20.04.1",
"5.13.0-1022.26~20.04.1",
"5.13.0-1023.27~20.04.1",
"5.13.0-1025.29~20.04.1",
"5.13.0-1028.33~20.04.1",
"5.13.0-1029.34~20.04.1",
"5.13.0-1031.37~20.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-azure-5.8-cloud-tools-5.8.0-1043",
"binary_version": "5.8.0-1043.46~20.04.1"
},
{
"binary_name": "linux-azure-5.8-headers-5.8.0-1043",
"binary_version": "5.8.0-1043.46~20.04.1"
},
{
"binary_name": "linux-azure-5.8-tools-5.8.0-1043",
"binary_version": "5.8.0-1043.46~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.8.0-1043-azure",
"binary_version": "5.8.0-1043.46~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.8.0-1043-azure",
"binary_version": "5.8.0-1043.46~20.04.1"
},
{
"binary_name": "linux-headers-5.8.0-1043-azure",
"binary_version": "5.8.0-1043.46~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.8.0-1043-azure",
"binary_version": "5.8.0-1043.46~20.04.1"
},
{
"binary_name": "linux-modules-5.8.0-1043-azure",
"binary_version": "5.8.0-1043.46~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.8.0-1043-azure",
"binary_version": "5.8.0-1043.46~20.04.1"
},
{
"binary_name": "linux-tools-5.8.0-1043-azure",
"binary_version": "5.8.0-1043.46~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-azure-5.8",
"purl": "pkg:deb/ubuntu/linux-azure-5.8@5.8.0-1043.46~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.8.0-1033.35~20.04.1",
"5.8.0-1036.38~20.04.1",
"5.8.0-1039.42~20.04.1",
"5.8.0-1040.43~20.04.1",
"5.8.0-1041.44~20.04.1",
"5.8.0-1042.45~20.04.1",
"5.8.0-1043.46~20.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-image-unsigned-5.4.0-1103-azure-fde",
"binary_version": "5.4.0-1103.109+cvm1.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-azure-fde",
"purl": "pkg:deb/ubuntu/linux-azure-fde@5.4.0-1103.109+cvm1.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1063.66+cvm2.2",
"5.4.0-1063.66+cvm3.2",
"5.4.0-1064.67+cvm1.1",
"5.4.0-1065.68+cvm2.1",
"5.4.0-1067.70+cvm1.1",
"5.4.0-1068.71+cvm1.1",
"5.4.0-1069.72+cvm1.1",
"5.4.0-1070.73+cvm1.1",
"5.4.0-1072.75+cvm1.1",
"5.4.0-1073.76+cvm1.1",
"5.4.0-1074.77+cvm1.1",
"5.4.0-1076.79+cvm1.1",
"5.4.0-1078.81+cvm1.1",
"5.4.0-1080.83+cvm1.1",
"5.4.0-1083.87+cvm1.1",
"5.4.0-1085.90+cvm1.1",
"5.4.0-1085.90+cvm2.1",
"5.4.0-1086.91+cvm1.1",
"5.4.0-1089.94+cvm1.2",
"5.4.0-1090.95+cvm1.1",
"5.4.0-1091.96+cvm1.1",
"5.4.0-1092.97+cvm1.1",
"5.4.0-1095.101+cvm1.1",
"5.4.0-1098.104+cvm1.1",
"5.4.0-1100.106+cvm1.1",
"5.4.0-1103.109+cvm1.1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-azure-fde-5.15-cloud-tools-5.15.0-1114",
"binary_version": "5.15.0-1114.123~20.04.1"
},
{
"binary_name": "linux-azure-fde-5.15-headers-5.15.0-1114",
"binary_version": "5.15.0-1114.123~20.04.1"
},
{
"binary_name": "linux-azure-fde-5.15-tools-5.15.0-1114",
"binary_version": "5.15.0-1114.123~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.15.0-1114-azure-fde",
"binary_version": "5.15.0-1114.123~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1114-azure-fde",
"binary_version": "5.15.0-1114.123~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1114-azure-fde",
"binary_version": "5.15.0-1114.123~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1114-azure-fde",
"binary_version": "5.15.0-1114.123~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1114-azure-fde",
"binary_version": "5.15.0-1114.123~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1114-azure-fde",
"binary_version": "5.15.0-1114.123~20.04.1"
},
{
"binary_name": "linux-modules-involflt-5.15.0-1114-azure-fde",
"binary_version": "5.15.0-1114.123~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1114-azure-fde",
"binary_version": "5.15.0-1114.123~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:20.04:LTS",
"name": "linux-azure-fde-5.15",
"purl": "pkg:deb/ubuntu/linux-azure-fde-5.15@5.15.0-1114.123~20.04.1?arch=source\u0026distro=esm-infra/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1114.123~20.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1019.24~20.04.1.1",
"5.15.0-1020.25~20.04.1.1",
"5.15.0-1021.26~20.04.1.1",
"5.15.0-1029.36~20.04.1.1",
"5.15.0-1030.37~20.04.1.1",
"5.15.0-1031.38~20.04.1.1",
"5.15.0-1033.40~20.04.1.1",
"5.15.0-1034.41~20.04.1.2",
"5.15.0-1035.42~20.04.1.1",
"5.15.0-1036.43~20.04.1.1",
"5.15.0-1037.44~20.04.1.1",
"5.15.0-1038.45~20.04.1.1",
"5.15.0-1039.46~20.04.1.1",
"5.15.0-1040.47~20.04.1.1",
"5.15.0-1041.48~20.04.1.1",
"5.15.0-1042.49~20.04.1.1",
"5.15.0-1043.50~20.04.1.1",
"5.15.0-1046.53~20.04.1.1",
"5.15.0-1047.54~20.04.1.1",
"5.15.0-1049.56~20.04.1.1",
"5.15.0-1050.57~20.04.1.1",
"5.15.0-1051.59~20.04.1.1",
"5.15.0-1052.60~20.04.1.1",
"5.15.0-1053.61~20.04.1.1",
"5.15.0-1054.62~20.04.1.1",
"5.15.0-1056.64~20.04.1.1",
"5.15.0-1057.65~20.04.1.1",
"5.15.0-1058.66~20.04.2.1",
"5.15.0-1059.67~20.04.1.1",
"5.15.0-1060.69~20.04.1.1",
"5.15.0-1061.70~20.04.1.1",
"5.15.0-1063.72~20.04.1.1",
"5.15.0-1064.73~20.04.1.1",
"5.15.0-1065.74~20.04.1.1",
"5.15.0-1067.76~20.04.1.1",
"5.15.0-1068.77~20.04.1.1",
"5.15.0-1070.79~20.04.1.1",
"5.15.0-1071.80~20.04.1.1",
"5.15.0-1072.81~20.04.1.1",
"5.15.0-1073.82~20.04.1.1",
"5.15.0-1074.83~20.04.1.1",
"5.15.0-1076.85~20.04.1.1",
"5.15.0-1078.87~20.04.1.1",
"5.15.0-1081.90~20.04.1.1",
"5.15.0-1082.91~20.04.1.1",
"5.15.0-1086.95~20.04.1.1",
"5.15.0-1087.96~20.04.1.1",
"5.15.0-1088.97~20.04.1.1",
"5.15.0-1089.98~20.04.1.1",
"5.15.0-1091.100~20.04.1.1",
"5.15.0-1094.103~20.04.1.1",
"5.15.0-1096.105~20.04.1.1",
"5.15.0-1097.106~20.04.1.1",
"5.15.0-1098.107~20.04.1.1",
"5.15.0-1102.111~20.04.1.1",
"5.15.0-1103.112~20.04.1.1",
"5.15.0-1111.120~20.04.1.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.11.0-1029-gcp",
"binary_version": "5.11.0-1029.33~20.04.3"
},
{
"binary_name": "linux-gcp-5.11-headers-5.11.0-1029",
"binary_version": "5.11.0-1029.33~20.04.3"
},
{
"binary_name": "linux-gcp-5.11-tools-5.11.0-1029",
"binary_version": "5.11.0-1029.33~20.04.3"
},
{
"binary_name": "linux-headers-5.11.0-1029-gcp",
"binary_version": "5.11.0-1029.33~20.04.3"
},
{
"binary_name": "linux-image-unsigned-5.11.0-1029-gcp",
"binary_version": "5.11.0-1029.33~20.04.3"
},
{
"binary_name": "linux-modules-5.11.0-1029-gcp",
"binary_version": "5.11.0-1029.33~20.04.3"
},
{
"binary_name": "linux-modules-extra-5.11.0-1029-gcp",
"binary_version": "5.11.0-1029.33~20.04.3"
},
{
"binary_name": "linux-tools-5.11.0-1029-gcp",
"binary_version": "5.11.0-1029.33~20.04.3"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-gcp-5.11",
"purl": "pkg:deb/ubuntu/linux-gcp-5.11@5.11.0-1029.33~20.04.3?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.11.0-1009.10~20.04.1",
"5.11.0-1014.16~20.04.1",
"5.11.0-1017.19~20.04.1",
"5.11.0-1018.20~20.04.2",
"5.11.0-1020.22~20.04.1",
"5.11.0-1021.23~20.04.1",
"5.11.0-1022.24~20.04.1",
"5.11.0-1023.25~20.04.1",
"5.11.0-1024.26~20.04.1",
"5.11.0-1026.29~20.04.1",
"5.11.0-1028.32~20.04.1",
"5.11.0-1029.33~20.04.3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.13.0-1033-gcp",
"binary_version": "5.13.0-1033.40~20.04.1"
},
{
"binary_name": "linux-gcp-5.13-headers-5.13.0-1033",
"binary_version": "5.13.0-1033.40~20.04.1"
},
{
"binary_name": "linux-gcp-5.13-tools-5.13.0-1033",
"binary_version": "5.13.0-1033.40~20.04.1"
},
{
"binary_name": "linux-headers-5.13.0-1033-gcp",
"binary_version": "5.13.0-1033.40~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.13.0-1033-gcp",
"binary_version": "5.13.0-1033.40~20.04.1"
},
{
"binary_name": "linux-modules-5.13.0-1033-gcp",
"binary_version": "5.13.0-1033.40~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.13.0-1033-gcp",
"binary_version": "5.13.0-1033.40~20.04.1"
},
{
"binary_name": "linux-tools-5.13.0-1033-gcp",
"binary_version": "5.13.0-1033.40~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-gcp-5.13",
"purl": "pkg:deb/ubuntu/linux-gcp-5.13@5.13.0-1033.40~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-1008.9~20.04.3",
"5.13.0-1012.15~20.04.1",
"5.13.0-1013.16~20.04.1",
"5.13.0-1015.18~20.04.1",
"5.13.0-1019.23~20.04.1",
"5.13.0-1021.25~20.04.1",
"5.13.0-1023.28~20.04.1",
"5.13.0-1024.29~20.04.1",
"5.13.0-1025.30~20.04.1",
"5.13.0-1027.32~20.04.1",
"5.13.0-1030.36~20.04.1",
"5.13.0-1031.37~20.04.1",
"5.13.0-1033.40~20.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.8.0-1039-gcp",
"binary_version": "5.8.0-1039.41"
},
{
"binary_name": "linux-gcp-5.8-headers-5.8.0-1039",
"binary_version": "5.8.0-1039.41"
},
{
"binary_name": "linux-gcp-5.8-tools-5.8.0-1039",
"binary_version": "5.8.0-1039.41"
},
{
"binary_name": "linux-headers-5.8.0-1039-gcp",
"binary_version": "5.8.0-1039.41"
},
{
"binary_name": "linux-image-unsigned-5.8.0-1039-gcp",
"binary_version": "5.8.0-1039.41"
},
{
"binary_name": "linux-modules-5.8.0-1039-gcp",
"binary_version": "5.8.0-1039.41"
},
{
"binary_name": "linux-modules-extra-5.8.0-1039-gcp",
"binary_version": "5.8.0-1039.41"
},
{
"binary_name": "linux-tools-5.8.0-1039-gcp",
"binary_version": "5.8.0-1039.41"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-gcp-5.8",
"purl": "pkg:deb/ubuntu/linux-gcp-5.8@5.8.0-1039.41?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.8.0-1032.34~20.04.1",
"5.8.0-1035.37~20.04.1",
"5.8.0-1038.40~20.04.1",
"5.8.0-1039.41"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1105-gke",
"binary_version": "5.4.0-1105.112"
},
{
"binary_name": "linux-gke-headers-5.4.0-1105",
"binary_version": "5.4.0-1105.112"
},
{
"binary_name": "linux-gke-tools-5.4.0-1105",
"binary_version": "5.4.0-1105.112"
},
{
"binary_name": "linux-headers-5.4.0-1105-gke",
"binary_version": "5.4.0-1105.112"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1105-gke",
"binary_version": "5.4.0-1105.112"
},
{
"binary_name": "linux-modules-5.4.0-1105-gke",
"binary_version": "5.4.0-1105.112"
},
{
"binary_name": "linux-modules-extra-5.4.0-1105-gke",
"binary_version": "5.4.0-1105.112"
},
{
"binary_name": "linux-tools-5.4.0-1105-gke",
"binary_version": "5.4.0-1105.112"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-gke",
"purl": "pkg:deb/ubuntu/linux-gke@5.4.0-1105.112?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1033.35",
"5.4.0-1035.37",
"5.4.0-1036.38",
"5.4.0-1037.39",
"5.4.0-1039.41",
"5.4.0-1041.43",
"5.4.0-1042.44",
"5.4.0-1043.45",
"5.4.0-1044.46",
"5.4.0-1046.48",
"5.4.0-1049.52",
"5.4.0-1051.54",
"5.4.0-1052.55",
"5.4.0-1053.56",
"5.4.0-1054.57",
"5.4.0-1055.58",
"5.4.0-1056.59",
"5.4.0-1057.60",
"5.4.0-1059.62",
"5.4.0-1061.64",
"5.4.0-1062.65",
"5.4.0-1063.66",
"5.4.0-1065.68",
"5.4.0-1066.69",
"5.4.0-1067.70",
"5.4.0-1068.71",
"5.4.0-1071.76",
"5.4.0-1072.77",
"5.4.0-1074.79",
"5.4.0-1076.82",
"5.4.0-1078.84",
"5.4.0-1080.86",
"5.4.0-1081.87",
"5.4.0-1083.89",
"5.4.0-1084.90",
"5.4.0-1086.93",
"5.4.0-1087.94",
"5.4.0-1090.97",
"5.4.0-1091.98",
"5.4.0-1094.101",
"5.4.0-1095.102",
"5.4.0-1096.103",
"5.4.0-1097.104",
"5.4.0-1098.105",
"5.4.0-1099.106",
"5.4.0-1100.107",
"5.4.0-1101.108",
"5.4.0-1102.109",
"5.4.0-1103.110",
"5.4.0-1104.111",
"5.4.0-1105.112"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1039-gke",
"binary_version": "5.15.0-1039.44~20.04.1"
},
{
"binary_name": "linux-gke-5.15-headers-5.15.0-1039",
"binary_version": "5.15.0-1039.44~20.04.1"
},
{
"binary_name": "linux-gke-5.15-tools-5.15.0-1039",
"binary_version": "5.15.0-1039.44~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1039-gke",
"binary_version": "5.15.0-1039.44~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1039-gke",
"binary_version": "5.15.0-1039.44~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1039-gke",
"binary_version": "5.15.0-1039.44~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1039-gke",
"binary_version": "5.15.0-1039.44~20.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-1039-gke",
"binary_version": "5.15.0-1039.44~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1039-gke",
"binary_version": "5.15.0-1039.44~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-gke-5.15",
"purl": "pkg:deb/ubuntu/linux-gke-5.15@5.15.0-1039.44~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1011.14~20.04.1",
"5.15.0-1014.17~20.04.1",
"5.15.0-1015.18~20.04.1",
"5.15.0-1016.19~20.04.1",
"5.15.0-1019.23~20.04.1",
"5.15.0-1020.25~20.04.1",
"5.15.0-1023.28~20.04.2",
"5.15.0-1027.32~20.04.1",
"5.15.0-1028.33~20.04.1",
"5.15.0-1029.34~20.04.1",
"5.15.0-1031.36~20.04.1",
"5.15.0-1032.37~20.04.1",
"5.15.0-1033.38~20.04.1",
"5.15.0-1034.39~20.04.1",
"5.15.0-1036.41~20.04.1",
"5.15.0-1037.42~20.04.1",
"5.15.0-1038.43~20.04.1",
"5.15.0-1039.44~20.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "block-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "block-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "block-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "crypto-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "crypto-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "crypto-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "dasd-extra-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "dasd-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fat-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fat-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fat-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fb-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "firewire-core-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "floppy-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fs-core-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fs-core-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fs-core-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "input-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "input-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "input-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "ipmi-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "ipmi-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "ipmi-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "kernel-image-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "kernel-image-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "kernel-image-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.11.0-46-generic",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.11.0-46-generic-64k",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.11.0-46-generic-lpae",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.11.0-46-lowlatency",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.11.0-46-generic",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.11.0-46-lowlatency",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-headers-5.11.0-46-generic",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-headers-5.11.0-46-generic-64k",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-headers-5.11.0-46-generic-lpae",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-headers-5.11.0-46-lowlatency",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-cloud-tools-5.11.0-46",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-cloud-tools-common",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-headers-5.11.0-46",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-source-5.11.0",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-tools-5.11.0-46",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-tools-common",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-tools-host",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-udebs-generic",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-udebs-generic-64k",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-udebs-generic-lpae",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-image-5.11.0-46-generic",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-image-5.11.0-46-generic-lpae",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.11.0-46-generic",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.11.0-46-generic-64k",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.11.0-46-lowlatency",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-modules-5.11.0-46-generic",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-modules-5.11.0-46-generic-64k",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-modules-5.11.0-46-generic-lpae",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-modules-5.11.0-46-lowlatency",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.11.0-46-generic",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-tools-5.11.0-46-generic",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-tools-5.11.0-46-generic-64k",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-tools-5.11.0-46-generic-lpae",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-tools-5.11.0-46-lowlatency",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "md-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "md-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "md-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "message-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "message-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "mouse-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "mouse-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "mouse-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "multipath-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "multipath-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "multipath-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nfs-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nfs-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nfs-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-pcmcia-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "parport-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "parport-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "parport-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "pata-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "pcmcia-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "pcmcia-storage-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "plip-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "plip-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "plip-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "ppp-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "ppp-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "ppp-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "sata-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "sata-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "sata-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "scsi-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "scsi-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "scsi-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "serial-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "storage-core-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "storage-core-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "storage-core-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "usb-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "usb-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "usb-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "virtio-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "virtio-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "vlan-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "vlan-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "vlan-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-hwe-5.11",
"purl": "pkg:deb/ubuntu/linux-hwe-5.11@5.11.0-46.51~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.11.0-22.23~20.04.1",
"5.11.0-25.27~20.04.1",
"5.11.0-27.29~20.04.1",
"5.11.0-34.36~20.04.1",
"5.11.0-36.40~20.04.1",
"5.11.0-37.41~20.04.2",
"5.11.0-38.42~20.04.1",
"5.11.0-40.44~20.04.2",
"5.11.0-41.45~20.04.1",
"5.11.0-43.47~20.04.2",
"5.11.0-44.48~20.04.2",
"5.11.0-46.51~20.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "block-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "block-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "block-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "crypto-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "crypto-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "crypto-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "dasd-extra-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "dasd-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fat-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fat-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fat-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fb-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "firewire-core-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "floppy-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fs-core-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fs-core-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fs-core-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "input-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "input-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "input-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "ipmi-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "ipmi-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "ipmi-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "kernel-image-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "kernel-image-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "kernel-image-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.13.0-52-generic",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.13.0-52-generic-64k",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.13.0-52-generic-lpae",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.13.0-52-lowlatency",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.13.0-52-generic",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.13.0-52-lowlatency",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-headers-5.13.0-52-generic",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-headers-5.13.0-52-generic-64k",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-headers-5.13.0-52-generic-lpae",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-headers-5.13.0-52-lowlatency",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-cloud-tools-5.13.0-52",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-cloud-tools-common",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-headers-5.13.0-52",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-source-5.13.0",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-tools-5.13.0-52",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-tools-common",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-tools-host",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-udebs-generic",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-udebs-generic-64k",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-udebs-generic-lpae",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-image-5.13.0-52-generic",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-image-5.13.0-52-generic-lpae",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.13.0-52-generic",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.13.0-52-generic-64k",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.13.0-52-lowlatency",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-modules-5.13.0-52-generic",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-modules-5.13.0-52-generic-64k",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-modules-5.13.0-52-generic-lpae",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-modules-5.13.0-52-lowlatency",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.13.0-52-generic",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-tools-5.13.0-52-generic",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-tools-5.13.0-52-generic-64k",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-tools-5.13.0-52-generic-lpae",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-tools-5.13.0-52-lowlatency",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "md-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "md-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "md-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "message-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "message-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "mouse-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "mouse-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "mouse-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "multipath-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "multipath-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "multipath-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nfs-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nfs-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nfs-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-pcmcia-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "parport-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "parport-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "parport-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "pata-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "pcmcia-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "pcmcia-storage-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "plip-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "plip-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "plip-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "ppp-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "ppp-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "ppp-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "sata-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "sata-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "sata-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "scsi-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "scsi-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "scsi-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "serial-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "storage-core-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "storage-core-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "storage-core-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "usb-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "usb-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "usb-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "virtio-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "virtio-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "vlan-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "vlan-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "vlan-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-hwe-5.13",
"purl": "pkg:deb/ubuntu/linux-hwe-5.13@5.13.0-52.59~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-21.21~20.04.1",
"5.13.0-22.22~20.04.1",
"5.13.0-23.23~20.04.2",
"5.13.0-25.26~20.04.1",
"5.13.0-27.29~20.04.1",
"5.13.0-28.31~20.04.1",
"5.13.0-30.33~20.04.1",
"5.13.0-35.40~20.04.1",
"5.13.0-37.42~20.04.1",
"5.13.0-39.44~20.04.1",
"5.13.0-40.45~20.04.1",
"5.13.0-41.46~20.04.1",
"5.13.0-44.49~20.04.1",
"5.13.0-48.54~20.04.1",
"5.13.0-51.58~20.04.1",
"5.13.0-52.59~20.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "block-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "block-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "block-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "crypto-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "crypto-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "crypto-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "dasd-extra-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "dasd-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fat-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fat-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fat-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fb-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "firewire-core-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "floppy-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fs-core-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fs-core-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fs-core-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "input-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "input-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "input-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "ipmi-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "ipmi-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "ipmi-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "kernel-image-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "kernel-image-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "kernel-image-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.8.0-63-generic",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.8.0-63-generic-64k",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.8.0-63-generic-lpae",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.8.0-63-lowlatency",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.8.0-63-generic",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.8.0-63-lowlatency",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-headers-5.8.0-63-generic",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-headers-5.8.0-63-generic-64k",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-headers-5.8.0-63-generic-lpae",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-headers-5.8.0-63-lowlatency",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-cloud-tools-5.8.0-63",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-cloud-tools-common",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-headers-5.8.0-63",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-source-5.8.0",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-tools-5.8.0-63",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-tools-common",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-tools-host",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-udebs-generic",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-udebs-generic-64k",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-udebs-generic-lpae",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-image-5.8.0-63-generic",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-image-5.8.0-63-generic-lpae",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.8.0-63-generic",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.8.0-63-generic-64k",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.8.0-63-lowlatency",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-modules-5.8.0-63-generic",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-modules-5.8.0-63-generic-64k",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-modules-5.8.0-63-generic-lpae",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-modules-5.8.0-63-lowlatency",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.8.0-63-generic",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-tools-5.8.0-63-generic",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-tools-5.8.0-63-generic-64k",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-tools-5.8.0-63-generic-lpae",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-tools-5.8.0-63-lowlatency",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "md-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "md-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "md-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "message-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "message-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "mouse-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "mouse-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "mouse-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "multipath-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "multipath-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "multipath-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nfs-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nfs-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nfs-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-pcmcia-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "parport-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "parport-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "parport-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "pata-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "pcmcia-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "pcmcia-storage-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "plip-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "plip-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "plip-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "ppp-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "ppp-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "ppp-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "sata-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "sata-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "sata-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "scsi-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "scsi-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "scsi-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "serial-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "storage-core-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "storage-core-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "storage-core-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "usb-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "usb-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "usb-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "virtio-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "virtio-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "vlan-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "vlan-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "vlan-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-hwe-5.8",
"purl": "pkg:deb/ubuntu/linux-hwe-5.8@5.8.0-63.71~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.8.0-23.24~20.04.1",
"5.8.0-25.26~20.04.1",
"5.8.0-28.30~20.04.1",
"5.8.0-29.31~20.04.1",
"5.8.0-31.33~20.04.1",
"5.8.0-33.36~20.04.1",
"5.8.0-34.37~20.04.2",
"5.8.0-36.40~20.04.1",
"5.8.0-38.43~20.04.1",
"5.8.0-40.45~20.04.1",
"5.8.0-41.46~20.04.1",
"5.8.0-43.49~20.04.1",
"5.8.0-44.50~20.04.1",
"5.8.0-45.51~20.04.1",
"5.8.0-48.54~20.04.1",
"5.8.0-49.55~20.04.1",
"5.8.0-50.56~20.04.1",
"5.8.0-53.60~20.04.1",
"5.8.0-55.62~20.04.1",
"5.8.0-59.66~20.04.1",
"5.8.0-63.71~20.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.13.0-1017-intel",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-cloud-tools-5.13.0-1017-intel",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-headers-5.13.0-1017-intel",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-image-unsigned-5.13.0-1017-intel",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-intel-5.13-cloud-tools-5.13.0-1017",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-intel-5.13-cloud-tools-common",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-intel-5.13-headers-5.13.0-1017",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-intel-5.13-source-5.13.0",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-intel-5.13-tools-5.13.0-1017",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-intel-5.13-tools-common",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-intel-5.13-tools-host",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-modules-5.13.0-1017-intel",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-modules-extra-5.13.0-1017-intel",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-tools-5.13.0-1017-intel",
"binary_version": "5.13.0-1017.19"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-intel-5.13",
"purl": "pkg:deb/ubuntu/linux-intel-5.13@5.13.0-1017.19?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-1007.7",
"5.13.0-1008.8",
"5.13.0-1009.9",
"5.13.0-1010.10",
"5.13.0-1011.11",
"5.13.0-1014.15",
"5.13.0-1017.19"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.10.0-1057-oem",
"binary_version": "5.10.0-1057.61"
},
{
"binary_name": "linux-headers-5.10.0-1057-oem",
"binary_version": "5.10.0-1057.61"
},
{
"binary_name": "linux-image-unsigned-5.10.0-1057-oem",
"binary_version": "5.10.0-1057.61"
},
{
"binary_name": "linux-modules-5.10.0-1057-oem",
"binary_version": "5.10.0-1057.61"
},
{
"binary_name": "linux-oem-5.10-headers-5.10.0-1057",
"binary_version": "5.10.0-1057.61"
},
{
"binary_name": "linux-oem-5.10-tools-5.10.0-1057",
"binary_version": "5.10.0-1057.61"
},
{
"binary_name": "linux-oem-5.10-tools-host",
"binary_version": "5.10.0-1057.61"
},
{
"binary_name": "linux-tools-5.10.0-1057-oem",
"binary_version": "5.10.0-1057.61"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-oem-5.10",
"purl": "pkg:deb/ubuntu/linux-oem-5.10@5.10.0-1057.61?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.10.0-1008.9",
"5.10.0-1011.12",
"5.10.0-1013.14",
"5.10.0-1014.15",
"5.10.0-1016.17",
"5.10.0-1017.18",
"5.10.0-1019.20",
"5.10.0-1021.22",
"5.10.0-1022.23",
"5.10.0-1023.24",
"5.10.0-1025.26",
"5.10.0-1026.27",
"5.10.0-1029.30",
"5.10.0-1032.33",
"5.10.0-1033.34",
"5.10.0-1034.35",
"5.10.0-1038.40",
"5.10.0-1044.46",
"5.10.0-1045.47",
"5.10.0-1049.51",
"5.10.0-1050.52",
"5.10.0-1051.53",
"5.10.0-1052.54",
"5.10.0-1053.55",
"5.10.0-1055.58",
"5.10.0-1057.61"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.13.0-1029-oem",
"binary_version": "5.13.0-1029.36"
},
{
"binary_name": "linux-headers-5.13.0-1029-oem",
"binary_version": "5.13.0-1029.36"
},
{
"binary_name": "linux-image-unsigned-5.13.0-1029-oem",
"binary_version": "5.13.0-1029.36"
},
{
"binary_name": "linux-modules-5.13.0-1029-oem",
"binary_version": "5.13.0-1029.36"
},
{
"binary_name": "linux-oem-5.13-headers-5.13.0-1029",
"binary_version": "5.13.0-1029.36"
},
{
"binary_name": "linux-oem-5.13-tools-5.13.0-1029",
"binary_version": "5.13.0-1029.36"
},
{
"binary_name": "linux-oem-5.13-tools-host",
"binary_version": "5.13.0-1029.36"
},
{
"binary_name": "linux-tools-5.13.0-1029-oem",
"binary_version": "5.13.0-1029.36"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-oem-5.13",
"purl": "pkg:deb/ubuntu/linux-oem-5.13@5.13.0-1029.36?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-1009.10",
"5.13.0-1010.11",
"5.13.0-1012.16",
"5.13.0-1014.18",
"5.13.0-1017.21",
"5.13.0-1019.23",
"5.13.0-1020.24",
"5.13.0-1021.25",
"5.13.0-1022.26",
"5.13.0-1026.32",
"5.13.0-1028.35",
"5.13.0-1029.36"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.14.0-1059-oem",
"binary_version": "5.14.0-1059.67"
},
{
"binary_name": "linux-headers-5.14.0-1059-oem",
"binary_version": "5.14.0-1059.67"
},
{
"binary_name": "linux-image-unsigned-5.14.0-1059-oem",
"binary_version": "5.14.0-1059.67"
},
{
"binary_name": "linux-modules-5.14.0-1059-oem",
"binary_version": "5.14.0-1059.67"
},
{
"binary_name": "linux-modules-iwlwifi-5.14.0-1059-oem",
"binary_version": "5.14.0-1059.67"
},
{
"binary_name": "linux-oem-5.14-headers-5.14.0-1059",
"binary_version": "5.14.0-1059.67"
},
{
"binary_name": "linux-oem-5.14-tools-5.14.0-1059",
"binary_version": "5.14.0-1059.67"
},
{
"binary_name": "linux-oem-5.14-tools-host",
"binary_version": "5.14.0-1059.67"
},
{
"binary_name": "linux-tools-5.14.0-1059-oem",
"binary_version": "5.14.0-1059.67"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-oem-5.14",
"purl": "pkg:deb/ubuntu/linux-oem-5.14@5.14.0-1059.67?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.14.0-1004.4",
"5.14.0-1005.5",
"5.14.0-1007.7",
"5.14.0-1008.8",
"5.14.0-1010.10",
"5.14.0-1011.11",
"5.14.0-1013.13",
"5.14.0-1018.19",
"5.14.0-1020.22",
"5.14.0-1022.24",
"5.14.0-1024.26",
"5.14.0-1027.30",
"5.14.0-1029.32",
"5.14.0-1031.34",
"5.14.0-1032.35",
"5.14.0-1033.36",
"5.14.0-1034.37",
"5.14.0-1036.40",
"5.14.0-1038.42",
"5.14.0-1042.47",
"5.14.0-1044.49",
"5.14.0-1045.51",
"5.14.0-1046.53",
"5.14.0-1047.54",
"5.14.0-1048.55",
"5.14.0-1049.56",
"5.14.0-1050.57",
"5.14.0-1051.58",
"5.14.0-1052.59",
"5.14.0-1054.61",
"5.14.0-1055.62",
"5.14.0-1056.63",
"5.14.0-1057.64",
"5.14.0-1058.66",
"5.14.0-1059.67"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.6.0-1056-oem",
"binary_version": "5.6.0-1056.60"
},
{
"binary_name": "linux-headers-5.6.0-1056-oem",
"binary_version": "5.6.0-1056.60"
},
{
"binary_name": "linux-image-unsigned-5.6.0-1056-oem",
"binary_version": "5.6.0-1056.60"
},
{
"binary_name": "linux-modules-5.6.0-1056-oem",
"binary_version": "5.6.0-1056.60"
},
{
"binary_name": "linux-oem-5.6-headers-5.6.0-1056",
"binary_version": "5.6.0-1056.60"
},
{
"binary_name": "linux-oem-5.6-tools-5.6.0-1056",
"binary_version": "5.6.0-1056.60"
},
{
"binary_name": "linux-oem-5.6-tools-host",
"binary_version": "5.6.0-1056.60"
},
{
"binary_name": "linux-tools-5.6.0-1056-oem",
"binary_version": "5.6.0-1056.60"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-oem-5.6",
"purl": "pkg:deb/ubuntu/linux-oem-5.6@5.6.0-1056.60?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.6.0-1007.7",
"5.6.0-1008.8",
"5.6.0-1010.10",
"5.6.0-1011.11",
"5.6.0-1013.13",
"5.6.0-1017.17",
"5.6.0-1018.18",
"5.6.0-1020.20",
"5.6.0-1021.21",
"5.6.0-1023.23",
"5.6.0-1026.26",
"5.6.0-1027.27",
"5.6.0-1028.28",
"5.6.0-1031.32",
"5.6.0-1032.33",
"5.6.0-1033.35",
"5.6.0-1034.36",
"5.6.0-1035.37",
"5.6.0-1036.39",
"5.6.0-1039.43",
"5.6.0-1042.46",
"5.6.0-1047.51",
"5.6.0-1048.52",
"5.6.0-1050.54",
"5.6.0-1052.56",
"5.6.0-1053.57",
"5.6.0-1054.58",
"5.6.0-1055.59",
"5.6.0-1056.60"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.11.0-1028-oracle",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-headers-5.11.0-1028-oracle",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.11.0-1028-oracle",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-modules-5.11.0-1028-oracle",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.11.0-1028-oracle",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-oracle-5.11-headers-5.11.0-1028",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-oracle-5.11-tools-5.11.0-1028",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-tools-5.11.0-1028-oracle",
"binary_version": "5.11.0-1028.31~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-oracle-5.11",
"purl": "pkg:deb/ubuntu/linux-oracle-5.11@5.11.0-1028.31~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.11.0-1008.8~20.04.1",
"5.11.0-1013.14~20.04.1",
"5.11.0-1016.17~20.04.1",
"5.11.0-1017.18~20.04.1",
"5.11.0-1019.20~20.04.1",
"5.11.0-1020.21~20.04.1",
"5.11.0-1021.22~20.04.1",
"5.11.0-1022.23~20.04.1",
"5.11.0-1023.24~20.04.1",
"5.11.0-1025.27~20.04.1",
"5.11.0-1027.30~20.04.1",
"5.11.0-1028.31~20.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.13.0-1036-oracle",
"binary_version": "5.13.0-1036.43~20.04.1"
},
{
"binary_name": "linux-headers-5.13.0-1036-oracle",
"binary_version": "5.13.0-1036.43~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.13.0-1036-oracle",
"binary_version": "5.13.0-1036.43~20.04.1"
},
{
"binary_name": "linux-modules-5.13.0-1036-oracle",
"binary_version": "5.13.0-1036.43~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.13.0-1036-oracle",
"binary_version": "5.13.0-1036.43~20.04.1"
},
{
"binary_name": "linux-oracle-5.13-headers-5.13.0-1036",
"binary_version": "5.13.0-1036.43~20.04.1"
},
{
"binary_name": "linux-oracle-5.13-tools-5.13.0-1036",
"binary_version": "5.13.0-1036.43~20.04.1"
},
{
"binary_name": "linux-tools-5.13.0-1036-oracle",
"binary_version": "5.13.0-1036.43~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-oracle-5.13",
"purl": "pkg:deb/ubuntu/linux-oracle-5.13@5.13.0-1036.43~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-1011.13~20.04.2",
"5.13.0-1015.19~20.04.1",
"5.13.0-1016.20~20.04.1",
"5.13.0-1018.22~20.04.1",
"5.13.0-1021.26~20.04.1",
"5.13.0-1025.30~20.04.1",
"5.13.0-1027.32~20.04.1",
"5.13.0-1028.33~20.04.1",
"5.13.0-1030.35~20.04.1",
"5.13.0-1033.39~20.04.1",
"5.13.0-1034.40~20.04.1",
"5.13.0-1036.43~20.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.8.0-1038-oracle",
"binary_version": "5.8.0-1038.39~20.04.1"
},
{
"binary_name": "linux-headers-5.8.0-1038-oracle",
"binary_version": "5.8.0-1038.39~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.8.0-1038-oracle",
"binary_version": "5.8.0-1038.39~20.04.1"
},
{
"binary_name": "linux-modules-5.8.0-1038-oracle",
"binary_version": "5.8.0-1038.39~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.8.0-1038-oracle",
"binary_version": "5.8.0-1038.39~20.04.1"
},
{
"binary_name": "linux-oracle-5.8-headers-5.8.0-1038",
"binary_version": "5.8.0-1038.39~20.04.1"
},
{
"binary_name": "linux-oracle-5.8-tools-5.8.0-1038",
"binary_version": "5.8.0-1038.39~20.04.1"
},
{
"binary_name": "linux-tools-5.8.0-1038-oracle",
"binary_version": "5.8.0-1038.39~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-oracle-5.8",
"purl": "pkg:deb/ubuntu/linux-oracle-5.8@5.8.0-1038.39~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.8.0-1031.32~20.04.2",
"5.8.0-1033.34~20.04.1",
"5.8.0-1034.35~20.04.2",
"5.8.0-1037.38~20.04.1",
"5.8.0-1038.39~20.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1006-raspi2",
"binary_version": "5.4.0-1006.6"
},
{
"binary_name": "linux-headers-5.4.0-1006-raspi2",
"binary_version": "5.4.0-1006.6"
},
{
"binary_name": "linux-image-5.4.0-1006-raspi2",
"binary_version": "5.4.0-1006.6"
},
{
"binary_name": "linux-modules-5.4.0-1006-raspi2",
"binary_version": "5.4.0-1006.6"
},
{
"binary_name": "linux-raspi2-headers-5.4.0-1006",
"binary_version": "5.4.0-1006.6"
},
{
"binary_name": "linux-raspi2-tools-5.4.0-1006",
"binary_version": "5.4.0-1006.6"
},
{
"binary_name": "linux-tools-5.4.0-1006-raspi2",
"binary_version": "5.4.0-1006.6"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-raspi2",
"purl": "pkg:deb/ubuntu/linux-raspi2@5.4.0-1006.6?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.3.0-1007.8",
"5.3.0-1014.16",
"5.3.0-1015.17",
"5.3.0-1017.19",
"5.4.0-1004.4",
"5.4.0-1006.6"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "block-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "crypto-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "fat-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "firewire-core-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "fs-core-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "fs-secondary-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "input-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "ipmi-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "kernel-image-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "linux-buildinfo-5.4.0-40-generic",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "linux-headers-5.4.0-40-generic",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "linux-image-5.4.0-40-generic",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "linux-modules-5.4.0-40-generic",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "linux-modules-extra-5.4.0-40-generic",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "linux-riscv-headers-5.4.0-40",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "linux-riscv-tools-5.4.0-40",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "linux-tools-5.4.0-40-generic",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "linux-udebs-generic",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "md-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "message-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "mouse-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "multipath-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "nfs-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "nic-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "nic-shared-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "nic-usb-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "parport-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "pata-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "plip-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "ppp-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "sata-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "scsi-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "storage-core-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "usb-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "virtio-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "vlan-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-riscv",
"purl": "pkg:deb/ubuntu/linux-riscv@5.4.0-40.45?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-24.28",
"5.4.0-26.30",
"5.4.0-27.31",
"5.4.0-28.32",
"5.4.0-30.34",
"5.4.0-31.35",
"5.4.0-33.37",
"5.4.0-34.38",
"5.4.0-36.41",
"5.4.0-37.42",
"5.4.0-39.44",
"5.4.0-40.45"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.11.0-1031-generic",
"binary_version": "5.11.0-1031.35"
},
{
"binary_name": "linux-headers-5.11.0-1031-generic",
"binary_version": "5.11.0-1031.35"
},
{
"binary_name": "linux-image-5.11.0-1031-generic",
"binary_version": "5.11.0-1031.35"
},
{
"binary_name": "linux-modules-5.11.0-1031-generic",
"binary_version": "5.11.0-1031.35"
},
{
"binary_name": "linux-modules-extra-5.11.0-1031-generic",
"binary_version": "5.11.0-1031.35"
},
{
"binary_name": "linux-riscv-5.11-headers-5.11.0-1031",
"binary_version": "5.11.0-1031.35"
},
{
"binary_name": "linux-riscv-5.11-tools-5.11.0-1031",
"binary_version": "5.11.0-1031.35"
},
{
"binary_name": "linux-tools-5.11.0-1031-generic",
"binary_version": "5.11.0-1031.35"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-riscv-5.11",
"purl": "pkg:deb/ubuntu/linux-riscv-5.11@5.11.0-1031.35?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.11.0-1015.16~20.04.1",
"5.11.0-1017.18~20.04.1",
"5.11.0-1018.19~20.04.2",
"5.11.0-1020.21~20.04.1",
"5.11.0-1021.22~20.04.1",
"5.11.0-1022.23~20.04.1",
"5.11.0-1023.24~20.04.1",
"5.11.0-1024.25~20.04.1",
"5.11.0-1026.28~20.04.1",
"5.11.0-1028.31~20.04.1",
"5.11.0-1029.32~20.04.1",
"5.11.0-1030.34",
"5.11.0-1031.35"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "block-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "crypto-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "fat-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "firewire-core-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "fs-core-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "input-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "ipmi-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "kernel-image-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.8.0-29-generic",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "linux-headers-5.8.0-29-generic",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "linux-image-5.8.0-29-generic",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "linux-modules-5.8.0-29-generic",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.8.0-29-generic",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "linux-riscv-5.8-headers-5.8.0-29",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "linux-riscv-5.8-tools-5.8.0-29",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "linux-tools-5.8.0-29-generic",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "linux-udebs-generic",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "md-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "message-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "mouse-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "multipath-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "nfs-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "nic-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "parport-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "pata-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "plip-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "ppp-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "sata-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "scsi-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "storage-core-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "usb-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "virtio-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "vlan-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-riscv-5.8",
"purl": "pkg:deb/ubuntu/linux-riscv-5.8@5.8.0-29.31~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.8.0-14.16~20.04.1",
"5.8.0-14.16~20.04.3",
"5.8.0-16.18~20.04.1",
"5.8.0-17.19~20.04.1",
"5.8.0-18.20~20.04.1",
"5.8.0-20.22~20.04.1",
"5.8.0-22.24~20.04.1",
"5.8.0-25.27~20.04.1",
"5.8.0-26.28~20.04.1",
"5.8.0-29.31~20.04.1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-aws-fips-headers-5.4.0-1135",
"binary_version": "5.4.0-1135.145+fips1"
},
{
"binary_name": "linux-aws-fips-tools-5.4.0-1135",
"binary_version": "5.4.0-1135.145+fips1"
},
{
"binary_name": "linux-buildinfo-5.4.0-1135-aws-fips",
"binary_version": "5.4.0-1135.145+fips1"
},
{
"binary_name": "linux-headers-5.4.0-1135-aws-fips",
"binary_version": "5.4.0-1135.145+fips1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1135-aws-fips",
"binary_version": "5.4.0-1135.145+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.4.0-1135-aws-fips",
"binary_version": "5.4.0-1135.145+fips1"
},
{
"binary_name": "linux-modules-5.4.0-1135-aws-fips",
"binary_version": "5.4.0-1135.145+fips1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1135-aws-fips",
"binary_version": "5.4.0-1135.145+fips1"
},
{
"binary_name": "linux-tools-5.4.0-1135-aws-fips",
"binary_version": "5.4.0-1135.145+fips1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:20.04:LTS",
"name": "linux-aws-fips",
"purl": "pkg:deb/ubuntu/linux-aws-fips@5.4.0-1135.145+fips1?arch=source\u0026distro=fips-updates/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1135.145+fips1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1021.21+fips2",
"5.4.0-1069.73+fips2",
"5.4.0-1071.76+fips1",
"5.4.0-1072.77+fips1",
"5.4.0-1073.78+fips1",
"5.4.0-1078.84+fips1",
"5.4.0-1080.87+fips1",
"5.4.0-1081.88+fips1",
"5.4.0-1083.90+fips1",
"5.4.0-1085.92+fips1",
"5.4.0-1086.93+fips1",
"5.4.0-1088.96+fips1",
"5.4.0-1089.97+fips1",
"5.4.0-1092.100+fips1",
"5.4.0-1093.101+fips1",
"5.4.0-1094.102+fips1",
"5.4.0-1096.104+fips1",
"5.4.0-1099.107+fips1",
"5.4.0-1100.108+fips1",
"5.4.0-1101.109+fips1",
"5.4.0-1102.110+fips1",
"5.4.0-1103.111+fips1",
"5.4.0-1104.112+fips1",
"5.4.0-1105.113+fips1",
"5.4.0-1106.114+fips1",
"5.4.0-1107.115+fips1",
"5.4.0-1108.116+fips1",
"5.4.0-1109.118+fips1",
"5.4.0-1110.119+fips1",
"5.4.0-1111.120+fips1",
"5.4.0-1112.121+fips1",
"5.4.0-1113.123+fips1",
"5.4.0-1114.124+fips1",
"5.4.0-1116.126+fips1",
"5.4.0-1117.127+fips1",
"5.4.0-1118.128+fips1",
"5.4.0-1119.129+fips1",
"5.4.0-1120.130+fips1",
"5.4.0-1121.131+fips1",
"5.4.0-1122.132+fips1",
"5.4.0-1123.133+fips1",
"5.4.0-1124.134+fips1",
"5.4.0-1125.135+fips1",
"5.4.0-1126.136+fips2",
"5.4.0-1127.137+fips1",
"5.4.0-1128.138+fips1",
"5.4.0-1129.139+fips1",
"5.4.0-1130.140+fips1",
"5.4.0-1131.141+fips1",
"5.4.0-1132.142+fips1",
"5.4.0-1133.143+fips1",
"5.4.0-1134.144+fips1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-azure-fips-cloud-tools-5.4.0-1140",
"binary_version": "5.4.0-1140.147+fips1"
},
{
"binary_name": "linux-azure-fips-headers-5.4.0-1140",
"binary_version": "5.4.0-1140.147+fips1"
},
{
"binary_name": "linux-azure-fips-tools-5.4.0-1140",
"binary_version": "5.4.0-1140.147+fips1"
},
{
"binary_name": "linux-buildinfo-5.4.0-1140-azure-fips",
"binary_version": "5.4.0-1140.147+fips1"
},
{
"binary_name": "linux-cloud-tools-5.4.0-1140-azure-fips",
"binary_version": "5.4.0-1140.147+fips1"
},
{
"binary_name": "linux-headers-5.4.0-1140-azure-fips",
"binary_version": "5.4.0-1140.147+fips1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1140-azure-fips",
"binary_version": "5.4.0-1140.147+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.4.0-1140-azure-fips",
"binary_version": "5.4.0-1140.147+fips1"
},
{
"binary_name": "linux-modules-5.4.0-1140-azure-fips",
"binary_version": "5.4.0-1140.147+fips1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1140-azure-fips",
"binary_version": "5.4.0-1140.147+fips1"
},
{
"binary_name": "linux-tools-5.4.0-1140-azure-fips",
"binary_version": "5.4.0-1140.147+fips1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:20.04:LTS",
"name": "linux-azure-fips",
"purl": "pkg:deb/ubuntu/linux-azure-fips@5.4.0-1140.147+fips1?arch=source\u0026distro=fips-updates/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1140.147+fips1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1022.22+fips1",
"5.4.0-1073.76+fips1",
"5.4.0-1074.77+fips1",
"5.4.0-1076.79+fips1",
"5.4.0-1078.81+fips1",
"5.4.0-1080.83+fips1",
"5.4.0-1083.87+fips1",
"5.4.0-1085.90+fips1",
"5.4.0-1086.91+fips1",
"5.4.0-1089.94+fips1",
"5.4.0-1090.95+fips1",
"5.4.0-1091.96+fips1",
"5.4.0-1094.100+fips1",
"5.4.0-1095.101+fips1",
"5.4.0-1098.104+fips1",
"5.4.0-1100.106+fips1",
"5.4.0-1101.107+fips1",
"5.4.0-1103.109+fips1",
"5.4.0-1104.110+fips1",
"5.4.0-1105.111+fips1",
"5.4.0-1106.112+fips1",
"5.4.0-1107.113+fips1",
"5.4.0-1108.114+fips1",
"5.4.0-1109.115+fips1",
"5.4.0-1110.116+fips1",
"5.4.0-1111.117+fips1",
"5.4.0-1112.118+fips1",
"5.4.0-1113.119+fips1",
"5.4.0-1114.120+fips1",
"5.4.0-1115.122+fips1",
"5.4.0-1116.123+fips1",
"5.4.0-1117.124+fips1",
"5.4.0-1118.125+fips1",
"5.4.0-1119.126+fips1",
"5.4.0-1121.128+fips1",
"5.4.0-1122.129+fips1",
"5.4.0-1123.130+fips1",
"5.4.0-1124.131+fips1",
"5.4.0-1126.133+fips1",
"5.4.0-1127.134+fips1",
"5.4.0-1128.135+fips1",
"5.4.0-1129.136+fips1",
"5.4.0-1130.137+fips1",
"5.4.0-1131.138+fips1",
"5.4.0-1132.139+fips1",
"5.4.0-1133.140+fips1",
"5.4.0-1134.141+fips1",
"5.4.0-1135.142+fips1",
"5.4.0-1136.143+fips1",
"5.4.0-1137.144+fips1",
"5.4.0-1138.145+fips1",
"5.4.0-1139.146+fips1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1109-fips",
"binary_version": "5.4.0-1109.119"
},
{
"binary_name": "linux-fips-headers-5.4.0-1109",
"binary_version": "5.4.0-1109.119"
},
{
"binary_name": "linux-fips-tools-5.4.0-1109",
"binary_version": "5.4.0-1109.119"
},
{
"binary_name": "linux-fips-tools-host",
"binary_version": "5.4.0-1109.119"
},
{
"binary_name": "linux-headers-5.4.0-1109-fips",
"binary_version": "5.4.0-1109.119"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1109-fips",
"binary_version": "5.4.0-1109.119"
},
{
"binary_name": "linux-image-unsigned-hmac-5.4.0-1109-fips",
"binary_version": "5.4.0-1109.119"
},
{
"binary_name": "linux-modules-5.4.0-1109-fips",
"binary_version": "5.4.0-1109.119"
},
{
"binary_name": "linux-modules-extra-5.4.0-1109-fips",
"binary_version": "5.4.0-1109.119"
},
{
"binary_name": "linux-tools-5.4.0-1109-fips",
"binary_version": "5.4.0-1109.119"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:20.04:LTS",
"name": "linux-fips",
"purl": "pkg:deb/ubuntu/linux-fips@5.4.0-1109.119?arch=source\u0026distro=fips-updates/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1109.119"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1026.30",
"5.4.0-1028.32",
"5.4.0-1031.36",
"5.4.0-1032.37",
"5.4.0-1033.38",
"5.4.0-1034.40",
"5.4.0-1035.41",
"5.4.0-1036.42",
"5.4.0-1037.43",
"5.4.0-1038.44",
"5.4.0-1040.46",
"5.4.0-1041.47",
"5.4.0-1042.48",
"5.4.0-1043.49",
"5.4.0-1045.51",
"5.4.0-1046.52",
"5.4.0-1047.53",
"5.4.0-1048.54",
"5.4.0-1049.55",
"5.4.0-1051.57",
"5.4.0-1054.61",
"5.4.0-1056.64",
"5.4.0-1057.65",
"5.4.0-1059.67",
"5.4.0-1060.68",
"5.4.0-1061.69",
"5.4.0-1062.70",
"5.4.0-1064.73",
"5.4.0-1065.74",
"5.4.0-1068.77",
"5.4.0-1069.78",
"5.4.0-1070.79",
"5.4.0-1072.81",
"5.4.0-1073.82",
"5.4.0-1074.83",
"5.4.0-1075.84",
"5.4.0-1076.85",
"5.4.0-1077.86",
"5.4.0-1078.87",
"5.4.0-1079.88",
"5.4.0-1080.89",
"5.4.0-1081.90",
"5.4.0-1082.91",
"5.4.0-1083.92",
"5.4.0-1084.93",
"5.4.0-1085.94",
"5.4.0-1086.95",
"5.4.0-1087.96",
"5.4.0-1088.97",
"5.4.0-1089.98",
"5.4.0-1090.100",
"5.4.0-1091.101",
"5.4.0-1092.102",
"5.4.0-1094.104",
"5.4.0-1095.105",
"5.4.0-1096.106",
"5.4.0-1097.107",
"5.4.0-1098.108",
"5.4.0-1099.109",
"5.4.0-1100.110",
"5.4.0-1101.111",
"5.4.0-1102.112",
"5.4.0-1103.113",
"5.4.0-1104.114",
"5.4.0-1105.115",
"5.4.0-1106.116",
"5.4.0-1107.117",
"5.4.0-1108.118"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1139-gcp-fips",
"binary_version": "5.4.0-1139.148+fips1"
},
{
"binary_name": "linux-gcp-fips-headers-5.4.0-1139",
"binary_version": "5.4.0-1139.148+fips1"
},
{
"binary_name": "linux-gcp-fips-tools-5.4.0-1139",
"binary_version": "5.4.0-1139.148+fips1"
},
{
"binary_name": "linux-headers-5.4.0-1139-gcp-fips",
"binary_version": "5.4.0-1139.148+fips1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1139-gcp-fips",
"binary_version": "5.4.0-1139.148+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.4.0-1139-gcp-fips",
"binary_version": "5.4.0-1139.148+fips1"
},
{
"binary_name": "linux-modules-5.4.0-1139-gcp-fips",
"binary_version": "5.4.0-1139.148+fips1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1139-gcp-fips",
"binary_version": "5.4.0-1139.148+fips1"
},
{
"binary_name": "linux-tools-5.4.0-1139-gcp-fips",
"binary_version": "5.4.0-1139.148+fips1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:20.04:LTS",
"name": "linux-gcp-fips",
"purl": "pkg:deb/ubuntu/linux-gcp-fips@5.4.0-1139.148+fips1?arch=source\u0026distro=fips-updates/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1139.148+fips1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1021.21+fips1",
"5.4.0-1067.71~20.04.1",
"5.4.0-1069.73+fips2",
"5.4.0-1071.75+fips1",
"5.4.0-1073.78+fips1",
"5.4.0-1075.80+fips1",
"5.4.0-1078.84+fips1",
"5.4.0-1080.87+fips1",
"5.4.0-1081.88+fips1",
"5.4.0-1086.94+fips1",
"5.4.0-1087.95+fips1",
"5.4.0-1089.97+fips1",
"5.4.0-1092.101+fips1",
"5.4.0-1093.102+fips1",
"5.4.0-1096.105+fips1",
"5.4.0-1097.106+fips1",
"5.4.0-1098.107+fips1",
"5.4.0-1100.109+fips1",
"5.4.0-1101.110+fips1",
"5.4.0-1102.111+fips1",
"5.4.0-1103.112+fips1",
"5.4.0-1104.113+fips1",
"5.4.0-1105.114+fips1",
"5.4.0-1106.115+fips1",
"5.4.0-1107.116+fips1",
"5.4.0-1108.117+fips1",
"5.4.0-1109.118+fips1",
"5.4.0-1110.119+fips1",
"5.4.0-1111.120+fips1",
"5.4.0-1112.121+fips1",
"5.4.0-1113.122+fips1",
"5.4.0-1115.124+fips1",
"5.4.0-1116.125+fips1",
"5.4.0-1117.126+fips1",
"5.4.0-1118.127+fips1",
"5.4.0-1120.129+fips1",
"5.4.0-1121.130+fips1",
"5.4.0-1122.131+fips1",
"5.4.0-1124.133+fips1",
"5.4.0-1125.134+fips1",
"5.4.0-1126.135+fips1",
"5.4.0-1127.136+fips1",
"5.4.0-1128.137+fips1",
"5.4.0-1129.138+fips1",
"5.4.0-1130.139+fips1",
"5.4.0-1131.140+fips1",
"5.4.0-1132.141+fips1",
"5.4.0-1133.142+fips1",
"5.4.0-1134.143+fips1",
"5.4.0-1135.144+fips1",
"5.4.0-1136.145+fips1",
"5.4.0-1137.146+fips1",
"5.4.0-1138.147+fips1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-aws-fips-headers-5.4.0-1021",
"binary_version": "5.4.0-1021.21+fips2"
},
{
"binary_name": "linux-aws-fips-tools-5.4.0-1021",
"binary_version": "5.4.0-1021.21+fips2"
},
{
"binary_name": "linux-buildinfo-5.4.0-1021-aws-fips",
"binary_version": "5.4.0-1021.21+fips2"
},
{
"binary_name": "linux-headers-5.4.0-1021-aws-fips",
"binary_version": "5.4.0-1021.21+fips2"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1021-aws-fips",
"binary_version": "5.4.0-1021.21+fips2"
},
{
"binary_name": "linux-image-unsigned-hmac-5.4.0-1021-aws-fips",
"binary_version": "5.4.0-1021.21+fips2"
},
{
"binary_name": "linux-modules-5.4.0-1021-aws-fips",
"binary_version": "5.4.0-1021.21+fips2"
},
{
"binary_name": "linux-modules-extra-5.4.0-1021-aws-fips",
"binary_version": "5.4.0-1021.21+fips2"
},
{
"binary_name": "linux-tools-5.4.0-1021-aws-fips",
"binary_version": "5.4.0-1021.21+fips2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS:20.04:LTS",
"name": "linux-aws-fips",
"purl": "pkg:deb/ubuntu/linux-aws-fips@5.4.0-1021.21+fips2?arch=source\u0026distro=fips/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1021.21+fips2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-azure-fips-cloud-tools-5.4.0-1022",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-azure-fips-headers-5.4.0-1022",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-azure-fips-tools-5.4.0-1022",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-buildinfo-5.4.0-1022-azure-fips",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-cloud-tools-5.4.0-1022-azure-fips",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-headers-5.4.0-1022-azure-fips",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1022-azure-fips",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.4.0-1022-azure-fips",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-modules-5.4.0-1022-azure-fips",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1022-azure-fips",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-tools-5.4.0-1022-azure-fips",
"binary_version": "5.4.0-1022.22+fips1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS:20.04:LTS",
"name": "linux-azure-fips",
"purl": "pkg:deb/ubuntu/linux-azure-fips@5.4.0-1022.22+fips1?arch=source\u0026distro=fips/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1022.22+fips1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1007-fips",
"binary_version": "5.4.0-1007.8"
},
{
"binary_name": "linux-fips-headers-5.4.0-1007",
"binary_version": "5.4.0-1007.8"
},
{
"binary_name": "linux-fips-tools-5.4.0-1007",
"binary_version": "5.4.0-1007.8"
},
{
"binary_name": "linux-fips-tools-host",
"binary_version": "5.4.0-1007.8"
},
{
"binary_name": "linux-headers-5.4.0-1007-fips",
"binary_version": "5.4.0-1007.8"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1007-fips",
"binary_version": "5.4.0-1007.8"
},
{
"binary_name": "linux-image-unsigned-hmac-5.4.0-1007-fips",
"binary_version": "5.4.0-1007.8"
},
{
"binary_name": "linux-modules-5.4.0-1007-fips",
"binary_version": "5.4.0-1007.8"
},
{
"binary_name": "linux-modules-extra-5.4.0-1007-fips",
"binary_version": "5.4.0-1007.8"
},
{
"binary_name": "linux-tools-5.4.0-1007-fips",
"binary_version": "5.4.0-1007.8"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS:20.04:LTS",
"name": "linux-fips",
"purl": "pkg:deb/ubuntu/linux-fips@5.4.0-1007.8?arch=source\u0026distro=fips/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1007.8"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1021-gcp-fips",
"binary_version": "5.4.0-1021.21+fips1"
},
{
"binary_name": "linux-gcp-fips-headers-5.4.0-1021",
"binary_version": "5.4.0-1021.21+fips1"
},
{
"binary_name": "linux-gcp-fips-tools-5.4.0-1021",
"binary_version": "5.4.0-1021.21+fips1"
},
{
"binary_name": "linux-headers-5.4.0-1021-gcp-fips",
"binary_version": "5.4.0-1021.21+fips1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1021-gcp-fips",
"binary_version": "5.4.0-1021.21+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.4.0-1021-gcp-fips",
"binary_version": "5.4.0-1021.21+fips1"
},
{
"binary_name": "linux-modules-5.4.0-1021-gcp-fips",
"binary_version": "5.4.0-1021.21+fips1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1021-gcp-fips",
"binary_version": "5.4.0-1021.21+fips1"
},
{
"binary_name": "linux-tools-5.4.0-1021-gcp-fips",
"binary_version": "5.4.0-1021.21+fips1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS:20.04:LTS",
"name": "linux-gcp-fips",
"purl": "pkg:deb/ubuntu/linux-gcp-fips@5.4.0-1021.21+fips1?arch=source\u0026distro=fips/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1021.21+fips1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-125-generic",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-buildinfo-5.15.0-125-generic-64k",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-buildinfo-5.15.0-125-generic-lpae",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-cloud-tools-5.15.0-125",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-cloud-tools-5.15.0-125-generic",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-cloud-tools-common",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-headers-5.15.0-125",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-headers-5.15.0-125-generic",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-headers-5.15.0-125-generic-64k",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-headers-5.15.0-125-generic-lpae",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-image-5.15.0-125-generic",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-image-5.15.0-125-generic-lpae",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-image-unsigned-5.15.0-125-generic",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-image-unsigned-5.15.0-125-generic-64k",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-modules-5.15.0-125-generic",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-modules-5.15.0-125-generic-64k",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-modules-5.15.0-125-generic-lpae",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-modules-extra-5.15.0-125-generic",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-125-generic",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-source-5.15.0",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-tools-5.15.0-125",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-tools-5.15.0-125-generic",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-tools-5.15.0-125-generic-64k",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-tools-5.15.0-125-generic-lpae",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-tools-common",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-tools-host",
"binary_version": "5.15.0-125.135"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux",
"purl": "pkg:deb/ubuntu/linux@5.15.0-125.135?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-125.135"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-19.19",
"5.15.0-17.17",
"5.15.0-18.18",
"5.15.0-22.22",
"5.15.0-23.23",
"5.15.0-25.25",
"5.15.0-27.28",
"5.15.0-30.31",
"5.15.0-33.34",
"5.15.0-35.36",
"5.15.0-37.39",
"5.15.0-39.42",
"5.15.0-40.43",
"5.15.0-41.44",
"5.15.0-43.46",
"5.15.0-46.49",
"5.15.0-47.51",
"5.15.0-48.54",
"5.15.0-50.56",
"5.15.0-52.58",
"5.15.0-53.59",
"5.15.0-56.62",
"5.15.0-57.63",
"5.15.0-58.64",
"5.15.0-60.66",
"5.15.0-67.74",
"5.15.0-69.76",
"5.15.0-70.77",
"5.15.0-71.78",
"5.15.0-72.79",
"5.15.0-73.80",
"5.15.0-75.82",
"5.15.0-76.83",
"5.15.0-78.85",
"5.15.0-79.86",
"5.15.0-82.91",
"5.15.0-83.92",
"5.15.0-84.93",
"5.15.0-86.96",
"5.15.0-87.97",
"5.15.0-88.98",
"5.15.0-89.99",
"5.15.0-91.101",
"5.15.0-92.102",
"5.15.0-94.104",
"5.15.0-97.107",
"5.15.0-100.110",
"5.15.0-101.111",
"5.15.0-102.112",
"5.15.0-105.115",
"5.15.0-106.116",
"5.15.0-107.117",
"5.15.0-112.122",
"5.15.0-113.123",
"5.15.0-116.126",
"5.15.0-117.127",
"5.15.0-118.128",
"5.15.0-119.129",
"5.15.0-121.131",
"5.15.0-122.132",
"5.15.0-124.134"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-allwinner-5.19-headers-5.19.0-1015",
"binary_version": "5.19.0-1015.15~22.04.1"
},
{
"binary_name": "linux-allwinner-5.19-tools-5.19.0-1015",
"binary_version": "5.19.0-1015.15~22.04.1"
},
{
"binary_name": "linux-buildinfo-5.19.0-1015-allwinner",
"binary_version": "5.19.0-1015.15~22.04.1"
},
{
"binary_name": "linux-headers-5.19.0-1015-allwinner",
"binary_version": "5.19.0-1015.15~22.04.1"
},
{
"binary_name": "linux-image-5.19.0-1015-allwinner",
"binary_version": "5.19.0-1015.15~22.04.1"
},
{
"binary_name": "linux-modules-5.19.0-1015-allwinner",
"binary_version": "5.19.0-1015.15~22.04.1"
},
{
"binary_name": "linux-modules-extra-5.19.0-1015-allwinner",
"binary_version": "5.19.0-1015.15~22.04.1"
},
{
"binary_name": "linux-tools-5.19.0-1015-allwinner",
"binary_version": "5.19.0-1015.15~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-allwinner-5.19",
"purl": "pkg:deb/ubuntu/linux-allwinner-5.19@5.19.0-1015.15~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.19.0-1007.7~22.04.1",
"5.19.0-1009.9~22.04.1",
"5.19.0-1010.10~22.04.1",
"5.19.0-1011.11~22.04.1",
"5.19.0-1012.12~22.04.1",
"5.19.0-1013.13~22.04.1",
"5.19.0-1014.14~22.04.1",
"5.19.0-1015.15~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-aws-cloud-tools-5.15.0-1072",
"binary_version": "5.15.0-1072.78"
},
{
"binary_name": "linux-aws-headers-5.15.0-1072",
"binary_version": "5.15.0-1072.78"
},
{
"binary_name": "linux-aws-tools-5.15.0-1072",
"binary_version": "5.15.0-1072.78"
},
{
"binary_name": "linux-buildinfo-5.15.0-1072-aws",
"binary_version": "5.15.0-1072.78"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1072-aws",
"binary_version": "5.15.0-1072.78"
},
{
"binary_name": "linux-headers-5.15.0-1072-aws",
"binary_version": "5.15.0-1072.78"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1072-aws",
"binary_version": "5.15.0-1072.78"
},
{
"binary_name": "linux-modules-5.15.0-1072-aws",
"binary_version": "5.15.0-1072.78"
},
{
"binary_name": "linux-modules-extra-5.15.0-1072-aws",
"binary_version": "5.15.0-1072.78"
},
{
"binary_name": "linux-tools-5.15.0-1072-aws",
"binary_version": "5.15.0-1072.78"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-aws",
"purl": "pkg:deb/ubuntu/linux-aws@5.15.0-1072.78?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1072.78"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-1005.6",
"5.15.0-1002.4",
"5.15.0-1003.5",
"5.15.0-1004.6",
"5.15.0-1005.7",
"5.15.0-1008.10",
"5.15.0-1009.11",
"5.15.0-1011.14",
"5.15.0-1013.17",
"5.15.0-1014.18",
"5.15.0-1015.19",
"5.15.0-1017.21",
"5.15.0-1019.23",
"5.15.0-1020.24",
"5.15.0-1021.25",
"5.15.0-1022.26",
"5.15.0-1023.27",
"5.15.0-1026.30",
"5.15.0-1027.31",
"5.15.0-1028.32",
"5.15.0-1030.34",
"5.15.0-1031.35",
"5.15.0-1033.37",
"5.15.0-1034.38",
"5.15.0-1035.39",
"5.15.0-1036.40",
"5.15.0-1037.41",
"5.15.0-1038.43",
"5.15.0-1039.44",
"5.15.0-1040.45",
"5.15.0-1042.47",
"5.15.0-1043.48",
"5.15.0-1044.49",
"5.15.0-1045.50",
"5.15.0-1047.52",
"5.15.0-1048.53",
"5.15.0-1049.54",
"5.15.0-1050.55",
"5.15.0-1051.56",
"5.15.0-1052.57",
"5.15.0-1053.58",
"5.15.0-1055.60",
"5.15.0-1056.61",
"5.15.0-1057.63",
"5.15.0-1060.66",
"5.15.0-1061.67",
"5.15.0-1062.68",
"5.15.0-1063.69",
"5.15.0-1064.70",
"5.15.0-1065.71",
"5.15.0-1066.72",
"5.15.0-1067.73",
"5.15.0-1068.74",
"5.15.0-1069.75",
"5.15.0-1070.76",
"5.15.0-1071.77"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-aws-5.19-cloud-tools-5.19.0-1029",
"binary_version": "5.19.0-1029.30~22.04.1"
},
{
"binary_name": "linux-aws-5.19-headers-5.19.0-1029",
"binary_version": "5.19.0-1029.30~22.04.1"
},
{
"binary_name": "linux-aws-5.19-tools-5.19.0-1029",
"binary_version": "5.19.0-1029.30~22.04.1"
},
{
"binary_name": "linux-buildinfo-5.19.0-1029-aws",
"binary_version": "5.19.0-1029.30~22.04.1"
},
{
"binary_name": "linux-cloud-tools-5.19.0-1029-aws",
"binary_version": "5.19.0-1029.30~22.04.1"
},
{
"binary_name": "linux-headers-5.19.0-1029-aws",
"binary_version": "5.19.0-1029.30~22.04.1"
},
{
"binary_name": "linux-image-unsigned-5.19.0-1029-aws",
"binary_version": "5.19.0-1029.30~22.04.1"
},
{
"binary_name": "linux-modules-5.19.0-1029-aws",
"binary_version": "5.19.0-1029.30~22.04.1"
},
{
"binary_name": "linux-modules-extra-5.19.0-1029-aws",
"binary_version": "5.19.0-1029.30~22.04.1"
},
{
"binary_name": "linux-tools-5.19.0-1029-aws",
"binary_version": "5.19.0-1029.30~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-aws-5.19",
"purl": "pkg:deb/ubuntu/linux-aws-5.19@5.19.0-1029.30~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.19.0-1019.20~22.04.1",
"5.19.0-1020.21~22.04.1",
"5.19.0-1022.23~22.04.1",
"5.19.0-1023.24~22.04.1",
"5.19.0-1024.25~22.04.1",
"5.19.0-1025.26~22.04.1",
"5.19.0-1026.27~22.04.1",
"5.19.0-1027.28~22.04.1",
"5.19.0-1028.29~22.04.1",
"5.19.0-1029.30~22.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-aws-6.2-cloud-tools-6.2.0-1018",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-aws-6.2-headers-6.2.0-1018",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-aws-6.2-tools-6.2.0-1018",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.2.0-1018-aws",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.2.0-1018-aws",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-headers-6.2.0-1018-aws",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.2.0-1018-aws",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-modules-6.2.0-1018-aws",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.2.0-1018-aws",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-tools-6.2.0-1018-aws",
"binary_version": "6.2.0-1018.18~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-aws-6.2",
"purl": "pkg:deb/ubuntu/linux-aws-6.2@6.2.0-1018.18~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.2.0-1005.5~22.04.1",
"6.2.0-1006.6~22.04.1",
"6.2.0-1007.7~22.04.1",
"6.2.0-1008.8~22.04.1",
"6.2.0-1009.9~22.04.3",
"6.2.0-1010.10~22.04.1",
"6.2.0-1011.11~22.04.1",
"6.2.0-1012.12~22.04.1",
"6.2.0-1013.13~22.04.1",
"6.2.0-1014.14~22.04.1",
"6.2.0-1015.15~22.04.1",
"6.2.0-1016.16~22.04.1",
"6.2.0-1017.17~22.04.1",
"6.2.0-1018.18~22.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-aws-6.5-cloud-tools-6.5.0-1024",
"binary_version": "6.5.0-1024.24~22.04.1"
},
{
"binary_name": "linux-aws-6.5-headers-6.5.0-1024",
"binary_version": "6.5.0-1024.24~22.04.1"
},
{
"binary_name": "linux-aws-6.5-tools-6.5.0-1024",
"binary_version": "6.5.0-1024.24~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.5.0-1024-aws",
"binary_version": "6.5.0-1024.24~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.5.0-1024-aws",
"binary_version": "6.5.0-1024.24~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-1024-aws",
"binary_version": "6.5.0-1024.24~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.5.0-1024-aws",
"binary_version": "6.5.0-1024.24~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-1024-aws",
"binary_version": "6.5.0-1024.24~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.5.0-1024-aws",
"binary_version": "6.5.0-1024.24~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-1024-aws",
"binary_version": "6.5.0-1024.24~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-aws-6.5",
"purl": "pkg:deb/ubuntu/linux-aws-6.5@6.5.0-1024.24~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-1008.8~22.04.1",
"6.5.0-1010.10~22.04.1",
"6.5.0-1011.11~22.04.1",
"6.5.0-1012.12~22.04.1",
"6.5.0-1014.14~22.04.1",
"6.5.0-1015.15~22.04.1",
"6.5.0-1016.16~22.04.1",
"6.5.0-1017.17~22.04.2",
"6.5.0-1018.18~22.04.1",
"6.5.0-1020.20~22.04.1",
"6.5.0-1021.21~22.04.1",
"6.5.0-1022.22~22.04.1",
"6.5.0-1023.23~22.04.1",
"6.5.0-1024.24~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-aws-6.8-cloud-tools-6.8.0-1020",
"binary_version": "6.8.0-1020.22~22.04.1"
},
{
"binary_name": "linux-aws-6.8-headers-6.8.0-1020",
"binary_version": "6.8.0-1020.22~22.04.1"
},
{
"binary_name": "linux-aws-6.8-tools-6.8.0-1020",
"binary_version": "6.8.0-1020.22~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.8.0-1020-aws",
"binary_version": "6.8.0-1020.22~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.8.0-1020-aws",
"binary_version": "6.8.0-1020.22~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1020-aws",
"binary_version": "6.8.0-1020.22~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1020-aws",
"binary_version": "6.8.0-1020.22~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1020-aws",
"binary_version": "6.8.0-1020.22~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1020-aws",
"binary_version": "6.8.0-1020.22~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1020-aws",
"binary_version": "6.8.0-1020.22~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-aws-6.8",
"purl": "pkg:deb/ubuntu/linux-aws-6.8@6.8.0-1020.22~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1020.22~22.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1009.9~22.04.2",
"6.8.0-1010.10~22.04.2",
"6.8.0-1011.12~22.04.1",
"6.8.0-1013.14~22.04.1",
"6.8.0-1014.15~22.04.1",
"6.8.0-1015.16~22.04.1",
"6.8.0-1016.17~22.04.2",
"6.8.0-1017.18~22.04.1",
"6.8.0-1018.19~22.04.1",
"6.8.0-1019.21~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-azure-cloud-tools-5.15.0-1075",
"binary_version": "5.15.0-1075.84"
},
{
"binary_name": "linux-azure-headers-5.15.0-1075",
"binary_version": "5.15.0-1075.84"
},
{
"binary_name": "linux-azure-tools-5.15.0-1075",
"binary_version": "5.15.0-1075.84"
},
{
"binary_name": "linux-buildinfo-5.15.0-1075-azure",
"binary_version": "5.15.0-1075.84"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1075-azure",
"binary_version": "5.15.0-1075.84"
},
{
"binary_name": "linux-headers-5.15.0-1075-azure",
"binary_version": "5.15.0-1075.84"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1075-azure",
"binary_version": "5.15.0-1075.84"
},
{
"binary_name": "linux-modules-5.15.0-1075-azure",
"binary_version": "5.15.0-1075.84"
},
{
"binary_name": "linux-modules-extra-5.15.0-1075-azure",
"binary_version": "5.15.0-1075.84"
},
{
"binary_name": "linux-modules-involflt-5.15.0-1075-azure",
"binary_version": "5.15.0-1075.84"
},
{
"binary_name": "linux-tools-5.15.0-1075-azure",
"binary_version": "5.15.0-1075.84"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-azure",
"purl": "pkg:deb/ubuntu/linux-azure@5.15.0-1075.84?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1075.84"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-1006.7",
"5.15.0-1001.2",
"5.15.0-1002.3",
"5.15.0-1003.4",
"5.15.0-1005.6",
"5.15.0-1007.8",
"5.15.0-1008.9",
"5.15.0-1010.12",
"5.15.0-1012.15",
"5.15.0-1013.16",
"5.15.0-1014.17",
"5.15.0-1017.20",
"5.15.0-1019.24",
"5.15.0-1020.25",
"5.15.0-1021.26",
"5.15.0-1022.27",
"5.15.0-1023.29",
"5.15.0-1024.30",
"5.15.0-1029.36",
"5.15.0-1030.37",
"5.15.0-1031.38",
"5.15.0-1033.40",
"5.15.0-1034.41",
"5.15.0-1035.42",
"5.15.0-1036.43",
"5.15.0-1037.44",
"5.15.0-1038.45",
"5.15.0-1039.46",
"5.15.0-1040.47",
"5.15.0-1041.48",
"5.15.0-1042.49",
"5.15.0-1044.51",
"5.15.0-1045.52",
"5.15.0-1046.53",
"5.15.0-1047.54",
"5.15.0-1049.56",
"5.15.0-1050.57",
"5.15.0-1051.59",
"5.15.0-1052.60",
"5.15.0-1053.61",
"5.15.0-1054.62",
"5.15.0-1056.64",
"5.15.0-1057.65",
"5.15.0-1058.66",
"5.15.0-1059.67",
"5.15.0-1060.69",
"5.15.0-1061.70",
"5.15.0-1063.72",
"5.15.0-1064.73",
"5.15.0-1066.75",
"5.15.0-1067.76",
"5.15.0-1068.77",
"5.15.0-1070.79",
"5.15.0-1071.80",
"5.15.0-1072.81",
"5.15.0-1073.82",
"5.15.0-1074.83"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-azure-5.19-cloud-tools-5.19.0-1027",
"binary_version": "5.19.0-1027.30~22.04.2"
},
{
"binary_name": "linux-azure-5.19-headers-5.19.0-1027",
"binary_version": "5.19.0-1027.30~22.04.2"
},
{
"binary_name": "linux-azure-5.19-tools-5.19.0-1027",
"binary_version": "5.19.0-1027.30~22.04.2"
},
{
"binary_name": "linux-buildinfo-5.19.0-1027-azure",
"binary_version": "5.19.0-1027.30~22.04.2"
},
{
"binary_name": "linux-cloud-tools-5.19.0-1027-azure",
"binary_version": "5.19.0-1027.30~22.04.2"
},
{
"binary_name": "linux-headers-5.19.0-1027-azure",
"binary_version": "5.19.0-1027.30~22.04.2"
},
{
"binary_name": "linux-image-unsigned-5.19.0-1027-azure",
"binary_version": "5.19.0-1027.30~22.04.2"
},
{
"binary_name": "linux-modules-5.19.0-1027-azure",
"binary_version": "5.19.0-1027.30~22.04.2"
},
{
"binary_name": "linux-modules-extra-5.19.0-1027-azure",
"binary_version": "5.19.0-1027.30~22.04.2"
},
{
"binary_name": "linux-tools-5.19.0-1027-azure",
"binary_version": "5.19.0-1027.30~22.04.2"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-azure-5.19",
"purl": "pkg:deb/ubuntu/linux-azure-5.19@5.19.0-1027.30~22.04.2?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.19.0-1020.21~22.04.1",
"5.19.0-1021.22~22.04.1",
"5.19.0-1022.23~22.04.1",
"5.19.0-1023.24~22.04.1",
"5.19.0-1025.28~22.04.1",
"5.19.0-1026.29~22.04.1",
"5.19.0-1027.30~22.04.2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-azure-6.2-cloud-tools-6.2.0-1019",
"binary_version": "6.2.0-1019.19~22.04.1"
},
{
"binary_name": "linux-azure-6.2-headers-6.2.0-1019",
"binary_version": "6.2.0-1019.19~22.04.1"
},
{
"binary_name": "linux-azure-6.2-tools-6.2.0-1019",
"binary_version": "6.2.0-1019.19~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.2.0-1019-azure",
"binary_version": "6.2.0-1019.19~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.2.0-1019-azure",
"binary_version": "6.2.0-1019.19~22.04.1"
},
{
"binary_name": "linux-headers-6.2.0-1019-azure",
"binary_version": "6.2.0-1019.19~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.2.0-1019-azure",
"binary_version": "6.2.0-1019.19~22.04.1"
},
{
"binary_name": "linux-modules-6.2.0-1019-azure",
"binary_version": "6.2.0-1019.19~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.2.0-1019-azure",
"binary_version": "6.2.0-1019.19~22.04.1"
},
{
"binary_name": "linux-tools-6.2.0-1019-azure",
"binary_version": "6.2.0-1019.19~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-azure-6.2",
"purl": "pkg:deb/ubuntu/linux-azure-6.2@6.2.0-1019.19~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.2.0-1005.5~22.04.1",
"6.2.0-1006.6~22.04.1",
"6.2.0-1007.7~22.04.1",
"6.2.0-1008.8~22.04.1",
"6.2.0-1009.9~22.04.3",
"6.2.0-1011.11~22.04.1",
"6.2.0-1012.12~22.04.1",
"6.2.0-1014.14~22.04.1",
"6.2.0-1015.15~22.04.1",
"6.2.0-1016.16~22.04.1",
"6.2.0-1017.17~22.04.1",
"6.2.0-1018.18~22.04.1",
"6.2.0-1019.19~22.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-azure-6.5-cloud-tools-6.5.0-1025",
"binary_version": "6.5.0-1025.26~22.04.1"
},
{
"binary_name": "linux-azure-6.5-headers-6.5.0-1025",
"binary_version": "6.5.0-1025.26~22.04.1"
},
{
"binary_name": "linux-azure-6.5-tools-6.5.0-1025",
"binary_version": "6.5.0-1025.26~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.5.0-1025-azure",
"binary_version": "6.5.0-1025.26~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.5.0-1025-azure",
"binary_version": "6.5.0-1025.26~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-1025-azure",
"binary_version": "6.5.0-1025.26~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.5.0-1025-azure",
"binary_version": "6.5.0-1025.26~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-1025-azure",
"binary_version": "6.5.0-1025.26~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.5.0-1025-azure",
"binary_version": "6.5.0-1025.26~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-1025-azure",
"binary_version": "6.5.0-1025.26~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-azure-6.5",
"purl": "pkg:deb/ubuntu/linux-azure-6.5@6.5.0-1025.26~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-1007.7~22.04.1",
"6.5.0-1009.9~22.04.1",
"6.5.0-1010.10~22.04.1",
"6.5.0-1011.11~22.04.1",
"6.5.0-1015.15~22.04.1",
"6.5.0-1016.16~22.04.1",
"6.5.0-1017.17~22.04.1",
"6.5.0-1018.19~22.04.2",
"6.5.0-1019.20~22.04.1",
"6.5.0-1021.22~22.04.1",
"6.5.0-1022.23~22.04.1",
"6.5.0-1023.24~22.04.1",
"6.5.0-1024.25~22.04.1",
"6.5.0-1025.26~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-azure-6.8-cloud-tools-6.8.0-1020",
"binary_version": "6.8.0-1020.23~22.04.1"
},
{
"binary_name": "linux-azure-6.8-headers-6.8.0-1020",
"binary_version": "6.8.0-1020.23~22.04.1"
},
{
"binary_name": "linux-azure-6.8-tools-6.8.0-1020",
"binary_version": "6.8.0-1020.23~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23~22.04.1"
},
{
"binary_name": "linux-modules-involflt-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-azure-6.8",
"purl": "pkg:deb/ubuntu/linux-azure-6.8@6.8.0-1020.23~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1020.23~22.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1008.8~22.04.1",
"6.8.0-1009.9~22.04.1",
"6.8.0-1010.10~22.04.1",
"6.8.0-1012.14~22.04.1",
"6.8.0-1013.15~22.04.1",
"6.8.0-1014.16~22.04.1",
"6.8.0-1015.17~22.04.2",
"6.8.0-1017.20~22.04.1",
"6.8.0-1018.21~22.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-azure-fde-cloud-tools-5.15.0-1120",
"binary_version": "5.15.0-1120.129"
},
{
"binary_name": "linux-azure-fde-headers-5.15.0-1120",
"binary_version": "5.15.0-1120.129"
},
{
"binary_name": "linux-azure-fde-tools-5.15.0-1120",
"binary_version": "5.15.0-1120.129"
},
{
"binary_name": "linux-buildinfo-5.15.0-1120-azure-fde",
"binary_version": "5.15.0-1120.129"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1120-azure-fde",
"binary_version": "5.15.0-1120.129"
},
{
"binary_name": "linux-headers-5.15.0-1120-azure-fde",
"binary_version": "5.15.0-1120.129"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1120-azure-fde",
"binary_version": "5.15.0-1120.129"
},
{
"binary_name": "linux-modules-5.15.0-1120-azure-fde",
"binary_version": "5.15.0-1120.129"
},
{
"binary_name": "linux-modules-extra-5.15.0-1120-azure-fde",
"binary_version": "5.15.0-1120.129"
},
{
"binary_name": "linux-modules-involflt-5.15.0-1120-azure-fde",
"binary_version": "5.15.0-1120.129"
},
{
"binary_name": "linux-tools-5.15.0-1120-azure-fde",
"binary_version": "5.15.0-1120.129"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-azure-fde",
"purl": "pkg:deb/ubuntu/linux-azure-fde@5.15.0-1120.129?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1019.24.1",
"5.15.0-1024.30.1",
"5.15.0-1029.36.1",
"5.15.0-1030.37.1",
"5.15.0-1031.38.1",
"5.15.0-1033.40.1",
"5.15.0-1034.41.1",
"5.15.0-1035.42.1",
"5.15.0-1036.43.1",
"5.15.0-1037.44.1",
"5.15.0-1038.45.1",
"5.15.0-1039.46.1",
"5.15.0-1041.48.1",
"5.15.0-1042.49.1",
"5.15.0-1044.51.1",
"5.15.0-1045.52.1",
"5.15.0-1046.53.1",
"5.15.0-1047.54.1",
"5.15.0-1049.56.1",
"5.15.0-1050.57.1",
"5.15.0-1051.59.1",
"5.15.0-1052.60.1",
"5.15.0-1053.61.1",
"5.15.0-1054.62.1",
"5.15.0-1056.64.1",
"5.15.0-1057.65.1",
"5.15.0-1058.66.1",
"5.15.0-1059.67.1",
"5.15.0-1060.69.1",
"5.15.0-1061.70.1",
"5.15.0-1063.72.1",
"5.15.0-1064.73.1",
"5.15.0-1065.74.1",
"5.15.0-1067.76.1",
"5.15.0-1068.77.1",
"5.15.0-1070.79.1",
"5.15.0-1071.80.1",
"5.15.0-1072.81.1",
"5.15.0-1073.82.1",
"5.15.0-1076.85.1",
"5.15.0-1078.87.1",
"5.15.0-1081.90.1",
"5.15.0-1082.91.1",
"5.15.0-1084.93.1",
"5.15.0-1086.95.1",
"5.15.0-1087.96.1",
"5.15.0-1088.97.1",
"5.15.0-1089.98.1",
"5.15.0-1090.99.1",
"5.15.0-1091.100.1",
"5.15.0-1092.101.1",
"5.15.0-1094.103.1",
"5.15.0-1095.104.1",
"5.15.0-1096.105.1",
"5.15.0-1097.106.1",
"5.15.0-1098.107.1",
"5.15.0-1102.111.1",
"5.15.0-1109.118.1",
"5.15.0-1110.119.1",
"5.15.0-1111.120.1",
"5.15.0-1114.123",
"5.15.0-1116.125",
"5.15.0-1117.126",
"5.15.0-1118.127",
"5.15.0-1119.128",
"5.15.0-1120.129"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-image-unsigned-5.19.0-1027-azure-fde",
"binary_version": "5.19.0-1027.30~22.04.2.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-azure-fde-5.19",
"purl": "pkg:deb/ubuntu/linux-azure-fde-5.19@5.19.0-1027.30~22.04.2.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.19.0-1025.28~22.04.1.1",
"5.19.0-1026.29~22.04.1.1",
"5.19.0-1027.30~22.04.2.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-image-unsigned-6.2.0-1019-azure-fde",
"binary_version": "6.2.0-1019.19~22.04.1.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-azure-fde-6.2",
"purl": "pkg:deb/ubuntu/linux-azure-fde-6.2@6.2.0-1019.19~22.04.1.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.2.0-1008.8~22.04.1.1",
"6.2.0-1009.9~22.04.3.1",
"6.2.0-1011.11~22.04.1.1",
"6.2.0-1012.12~22.04.1.1",
"6.2.0-1014.14~22.04.1.1",
"6.2.0-1015.15~22.04.1.1",
"6.2.0-1016.16~22.04.1.1",
"6.2.0-1017.17~22.04.1.1",
"6.2.0-1018.18~22.04.1.1",
"6.2.0-1019.19~22.04.1.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1071-gcp",
"binary_version": "5.15.0-1071.79"
},
{
"binary_name": "linux-gcp-headers-5.15.0-1071",
"binary_version": "5.15.0-1071.79"
},
{
"binary_name": "linux-gcp-tools-5.15.0-1071",
"binary_version": "5.15.0-1071.79"
},
{
"binary_name": "linux-headers-5.15.0-1071-gcp",
"binary_version": "5.15.0-1071.79"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1071-gcp",
"binary_version": "5.15.0-1071.79"
},
{
"binary_name": "linux-modules-5.15.0-1071-gcp",
"binary_version": "5.15.0-1071.79"
},
{
"binary_name": "linux-modules-extra-5.15.0-1071-gcp",
"binary_version": "5.15.0-1071.79"
},
{
"binary_name": "linux-tools-5.15.0-1071-gcp",
"binary_version": "5.15.0-1071.79"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-gcp",
"purl": "pkg:deb/ubuntu/linux-gcp@5.15.0-1071.79?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1071.79"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-1005.6",
"5.15.0-1001.3",
"5.15.0-1002.5",
"5.15.0-1003.6",
"5.15.0-1004.7",
"5.15.0-1005.8",
"5.15.0-1006.9",
"5.15.0-1008.12",
"5.15.0-1010.15",
"5.15.0-1013.18",
"5.15.0-1016.21",
"5.15.0-1017.23",
"5.15.0-1018.24",
"5.15.0-1019.25",
"5.15.0-1021.28",
"5.15.0-1022.29",
"5.15.0-1025.32",
"5.15.0-1026.33",
"5.15.0-1027.34",
"5.15.0-1029.36",
"5.15.0-1030.37",
"5.15.0-1031.38",
"5.15.0-1032.40",
"5.15.0-1034.42",
"5.15.0-1035.43",
"5.15.0-1036.44",
"5.15.0-1037.45",
"5.15.0-1038.46",
"5.15.0-1039.47",
"5.15.0-1040.48",
"5.15.0-1041.49",
"5.15.0-1042.50",
"5.15.0-1044.52",
"5.15.0-1045.53",
"5.15.0-1046.54",
"5.15.0-1047.55",
"5.15.0-1048.56",
"5.15.0-1049.57",
"5.15.0-1051.59",
"5.15.0-1052.60",
"5.15.0-1053.61",
"5.15.0-1054.62",
"5.15.0-1055.63",
"5.15.0-1058.66",
"5.15.0-1059.67",
"5.15.0-1060.68",
"5.15.0-1062.70",
"5.15.0-1063.71",
"5.15.0-1064.72",
"5.15.0-1065.73",
"5.15.0-1066.74",
"5.15.0-1067.75",
"5.15.0-1068.76",
"5.15.0-1069.77",
"5.15.0-1070.78"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.19.0-1030-gcp",
"binary_version": "5.19.0-1030.32~22.04.1"
},
{
"binary_name": "linux-gcp-5.19-headers-5.19.0-1030",
"binary_version": "5.19.0-1030.32~22.04.1"
},
{
"binary_name": "linux-gcp-5.19-tools-5.19.0-1030",
"binary_version": "5.19.0-1030.32~22.04.1"
},
{
"binary_name": "linux-headers-5.19.0-1030-gcp",
"binary_version": "5.19.0-1030.32~22.04.1"
},
{
"binary_name": "linux-image-unsigned-5.19.0-1030-gcp",
"binary_version": "5.19.0-1030.32~22.04.1"
},
{
"binary_name": "linux-modules-5.19.0-1030-gcp",
"binary_version": "5.19.0-1030.32~22.04.1"
},
{
"binary_name": "linux-modules-extra-5.19.0-1030-gcp",
"binary_version": "5.19.0-1030.32~22.04.1"
},
{
"binary_name": "linux-tools-5.19.0-1030-gcp",
"binary_version": "5.19.0-1030.32~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-gcp-5.19",
"purl": "pkg:deb/ubuntu/linux-gcp-5.19@5.19.0-1030.32~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.19.0-1020.22~22.04.2",
"5.19.0-1021.23~22.04.1",
"5.19.0-1022.24~22.04.1",
"5.19.0-1024.26~22.04.1",
"5.19.0-1025.27~22.04.1",
"5.19.0-1026.28~22.04.1",
"5.19.0-1027.29~22.04.1",
"5.19.0-1030.32~22.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.2.0-1021-gcp",
"binary_version": "6.2.0-1021.23~22.04.1"
},
{
"binary_name": "linux-gcp-6.2-headers-6.2.0-1021",
"binary_version": "6.2.0-1021.23~22.04.1"
},
{
"binary_name": "linux-gcp-6.2-tools-6.2.0-1021",
"binary_version": "6.2.0-1021.23~22.04.1"
},
{
"binary_name": "linux-headers-6.2.0-1021-gcp",
"binary_version": "6.2.0-1021.23~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.2.0-1021-gcp",
"binary_version": "6.2.0-1021.23~22.04.1"
},
{
"binary_name": "linux-modules-6.2.0-1021-gcp",
"binary_version": "6.2.0-1021.23~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.2.0-1021-gcp",
"binary_version": "6.2.0-1021.23~22.04.1"
},
{
"binary_name": "linux-tools-6.2.0-1021-gcp",
"binary_version": "6.2.0-1021.23~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-gcp-6.2",
"purl": "pkg:deb/ubuntu/linux-gcp-6.2@6.2.0-1021.23~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.2.0-1009.9~22.04.3",
"6.2.0-1010.10~22.04.1",
"6.2.0-1011.11~22.04.1",
"6.2.0-1011.11~22.04.3",
"6.2.0-1012.12~22.04.1",
"6.2.0-1013.13~22.04.1",
"6.2.0-1014.14~22.04.1",
"6.2.0-1016.18~22.04.1",
"6.2.0-1017.19~22.04.1",
"6.2.0-1018.20~22.04.1",
"6.2.0-1019.21~22.04.1",
"6.2.0-1021.23~22.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.5.0-1025-gcp",
"binary_version": "6.5.0-1025.27~22.04.1"
},
{
"binary_name": "linux-gcp-6.5-headers-6.5.0-1025",
"binary_version": "6.5.0-1025.27~22.04.1"
},
{
"binary_name": "linux-gcp-6.5-tools-6.5.0-1025",
"binary_version": "6.5.0-1025.27~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-1025-gcp",
"binary_version": "6.5.0-1025.27~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.5.0-1025-gcp",
"binary_version": "6.5.0-1025.27~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-1025-gcp",
"binary_version": "6.5.0-1025.27~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.5.0-1025-gcp",
"binary_version": "6.5.0-1025.27~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.5.0-1025-gcp",
"binary_version": "6.5.0-1025.27~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-1025-gcp",
"binary_version": "6.5.0-1025.27~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-gcp-6.5",
"purl": "pkg:deb/ubuntu/linux-gcp-6.5@6.5.0-1025.27~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-1010.10~22.04.3",
"6.5.0-1011.11~22.04.1",
"6.5.0-1013.13~22.04.1",
"6.5.0-1014.14~22.04.1",
"6.5.0-1015.15~22.04.1",
"6.5.0-1016.16~22.04.1",
"6.5.0-1017.17~22.04.1",
"6.5.0-1018.18~22.04.1",
"6.5.0-1020.20~22.04.1",
"6.5.0-1022.24~22.04.1",
"6.5.0-1023.25~22.04.1",
"6.5.0-1024.26~22.04.1",
"6.5.0-1025.27~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1019-gcp",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-gcp-6.8-headers-6.8.0-1019",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-gcp-6.8-tools-6.8.0-1019",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1019-gcp",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1019-gcp",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1019-gcp",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1019-gcp",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1019-gcp",
"binary_version": "6.8.0-1019.21~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-gcp-6.8",
"purl": "pkg:deb/ubuntu/linux-gcp-6.8@6.8.0-1019.21~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1019.21~22.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1010.11~22.04.1",
"6.8.0-1011.12~22.04.1",
"6.8.0-1012.13~22.04.1",
"6.8.0-1013.14~22.04.1",
"6.8.0-1014.16~22.04.1",
"6.8.0-1015.17~22.04.1",
"6.8.0-1016.18~22.04.1",
"6.8.0-1017.19~22.04.1",
"6.8.0-1018.20~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1069-gke",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-gke-headers-5.15.0-1069",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-gke-tools-5.15.0-1069",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-headers-5.15.0-1069-gke",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1069-gke",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-modules-5.15.0-1069-gke",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-modules-extra-5.15.0-1069-gke",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-tools-5.15.0-1069-gke",
"binary_version": "5.15.0-1069.75"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-gke",
"purl": "pkg:deb/ubuntu/linux-gke@5.15.0-1069.75?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1069.75"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1002.2",
"5.15.0-1003.3",
"5.15.0-1004.5",
"5.15.0-1005.6",
"5.15.0-1006.7",
"5.15.0-1008.10",
"5.15.0-1010.13",
"5.15.0-1011.14",
"5.15.0-1014.17",
"5.15.0-1015.18",
"5.15.0-1016.19",
"5.15.0-1017.20",
"5.15.0-1019.23",
"5.15.0-1020.25",
"5.15.0-1023.28",
"5.15.0-1024.29",
"5.15.0-1027.32",
"5.15.0-1028.33",
"5.15.0-1030.35",
"5.15.0-1031.36",
"5.15.0-1032.37",
"5.15.0-1033.38",
"5.15.0-1034.39",
"5.15.0-1035.40",
"5.15.0-1036.41",
"5.15.0-1037.42",
"5.15.0-1038.43",
"5.15.0-1039.44",
"5.15.0-1040.45",
"5.15.0-1041.46",
"5.15.0-1042.47",
"5.15.0-1044.49",
"5.15.0-1045.50",
"5.15.0-1046.51",
"5.15.0-1047.52",
"5.15.0-1048.53",
"5.15.0-1049.54",
"5.15.0-1050.55",
"5.15.0-1051.56",
"5.15.0-1052.57",
"5.15.0-1053.58",
"5.15.0-1054.59",
"5.15.0-1057.62",
"5.15.0-1058.63",
"5.15.0-1059.64",
"5.15.0-1060.66",
"5.15.0-1061.67",
"5.15.0-1062.68",
"5.15.0-1063.69",
"5.15.0-1064.70",
"5.15.0-1065.71",
"5.15.0-1066.72",
"5.15.0-1067.73",
"5.15.0-1068.74"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1055-gkeop",
"binary_version": "5.15.0-1055.62"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1055-gkeop",
"binary_version": "5.15.0-1055.62"
},
{
"binary_name": "linux-gkeop-cloud-tools-5.15.0-1055",
"binary_version": "5.15.0-1055.62"
},
{
"binary_name": "linux-gkeop-headers-5.15.0-1055",
"binary_version": "5.15.0-1055.62"
},
{
"binary_name": "linux-gkeop-tools-5.15.0-1055",
"binary_version": "5.15.0-1055.62"
},
{
"binary_name": "linux-headers-5.15.0-1055-gkeop",
"binary_version": "5.15.0-1055.62"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1055-gkeop",
"binary_version": "5.15.0-1055.62"
},
{
"binary_name": "linux-modules-5.15.0-1055-gkeop",
"binary_version": "5.15.0-1055.62"
},
{
"binary_name": "linux-modules-extra-5.15.0-1055-gkeop",
"binary_version": "5.15.0-1055.62"
},
{
"binary_name": "linux-tools-5.15.0-1055-gkeop",
"binary_version": "5.15.0-1055.62"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-gkeop",
"purl": "pkg:deb/ubuntu/linux-gkeop@5.15.0-1055.62?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1055.62"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1001.2",
"5.15.0-1002.4",
"5.15.0-1003.5",
"5.15.0-1004.6",
"5.15.0-1005.7",
"5.15.0-1007.10",
"5.15.0-1008.12",
"5.15.0-1011.15",
"5.15.0-1012.16",
"5.15.0-1013.17",
"5.15.0-1015.19",
"5.15.0-1016.21",
"5.15.0-1017.22",
"5.15.0-1018.23",
"5.15.0-1019.24",
"5.15.0-1020.25",
"5.15.0-1021.26",
"5.15.0-1022.27",
"5.15.0-1023.28",
"5.15.0-1024.29",
"5.15.0-1025.30",
"5.15.0-1026.31",
"5.15.0-1027.32",
"5.15.0-1028.33",
"5.15.0-1030.35",
"5.15.0-1031.37",
"5.15.0-1032.38",
"5.15.0-1033.39",
"5.15.0-1034.40",
"5.15.0-1035.41",
"5.15.0-1036.42",
"5.15.0-1037.43",
"5.15.0-1038.44",
"5.15.0-1039.45",
"5.15.0-1040.46",
"5.15.0-1043.50",
"5.15.0-1044.51",
"5.15.0-1045.52",
"5.15.0-1046.53",
"5.15.0-1047.54",
"5.15.0-1048.55",
"5.15.0-1049.56",
"5.15.0-1050.57",
"5.15.0-1051.58",
"5.15.0-1052.59",
"5.15.0-1053.60",
"5.15.0-1054.61"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-buildinfo-5.19.0-50-generic-64k",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-buildinfo-5.19.0-50-generic-lpae",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-cloud-tools-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-headers-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-headers-5.19.0-50-generic-64k",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-headers-5.19.0-50-generic-lpae",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-hwe-5.19-cloud-tools-5.19.0-50",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-hwe-5.19-cloud-tools-common",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-hwe-5.19-headers-5.19.0-50",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-hwe-5.19-tools-5.19.0-50",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-hwe-5.19-tools-common",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-hwe-5.19-tools-host",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-image-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-image-5.19.0-50-generic-lpae",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-image-unsigned-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-image-unsigned-5.19.0-50-generic-64k",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-modules-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-modules-5.19.0-50-generic-64k",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-modules-5.19.0-50-generic-lpae",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-modules-extra-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-modules-ipu6-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-modules-ivsc-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-modules-iwlwifi-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-source-5.19.0",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-tools-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-tools-5.19.0-50-generic-64k",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-tools-5.19.0-50-generic-lpae",
"binary_version": "5.19.0-50.50"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-hwe-5.19",
"purl": "pkg:deb/ubuntu/linux-hwe-5.19@5.19.0-50.50?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.19.0-28.29~22.04.1",
"5.19.0-32.33~22.04.1",
"5.19.0-35.36~22.04.1",
"5.19.0-38.39~22.04.1",
"5.19.0-40.41~22.04.1",
"5.19.0-41.42~22.04.1",
"5.19.0-42.43~22.04.1",
"5.19.0-43.44~22.04.1",
"5.19.0-45.46~22.04.1",
"5.19.0-46.47~22.04.1",
"5.19.0-50.50"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.2.0-39-generic-64k",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.2.0-39-generic-lpae",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-headers-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-headers-6.2.0-39-generic-64k",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-headers-6.2.0-39-generic-lpae",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-hwe-6.2-cloud-tools-6.2.0-39",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-hwe-6.2-cloud-tools-common",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-hwe-6.2-headers-6.2.0-39",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-hwe-6.2-tools-6.2.0-39",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-hwe-6.2-tools-common",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-hwe-6.2-tools-host",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-image-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-image-6.2.0-39-generic-lpae",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.2.0-39-generic-64k",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-modules-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-modules-6.2.0-39-generic-64k",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-modules-6.2.0-39-generic-lpae",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-modules-ipu6-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-modules-ivsc-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-source-6.2.0",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-tools-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-tools-6.2.0-39-generic-64k",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-tools-6.2.0-39-generic-lpae",
"binary_version": "6.2.0-39.40~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-hwe-6.2",
"purl": "pkg:deb/ubuntu/linux-hwe-6.2@6.2.0-39.40~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.2.0-25.25~22.04.2",
"6.2.0-26.26~22.04.1",
"6.2.0-31.31~22.04.1",
"6.2.0-32.32~22.04.1",
"6.2.0-33.33~22.04.1",
"6.2.0-34.34~22.04.1",
"6.2.0-35.35~22.04.1",
"6.2.0-36.37~22.04.1",
"6.2.0-37.38~22.04.1",
"6.2.0-39.40~22.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.5.0-45-generic-64k",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-45-generic-64k",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-hwe-6.5-cloud-tools-6.5.0-45",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-hwe-6.5-cloud-tools-common",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-hwe-6.5-headers-6.5.0-45",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-hwe-6.5-tools-6.5.0-45",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-hwe-6.5-tools-common",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-hwe-6.5-tools-host",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-image-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.5.0-45-generic-64k",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-45-generic-64k",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-modules-ipu6-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-modules-ivsc-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-source-6.5.0",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-45-generic-64k",
"binary_version": "6.5.0-45.45~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-hwe-6.5",
"purl": "pkg:deb/ubuntu/linux-hwe-6.5@6.5.0-45.45~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-14.14~22.04.1",
"6.5.0-15.15~22.04.1",
"6.5.0-17.17~22.04.1",
"6.5.0-18.18~22.04.1",
"6.5.0-21.21~22.04.1",
"6.5.0-25.25~22.04.1",
"6.5.0-26.26~22.04.1",
"6.5.0-27.28~22.04.1",
"6.5.0-28.29~22.04.1",
"6.5.0-35.35~22.04.1",
"6.5.0-41.41~22.04.2",
"6.5.0-44.44~22.04.1",
"6.5.0-45.45~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-50-generic",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.8.0-50-generic-64k",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.8.0-50-generic",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-50-generic",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-50-generic-64k",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-hwe-6.8-cloud-tools-6.8.0-50",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-hwe-6.8-headers-6.8.0-50",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-hwe-6.8-tools-6.8.0-50",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-image-6.8.0-50-generic",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-50-generic",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-50-generic-64k",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-50-generic",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-50-generic-64k",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-50-generic",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-modules-ipu6-6.8.0-50-generic",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-50-generic",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-modules-usbio-6.8.0-50-generic",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-50-generic",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-50-generic-64k",
"binary_version": "6.8.0-50.51~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-hwe-6.8",
"purl": "pkg:deb/ubuntu/linux-hwe-6.8@6.8.0-50.51~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-50.51~22.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-38.38~22.04.1",
"6.8.0-39.39~22.04.1",
"6.8.0-40.40~22.04.3",
"6.8.0-45.45~22.04.1",
"6.8.0-47.47~22.04.1",
"6.8.0-48.48~22.04.1",
"6.8.0-49.49~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1065-ibm",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-headers-5.15.0-1065-ibm",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-ibm-cloud-tools-common",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-ibm-headers-5.15.0-1065",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-ibm-source-5.15.0",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-ibm-tools-5.15.0-1065",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-ibm-tools-common",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1065-ibm",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-modules-5.15.0-1065-ibm",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-modules-extra-5.15.0-1065-ibm",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-tools-5.15.0-1065-ibm",
"binary_version": "5.15.0-1065.68"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-ibm",
"purl": "pkg:deb/ubuntu/linux-ibm@5.15.0-1065.68?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1065.68"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1002.2",
"5.15.0-1003.3",
"5.15.0-1004.4",
"5.15.0-1005.5",
"5.15.0-1007.8",
"5.15.0-1009.11",
"5.15.0-1010.12",
"5.15.0-1012.14",
"5.15.0-1013.15",
"5.15.0-1015.17",
"5.15.0-1017.20",
"5.15.0-1018.21",
"5.15.0-1021.24",
"5.15.0-1022.25",
"5.15.0-1023.26",
"5.15.0-1025.28",
"5.15.0-1026.29",
"5.15.0-1027.30",
"5.15.0-1028.31",
"5.15.0-1029.32",
"5.15.0-1030.33",
"5.15.0-1031.34",
"5.15.0-1032.35",
"5.15.0-1033.36",
"5.15.0-1034.37",
"5.15.0-1035.38",
"5.15.0-1036.39",
"5.15.0-1037.40",
"5.15.0-1038.41",
"5.15.0-1040.43",
"5.15.0-1041.44",
"5.15.0-1042.45",
"5.15.0-1043.46",
"5.15.0-1044.47",
"5.15.0-1045.48",
"5.15.0-1046.49",
"5.15.0-1047.50",
"5.15.0-1048.51",
"5.15.0-1049.52",
"5.15.0-1050.53",
"5.15.0-1053.56",
"5.15.0-1054.57",
"5.15.0-1055.58",
"5.15.0-1056.59",
"5.15.0-1057.60",
"5.15.0-1058.61",
"5.15.0-1059.62",
"5.15.0-1060.63",
"5.15.0-1061.64",
"5.15.0-1062.65",
"5.15.0-1063.66",
"5.15.0-1064.67"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1017-ibm",
"binary_version": "6.8.0-1017.17~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1017-ibm",
"binary_version": "6.8.0-1017.17~22.04.1"
},
{
"binary_name": "linux-ibm-6.8-headers-6.8.0-1017",
"binary_version": "6.8.0-1017.17~22.04.1"
},
{
"binary_name": "linux-ibm-6.8-source-6.8.0",
"binary_version": "6.8.0-1017.17~22.04.1"
},
{
"binary_name": "linux-ibm-6.8-tools-6.8.0-1017",
"binary_version": "6.8.0-1017.17~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1017-ibm",
"binary_version": "6.8.0-1017.17~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1017-ibm",
"binary_version": "6.8.0-1017.17~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1017-ibm",
"binary_version": "6.8.0-1017.17~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-1017-ibm",
"binary_version": "6.8.0-1017.17~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1017-ibm",
"binary_version": "6.8.0-1017.17~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-ibm-6.8",
"purl": "pkg:deb/ubuntu/linux-ibm-6.8@6.8.0-1017.17~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1017.17~22.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1008.8~22.04.1",
"6.8.0-1010.10~22.04.1",
"6.8.0-1011.11~22.04.1",
"6.8.0-1012.12~22.04.1",
"6.8.0-1013.13~22.04.1",
"6.8.0-1014.14~22.04.1",
"6.8.0-1015.15~22.04.1",
"6.8.0-1016.16~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-headers-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-intel-iotg-cloud-tools-5.15.0-1067",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-intel-iotg-cloud-tools-common",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-intel-iotg-headers-5.15.0-1067",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-intel-iotg-tools-5.15.0-1067",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-intel-iotg-tools-common",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-intel-iotg-tools-host",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-modules-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-modules-extra-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-tools-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-intel-iotg",
"purl": "pkg:deb/ubuntu/linux-intel-iotg@5.15.0-1067.73?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1067.73"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1004.6",
"5.15.0-1008.11",
"5.15.0-1010.14",
"5.15.0-1013.17",
"5.15.0-1015.20",
"5.15.0-1016.21",
"5.15.0-1017.22",
"5.15.0-1018.23",
"5.15.0-1021.26",
"5.15.0-1023.28",
"5.15.0-1025.30",
"5.15.0-1026.31",
"5.15.0-1027.32",
"5.15.0-1028.33",
"5.15.0-1030.35",
"5.15.0-1031.36",
"5.15.0-1033.38",
"5.15.0-1034.39",
"5.15.0-1035.40",
"5.15.0-1036.41",
"5.15.0-1037.42",
"5.15.0-1038.43",
"5.15.0-1039.45",
"5.15.0-1040.46",
"5.15.0-1043.49",
"5.15.0-1045.51",
"5.15.0-1046.52",
"5.15.0-1047.53",
"5.15.0-1048.54",
"5.15.0-1049.55",
"5.15.0-1050.56",
"5.15.0-1051.57",
"5.15.0-1052.58",
"5.15.0-1055.61",
"5.15.0-1057.63",
"5.15.0-1058.64",
"5.15.0-1059.65",
"5.15.0-1060.66",
"5.15.0-1061.67",
"5.15.0-1062.68",
"5.15.0-1063.69",
"5.15.0-1064.70",
"5.15.0-1065.71",
"5.15.0-1066.72"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1069-kvm",
"binary_version": "5.15.0-1069.74"
},
{
"binary_name": "linux-headers-5.15.0-1069-kvm",
"binary_version": "5.15.0-1069.74"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1069-kvm",
"binary_version": "5.15.0-1069.74"
},
{
"binary_name": "linux-kvm-headers-5.15.0-1069",
"binary_version": "5.15.0-1069.74"
},
{
"binary_name": "linux-kvm-tools-5.15.0-1069",
"binary_version": "5.15.0-1069.74"
},
{
"binary_name": "linux-modules-5.15.0-1069-kvm",
"binary_version": "5.15.0-1069.74"
},
{
"binary_name": "linux-tools-5.15.0-1069-kvm",
"binary_version": "5.15.0-1069.74"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-kvm",
"purl": "pkg:deb/ubuntu/linux-kvm@5.15.0-1069.74?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1069.74"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-1004.4",
"5.13.0-1006.6+22.04.1",
"5.13.0-1007.7+22.04.1",
"5.13.0-1010.11+22.04.1",
"5.15.0-1002.2",
"5.15.0-1004.4",
"5.15.0-1005.5",
"5.15.0-1007.7",
"5.15.0-1008.8",
"5.15.0-1010.11",
"5.15.0-1012.14",
"5.15.0-1013.16",
"5.15.0-1016.19",
"5.15.0-1017.21",
"5.15.0-1018.22",
"5.15.0-1019.23",
"5.15.0-1020.24",
"5.15.0-1021.26",
"5.15.0-1024.29",
"5.15.0-1025.30",
"5.15.0-1026.31",
"5.15.0-1028.33",
"5.15.0-1029.34",
"5.15.0-1030.35",
"5.15.0-1031.36",
"5.15.0-1032.37",
"5.15.0-1033.38",
"5.15.0-1034.39",
"5.15.0-1035.40",
"5.15.0-1037.42",
"5.15.0-1038.43",
"5.15.0-1039.44",
"5.15.0-1040.45",
"5.15.0-1041.46",
"5.15.0-1042.47",
"5.15.0-1044.49",
"5.15.0-1045.50",
"5.15.0-1046.51",
"5.15.0-1047.52",
"5.15.0-1048.53",
"5.15.0-1049.54",
"5.15.0-1050.55",
"5.15.0-1051.56",
"5.15.0-1052.57",
"5.15.0-1053.58",
"5.15.0-1054.59",
"5.15.0-1057.62",
"5.15.0-1058.63",
"5.15.0-1059.64",
"5.15.0-1060.65",
"5.15.0-1061.66",
"5.15.0-1062.67",
"5.15.0-1063.68",
"5.15.0-1064.69",
"5.15.0-1065.70",
"5.15.0-1066.71",
"5.15.0-1067.72",
"5.15.0-1068.73"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-125-lowlatency",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-buildinfo-5.15.0-125-lowlatency-64k",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-cloud-tools-5.15.0-125-lowlatency",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-headers-5.15.0-125-lowlatency",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-headers-5.15.0-125-lowlatency-64k",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-image-unsigned-5.15.0-125-lowlatency",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-image-unsigned-5.15.0-125-lowlatency-64k",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-lowlatency-cloud-tools-5.15.0-125",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-lowlatency-cloud-tools-common",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-lowlatency-headers-5.15.0-125",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-lowlatency-tools-5.15.0-125",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-lowlatency-tools-common",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-lowlatency-tools-host",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-modules-5.15.0-125-lowlatency",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-modules-5.15.0-125-lowlatency-64k",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-125-lowlatency",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-tools-5.15.0-125-lowlatency",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-tools-5.15.0-125-lowlatency-64k",
"binary_version": "5.15.0-125.135"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-lowlatency",
"purl": "pkg:deb/ubuntu/linux-lowlatency@5.15.0-125.135?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-125.135"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-22.22",
"5.15.0-23.23",
"5.15.0-24.24",
"5.15.0-27.28",
"5.15.0-30.31",
"5.15.0-33.34",
"5.15.0-35.36",
"5.15.0-37.39",
"5.15.0-39.42",
"5.15.0-40.43",
"5.15.0-41.44",
"5.15.0-43.46",
"5.15.0-46.49",
"5.15.0-47.53",
"5.15.0-48.54",
"5.15.0-50.56",
"5.15.0-52.58",
"5.15.0-53.59",
"5.15.0-56.62",
"5.15.0-57.63",
"5.15.0-58.64",
"5.15.0-60.66",
"5.15.0-67.74",
"5.15.0-69.76",
"5.15.0-70.77",
"5.15.0-71.78",
"5.15.0-72.79",
"5.15.0-73.80",
"5.15.0-75.82",
"5.15.0-76.83",
"5.15.0-78.85",
"5.15.0-79.88",
"5.15.0-82.91",
"5.15.0-83.92",
"5.15.0-84.93",
"5.15.0-86.95",
"5.15.0-87.96",
"5.15.0-88.98",
"5.15.0-89.99",
"5.15.0-91.101",
"5.15.0-92.102",
"5.15.0-94.104",
"5.15.0-97.107",
"5.15.0-100.110",
"5.15.0-101.111",
"5.15.0-102.112",
"5.15.0-105.115",
"5.15.0-106.116",
"5.15.0-107.117",
"5.15.0-110.120",
"5.15.0-113.123",
"5.15.0-116.126",
"5.15.0-117.127",
"5.15.0-118.128",
"5.15.0-119.129",
"5.15.0-121.131",
"5.15.0-122.132",
"5.15.0-124.134"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.19.0-1030-lowlatency",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-buildinfo-5.19.0-1030-lowlatency-64k",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-cloud-tools-5.19.0-1030-lowlatency",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-headers-5.19.0-1030-lowlatency",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-headers-5.19.0-1030-lowlatency-64k",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-image-unsigned-5.19.0-1030-lowlatency",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-image-unsigned-5.19.0-1030-lowlatency-64k",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-lowlatency-hwe-5.19-cloud-tools-5.19.0-1030",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-lowlatency-hwe-5.19-cloud-tools-common",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-lowlatency-hwe-5.19-headers-5.19.0-1030",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-lowlatency-hwe-5.19-tools-5.19.0-1030",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-lowlatency-hwe-5.19-tools-common",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-lowlatency-hwe-5.19-tools-host",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-modules-5.19.0-1030-lowlatency",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-modules-5.19.0-1030-lowlatency-64k",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-modules-ipu6-5.19.0-1030-lowlatency",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-modules-ivsc-5.19.0-1030-lowlatency",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-modules-iwlwifi-5.19.0-1030-lowlatency",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-tools-5.19.0-1030-lowlatency",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-tools-5.19.0-1030-lowlatency-64k",
"binary_version": "5.19.0-1030.30"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-lowlatency-hwe-5.19",
"purl": "pkg:deb/ubuntu/linux-lowlatency-hwe-5.19@5.19.0-1030.30?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.19.0-1017.18~22.04.1",
"5.19.0-1018.19~22.04.1",
"5.19.0-1021.22~22.04.1",
"5.19.0-1022.23~22.04.1",
"5.19.0-1023.24~22.04.1",
"5.19.0-1024.25~22.04.1",
"5.19.0-1025.26~22.04.1",
"5.19.0-1027.28~22.04.1",
"5.19.0-1028.29~22.04.1",
"5.19.0-1030.30"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.2.0-1018-lowlatency",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.2.0-1018-lowlatency-64k",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.2.0-1018-lowlatency",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-headers-6.2.0-1018-lowlatency",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-headers-6.2.0-1018-lowlatency-64k",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.2.0-1018-lowlatency",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.2.0-1018-lowlatency-64k",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.2-cloud-tools-6.2.0-1018",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.2-cloud-tools-common",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.2-headers-6.2.0-1018",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.2-tools-6.2.0-1018",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.2-tools-common",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.2-tools-host",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-modules-6.2.0-1018-lowlatency",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-modules-6.2.0-1018-lowlatency-64k",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-modules-ipu6-6.2.0-1018-lowlatency",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-modules-ivsc-6.2.0-1018-lowlatency",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.2.0-1018-lowlatency",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-tools-6.2.0-1018-lowlatency",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-tools-6.2.0-1018-lowlatency-64k",
"binary_version": "6.2.0-1018.18~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-lowlatency-hwe-6.2",
"purl": "pkg:deb/ubuntu/linux-lowlatency-hwe-6.2@6.2.0-1018.18~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.2.0-1008.8~22.04.1",
"6.2.0-1009.9~22.04.1",
"6.2.0-1011.11~22.04.1",
"6.2.0-1012.12~22.04.1",
"6.2.0-1013.13~22.04.1",
"6.2.0-1014.14~22.04.1",
"6.2.0-1015.15~22.04.1",
"6.2.0-1016.16~22.04.1",
"6.2.0-1017.17~22.04.1",
"6.2.0-1018.18~22.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.5.0-45-lowlatency",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.5.0-45-lowlatency-64k",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.5.0-45-lowlatency",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-45-lowlatency",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-45-lowlatency-64k",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.5.0-45-lowlatency",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.5.0-45-lowlatency-64k",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.5-cloud-tools-6.5.0-45",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.5-cloud-tools-common",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.5-headers-6.5.0-45",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.5-lib-rust-6.5.0-45-lowlatency",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.5-tools-6.5.0-45",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.5-tools-common",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.5-tools-host",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-45-lowlatency",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-45-lowlatency-64k",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.5.0-45-lowlatency",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-45-lowlatency",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-45-lowlatency-64k",
"binary_version": "6.5.0-45.45.1~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-lowlatency-hwe-6.5",
"purl": "pkg:deb/ubuntu/linux-lowlatency-hwe-6.5@6.5.0-45.45.1~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-14.14.1~22.04.1",
"6.5.0-15.15.1.1~22.04.1",
"6.5.0-17.17.1.1.1~22.04.1",
"6.5.0-21.21.1~22.04.1",
"6.5.0-25.25.1~22.04.1",
"6.5.0-26.26.1~22.04.1",
"6.5.0-27.28.1~22.04.1",
"6.5.0-28.29.1~22.04.1",
"6.5.0-35.35.1~22.04.1",
"6.5.0-41.41.1~22.04.1",
"6.5.0-42.42.1~22.04.1",
"6.5.0-44.44.1~22.04.1",
"6.5.0-45.45.1~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.8.0-50-lowlatency-64k",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-50-lowlatency-64k",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-50-lowlatency-64k",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.8-cloud-tools-6.8.0-50",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.8-headers-6.8.0-50",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.8-lib-rust-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.8-tools-6.8.0-50",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-50-lowlatency-64k",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-50-lowlatency-64k",
"binary_version": "6.8.0-50.51.1~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-lowlatency-hwe-6.8",
"purl": "pkg:deb/ubuntu/linux-lowlatency-hwe-6.8@6.8.0-50.51.1~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-50.51.1~22.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-38.38.1~22.04.2",
"6.8.0-40.40.1~22.04.1",
"6.8.0-44.44.1~22.04.1",
"6.8.0-45.45.1~22.04.1",
"6.8.0-47.47.1~22.04.1",
"6.8.0-48.48.3~22.04.1",
"6.8.0-49.49.1~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1067-nvidia",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-buildinfo-5.15.0-1067-nvidia-lowlatency",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1067-nvidia",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1067-nvidia-lowlatency",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-headers-5.15.0-1067-nvidia",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-headers-5.15.0-1067-nvidia-lowlatency",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1067-nvidia",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1067-nvidia-lowlatency",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-modules-5.15.0-1067-nvidia",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-modules-5.15.0-1067-nvidia-lowlatency",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-modules-extra-5.15.0-1067-nvidia",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-modules-nvidia-fs-5.15.0-1067-nvidia",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-modules-nvidia-fs-5.15.0-1067-nvidia-lowlatency",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-nvidia-cloud-tools-5.15.0-1067",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-nvidia-cloud-tools-common",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-nvidia-headers-5.15.0-1067",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-nvidia-tools-5.15.0-1067",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-nvidia-tools-common",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-nvidia-tools-host",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-tools-5.15.0-1067-nvidia",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-tools-5.15.0-1067-nvidia-lowlatency",
"binary_version": "5.15.0-1067.68"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-nvidia",
"purl": "pkg:deb/ubuntu/linux-nvidia@5.15.0-1067.68?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1067.68"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1005.5",
"5.15.0-1007.7",
"5.15.0-1010.10",
"5.15.0-1015.15",
"5.15.0-1017.17",
"5.15.0-1018.18",
"5.15.0-1023.23",
"5.15.0-1025.25",
"5.15.0-1026.26",
"5.15.0-1027.27",
"5.15.0-1028.28",
"5.15.0-1029.29",
"5.15.0-1030.30",
"5.15.0-1031.31",
"5.15.0-1032.32",
"5.15.0-1033.33",
"5.15.0-1037.37",
"5.15.0-1039.39",
"5.15.0-1040.40",
"5.15.0-1041.41",
"5.15.0-1042.42",
"5.15.0-1043.43",
"5.15.0-1044.44",
"5.15.0-1045.45",
"5.15.0-1046.46",
"5.15.0-1047.47",
"5.15.0-1048.48",
"5.15.0-1053.54",
"5.15.0-1054.55",
"5.15.0-1055.56",
"5.15.0-1058.59",
"5.15.0-1059.60",
"5.15.0-1060.61",
"5.15.0-1061.62",
"5.15.0-1062.63",
"5.15.0-1063.64",
"5.15.0-1064.65",
"5.15.0-1065.66",
"5.15.0-1066.67"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.2.0-1015-nvidia",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-buildinfo-6.2.0-1015-nvidia-64k",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-headers-6.2.0-1015-nvidia",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-headers-6.2.0-1015-nvidia-64k",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-image-unsigned-6.2.0-1015-nvidia",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-image-unsigned-6.2.0-1015-nvidia-64k",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-modules-6.2.0-1015-nvidia",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-modules-6.2.0-1015-nvidia-64k",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-modules-extra-6.2.0-1015-nvidia",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-modules-nvidia-fs-6.2.0-1015-nvidia",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-modules-nvidia-fs-6.2.0-1015-nvidia-64k",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-nvidia-6.2-headers-6.2.0-1015",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-nvidia-6.2-tools-6.2.0-1015",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-nvidia-6.2-tools-host",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-tools-6.2.0-1015-nvidia",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-tools-6.2.0-1015-nvidia-64k",
"binary_version": "6.2.0-1015.15"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-nvidia-6.2",
"purl": "pkg:deb/ubuntu/linux-nvidia-6.2@6.2.0-1015.15?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.2.0-1003.3~22.04.1",
"6.2.0-1009.9",
"6.2.0-1010.10",
"6.2.0-1011.11",
"6.2.0-1012.12",
"6.2.0-1013.13",
"6.2.0-1015.15"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.5.0-1024-nvidia",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-buildinfo-6.5.0-1024-nvidia-64k",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-headers-6.5.0-1024-nvidia",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-headers-6.5.0-1024-nvidia-64k",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-image-unsigned-6.5.0-1024-nvidia",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-image-unsigned-6.5.0-1024-nvidia-64k",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-modules-6.5.0-1024-nvidia",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-modules-6.5.0-1024-nvidia-64k",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-modules-extra-6.5.0-1024-nvidia",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-modules-nvidia-fs-6.5.0-1024-nvidia",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-modules-nvidia-fs-6.5.0-1024-nvidia-64k",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-nvidia-6.5-headers-6.5.0-1024",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-nvidia-6.5-tools-6.5.0-1024",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-nvidia-6.5-tools-host",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-tools-6.5.0-1024-nvidia",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-tools-6.5.0-1024-nvidia-64k",
"binary_version": "6.5.0-1024.25"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-nvidia-6.5",
"purl": "pkg:deb/ubuntu/linux-nvidia-6.5@6.5.0-1024.25?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-1004.4",
"6.5.0-1007.7",
"6.5.0-1013.13",
"6.5.0-1014.14",
"6.5.0-1015.15",
"6.5.0-1018.18",
"6.5.0-1019.19",
"6.5.0-1021.22",
"6.5.0-1022.23",
"6.5.0-1023.24",
"6.5.0-1024.25"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1019-nvidia",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.8.0-1019-nvidia-64k",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1019-nvidia",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1019-nvidia-64k",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1019-nvidia",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1019-nvidia-64k",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1019-nvidia",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1019-nvidia-64k",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1019-nvidia",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-modules-nvidia-fs-6.8.0-1019-nvidia",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-modules-nvidia-fs-6.8.0-1019-nvidia-64k",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-nvidia-6.8-headers-6.8.0-1019",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-nvidia-6.8-tools-6.8.0-1019",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1019-nvidia",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1019-nvidia-64k",
"binary_version": "6.8.0-1019.21~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-nvidia-6.8",
"purl": "pkg:deb/ubuntu/linux-nvidia-6.8@6.8.0-1019.21~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1019.21~22.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1008.8~22.04.1",
"6.8.0-1009.9~22.04.1",
"6.8.0-1010.10~22.04.1",
"6.8.0-1011.11~22.04.1",
"6.8.0-1012.12~22.04.1",
"6.8.0-1013.14~22.04.1",
"6.8.0-1014.15~22.04.1",
"6.8.0-1015.16~22.04.1",
"6.8.0-1017.19~22.04.1",
"6.8.0-1018.20~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1032-nvidia-tegra",
"binary_version": "5.15.0-1032.32"
},
{
"binary_name": "linux-buildinfo-5.15.0-1032-nvidia-tegra-rt",
"binary_version": "5.15.0-1032.32"
},
{
"binary_name": "linux-headers-5.15.0-1032-nvidia-tegra",
"binary_version": "5.15.0-1032.32"
},
{
"binary_name": "linux-headers-5.15.0-1032-nvidia-tegra-rt",
"binary_version": "5.15.0-1032.32"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1032-nvidia-tegra",
"binary_version": "5.15.0-1032.32"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1032-nvidia-tegra-rt",
"binary_version": "5.15.0-1032.32"
},
{
"binary_name": "linux-modules-5.15.0-1032-nvidia-tegra",
"binary_version": "5.15.0-1032.32"
},
{
"binary_name": "linux-modules-5.15.0-1032-nvidia-tegra-rt",
"binary_version": "5.15.0-1032.32"
},
{
"binary_name": "linux-modules-extra-5.15.0-1032-nvidia-tegra",
"binary_version": "5.15.0-1032.32"
},
{
"binary_name": "linux-nvidia-tegra-headers-5.15.0-1032",
"binary_version": "5.15.0-1032.32"
},
{
"binary_name": "linux-nvidia-tegra-tools-5.15.0-1032",
"binary_version": "5.15.0-1032.32"
},
{
"binary_name": "linux-tools-5.15.0-1032-nvidia-tegra",
"binary_version": "5.15.0-1032.32"
},
{
"binary_name": "linux-tools-5.15.0-1032-nvidia-tegra-rt",
"binary_version": "5.15.0-1032.32"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-nvidia-tegra",
"purl": "pkg:deb/ubuntu/linux-nvidia-tegra@5.15.0-1032.32?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1032.32"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1009.9",
"5.15.0-1010.10",
"5.15.0-1012.12",
"5.15.0-1013.13",
"5.15.0-1014.14",
"5.15.0-1015.15",
"5.15.0-1016.16",
"5.15.0-1017.17",
"5.15.0-1018.18",
"5.15.0-1019.19",
"5.15.0-1020.20",
"5.15.0-1021.21",
"5.15.0-1022.22",
"5.15.0-1025.25",
"5.15.0-1026.26",
"5.15.0-1027.27",
"5.15.0-1028.28",
"5.15.0-1030.30"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1020-nvidia-tegra-igx",
"binary_version": "5.15.0-1020.20"
},
{
"binary_name": "linux-buildinfo-5.15.0-1020-nvidia-tegra-igx-rt",
"binary_version": "5.15.0-1020.20"
},
{
"binary_name": "linux-headers-5.15.0-1020-nvidia-tegra-igx",
"binary_version": "5.15.0-1020.20"
},
{
"binary_name": "linux-headers-5.15.0-1020-nvidia-tegra-igx-rt",
"binary_version": "5.15.0-1020.20"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1020-nvidia-tegra-igx",
"binary_version": "5.15.0-1020.20"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1020-nvidia-tegra-igx-rt",
"binary_version": "5.15.0-1020.20"
},
{
"binary_name": "linux-modules-5.15.0-1020-nvidia-tegra-igx",
"binary_version": "5.15.0-1020.20"
},
{
"binary_name": "linux-modules-5.15.0-1020-nvidia-tegra-igx-rt",
"binary_version": "5.15.0-1020.20"
},
{
"binary_name": "linux-modules-extra-5.15.0-1020-nvidia-tegra-igx",
"binary_version": "5.15.0-1020.20"
},
{
"binary_name": "linux-nvidia-tegra-igx-headers-5.15.0-1020",
"binary_version": "5.15.0-1020.20"
},
{
"binary_name": "linux-nvidia-tegra-igx-tools-5.15.0-1020",
"binary_version": "5.15.0-1020.20"
},
{
"binary_name": "linux-tools-5.15.0-1020-nvidia-tegra-igx",
"binary_version": "5.15.0-1020.20"
},
{
"binary_name": "linux-tools-5.15.0-1020-nvidia-tegra-igx-rt",
"binary_version": "5.15.0-1020.20"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-nvidia-tegra-igx",
"purl": "pkg:deb/ubuntu/linux-nvidia-tegra-igx@5.15.0-1020.20?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1020.20"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1001.1",
"5.15.0-1002.2",
"5.15.0-1004.4",
"5.15.0-1005.5",
"5.15.0-1006.6",
"5.15.0-1007.7",
"5.15.0-1008.8",
"5.15.0-1009.9",
"5.15.0-1012.12",
"5.15.0-1013.13",
"5.15.0-1015.15",
"5.15.0-1016.16",
"5.15.0-1018.18",
"5.15.0-1019.19"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.17.0-1035-oem",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-headers-5.17.0-1035-oem",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-image-unsigned-5.17.0-1035-oem",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-modules-5.17.0-1035-oem",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-modules-ipu6-5.17.0-1035-oem",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-modules-ivsc-5.17.0-1035-oem",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-modules-iwlwifi-5.17.0-1035-oem",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-oem-5.17-headers-5.17.0-1035",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-oem-5.17-tools-5.17.0-1035",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-oem-5.17-tools-host",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-tools-5.17.0-1035-oem",
"binary_version": "5.17.0-1035.36"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-oem-5.17",
"purl": "pkg:deb/ubuntu/linux-oem-5.17@5.17.0-1035.36?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.17.0-1003.3",
"5.17.0-1004.4",
"5.17.0-1006.6",
"5.17.0-1011.12",
"5.17.0-1012.13",
"5.17.0-1013.14",
"5.17.0-1014.15",
"5.17.0-1015.16",
"5.17.0-1016.17",
"5.17.0-1017.18",
"5.17.0-1018.19",
"5.17.0-1019.20",
"5.17.0-1020.21",
"5.17.0-1021.22",
"5.17.0-1024.25",
"5.17.0-1025.26",
"5.17.0-1026.27",
"5.17.0-1027.28",
"5.17.0-1028.29",
"5.17.0-1029.30",
"5.17.0-1030.31",
"5.17.0-1031.32",
"5.17.0-1032.33",
"5.17.0-1033.34",
"5.17.0-1034.35",
"5.17.0-1035.36"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.0.0-1021-oem",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-headers-6.0.0-1021-oem",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-image-unsigned-6.0.0-1021-oem",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-modules-6.0.0-1021-oem",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-modules-ipu6-6.0.0-1021-oem",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-modules-ivsc-6.0.0-1021-oem",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-modules-iwlwifi-6.0.0-1021-oem",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-oem-6.0-headers-6.0.0-1021",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-oem-6.0-tools-6.0.0-1021",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-oem-6.0-tools-host",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-tools-6.0.0-1021-oem",
"binary_version": "6.0.0-1021.21"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-oem-6.0",
"purl": "pkg:deb/ubuntu/linux-oem-6.0@6.0.0-1021.21?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.0.0-1006.6",
"6.0.0-1007.7",
"6.0.0-1008.8",
"6.0.0-1009.9",
"6.0.0-1010.10",
"6.0.0-1011.11",
"6.0.0-1012.12",
"6.0.0-1013.13",
"6.0.0-1014.14",
"6.0.0-1015.15",
"6.0.0-1016.16",
"6.0.0-1017.17",
"6.0.0-1018.18",
"6.0.0-1019.19",
"6.0.0-1020.20",
"6.0.0-1021.21"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.1.0-1036-oem",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-headers-6.1.0-1036-oem",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-image-unsigned-6.1.0-1036-oem",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-modules-6.1.0-1036-oem",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-modules-ipu6-6.1.0-1036-oem",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-modules-ivsc-6.1.0-1036-oem",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-modules-iwlwifi-6.1.0-1036-oem",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-oem-6.1-headers-6.1.0-1036",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-oem-6.1-tools-6.1.0-1036",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-oem-6.1-tools-host",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-tools-6.1.0-1036-oem",
"binary_version": "6.1.0-1036.36"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-oem-6.1",
"purl": "pkg:deb/ubuntu/linux-oem-6.1@6.1.0-1036.36?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.1.0-1004.4",
"6.1.0-1006.6",
"6.1.0-1007.7",
"6.1.0-1008.8",
"6.1.0-1009.9",
"6.1.0-1010.10",
"6.1.0-1012.12",
"6.1.0-1013.13",
"6.1.0-1014.14",
"6.1.0-1015.15",
"6.1.0-1016.16",
"6.1.0-1017.17",
"6.1.0-1019.19",
"6.1.0-1020.20",
"6.1.0-1021.21",
"6.1.0-1022.22",
"6.1.0-1023.23",
"6.1.0-1024.24",
"6.1.0-1025.25",
"6.1.0-1026.26",
"6.1.0-1027.27",
"6.1.0-1028.28",
"6.1.0-1029.29",
"6.1.0-1033.33",
"6.1.0-1034.34",
"6.1.0-1035.35",
"6.1.0-1036.36"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-headers-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-image-unsigned-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-modules-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-modules-ipu6-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-modules-ivsc-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-modules-iwlwifi-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-modules-usbio-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-oem-6.5-headers-6.5.0-1027",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-oem-6.5-lib-rust-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-oem-6.5-tools-6.5.0-1027",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-oem-6.5-tools-host",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-tools-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-oem-6.5",
"purl": "pkg:deb/ubuntu/linux-oem-6.5@6.5.0-1027.28?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-1003.3",
"6.5.0-1004.4",
"6.5.0-1006.6",
"6.5.0-1007.7",
"6.5.0-1008.8",
"6.5.0-1009.10",
"6.5.0-1011.12",
"6.5.0-1013.14",
"6.5.0-1014.15",
"6.5.0-1015.16",
"6.5.0-1016.17",
"6.5.0-1018.19",
"6.5.0-1019.20",
"6.5.0-1020.21",
"6.5.0-1022.23",
"6.5.0-1023.24",
"6.5.0-1024.25",
"6.5.0-1025.26",
"6.5.0-1027.28"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1070-oracle",
"binary_version": "5.15.0-1070.76"
},
{
"binary_name": "linux-headers-5.15.0-1070-oracle",
"binary_version": "5.15.0-1070.76"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1070-oracle",
"binary_version": "5.15.0-1070.76"
},
{
"binary_name": "linux-modules-5.15.0-1070-oracle",
"binary_version": "5.15.0-1070.76"
},
{
"binary_name": "linux-modules-extra-5.15.0-1070-oracle",
"binary_version": "5.15.0-1070.76"
},
{
"binary_name": "linux-oracle-headers-5.15.0-1070",
"binary_version": "5.15.0-1070.76"
},
{
"binary_name": "linux-oracle-tools-5.15.0-1070",
"binary_version": "5.15.0-1070.76"
},
{
"binary_name": "linux-tools-5.15.0-1070-oracle",
"binary_version": "5.15.0-1070.76"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-oracle",
"purl": "pkg:deb/ubuntu/linux-oracle@5.15.0-1070.76?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1070.76"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-1008.10",
"5.15.0-1001.3",
"5.15.0-1002.4",
"5.15.0-1003.5",
"5.15.0-1006.8",
"5.15.0-1007.9",
"5.15.0-1009.12",
"5.15.0-1011.15",
"5.15.0-1013.17",
"5.15.0-1016.20",
"5.15.0-1017.22",
"5.15.0-1018.23",
"5.15.0-1019.24",
"5.15.0-1021.27",
"5.15.0-1022.28",
"5.15.0-1025.31",
"5.15.0-1026.32",
"5.15.0-1027.33",
"5.15.0-1029.35",
"5.15.0-1030.36",
"5.15.0-1032.38",
"5.15.0-1033.39",
"5.15.0-1034.40",
"5.15.0-1035.41",
"5.15.0-1036.42",
"5.15.0-1037.43",
"5.15.0-1038.44",
"5.15.0-1039.45",
"5.15.0-1040.46",
"5.15.0-1041.47",
"5.15.0-1042.48",
"5.15.0-1044.50",
"5.15.0-1045.51",
"5.15.0-1046.52",
"5.15.0-1047.53",
"5.15.0-1048.54",
"5.15.0-1049.55",
"5.15.0-1050.56",
"5.15.0-1051.57",
"5.15.0-1052.58",
"5.15.0-1053.59",
"5.15.0-1054.60",
"5.15.0-1055.61",
"5.15.0-1058.64",
"5.15.0-1059.65",
"5.15.0-1060.66",
"5.15.0-1061.67",
"5.15.0-1062.68",
"5.15.0-1063.69",
"5.15.0-1064.70",
"5.15.0-1065.71",
"5.15.0-1066.72",
"5.15.0-1067.73",
"5.15.0-1068.74",
"5.15.0-1069.75"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.5.0-1027-oracle",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.5.0-1027-oracle-64k",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-1027-oracle",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-1027-oracle-64k",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.5.0-1027-oracle",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.5.0-1027-oracle-64k",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-1027-oracle",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-1027-oracle-64k",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.5.0-1027-oracle",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.5.0-1027-oracle-64k",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-oracle-6.5-headers-6.5.0-1027",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-oracle-6.5-tools-6.5.0-1027",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-1027-oracle",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-1027-oracle-64k",
"binary_version": "6.5.0-1027.27~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-oracle-6.5",
"purl": "pkg:deb/ubuntu/linux-oracle-6.5@6.5.0-1027.27~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-1013.13~22.04.4",
"6.5.0-1014.14~22.04.1",
"6.5.0-1015.15~22.04.1",
"6.5.0-1016.16~22.04.1",
"6.5.0-1018.18~22.04.1",
"6.5.0-1019.19~22.04.1",
"6.5.0-1020.20~22.04.1",
"6.5.0-1021.21~22.04.1",
"6.5.0-1023.23~22.04.1",
"6.5.0-1024.24~22.04.1",
"6.5.0-1025.25~22.04.1",
"6.5.0-1026.26~22.04.1",
"6.5.0-1027.27~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1017-oracle",
"binary_version": "6.8.0-1017.18~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.8.0-1017-oracle-64k",
"binary_version": "6.8.0-1017.18~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1017-oracle",
"binary_version": "6.8.0-1017.18~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1017-oracle-64k",
"binary_version": "6.8.0-1017.18~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1017-oracle",
"binary_version": "6.8.0-1017.18~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1017-oracle-64k",
"binary_version": "6.8.0-1017.18~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1017-oracle",
"binary_version": "6.8.0-1017.18~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1017-oracle-64k",
"binary_version": "6.8.0-1017.18~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1017-oracle",
"binary_version": "6.8.0-1017.18~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1017-oracle-64k",
"binary_version": "6.8.0-1017.18~22.04.1"
},
{
"binary_name": "linux-oracle-6.8-headers-6.8.0-1017",
"binary_version": "6.8.0-1017.18~22.04.1"
},
{
"binary_name": "linux-oracle-6.8-tools-6.8.0-1017",
"binary_version": "6.8.0-1017.18~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1017-oracle",
"binary_version": "6.8.0-1017.18~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1017-oracle-64k",
"binary_version": "6.8.0-1017.18~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-oracle-6.8",
"purl": "pkg:deb/ubuntu/linux-oracle-6.8@6.8.0-1017.18~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1017.18~22.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1006.6~22.04.3",
"6.8.0-1008.8~22.04.1",
"6.8.0-1010.10~22.04.1",
"6.8.0-1011.11~22.04.1",
"6.8.0-1012.12~22.04.1",
"6.8.0-1013.13~22.04.1",
"6.8.0-1014.14~22.04.1",
"6.8.0-1015.15~22.04.1",
"6.8.0-1016.17~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1065-raspi",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-headers-5.15.0-1065-raspi",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-image-5.15.0-1065-raspi",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-modules-5.15.0-1065-raspi",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-modules-extra-5.15.0-1065-raspi",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-raspi-headers-5.15.0-1065",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-raspi-tools-5.15.0-1065",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-tools-5.15.0-1065-raspi",
"binary_version": "5.15.0-1065.68"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-raspi",
"purl": "pkg:deb/ubuntu/linux-raspi@5.15.0-1065.68?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1065.68"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-1008.9",
"5.15.0-1002.2",
"5.15.0-1003.3",
"5.15.0-1004.4",
"5.15.0-1005.5",
"5.15.0-1006.6",
"5.15.0-1008.8",
"5.15.0-1011.13",
"5.15.0-1012.14",
"5.15.0-1013.15",
"5.15.0-1014.16",
"5.15.0-1015.17",
"5.15.0-1016.18",
"5.15.0-1017.19",
"5.15.0-1018.20",
"5.15.0-1021.23",
"5.15.0-1022.24",
"5.15.0-1023.25",
"5.15.0-1024.26",
"5.15.0-1025.27",
"5.15.0-1026.28",
"5.15.0-1027.29",
"5.15.0-1028.30",
"5.15.0-1029.31",
"5.15.0-1030.32",
"5.15.0-1032.35",
"5.15.0-1033.36",
"5.15.0-1034.37",
"5.15.0-1035.38",
"5.15.0-1036.39",
"5.15.0-1037.40",
"5.15.0-1038.41",
"5.15.0-1040.43",
"5.15.0-1041.44",
"5.15.0-1042.45",
"5.15.0-1043.46",
"5.15.0-1044.47",
"5.15.0-1045.48",
"5.15.0-1046.49",
"5.15.0-1047.50",
"5.15.0-1048.51",
"5.15.0-1049.52",
"5.15.0-1050.53",
"5.15.0-1053.56",
"5.15.0-1054.57",
"5.15.0-1055.58",
"5.15.0-1058.61",
"5.15.0-1059.62",
"5.15.0-1060.63",
"5.15.0-1061.64",
"5.15.0-1062.65",
"5.15.0-1063.66",
"5.15.0-1064.67"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1032-realtime",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1032-realtime",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-headers-5.15.0-1032-realtime",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1032-realtime",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-modules-5.15.0-1032-realtime",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-modules-extra-5.15.0-1032-realtime",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-realtime-cloud-tools-5.15.0-1032",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-realtime-cloud-tools-common",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-realtime-headers-5.15.0-1032",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-realtime-tools-5.15.0-1032",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-realtime-tools-common",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-realtime-tools-host",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-tools-5.15.0-1032-realtime",
"binary_version": "5.15.0-1032.35"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-realtime",
"purl": "pkg:deb/ubuntu/linux-realtime@5.15.0-1032.35?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1032.35"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1028-generic",
"binary_version": "5.15.0-1028.32"
},
{
"binary_name": "linux-headers-5.15.0-1028-generic",
"binary_version": "5.15.0-1028.32"
},
{
"binary_name": "linux-image-5.15.0-1028-generic",
"binary_version": "5.15.0-1028.32"
},
{
"binary_name": "linux-modules-5.15.0-1028-generic",
"binary_version": "5.15.0-1028.32"
},
{
"binary_name": "linux-modules-extra-5.15.0-1028-generic",
"binary_version": "5.15.0-1028.32"
},
{
"binary_name": "linux-riscv-headers-5.15.0-1028",
"binary_version": "5.15.0-1028.32"
},
{
"binary_name": "linux-riscv-tools-5.15.0-1028",
"binary_version": "5.15.0-1028.32"
},
{
"binary_name": "linux-tools-5.15.0-1028-generic",
"binary_version": "5.15.0-1028.32"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-riscv",
"purl": "pkg:deb/ubuntu/linux-riscv@5.15.0-1028.32?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-1004.4",
"5.13.0-1006.6+22.04.1",
"5.13.0-1007.7+22.04.1",
"5.13.0-1010.11+22.04.1",
"5.15.0-1004.4",
"5.15.0-1005.5",
"5.15.0-1006.6",
"5.15.0-1007.7",
"5.15.0-1008.8",
"5.15.0-1011.12",
"5.15.0-1012.13",
"5.15.0-1014.16",
"5.15.0-1015.17",
"5.15.0-1016.18",
"5.15.0-1017.19",
"5.15.0-1018.21",
"5.15.0-1019.22",
"5.15.0-1020.23",
"5.15.0-1022.26",
"5.15.0-1023.27",
"5.15.0-1026.30",
"5.15.0-1027.31",
"5.15.0-1028.32"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.19.0-1021-generic",
"binary_version": "5.19.0-1021.23~22.04.1"
},
{
"binary_name": "linux-headers-5.19.0-1021-generic",
"binary_version": "5.19.0-1021.23~22.04.1"
},
{
"binary_name": "linux-image-5.19.0-1021-generic",
"binary_version": "5.19.0-1021.23~22.04.1"
},
{
"binary_name": "linux-modules-5.19.0-1021-generic",
"binary_version": "5.19.0-1021.23~22.04.1"
},
{
"binary_name": "linux-modules-extra-5.19.0-1021-generic",
"binary_version": "5.19.0-1021.23~22.04.1"
},
{
"binary_name": "linux-riscv-5.19-headers-5.19.0-1021",
"binary_version": "5.19.0-1021.23~22.04.1"
},
{
"binary_name": "linux-riscv-5.19-tools-5.19.0-1021",
"binary_version": "5.19.0-1021.23~22.04.1"
},
{
"binary_name": "linux-tools-5.19.0-1021-generic",
"binary_version": "5.19.0-1021.23~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-riscv-5.19",
"purl": "pkg:deb/ubuntu/linux-riscv-5.19@5.19.0-1021.23~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.19.0-1012.13~22.04.1",
"5.19.0-1015.16~22.04.1",
"5.19.0-1016.17~22.04.1",
"5.19.0-1017.18~22.04.1",
"5.19.0-1018.19~22.04.1",
"5.19.0-1019.21~22.04.1",
"5.19.0-1020.22~22.04.1",
"5.19.0-1021.23~22.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.5.0-45-generic",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-45-generic",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-image-6.5.0-45-generic",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-45-generic",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.5.0-45-generic",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-riscv-6.5-headers-6.5.0-45",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-riscv-6.5-tools-6.5.0-45",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-45-generic",
"binary_version": "6.5.0-45.45.1~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-riscv-6.5",
"purl": "pkg:deb/ubuntu/linux-riscv-6.5@6.5.0-45.45.1~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-17.17.1.1~22.04.1",
"6.5.0-21.21.1~22.04.1",
"6.5.0-25.25.1~22.04.1",
"6.5.0-26.26.1~22.04.1",
"6.5.0-27.28.1~22.04.1",
"6.5.0-28.29.1~22.04.1",
"6.5.0-35.35.1~22.04.1",
"6.5.0-40.40.1~22.04.1",
"6.5.0-42.42.1~22.04.1",
"6.5.0-45.45.1~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-50-generic",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-50-generic",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-image-6.8.0-50-generic",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-50-generic",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-riscv-6.8-headers-6.8.0-50",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-riscv-6.8-tools-6.8.0-50",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-50-generic",
"binary_version": "6.8.0-50.51.1~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-riscv-6.8",
"purl": "pkg:deb/ubuntu/linux-riscv-6.8@6.8.0-50.51.1~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-50.51.1~22.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-38.38.1~22.04.1",
"6.8.0-39.39.1~22.04.1",
"6.8.0-40.40.1~22.04.1",
"6.8.0-41.41.1~22.04.1",
"6.8.0-44.44.1~22.04.1",
"6.8.0-47.47.1~22.04.1",
"6.8.0-48.48.1~22.04.2",
"6.8.0-49.49.1~22.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.19.0-1020-starfive",
"binary_version": "5.19.0-1020.22~22.04.1"
},
{
"binary_name": "linux-headers-5.19.0-1020-starfive",
"binary_version": "5.19.0-1020.22~22.04.1"
},
{
"binary_name": "linux-image-5.19.0-1020-starfive",
"binary_version": "5.19.0-1020.22~22.04.1"
},
{
"binary_name": "linux-modules-5.19.0-1020-starfive",
"binary_version": "5.19.0-1020.22~22.04.1"
},
{
"binary_name": "linux-modules-extra-5.19.0-1020-starfive",
"binary_version": "5.19.0-1020.22~22.04.1"
},
{
"binary_name": "linux-starfive-5.19-headers-5.19.0-1020",
"binary_version": "5.19.0-1020.22~22.04.1"
},
{
"binary_name": "linux-starfive-5.19-tools-5.19.0-1020",
"binary_version": "5.19.0-1020.22~22.04.1"
},
{
"binary_name": "linux-tools-5.19.0-1020-starfive",
"binary_version": "5.19.0-1020.22~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-starfive-5.19",
"purl": "pkg:deb/ubuntu/linux-starfive-5.19@5.19.0-1020.22~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.19.0-1014.16~22.04.1",
"5.19.0-1015.17~22.04.1",
"5.19.0-1016.18~22.04.1",
"5.19.0-1017.19~22.04.1",
"5.19.0-1018.20~22.04.1",
"5.19.0-1019.21~22.04.1",
"5.19.0-1020.22~22.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.2.0-1009-starfive",
"binary_version": "6.2.0-1009.10~22.04.1"
},
{
"binary_name": "linux-headers-6.2.0-1009-starfive",
"binary_version": "6.2.0-1009.10~22.04.1"
},
{
"binary_name": "linux-image-6.2.0-1009-starfive",
"binary_version": "6.2.0-1009.10~22.04.1"
},
{
"binary_name": "linux-modules-6.2.0-1009-starfive",
"binary_version": "6.2.0-1009.10~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.2.0-1009-starfive",
"binary_version": "6.2.0-1009.10~22.04.1"
},
{
"binary_name": "linux-starfive-6.2-headers-6.2.0-1009",
"binary_version": "6.2.0-1009.10~22.04.1"
},
{
"binary_name": "linux-starfive-6.2-tools-6.2.0-1009",
"binary_version": "6.2.0-1009.10~22.04.1"
},
{
"binary_name": "linux-tools-6.2.0-1009-starfive",
"binary_version": "6.2.0-1009.10~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-starfive-6.2",
"purl": "pkg:deb/ubuntu/linux-starfive-6.2@6.2.0-1009.10~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.2.0-1006.7~22.04.1",
"6.2.0-1007.8~22.04.1",
"6.2.0-1009.10~22.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.5.0-1018-starfive",
"binary_version": "6.5.0-1018.19~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-1018-starfive",
"binary_version": "6.5.0-1018.19~22.04.1"
},
{
"binary_name": "linux-image-6.5.0-1018-starfive",
"binary_version": "6.5.0-1018.19~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-1018-starfive",
"binary_version": "6.5.0-1018.19~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.5.0-1018-starfive",
"binary_version": "6.5.0-1018.19~22.04.1"
},
{
"binary_name": "linux-starfive-6.5-headers-6.5.0-1018",
"binary_version": "6.5.0-1018.19~22.04.1"
},
{
"binary_name": "linux-starfive-6.5-tools-6.5.0-1018",
"binary_version": "6.5.0-1018.19~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-1018-starfive",
"binary_version": "6.5.0-1018.19~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-starfive-6.5",
"purl": "pkg:deb/ubuntu/linux-starfive-6.5@6.5.0-1018.19~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-1007.8~22.04.1",
"6.5.0-1008.9~22.04.1",
"6.5.0-1009.10~22.04.1",
"6.5.0-1010.11~22.04.1",
"6.5.0-1011.12~22.04.1",
"6.5.0-1012.13~22.04.1",
"6.5.0-1014.15~22.04.1",
"6.5.0-1015.16~22.04.1",
"6.5.0-1016.17~22.04.1",
"6.5.0-1017.18~22.04.1",
"6.5.0-1018.19~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1038-xilinx-zynqmp",
"binary_version": "5.15.0-1038.42"
},
{
"binary_name": "linux-headers-5.15.0-1038-xilinx-zynqmp",
"binary_version": "5.15.0-1038.42"
},
{
"binary_name": "linux-image-5.15.0-1038-xilinx-zynqmp",
"binary_version": "5.15.0-1038.42"
},
{
"binary_name": "linux-modules-5.15.0-1038-xilinx-zynqmp",
"binary_version": "5.15.0-1038.42"
},
{
"binary_name": "linux-tools-5.15.0-1038-xilinx-zynqmp",
"binary_version": "5.15.0-1038.42"
},
{
"binary_name": "linux-xilinx-zynqmp-headers-5.15.0-1038",
"binary_version": "5.15.0-1038.42"
},
{
"binary_name": "linux-xilinx-zynqmp-tools-5.15.0-1038",
"binary_version": "5.15.0-1038.42"
},
{
"binary_name": "linux-xilinx-zynqmp-tools-common",
"binary_version": "5.15.0-1038.42"
},
{
"binary_name": "linux-xilinx-zynqmp-tools-host",
"binary_version": "5.15.0-1038.42"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-xilinx-zynqmp",
"purl": "pkg:deb/ubuntu/linux-xilinx-zynqmp@5.15.0-1038.42?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1038.42"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1022.26",
"5.15.0-1023.27",
"5.15.0-1025.29",
"5.15.0-1027.31",
"5.15.0-1030.34",
"5.15.0-1031.35",
"5.15.0-1035.39",
"5.15.0-1036.40",
"5.15.0-1037.41"
]
},
{
"ecosystem_specific": {
"availability": "Available for NVIDIA BlueField platforms",
"binaries": [
{
"binary_name": "linux-bluefield-cloud-tools-common",
"binary_version": "5.15.0-1056.58"
},
{
"binary_name": "linux-bluefield-headers-5.15.0-1056",
"binary_version": "5.15.0-1056.58"
},
{
"binary_name": "linux-bluefield-tools-5.15.0-1056",
"binary_version": "5.15.0-1056.58"
},
{
"binary_name": "linux-bluefield-tools-host",
"binary_version": "5.15.0-1056.58"
},
{
"binary_name": "linux-buildinfo-5.15.0-1056-bluefield",
"binary_version": "5.15.0-1056.58"
},
{
"binary_name": "linux-headers-5.15.0-1056-bluefield",
"binary_version": "5.15.0-1056.58"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1056-bluefield",
"binary_version": "5.15.0-1056.58"
},
{
"binary_name": "linux-modules-5.15.0-1056-bluefield",
"binary_version": "5.15.0-1056.58"
},
{
"binary_name": "linux-modules-extra-5.15.0-1056-bluefield",
"binary_version": "5.15.0-1056.58"
},
{
"binary_name": "linux-tools-5.15.0-1056-bluefield",
"binary_version": "5.15.0-1056.58"
}
]
},
"package": {
"ecosystem": "Ubuntu:Nvidia-BlueField:22.04:LTS",
"name": "linux-bluefield",
"purl": "pkg:deb/ubuntu/linux-bluefield@5.15.0-1056.58?arch=source\u0026distro=bluefield/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1056.58"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1011.13",
"5.15.0-1014.16",
"5.15.0-1015.17",
"5.15.0-1017.19",
"5.15.0-1019.21",
"5.15.0-1021.23",
"5.15.0-1022.24",
"5.15.0-1023.25",
"5.15.0-1024.26",
"5.15.0-1027.29",
"5.15.0-1028.30",
"5.15.0-1031.33",
"5.15.0-1032.34",
"5.15.0-1033.35",
"5.15.0-1035.37",
"5.15.0-1036.38",
"5.15.0-1037.39",
"5.15.0-1038.40",
"5.15.0-1040.42",
"5.15.0-1042.44",
"5.15.0-1043.45",
"5.15.0-1044.46",
"5.15.0-1045.47",
"5.15.0-1047.49",
"5.15.0-1048.50",
"5.15.0-1050.52",
"5.15.0-1051.53",
"5.15.0-1052.54",
"5.15.0-1053.55",
"5.15.0-1054.56"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-aws-fips-cloud-tools-5.15.0-1051",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-aws-fips-headers-5.15.0-1051",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-aws-fips-tools-5.15.0-1051",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-buildinfo-5.15.0-1051-aws-fips",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1051-aws-fips",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-headers-5.15.0-1051-aws-fips",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1051-aws-fips",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.15.0-1051-aws-fips",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-modules-5.15.0-1051-aws-fips",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1051-aws-fips",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-tools-5.15.0-1051-aws-fips",
"binary_version": "5.15.0-1051.56+fips1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-preview:22.04:LTS",
"name": "linux-aws-fips",
"purl": "pkg:deb/ubuntu/linux-aws-fips@5.15.0-1051.56+fips1?arch=source\u0026distro=fips-preview/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1042.47+fips1",
"5.15.0-1051.56+fips1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-azure-fips-cloud-tools-5.15.0-1053",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-azure-fips-headers-5.15.0-1053",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-azure-fips-tools-5.15.0-1053",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-buildinfo-5.15.0-1053-azure-fips",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1053-azure-fips",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-headers-5.15.0-1053-azure-fips",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1053-azure-fips",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.15.0-1053-azure-fips",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-modules-5.15.0-1053-azure-fips",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1053-azure-fips",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-tools-5.15.0-1053-azure-fips",
"binary_version": "5.15.0-1053.61+fips1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-preview:22.04:LTS",
"name": "linux-azure-fips",
"purl": "pkg:deb/ubuntu/linux-azure-fips@5.15.0-1053.61+fips1?arch=source\u0026distro=fips-preview/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1053.61+fips1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-73-fips",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-fips-headers-5.15.0-73",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-fips-tools-5.15.0-73",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-fips-tools-host",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-headers-5.15.0-73-fips",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-73-fips",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.15.0-73-fips",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-modules-5.15.0-73-fips",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-modules-extra-5.15.0-73-fips",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-73-fips",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-tools-5.15.0-73-fips",
"binary_version": "5.15.0-73.80+fips1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-preview:22.04:LTS",
"name": "linux-fips",
"purl": "pkg:deb/ubuntu/linux-fips@5.15.0-73.80+fips1?arch=source\u0026distro=fips-preview/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-73.80+fips1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1048-gcp-fips",
"binary_version": "5.15.0-1048.56+fips1"
},
{
"binary_name": "linux-gcp-fips-headers-5.15.0-1048",
"binary_version": "5.15.0-1048.56+fips1"
},
{
"binary_name": "linux-gcp-fips-tools-5.15.0-1048",
"binary_version": "5.15.0-1048.56+fips1"
},
{
"binary_name": "linux-headers-5.15.0-1048-gcp-fips",
"binary_version": "5.15.0-1048.56+fips1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1048-gcp-fips",
"binary_version": "5.15.0-1048.56+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.15.0-1048-gcp-fips",
"binary_version": "5.15.0-1048.56+fips1"
},
{
"binary_name": "linux-modules-5.15.0-1048-gcp-fips",
"binary_version": "5.15.0-1048.56+fips1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1048-gcp-fips",
"binary_version": "5.15.0-1048.56+fips1"
},
{
"binary_name": "linux-tools-5.15.0-1048-gcp-fips",
"binary_version": "5.15.0-1048.56+fips1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-preview:22.04:LTS",
"name": "linux-gcp-fips",
"purl": "pkg:deb/ubuntu/linux-gcp-fips@5.15.0-1048.56+fips1?arch=source\u0026distro=fips-preview/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1048.56+fips1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-aws-fips-cloud-tools-5.15.0-1072",
"binary_version": "5.15.0-1072.78+fips1"
},
{
"binary_name": "linux-aws-fips-headers-5.15.0-1072",
"binary_version": "5.15.0-1072.78+fips1"
},
{
"binary_name": "linux-aws-fips-tools-5.15.0-1072",
"binary_version": "5.15.0-1072.78+fips1"
},
{
"binary_name": "linux-buildinfo-5.15.0-1072-aws-fips",
"binary_version": "5.15.0-1072.78+fips1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1072-aws-fips",
"binary_version": "5.15.0-1072.78+fips1"
},
{
"binary_name": "linux-headers-5.15.0-1072-aws-fips",
"binary_version": "5.15.0-1072.78+fips1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1072-aws-fips",
"binary_version": "5.15.0-1072.78+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.15.0-1072-aws-fips",
"binary_version": "5.15.0-1072.78+fips1"
},
{
"binary_name": "linux-modules-5.15.0-1072-aws-fips",
"binary_version": "5.15.0-1072.78+fips1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1072-aws-fips",
"binary_version": "5.15.0-1072.78+fips1"
},
{
"binary_name": "linux-tools-5.15.0-1072-aws-fips",
"binary_version": "5.15.0-1072.78+fips1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:22.04:LTS",
"name": "linux-aws-fips",
"purl": "pkg:deb/ubuntu/linux-aws-fips@5.15.0-1072.78+fips1?arch=source\u0026distro=fips-updates/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1072.78+fips1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1051.56+fips1",
"5.15.0-1052.57+fips1",
"5.15.0-1053.58+fips1",
"5.15.0-1055.60+fips1",
"5.15.0-1056.61+fips1",
"5.15.0-1057.63+fips1",
"5.15.0-1060.66+fips1",
"5.15.0-1061.67+fips1",
"5.15.0-1062.68+fips1",
"5.15.0-1063.69+fips1",
"5.15.0-1064.70+fips1",
"5.15.0-1065.71+fips1",
"5.15.0-1066.72+fips1",
"5.15.0-1067.73+fips1",
"5.15.0-1068.74+fips1",
"5.15.0-1069.75+fips1",
"5.15.0-1070.76+fips1",
"5.15.0-1071.77+fips1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-azure-fips-cloud-tools-5.15.0-1075",
"binary_version": "5.15.0-1075.84+fips1"
},
{
"binary_name": "linux-azure-fips-headers-5.15.0-1075",
"binary_version": "5.15.0-1075.84+fips1"
},
{
"binary_name": "linux-azure-fips-tools-5.15.0-1075",
"binary_version": "5.15.0-1075.84+fips1"
},
{
"binary_name": "linux-buildinfo-5.15.0-1075-azure-fips",
"binary_version": "5.15.0-1075.84+fips1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1075-azure-fips",
"binary_version": "5.15.0-1075.84+fips1"
},
{
"binary_name": "linux-headers-5.15.0-1075-azure-fips",
"binary_version": "5.15.0-1075.84+fips1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1075-azure-fips",
"binary_version": "5.15.0-1075.84+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.15.0-1075-azure-fips",
"binary_version": "5.15.0-1075.84+fips1"
},
{
"binary_name": "linux-modules-5.15.0-1075-azure-fips",
"binary_version": "5.15.0-1075.84+fips1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1075-azure-fips",
"binary_version": "5.15.0-1075.84+fips1"
},
{
"binary_name": "linux-modules-involflt-5.15.0-1075-azure-fips",
"binary_version": "5.15.0-1075.84+fips1"
},
{
"binary_name": "linux-tools-5.15.0-1075-azure-fips",
"binary_version": "5.15.0-1075.84+fips1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:22.04:LTS",
"name": "linux-azure-fips",
"purl": "pkg:deb/ubuntu/linux-azure-fips@5.15.0-1075.84+fips1?arch=source\u0026distro=fips-updates/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1075.84+fips1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1053.61+fips1",
"5.15.0-1058.66+fips1",
"5.15.0-1059.67+fips1",
"5.15.0-1060.69+fips1",
"5.15.0-1061.70+fips1",
"5.15.0-1063.72+fips1",
"5.15.0-1064.73+fips1",
"5.15.0-1065.74+fips1",
"5.15.0-1067.76+fips1",
"5.15.0-1068.77+fips1",
"5.15.0-1070.79+fips1",
"5.15.0-1071.80+fips1",
"5.15.0-1072.81+fips1",
"5.15.0-1073.82+fips1",
"5.15.0-1074.83+fips1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-125-fips",
"binary_version": "5.15.0-125.135+fips1"
},
{
"binary_name": "linux-fips-headers-5.15.0-125",
"binary_version": "5.15.0-125.135+fips1"
},
{
"binary_name": "linux-fips-tools-5.15.0-125",
"binary_version": "5.15.0-125.135+fips1"
},
{
"binary_name": "linux-headers-5.15.0-125-fips",
"binary_version": "5.15.0-125.135+fips1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-125-fips",
"binary_version": "5.15.0-125.135+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.15.0-125-fips",
"binary_version": "5.15.0-125.135+fips1"
},
{
"binary_name": "linux-modules-5.15.0-125-fips",
"binary_version": "5.15.0-125.135+fips1"
},
{
"binary_name": "linux-modules-extra-5.15.0-125-fips",
"binary_version": "5.15.0-125.135+fips1"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-125-fips",
"binary_version": "5.15.0-125.135+fips1"
},
{
"binary_name": "linux-tools-5.15.0-125-fips",
"binary_version": "5.15.0-125.135+fips1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:22.04:LTS",
"name": "linux-fips",
"purl": "pkg:deb/ubuntu/linux-fips@5.15.0-125.135+fips1?arch=source\u0026distro=fips-updates/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-125.135+fips1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-73.80+fips1",
"5.15.0-92.102+fips1",
"5.15.0-94.104+fips1",
"5.15.0-97.107+fips1",
"5.15.0-100.110+fips1",
"5.15.0-101.111+fips1",
"5.15.0-102.112+fips1",
"5.15.0-105.115+fips1",
"5.15.0-106.116+fips1",
"5.15.0-107.117+fips1",
"5.15.0-111.121+fips1",
"5.15.0-113.123+fips1",
"5.15.0-115.125+fips1",
"5.15.0-117.127+fips1",
"5.15.0-118.128+fips1",
"5.15.0-119.129+fips1",
"5.15.0-121.131+fips1",
"5.15.0-122.132+fips1",
"5.15.0-124.134+fips1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1071-gcp-fips",
"binary_version": "5.15.0-1071.79+fips1"
},
{
"binary_name": "linux-gcp-fips-headers-5.15.0-1071",
"binary_version": "5.15.0-1071.79+fips1"
},
{
"binary_name": "linux-gcp-fips-tools-5.15.0-1071",
"binary_version": "5.15.0-1071.79+fips1"
},
{
"binary_name": "linux-headers-5.15.0-1071-gcp-fips",
"binary_version": "5.15.0-1071.79+fips1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1071-gcp-fips",
"binary_version": "5.15.0-1071.79+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.15.0-1071-gcp-fips",
"binary_version": "5.15.0-1071.79+fips1"
},
{
"binary_name": "linux-modules-5.15.0-1071-gcp-fips",
"binary_version": "5.15.0-1071.79+fips1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1071-gcp-fips",
"binary_version": "5.15.0-1071.79+fips1"
},
{
"binary_name": "linux-tools-5.15.0-1071-gcp-fips",
"binary_version": "5.15.0-1071.79+fips1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:22.04:LTS",
"name": "linux-gcp-fips",
"purl": "pkg:deb/ubuntu/linux-gcp-fips@5.15.0-1071.79+fips1?arch=source\u0026distro=fips-updates/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1071.79+fips1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1048.56+fips1",
"5.15.0-1055.63+fips2",
"5.15.0-1058.66+fips1",
"5.15.0-1059.67+fips1",
"5.15.0-1060.68+fips1",
"5.15.0-1062.70+fips1",
"5.15.0-1063.71+fips1",
"5.15.0-1064.72+fips1",
"5.15.0-1065.73+fips1",
"5.15.0-1066.74+fips1",
"5.15.0-1067.75+fips1",
"5.15.0-1068.76+fips1",
"5.15.0-1069.77+fips1",
"5.15.0-1070.78+fips1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1066-intel-iot-realtime",
"binary_version": "5.15.0-1066.68"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1066-intel-iot-realtime",
"binary_version": "5.15.0-1066.68"
},
{
"binary_name": "linux-headers-5.15.0-1066-intel-iot-realtime",
"binary_version": "5.15.0-1066.68"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1066-intel-iot-realtime",
"binary_version": "5.15.0-1066.68"
},
{
"binary_name": "linux-intel-iot-realtime-cloud-tools-5.15.0-1066",
"binary_version": "5.15.0-1066.68"
},
{
"binary_name": "linux-intel-iot-realtime-cloud-tools-common",
"binary_version": "5.15.0-1066.68"
},
{
"binary_name": "linux-intel-iot-realtime-headers-5.15.0-1066",
"binary_version": "5.15.0-1066.68"
},
{
"binary_name": "linux-intel-iot-realtime-tools-5.15.0-1066",
"binary_version": "5.15.0-1066.68"
},
{
"binary_name": "linux-intel-iot-realtime-tools-common",
"binary_version": "5.15.0-1066.68"
},
{
"binary_name": "linux-intel-iot-realtime-tools-host",
"binary_version": "5.15.0-1066.68"
},
{
"binary_name": "linux-modules-5.15.0-1066-intel-iot-realtime",
"binary_version": "5.15.0-1066.68"
},
{
"binary_name": "linux-modules-extra-5.15.0-1066-intel-iot-realtime",
"binary_version": "5.15.0-1066.68"
},
{
"binary_name": "linux-tools-5.15.0-1066-intel-iot-realtime",
"binary_version": "5.15.0-1066.68"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:Realtime:22.04:LTS",
"name": "linux-intel-iot-realtime",
"purl": "pkg:deb/ubuntu/linux-intel-iot-realtime@5.15.0-1066.68?arch=source\u0026distro=realtime/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1066.68"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1021.26",
"5.15.0-1022.27",
"5.15.0-1023.28",
"5.15.0-1024.29",
"5.15.0-1028.33",
"5.15.0-1033.35",
"5.15.0-1034.36",
"5.15.0-1035.37",
"5.15.0-1036.38",
"5.15.0-1037.39",
"5.15.0-1038.40",
"5.15.0-1039.41",
"5.15.0-1040.42",
"5.15.0-1041.43",
"5.15.0-1042.44",
"5.15.0-1043.45",
"5.15.0-1044.46",
"5.15.0-1046.48",
"5.15.0-1047.49",
"5.15.0-1048.50",
"5.15.0-1049.51",
"5.15.0-1050.52",
"5.15.0-1053.55",
"5.15.0-1054.56",
"5.15.0-1055.57",
"5.15.0-1056.58",
"5.15.0-1057.59",
"5.15.0-1058.60",
"5.15.0-1059.61",
"5.15.0-1060.62",
"5.15.0-1061.63",
"5.15.0-1063.65",
"5.15.0-1064.66"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1073-realtime",
"binary_version": "5.15.0-1073.81"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1073-realtime",
"binary_version": "5.15.0-1073.81"
},
{
"binary_name": "linux-headers-5.15.0-1073-realtime",
"binary_version": "5.15.0-1073.81"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1073-realtime",
"binary_version": "5.15.0-1073.81"
},
{
"binary_name": "linux-modules-5.15.0-1073-realtime",
"binary_version": "5.15.0-1073.81"
},
{
"binary_name": "linux-modules-extra-5.15.0-1073-realtime",
"binary_version": "5.15.0-1073.81"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-1073-realtime",
"binary_version": "5.15.0-1073.81"
},
{
"binary_name": "linux-realtime-cloud-tools-5.15.0-1073",
"binary_version": "5.15.0-1073.81"
},
{
"binary_name": "linux-realtime-cloud-tools-common",
"binary_version": "5.15.0-1073.81"
},
{
"binary_name": "linux-realtime-headers-5.15.0-1073",
"binary_version": "5.15.0-1073.81"
},
{
"binary_name": "linux-realtime-tools-5.15.0-1073",
"binary_version": "5.15.0-1073.81"
},
{
"binary_name": "linux-realtime-tools-common",
"binary_version": "5.15.0-1073.81"
},
{
"binary_name": "linux-realtime-tools-host",
"binary_version": "5.15.0-1073.81"
},
{
"binary_name": "linux-tools-5.15.0-1073-realtime",
"binary_version": "5.15.0-1073.81"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:Realtime:22.04:LTS",
"name": "linux-realtime",
"purl": "pkg:deb/ubuntu/linux-realtime@5.15.0-1073.81?arch=source\u0026distro=realtime/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1073.81"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1006.6",
"5.15.0-1007.7",
"5.15.0-1009.9",
"5.15.0-1011.11",
"5.15.0-1014.14",
"5.15.0-1015.15",
"5.15.0-1016.16",
"5.15.0-1019.19",
"5.15.0-1020.20",
"5.15.0-1021.21",
"5.15.0-1022.22",
"5.15.0-1024.25",
"5.15.0-1025.28",
"5.15.0-1028.31",
"5.15.0-1029.32",
"5.15.0-1030.33",
"5.15.0-1032.35",
"5.15.0-1033.36",
"5.15.0-1034.37",
"5.15.0-1036.39",
"5.15.0-1037.40",
"5.15.0-1038.41",
"5.15.0-1039.42",
"5.15.0-1040.45",
"5.15.0-1041.46",
"5.15.0-1042.47",
"5.15.0-1043.48",
"5.15.0-1044.49",
"5.15.0-1045.50",
"5.15.0-1046.52",
"5.15.0-1048.54",
"5.15.0-1049.55",
"5.15.0-1050.56",
"5.15.0-1051.57",
"5.15.0-1052.58",
"5.15.0-1053.59",
"5.15.0-1054.60",
"5.15.0-1055.62",
"5.15.0-1056.63",
"5.15.0-1057.64",
"5.15.0-1058.66",
"5.15.0-1061.69",
"5.15.0-1062.70",
"5.15.0-1063.71",
"5.15.0-1064.72",
"5.15.0-1065.73",
"5.15.0-1066.74",
"5.15.0-1067.75",
"5.15.0-1068.76",
"5.15.0-1069.77",
"5.15.0-1070.78",
"5.15.0-1071.79",
"5.15.0-1072.80"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14~22.04.1"
},
{
"binary_name": "linux-headers-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14~22.04.1"
},
{
"binary_name": "linux-modules-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14~22.04.1"
},
{
"binary_name": "linux-realtime-6.8-cloud-tools-6.8.1-1013",
"binary_version": "6.8.1-1013.14~22.04.1"
},
{
"binary_name": "linux-realtime-6.8-headers-6.8.1-1013",
"binary_version": "6.8.1-1013.14~22.04.1"
},
{
"binary_name": "linux-realtime-6.8-tools-6.8.1-1013",
"binary_version": "6.8.1-1013.14~22.04.1"
},
{
"binary_name": "linux-tools-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:Realtime:22.04:LTS",
"name": "linux-realtime-6.8",
"purl": "pkg:deb/ubuntu/linux-realtime-6.8@6.8.1-1013.14~22.04.1?arch=source\u0026distro=realtime/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.1-1013.14~22.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.1-1004.4~22.04.1",
"6.8.1-1005.5~22.04.2",
"6.8.1-1006.6~22.04.1",
"6.8.1-1007.7~22.04.1",
"6.8.1-1008.8~22.04.1",
"6.8.1-1009.9~22.04.1",
"6.8.1-1010.10~22.04.1",
"6.8.1-1011.11~22.04.1",
"6.8.1-1012.12~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-50-generic",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-buildinfo-6.8.0-50-generic-64k",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-cloud-tools-6.8.0-50",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-cloud-tools-6.8.0-50-generic",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-cloud-tools-common",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-headers-6.8.0-50",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-headers-6.8.0-50-generic",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-headers-6.8.0-50-generic-64k",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-image-6.8.0-50-generic",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-image-unsigned-6.8.0-50-generic",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-image-unsigned-6.8.0-50-generic-64k",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-lib-rust-6.8.0-50-generic",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-modules-6.8.0-50-generic",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-modules-6.8.0-50-generic-64k",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-modules-extra-6.8.0-50-generic",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-modules-ipu6-6.8.0-50-generic",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-50-generic",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-modules-usbio-6.8.0-50-generic",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-source-6.8.0",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-tools-6.8.0-50",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-tools-6.8.0-50-generic",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-tools-6.8.0-50-generic-64k",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-tools-common",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-tools-host",
"binary_version": "6.8.0-50.51"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux",
"purl": "pkg:deb/ubuntu/linux@6.8.0-50.51?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-50.51"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-9.9",
"6.6.0-14.14",
"6.8.0-11.11",
"6.8.0-20.20",
"6.8.0-22.22",
"6.8.0-28.28",
"6.8.0-31.31",
"6.8.0-35.35",
"6.8.0-36.36",
"6.8.0-38.38",
"6.8.0-39.39",
"6.8.0-40.40",
"6.8.0-41.41",
"6.8.0-44.44",
"6.8.0-45.45",
"6.8.0-47.47",
"6.8.0-48.48",
"6.8.0-49.49"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-aws-cloud-tools-6.8.0-1020",
"binary_version": "6.8.0-1020.22"
},
{
"binary_name": "linux-aws-headers-6.8.0-1020",
"binary_version": "6.8.0-1020.22"
},
{
"binary_name": "linux-aws-tools-6.8.0-1020",
"binary_version": "6.8.0-1020.22"
},
{
"binary_name": "linux-buildinfo-6.8.0-1020-aws",
"binary_version": "6.8.0-1020.22"
},
{
"binary_name": "linux-cloud-tools-6.8.0-1020-aws",
"binary_version": "6.8.0-1020.22"
},
{
"binary_name": "linux-headers-6.8.0-1020-aws",
"binary_version": "6.8.0-1020.22"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1020-aws",
"binary_version": "6.8.0-1020.22"
},
{
"binary_name": "linux-modules-6.8.0-1020-aws",
"binary_version": "6.8.0-1020.22"
},
{
"binary_name": "linux-modules-extra-6.8.0-1020-aws",
"binary_version": "6.8.0-1020.22"
},
{
"binary_name": "linux-tools-6.8.0-1020-aws",
"binary_version": "6.8.0-1020.22"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-aws",
"purl": "pkg:deb/ubuntu/linux-aws@6.8.0-1020.22?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1020.22"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-1008.8",
"6.6.0-1001.1",
"6.8.0-1001.1",
"6.8.0-1006.6",
"6.8.0-1008.8",
"6.8.0-1009.9",
"6.8.0-1010.10",
"6.8.0-1011.12",
"6.8.0-1012.13",
"6.8.0-1013.14",
"6.8.0-1014.15",
"6.8.0-1015.16",
"6.8.0-1016.17",
"6.8.0-1017.18",
"6.8.0-1018.20",
"6.8.0-1019.21"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-azure-cloud-tools-6.8.0-1020",
"binary_version": "6.8.0-1020.23"
},
{
"binary_name": "linux-azure-headers-6.8.0-1020",
"binary_version": "6.8.0-1020.23"
},
{
"binary_name": "linux-azure-tools-6.8.0-1020",
"binary_version": "6.8.0-1020.23"
},
{
"binary_name": "linux-buildinfo-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23"
},
{
"binary_name": "linux-cloud-tools-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23"
},
{
"binary_name": "linux-headers-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23"
},
{
"binary_name": "linux-modules-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23"
},
{
"binary_name": "linux-modules-extra-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23"
},
{
"binary_name": "linux-modules-involflt-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23"
},
{
"binary_name": "linux-tools-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-azure",
"purl": "pkg:deb/ubuntu/linux-azure@6.8.0-1020.23?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1020.23"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-1007.7",
"6.6.0-1001.1",
"6.8.0-1001.1",
"6.8.0-1005.5",
"6.8.0-1006.6",
"6.8.0-1007.7",
"6.8.0-1008.8",
"6.8.0-1009.9",
"6.8.0-1010.10",
"6.8.0-1012.14",
"6.8.0-1013.15",
"6.8.0-1014.16",
"6.8.0-1015.17",
"6.8.0-1016.18",
"6.8.0-1017.20",
"6.8.0-1018.21"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1019-gcp",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-gcp-headers-6.8.0-1019",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-gcp-tools-6.8.0-1019",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-headers-6.8.0-1019-gcp",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1019-gcp",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-modules-6.8.0-1019-gcp",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-modules-extra-6.8.0-1019-gcp",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-tools-6.8.0-1019-gcp",
"binary_version": "6.8.0-1019.21"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-gcp",
"purl": "pkg:deb/ubuntu/linux-gcp@6.8.0-1019.21?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1019.21"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-1007.7",
"6.6.0-1001.1",
"6.8.0-1002.2",
"6.8.0-1005.5",
"6.8.0-1006.6",
"6.8.0-1007.7",
"6.8.0-1008.9",
"6.8.0-1009.10",
"6.8.0-1010.11",
"6.8.0-1011.12",
"6.8.0-1012.13",
"6.8.0-1013.14",
"6.8.0-1014.16",
"6.8.0-1015.17",
"6.8.0-1016.18",
"6.8.0-1017.19",
"6.8.0-1018.20"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1015-gke",
"binary_version": "6.8.0-1015.19"
},
{
"binary_name": "linux-gke-headers-6.8.0-1015",
"binary_version": "6.8.0-1015.19"
},
{
"binary_name": "linux-gke-tools-6.8.0-1015",
"binary_version": "6.8.0-1015.19"
},
{
"binary_name": "linux-headers-6.8.0-1015-gke",
"binary_version": "6.8.0-1015.19"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1015-gke",
"binary_version": "6.8.0-1015.19"
},
{
"binary_name": "linux-modules-6.8.0-1015-gke",
"binary_version": "6.8.0-1015.19"
},
{
"binary_name": "linux-modules-extra-6.8.0-1015-gke",
"binary_version": "6.8.0-1015.19"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-1015-gke",
"binary_version": "6.8.0-1015.19"
},
{
"binary_name": "linux-tools-6.8.0-1015-gke",
"binary_version": "6.8.0-1015.19"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-gke",
"purl": "pkg:deb/ubuntu/linux-gke@6.8.0-1015.19?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1015.19"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1003.5",
"6.8.0-1004.7",
"6.8.0-1005.8",
"6.8.0-1006.9",
"6.8.0-1007.10",
"6.8.0-1008.11",
"6.8.0-1009.12",
"6.8.0-1010.13",
"6.8.0-1011.14",
"6.8.0-1012.15",
"6.8.0-1013.17",
"6.8.0-1014.18"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1002-gkeop",
"binary_version": "6.8.0-1002.4"
},
{
"binary_name": "linux-cloud-tools-6.8.0-1002-gkeop",
"binary_version": "6.8.0-1002.4"
},
{
"binary_name": "linux-gkeop-cloud-tools-6.8.0-1002",
"binary_version": "6.8.0-1002.4"
},
{
"binary_name": "linux-gkeop-headers-6.8.0-1002",
"binary_version": "6.8.0-1002.4"
},
{
"binary_name": "linux-gkeop-tools-6.8.0-1002",
"binary_version": "6.8.0-1002.4"
},
{
"binary_name": "linux-headers-6.8.0-1002-gkeop",
"binary_version": "6.8.0-1002.4"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1002-gkeop",
"binary_version": "6.8.0-1002.4"
},
{
"binary_name": "linux-modules-6.8.0-1002-gkeop",
"binary_version": "6.8.0-1002.4"
},
{
"binary_name": "linux-modules-extra-6.8.0-1002-gkeop",
"binary_version": "6.8.0-1002.4"
},
{
"binary_name": "linux-tools-6.8.0-1002-gkeop",
"binary_version": "6.8.0-1002.4"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-gkeop",
"purl": "pkg:deb/ubuntu/linux-gkeop@6.8.0-1002.4?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1002.4"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1001.3"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1017-ibm",
"binary_version": "6.8.0-1017.17"
},
{
"binary_name": "linux-headers-6.8.0-1017-ibm",
"binary_version": "6.8.0-1017.17"
},
{
"binary_name": "linux-ibm-cloud-tools-common",
"binary_version": "6.8.0-1017.17"
},
{
"binary_name": "linux-ibm-headers-6.8.0-1017",
"binary_version": "6.8.0-1017.17"
},
{
"binary_name": "linux-ibm-source-6.8.0",
"binary_version": "6.8.0-1017.17"
},
{
"binary_name": "linux-ibm-tools-6.8.0-1017",
"binary_version": "6.8.0-1017.17"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1017-ibm",
"binary_version": "6.8.0-1017.17"
},
{
"binary_name": "linux-modules-6.8.0-1017-ibm",
"binary_version": "6.8.0-1017.17"
},
{
"binary_name": "linux-modules-extra-6.8.0-1017-ibm",
"binary_version": "6.8.0-1017.17"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-1017-ibm",
"binary_version": "6.8.0-1017.17"
},
{
"binary_name": "linux-tools-6.8.0-1017-ibm",
"binary_version": "6.8.0-1017.17"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-ibm",
"purl": "pkg:deb/ubuntu/linux-ibm@6.8.0-1017.17?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1017.17"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-1009.9",
"6.8.0-1001.1",
"6.8.0-1003.3",
"6.8.0-1004.4",
"6.8.0-1005.5",
"6.8.0-1006.6",
"6.8.0-1007.7",
"6.8.0-1008.8",
"6.8.0-1009.9",
"6.8.0-1010.10",
"6.8.0-1011.11",
"6.8.0-1012.12",
"6.8.0-1013.13",
"6.8.0-1014.14",
"6.8.0-1015.15",
"6.8.0-1016.16"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-buildinfo-6.8.0-50-lowlatency-64k",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-cloud-tools-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-headers-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-headers-6.8.0-50-lowlatency-64k",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-50-lowlatency-64k",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-lowlatency-cloud-tools-6.8.0-50",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-lowlatency-headers-6.8.0-50",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-lowlatency-lib-rust-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-lowlatency-tools-6.8.0-50",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-modules-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-modules-6.8.0-50-lowlatency-64k",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-tools-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-tools-6.8.0-50-lowlatency-64k",
"binary_version": "6.8.0-50.51.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-lowlatency",
"purl": "pkg:deb/ubuntu/linux-lowlatency@6.8.0-50.51.1?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-50.51.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-9.9.1",
"6.6.0-14.14.1",
"6.8.0-7.7.1",
"6.8.0-25.25.3",
"6.8.0-28.28.1",
"6.8.0-31.31.1",
"6.8.0-35.35.1",
"6.8.0-36.36.1",
"6.8.0-38.38.1",
"6.8.0-39.39.1",
"6.8.0-40.40.1",
"6.8.0-41.41.1",
"6.8.0-44.44.1",
"6.8.0-45.45.1",
"6.8.0-47.47.1",
"6.8.0-48.48.3",
"6.8.0-49.49.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1019-nvidia",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-buildinfo-6.8.0-1019-nvidia-64k",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-headers-6.8.0-1019-nvidia",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-headers-6.8.0-1019-nvidia-64k",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1019-nvidia",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1019-nvidia-64k",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-modules-6.8.0-1019-nvidia",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-modules-6.8.0-1019-nvidia-64k",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-modules-extra-6.8.0-1019-nvidia",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-modules-nvidia-fs-6.8.0-1019-nvidia",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-modules-nvidia-fs-6.8.0-1019-nvidia-64k",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-nvidia-headers-6.8.0-1019",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-nvidia-tools-6.8.0-1019",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-tools-6.8.0-1019-nvidia",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-tools-6.8.0-1019-nvidia-64k",
"binary_version": "6.8.0-1019.21"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-nvidia",
"purl": "pkg:deb/ubuntu/linux-nvidia@6.8.0-1019.21?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1019.21"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1007.7",
"6.8.0-1008.8",
"6.8.0-1009.9",
"6.8.0-1010.10",
"6.8.0-1011.11",
"6.8.0-1012.12",
"6.8.0-1013.14",
"6.8.0-1014.15",
"6.8.0-1015.16",
"6.8.0-1017.19",
"6.8.0-1018.20"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1019-nvidia-lowlatency",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-buildinfo-6.8.0-1019-nvidia-lowlatency-64k",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-headers-6.8.0-1019-nvidia-lowlatency",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-headers-6.8.0-1019-nvidia-lowlatency-64k",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1019-nvidia-lowlatency",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1019-nvidia-lowlatency-64k",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-modules-6.8.0-1019-nvidia-lowlatency",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-modules-6.8.0-1019-nvidia-lowlatency-64k",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1019-nvidia-lowlatency",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-modules-nvidia-fs-6.8.0-1019-nvidia-lowlatency",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-modules-nvidia-fs-6.8.0-1019-nvidia-lowlatency-64k",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-nvidia-lowlatency-headers-6.8.0-1019",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-nvidia-lowlatency-tools-6.8.0-1019",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-nvidia-lowlatency-tools-host",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-tools-6.8.0-1019-nvidia-lowlatency",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-tools-6.8.0-1019-nvidia-lowlatency-64k",
"binary_version": "6.8.0-1019.21.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-nvidia-lowlatency",
"purl": "pkg:deb/ubuntu/linux-nvidia-lowlatency@6.8.0-1019.21.1?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1019.21.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1009.9.1",
"6.8.0-1011.11.1",
"6.8.0-1012.12.1",
"6.8.0-1013.14.1",
"6.8.0-1014.15.1",
"6.8.0-1015.16.1",
"6.8.0-1017.19.1",
"6.8.0-1018.20.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1018-oem",
"binary_version": "6.8.0-1018.18"
},
{
"binary_name": "linux-headers-6.8.0-1018-oem",
"binary_version": "6.8.0-1018.18"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1018-oem",
"binary_version": "6.8.0-1018.18"
},
{
"binary_name": "linux-modules-6.8.0-1018-oem",
"binary_version": "6.8.0-1018.18"
},
{
"binary_name": "linux-modules-ipu6-6.8.0-1018-oem",
"binary_version": "6.8.0-1018.18"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-1018-oem",
"binary_version": "6.8.0-1018.18"
},
{
"binary_name": "linux-modules-usbio-6.8.0-1018-oem",
"binary_version": "6.8.0-1018.18"
},
{
"binary_name": "linux-oem-6.8-headers-6.8.0-1018",
"binary_version": "6.8.0-1018.18"
},
{
"binary_name": "linux-oem-6.8-tools-6.8.0-1018",
"binary_version": "6.8.0-1018.18"
},
{
"binary_name": "linux-tools-6.8.0-1018-oem",
"binary_version": "6.8.0-1018.18"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-oem-6.8",
"purl": "pkg:deb/ubuntu/linux-oem-6.8@6.8.0-1018.18?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1018.18"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1003.3",
"6.8.0-1004.4",
"6.8.0-1005.5",
"6.8.0-1006.6",
"6.8.0-1007.7",
"6.8.0-1008.8",
"6.8.0-1009.9",
"6.8.0-1010.10",
"6.8.0-1011.11",
"6.8.0-1012.12",
"6.8.0-1013.13",
"6.8.0-1014.14",
"6.8.0-1016.16",
"6.8.0-1017.17"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1017-oracle",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-buildinfo-6.8.0-1017-oracle-64k",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-headers-6.8.0-1017-oracle",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-headers-6.8.0-1017-oracle-64k",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1017-oracle",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1017-oracle-64k",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-modules-6.8.0-1017-oracle",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-modules-6.8.0-1017-oracle-64k",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-modules-extra-6.8.0-1017-oracle",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-modules-extra-6.8.0-1017-oracle-64k",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-oracle-headers-6.8.0-1017",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-oracle-tools-6.8.0-1017",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-tools-6.8.0-1017-oracle",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-tools-6.8.0-1017-oracle-64k",
"binary_version": "6.8.0-1017.18"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-oracle",
"purl": "pkg:deb/ubuntu/linux-oracle@6.8.0-1017.18?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1017.18"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-1010.10",
"6.6.0-1001.1",
"6.8.0-1001.1",
"6.8.0-1004.4",
"6.8.0-1005.5",
"6.8.0-1006.6",
"6.8.0-1008.8",
"6.8.0-1010.10",
"6.8.0-1011.11",
"6.8.0-1012.12",
"6.8.0-1013.13",
"6.8.0-1014.14",
"6.8.0-1015.16",
"6.8.0-1016.17"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1016-raspi",
"binary_version": "6.8.0-1016.18"
},
{
"binary_name": "linux-headers-6.8.0-1016-raspi",
"binary_version": "6.8.0-1016.18"
},
{
"binary_name": "linux-image-6.8.0-1016-raspi",
"binary_version": "6.8.0-1016.18"
},
{
"binary_name": "linux-modules-6.8.0-1016-raspi",
"binary_version": "6.8.0-1016.18"
},
{
"binary_name": "linux-raspi-headers-6.8.0-1016",
"binary_version": "6.8.0-1016.18"
},
{
"binary_name": "linux-raspi-tools-6.8.0-1016",
"binary_version": "6.8.0-1016.18"
},
{
"binary_name": "linux-tools-6.8.0-1016-raspi",
"binary_version": "6.8.0-1016.18"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-raspi",
"purl": "pkg:deb/ubuntu/linux-raspi@6.8.0-1016.18?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1016.18"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-1005.7",
"6.7.0-1001.1",
"6.8.0-1001.1",
"6.8.0-1002.2",
"6.8.0-1003.3",
"6.8.0-1004.4",
"6.8.0-1005.5",
"6.8.0-1006.6",
"6.8.0-1007.7",
"6.8.0-1008.8",
"6.8.0-1009.10",
"6.8.0-1010.11",
"6.8.0-1011.12",
"6.8.0-1012.13",
"6.8.0-1013.14",
"6.8.0-1014.16",
"6.8.0-1015.17"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-50-generic",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-headers-6.8.0-50-generic",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-image-6.8.0-50-generic",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-modules-6.8.0-50-generic",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-riscv-headers-6.8.0-50",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-riscv-tools-6.8.0-50",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-tools-6.8.0-50-generic",
"binary_version": "6.8.0-50.51.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-riscv",
"purl": "pkg:deb/ubuntu/linux-riscv@6.8.0-50.51.1?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-50.51.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-9.9.1",
"6.8.0-20.20.1",
"6.8.0-28.28.1",
"6.8.0-31.31.1",
"6.8.0-35.35.1",
"6.8.0-36.36.1",
"6.8.0-38.38.1",
"6.8.0-39.39.1",
"6.8.0-40.40.1",
"6.8.0-41.41.1",
"6.8.0-44.44.1",
"6.8.0-47.47.1",
"6.8.0-48.48.1",
"6.8.0-49.49.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1017-xilinx",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-headers-6.8.0-1017-xilinx",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-image-6.8.0-1017-xilinx",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-modules-6.8.0-1017-xilinx",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-tools-6.8.0-1017-xilinx",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-xilinx-headers-6.8.0-1017",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-xilinx-tools-6.8.0-1017",
"binary_version": "6.8.0-1017.18"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-xilinx",
"purl": "pkg:deb/ubuntu/linux-xilinx@6.8.0-1017.18?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1017.18"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1008.9",
"6.8.0-1009.10",
"6.8.0-1011.12",
"6.8.0-1012.13",
"6.8.0-1013.14",
"6.8.0-1014.15",
"6.8.0-1015.16"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-fips-headers-6.8.0-78",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-fips-lib-rust-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-fips-tools-6.8.0-78",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-headers-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-image-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-image-hmac-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-modules-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-modules-extra-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-modules-ipu6-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-modules-usbio-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-tools-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:24.04:LTS",
"name": "linux-fips",
"purl": "pkg:deb/ubuntu/linux-fips@6.8.0-78.78+fips1?arch=source\u0026distro=fips-updates/noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-78.78+fips1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-38.38+fips4"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-2015-raspi-realtime",
"binary_version": "6.8.0-2015.16"
},
{
"binary_name": "linux-headers-6.8.0-2015-raspi-realtime",
"binary_version": "6.8.0-2015.16"
},
{
"binary_name": "linux-image-6.8.0-2015-raspi-realtime",
"binary_version": "6.8.0-2015.16"
},
{
"binary_name": "linux-modules-6.8.0-2015-raspi-realtime",
"binary_version": "6.8.0-2015.16"
},
{
"binary_name": "linux-raspi-realtime-headers-6.8.0-2015",
"binary_version": "6.8.0-2015.16"
},
{
"binary_name": "linux-raspi-realtime-tools-6.8.0-2015",
"binary_version": "6.8.0-2015.16"
},
{
"binary_name": "linux-tools-6.8.0-2015-raspi-realtime",
"binary_version": "6.8.0-2015.16"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:Realtime:24.04:LTS",
"name": "linux-raspi-realtime",
"purl": "pkg:deb/ubuntu/linux-raspi-realtime@6.8.0-2015.16?arch=source\u0026distro=realtime/noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-2015.16"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.7.0-2001.1",
"6.8.0-2001.1",
"6.8.0-2002.2",
"6.8.0-2004.4",
"6.8.0-2005.5",
"6.8.0-2006.6",
"6.8.0-2007.7",
"6.8.0-2008.8",
"6.8.0-2009.9",
"6.8.0-2010.10",
"6.8.0-2011.11",
"6.8.0-2012.12",
"6.8.0-2013.14",
"6.8.0-2014.15"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14"
},
{
"binary_name": "linux-cloud-tools-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14"
},
{
"binary_name": "linux-headers-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14"
},
{
"binary_name": "linux-image-unsigned-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14"
},
{
"binary_name": "linux-modules-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14"
},
{
"binary_name": "linux-modules-extra-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14"
},
{
"binary_name": "linux-realtime-cloud-tools-6.8.1-1013",
"binary_version": "6.8.1-1013.14"
},
{
"binary_name": "linux-realtime-headers-6.8.1-1013",
"binary_version": "6.8.1-1013.14"
},
{
"binary_name": "linux-realtime-tools-6.8.1-1013",
"binary_version": "6.8.1-1013.14"
},
{
"binary_name": "linux-tools-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:Realtime:24.04:LTS",
"name": "linux-realtime",
"purl": "pkg:deb/ubuntu/linux-realtime@6.8.1-1013.14?arch=source\u0026distro=realtime/noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.1-1013.14"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1008.19",
"6.8.1-1001.1",
"6.8.1-1002.2",
"6.8.1-1003.3",
"6.8.1-1004.4",
"6.8.1-1005.5",
"6.8.1-1006.6",
"6.8.1-1007.7",
"6.8.1-1008.8",
"6.8.1-1009.9",
"6.8.1-1010.10",
"6.8.1-1011.11",
"6.8.1-1012.12"
]
}
],
"aliases": [],
"details": "In the Linux kernel, the following vulnerability has been resolved: smack: tcp: ipv4, fix incorrect labeling Currently, Smack mirrors the label of incoming tcp/ipv4 connections: when a label \u0027foo\u0027 connects to a label \u0027bar\u0027 with tcp/ipv4, \u0027foo\u0027 always gets \u0027foo\u0027 in returned ipv4 packets. So, 1) returned packets are incorrectly labeled (\u0027foo\u0027 instead of \u0027bar\u0027) 2) \u0027bar\u0027 can write to \u0027foo\u0027 without being authorized to write. Here is a scenario how to see this: * Take two machines, let\u0027s call them C and S, with active Smack in the default state (no settings, no rules, no labeled hosts, only builtin labels) * At S, add Smack rule \u0027foo bar w\u0027 (labels \u0027foo\u0027 and \u0027bar\u0027 are instantiated at S at this moment) * At S, at label \u0027bar\u0027, launch a program that listens for incoming tcp/ipv4 connections * From C, at label \u0027foo\u0027, connect to the listener at S. (label \u0027foo\u0027 is instantiated at C at this moment) Connection succeedes and works. * Send some data in both directions. * Collect network traffic of this connection. All packets in both directions are labeled with the CIPSO of the label \u0027foo\u0027. Hence, label \u0027bar\u0027 writes to \u0027foo\u0027 without being authorized, and even without ever being known at C. If anybody cares: exactly the same happens with DCCP. This behavior 1st manifested in release 2.6.29.4 (see Fixes below) and it looks unintentional. At least, no explanation was provided. I changed returned packes label into the \u0027bar\u0027, to bring it into line with the Smack documentation claims.",
"id": "UBUNTU-CVE-2024-47659",
"modified": "2026-09-17T16:24:48Z",
"published": "2024-10-09T14:15:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2024-47659"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-47659"
},
{
"type": "REPORT",
"url": "https://git.kernel.org/stable/c/d3f56c653c65f170b172d3c23120bc64ada645d8"
},
{
"type": "REPORT",
"url": "https://git.kernel.org/stable/c/5b4b304f196c070342e32a4752e1fa2e22fc0671"
},
{
"type": "REPORT",
"url": "https://git.kernel.org/stable/c/a948ec993541db4ef392b555c37a1186f4d61670"
},
{
"type": "REPORT",
"url": "https://git.kernel.org/stable/c/0aea09e82eafa50a373fc8a4b84c1d4734751e2c"
},
{
"type": "REPORT",
"url": "https://git.kernel.org/stable/c/0776bcf9cb6de46fdd94d10118de1cf9b05f83b9"
},
{
"type": "REPORT",
"url": "https://git.kernel.org/stable/c/4be9fd15c3c88775bdf6fa37acabe6de85beebff"
},
{
"type": "REPORT",
"url": "https://git.kernel.org/stable/c/d3703fa94116fed91f64c7d1c7d284fb4369070f"
},
{
"type": "REPORT",
"url": "https://git.kernel.org/stable/c/2fe209d0ad2e2729f7e22b9b31a86cc3ff0db550"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7088-1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7088-2"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7088-3"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7088-4"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7100-1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7100-2"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7088-5"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7119-1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7123-1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7144-1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7154-1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7155-1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7156-1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7154-2"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7194-1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7196-1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-8070-1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-8070-2"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-8070-3"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-8112-1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-8112-2"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-8112-3"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-8112-4"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-8112-5"
}
],
"related": [
"USN-7088-1",
"USN-7088-2",
"USN-7088-3",
"USN-7088-4",
"USN-7100-1",
"USN-7100-2",
"USN-7088-5",
"USN-7119-1",
"USN-7123-1",
"USN-7144-1",
"USN-7154-1",
"USN-7155-1",
"USN-7156-1",
"USN-7154-2",
"USN-7194-1",
"USN-7196-1",
"USN-8070-1",
"USN-8070-2",
"USN-8070-3",
"USN-8112-1",
"USN-8112-2",
"USN-8112-3",
"USN-8112-4",
"USN-8112-5"
],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
},
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2024-47659"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.