Action not permitted
Modal body text goes here.
Modal Title
Modal Body
CVE-2024-38605 (GCVE-0-2024-38605)
Vulnerability from cvelistv5 – Published: 2024-06-19 13:48 – Updated: 2026-08-05 11:33- CWE-476 - NULL Pointer Dereference
| Vendor | Product | Version | |
|---|---|---|---|
| Linux | Linux |
Affected:
81033c6b584b44514cbb16fffc26ca29a0fa6270 , < d7ff29a429b56f04783152ad7bbd7233b740e434
(git)
Affected: 81033c6b584b44514cbb16fffc26ca29a0fa6270 , < e7e0ca200772bdb2fdc6d43d32d341e87a36f811 (git) Affected: 81033c6b584b44514cbb16fffc26ca29a0fa6270 , < e007476725730c1a68387b54b7629486d8a8301e (git) Affected: 81033c6b584b44514cbb16fffc26ca29a0fa6270 , < e644036a3e2b2c9b3eee3c61b5d31c2ca8b5ba92 (git) Affected: 81033c6b584b44514cbb16fffc26ca29a0fa6270 , < c935e72139e6d523defd60fe875c01eb1f9ea5c5 (git) Affected: 81033c6b584b44514cbb16fffc26ca29a0fa6270 , < 6b8374ee2cabcf034faa34e69a855dc496a9ec12 (git) Affected: 81033c6b584b44514cbb16fffc26ca29a0fa6270 , < 39381fe7394e5eafac76e7e9367e7351138a29c1 (git) |
|
| Linux | Linux |
Affected:
5.9
Unaffected: 0 , < 5.9 (semver) Unaffected: 5.10.219 , ≤ 5.10.* (semver) Unaffected: 5.15.161 , ≤ 5.15.* (semver) Unaffected: 6.1.93 , ≤ 6.1.* (semver) Unaffected: 6.6.33 , ≤ 6.6.* (semver) Unaffected: 6.8.12 , ≤ 6.8.* (semver) Unaffected: 6.9.3 , ≤ 6.9.* (semver) Unaffected: 6.10 , ≤ * (original_commit_for_fix) |
|
| linux | linux_kernel |
Affected:
81033c6b584b , < d7ff29a429b5
(custom)
cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:* |
|
| linux | linux_kernel |
Affected:
81033c6b584b , < e7e0ca200772
(custom)
cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:* |
|
| linux | linux_kernel |
Affected:
81033c6b584b , < e00747672573
(custom)
cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:* |
|
| linux | linux_kernel |
Affected:
81033c6b584b , < e644036a3e2b
(custom)
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* |
|
| linux | linux_kernel |
Affected:
81033c6b584b , < c935e72139e6
(custom)
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* |
|
| linux | linux_kernel |
Affected:
81033c6b584b , < 6b8374ee2cab
(custom)
cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:* |
|
| linux | linux_kernel |
Affected:
81033c6b584b , < 39381fe7394e
(custom)
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* |
|
| linux | linux_kernel |
Affected:
5.9
cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:* |
|
| linux | linux_kernel |
Unaffected:
0 , < 5.9
(custom)
cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:* |
|
| linux | linux_kernel |
Unaffected:
5.10.219 , ≤ 5.11
(custom)
cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:* |
|
| linux | linux_kernel |
Unaffected:
5.15.161 , ≤ 5.16
(custom)
cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:* |
|
| linux | linux_kernel |
Unaffected:
6.1.93 , ≤ 6.2
(custom)
cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:* |
|
| linux | linux_kernel |
Unaffected:
6.6.33 , ≤ 6.7
(custom)
cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:* |
|
| linux | linux_kernel |
Unaffected:
6.8.12 , ≤ 6.9
(custom)
cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:* |
|
| linux | linux_kernel |
Unaffected:
6.9.3 , ≤ 6.7
(custom)
cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:* |
|
| linux | linux_kernel |
Unaffected:
6.10-rc1
cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:* |
{
"containers": {
"adp": [
{
"affected": [
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"lessThan": "d7ff29a429b5",
"status": "affected",
"version": "81033c6b584b",
"versionType": "custom"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"lessThan": "e7e0ca200772",
"status": "affected",
"version": "81033c6b584b",
"versionType": "custom"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"lessThan": "e00747672573",
"status": "affected",
"version": "81033c6b584b",
"versionType": "custom"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"lessThan": "e644036a3e2b",
"status": "affected",
"version": "81033c6b584b",
"versionType": "custom"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"lessThan": "c935e72139e6",
"status": "affected",
"version": "81033c6b584b",
"versionType": "custom"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"lessThan": "6b8374ee2cab",
"status": "affected",
"version": "81033c6b584b",
"versionType": "custom"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"lessThan": "39381fe7394e",
"status": "affected",
"version": "81033c6b584b",
"versionType": "custom"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"status": "affected",
"version": "5.9"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"lessThan": "5.9",
"status": "unaffected",
"version": "0",
"versionType": "custom"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"lessThanOrEqual": "5.11",
"status": "unaffected",
"version": "5.10.219",
"versionType": "custom"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"lessThanOrEqual": "5.16",
"status": "unaffected",
"version": "5.15.161",
"versionType": "custom"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"lessThanOrEqual": "6.2",
"status": "unaffected",
"version": "6.1.93",
"versionType": "custom"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"lessThanOrEqual": "6.7",
"status": "unaffected",
"version": "6.6.33",
"versionType": "custom"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"lessThanOrEqual": "6.9",
"status": "unaffected",
"version": "6.8.12",
"versionType": "custom"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"lessThanOrEqual": "6.7",
"status": "unaffected",
"version": "6.9.3",
"versionType": "custom"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"status": "unaffected",
"version": "6.10-rc1"
}
]
}
],
"metrics": [
{
"cvssV3_1": {
"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"
}
},
{
"other": {
"content": {
"id": "CVE-2024-38605",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2024-06-27T17:45:58.997847Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-476",
"description": "CWE-476 NULL Pointer Dereference",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2024-06-27T18:08:30.086Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
},
{
"providerMetadata": {
"dateUpdated": "2024-08-02T04:12:25.960Z",
"orgId": "af854a3a-2127-422b-91ae-364da2661108",
"shortName": "CVE"
},
"references": [
{
"tags": [
"x_transferred"
],
"url": "https://git.kernel.org/stable/c/d7ff29a429b56f04783152ad7bbd7233b740e434"
},
{
"tags": [
"x_transferred"
],
"url": "https://git.kernel.org/stable/c/e7e0ca200772bdb2fdc6d43d32d341e87a36f811"
},
{
"tags": [
"x_transferred"
],
"url": "https://git.kernel.org/stable/c/e007476725730c1a68387b54b7629486d8a8301e"
},
{
"tags": [
"x_transferred"
],
"url": "https://git.kernel.org/stable/c/e644036a3e2b2c9b3eee3c61b5d31c2ca8b5ba92"
},
{
"tags": [
"x_transferred"
],
"url": "https://git.kernel.org/stable/c/c935e72139e6d523defd60fe875c01eb1f9ea5c5"
},
{
"tags": [
"x_transferred"
],
"url": "https://git.kernel.org/stable/c/6b8374ee2cabcf034faa34e69a855dc496a9ec12"
},
{
"tags": [
"x_transferred"
],
"url": "https://git.kernel.org/stable/c/39381fe7394e5eafac76e7e9367e7351138a29c1"
}
],
"title": "CVE Program Container"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"sound/core/init.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "d7ff29a429b56f04783152ad7bbd7233b740e434",
"status": "affected",
"version": "81033c6b584b44514cbb16fffc26ca29a0fa6270",
"versionType": "git"
},
{
"lessThan": "e7e0ca200772bdb2fdc6d43d32d341e87a36f811",
"status": "affected",
"version": "81033c6b584b44514cbb16fffc26ca29a0fa6270",
"versionType": "git"
},
{
"lessThan": "e007476725730c1a68387b54b7629486d8a8301e",
"status": "affected",
"version": "81033c6b584b44514cbb16fffc26ca29a0fa6270",
"versionType": "git"
},
{
"lessThan": "e644036a3e2b2c9b3eee3c61b5d31c2ca8b5ba92",
"status": "affected",
"version": "81033c6b584b44514cbb16fffc26ca29a0fa6270",
"versionType": "git"
},
{
"lessThan": "c935e72139e6d523defd60fe875c01eb1f9ea5c5",
"status": "affected",
"version": "81033c6b584b44514cbb16fffc26ca29a0fa6270",
"versionType": "git"
},
{
"lessThan": "6b8374ee2cabcf034faa34e69a855dc496a9ec12",
"status": "affected",
"version": "81033c6b584b44514cbb16fffc26ca29a0fa6270",
"versionType": "git"
},
{
"lessThan": "39381fe7394e5eafac76e7e9367e7351138a29c1",
"status": "affected",
"version": "81033c6b584b44514cbb16fffc26ca29a0fa6270",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"sound/core/init.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.9"
},
{
"lessThan": "5.9",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.10.*",
"status": "unaffected",
"version": "5.10.219",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.15.*",
"status": "unaffected",
"version": "5.15.161",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.93",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.33",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.8.*",
"status": "unaffected",
"version": "6.8.12",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.9.*",
"status": "unaffected",
"version": "6.9.3",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "6.10",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.10.219",
"versionStartIncluding": "5.9",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.15.161",
"versionStartIncluding": "5.9",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.1.93",
"versionStartIncluding": "5.9",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.6.33",
"versionStartIncluding": "5.9",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.8.12",
"versionStartIncluding": "5.9",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.9.3",
"versionStartIncluding": "5.9",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.10",
"versionStartIncluding": "5.9",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nALSA: core: Fix NULL module pointer assignment at card init\n\nThe commit 81033c6b584b (\"ALSA: core: Warn on empty module\")\nintroduced a WARN_ON() for a NULL module pointer passed at snd_card\nobject creation, and it also wraps the code around it with \u0027#ifdef\nMODULE\u0027. This works in most cases, but the devils are always in\ndetails. \"MODULE\" is defined when the target code (i.e. the sound\ncore) is built as a module; but this doesn\u0027t mean that the caller is\nalso built-in or not. Namely, when only the sound core is built-in\n(CONFIG_SND=y) while the driver is a module (CONFIG_SND_USB_AUDIO=m),\nthe passed module pointer is ignored even if it\u0027s non-NULL, and\ncard-\u003emodule remains as NULL. This would result in the missing module\nreference up/down at the device open/close, leading to a race with the\ncode execution after the module removal.\n\nFor addressing the bug, move the assignment of card-\u003emodule again out\nof ifdef. The WARN_ON() is still wrapped with ifdef because the\nmodule can be really NULL when all sound drivers are built-in.\n\nNote that we keep \u0027ifdef MODULE\u0027 for WARN_ON(), otherwise it would\nlead to a false-positive NULL module check. Admittedly it won\u0027t catch\nperfectly, i.e. no check is performed when CONFIG_SND=y. But, it\u0027s no\nreal problem as it\u0027s only for debugging, and the condition is pretty\nrare."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 7.8,
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"scenarios": [
{
"lang": "en",
"value": "AV:L - Exploitation requires opening a local ALSA device node (/dev/snd/pcmC*D*, controlC*, hwC*D*, timer, or an OSS/proc equivalent); there is no network-reachable path into snd_card_init or the affected open handlers.\nAC:L - The affected configuration (CONFIG_SND=y with a driver built as a module) is a shipped mainline defconfig, and the attacker deterministically creates the dangling state simply by holding an fd open \u2014 no memory-layout luck or unwinnable race is needed for the stale function-pointer call on release.\nPR:L - Only ordinary access to /dev/snd is needed, which is granted to the logged-in local user via session ACLs or the audio group on desktops and to the audio/media UID on Android \u2014 no capability is required to open the device and defeat the module-reference interlock.\nUI:N - No victim must be tricked into any action; the module removal that triggers the use-after-free occurs autonomously during routine driver updates, power-management, and hotplug scripts, and the attacker\u0027s own open() is what removes the safety interlock.\nS:U - The corruption and its consequences are confined to the kernel\u0027s own security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - The card, substream, kcontrol and hwdep objects retain pointers into freed module text and data, so reads through those stale pointers disclose whatever now occupies the reclaimed module region, and a use-after-free of this class is leverageable into arbitrary kernel memory disclosure.\nI:H - Release and teardown perform indirect calls through substream-\u003eops and card-\u003eprivate_free into freed module memory that can be reallocated with attacker-influenced content, yielding a control-flow hijack primitive rather than a simple fault.\nA:H - Even without weaponization, dereferencing freed module text on close reliably oopses or panics the kernel, and the attacker can arrange this repeatedly."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-05T11:33:05.452Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/d7ff29a429b56f04783152ad7bbd7233b740e434"
},
{
"url": "https://git.kernel.org/stable/c/e7e0ca200772bdb2fdc6d43d32d341e87a36f811"
},
{
"url": "https://git.kernel.org/stable/c/e007476725730c1a68387b54b7629486d8a8301e"
},
{
"url": "https://git.kernel.org/stable/c/e644036a3e2b2c9b3eee3c61b5d31c2ca8b5ba92"
},
{
"url": "https://git.kernel.org/stable/c/c935e72139e6d523defd60fe875c01eb1f9ea5c5"
},
{
"url": "https://git.kernel.org/stable/c/6b8374ee2cabcf034faa34e69a855dc496a9ec12"
},
{
"url": "https://git.kernel.org/stable/c/39381fe7394e5eafac76e7e9367e7351138a29c1"
}
],
"title": "ALSA: core: Fix NULL module pointer assignment at card init",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2024-38605",
"datePublished": "2024-06-19T13:48:15.769Z",
"dateReserved": "2024-06-18T19:36:34.934Z",
"dateUpdated": "2026-08-05T11:33:05.452Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2024-38605",
"date": "2026-11-19",
"epss": "0.00748",
"percentile": "0.55687"
},
"redhat_vex": {
"aggregate_severity": "Low",
"current_release_date": "2026-11-06T14:16:42+00:00",
"cve": "CVE-2024-38605",
"id": "CVE-2024-38605",
"initial_release_date": "2024-06-19T00:00:00+00:00",
"product_status:fixed": "280",
"product_status:known_affected": "112",
"product_status:known_not_affected": "8",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: ALSA: core: Fix NULL module pointer assignment at card init",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2024/cve-2024-38605.json",
"version": "3"
},
"vulnrichment": {
"containers": {
"adp": [
{
"providerMetadata": {
"dateUpdated": "2024-08-02T04:12:25.960Z",
"orgId": "af854a3a-2127-422b-91ae-364da2661108",
"shortName": "CVE"
},
"references": [
{
"tags": [
"x_transferred"
],
"url": "https://git.kernel.org/stable/c/d7ff29a429b56f04783152ad7bbd7233b740e434"
},
{
"tags": [
"x_transferred"
],
"url": "https://git.kernel.org/stable/c/e7e0ca200772bdb2fdc6d43d32d341e87a36f811"
},
{
"tags": [
"x_transferred"
],
"url": "https://git.kernel.org/stable/c/e007476725730c1a68387b54b7629486d8a8301e"
},
{
"tags": [
"x_transferred"
],
"url": "https://git.kernel.org/stable/c/e644036a3e2b2c9b3eee3c61b5d31c2ca8b5ba92"
},
{
"tags": [
"x_transferred"
],
"url": "https://git.kernel.org/stable/c/c935e72139e6d523defd60fe875c01eb1f9ea5c5"
},
{
"tags": [
"x_transferred"
],
"url": "https://git.kernel.org/stable/c/6b8374ee2cabcf034faa34e69a855dc496a9ec12"
},
{
"tags": [
"x_transferred"
],
"url": "https://git.kernel.org/stable/c/39381fe7394e5eafac76e7e9367e7351138a29c1"
}
],
"title": "CVE Program Container"
},
{
"affected": [
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"lessThan": "d7ff29a429b5",
"status": "affected",
"version": "81033c6b584b",
"versionType": "custom"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"lessThan": "e7e0ca200772",
"status": "affected",
"version": "81033c6b584b",
"versionType": "custom"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"lessThan": "e00747672573",
"status": "affected",
"version": "81033c6b584b",
"versionType": "custom"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"lessThan": "e644036a3e2b",
"status": "affected",
"version": "81033c6b584b",
"versionType": "custom"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"lessThan": "c935e72139e6",
"status": "affected",
"version": "81033c6b584b",
"versionType": "custom"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"lessThan": "6b8374ee2cab",
"status": "affected",
"version": "81033c6b584b",
"versionType": "custom"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"lessThan": "39381fe7394e",
"status": "affected",
"version": "81033c6b584b",
"versionType": "custom"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"status": "affected",
"version": "5.9"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"lessThan": "5.9",
"status": "unaffected",
"version": "0",
"versionType": "custom"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"lessThanOrEqual": "5.11",
"status": "unaffected",
"version": "5.10.219",
"versionType": "custom"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"lessThanOrEqual": "5.16",
"status": "unaffected",
"version": "5.15.161",
"versionType": "custom"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"lessThanOrEqual": "6.2",
"status": "unaffected",
"version": "6.1.93",
"versionType": "custom"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"lessThanOrEqual": "6.7",
"status": "unaffected",
"version": "6.6.33",
"versionType": "custom"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"lessThanOrEqual": "6.9",
"status": "unaffected",
"version": "6.8.12",
"versionType": "custom"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"lessThanOrEqual": "6.7",
"status": "unaffected",
"version": "6.9.3",
"versionType": "custom"
}
]
},
{
"cpes": [
"cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "linux_kernel",
"vendor": "linux",
"versions": [
{
"status": "unaffected",
"version": "6.10-rc1"
}
]
}
],
"metrics": [
{
"cvssV3_1": {
"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"
}
},
{
"other": {
"content": {
"id": "CVE-2024-38605",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2024-06-27T17:45:58.997847Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-476",
"description": "CWE-476 NULL Pointer Dereference",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2024-06-27T17:49:16.979Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"sound/core/init.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "d7ff29a429b56f04783152ad7bbd7233b740e434",
"status": "affected",
"version": "81033c6b584b44514cbb16fffc26ca29a0fa6270",
"versionType": "git"
},
{
"lessThan": "e7e0ca200772bdb2fdc6d43d32d341e87a36f811",
"status": "affected",
"version": "81033c6b584b44514cbb16fffc26ca29a0fa6270",
"versionType": "git"
},
{
"lessThan": "e007476725730c1a68387b54b7629486d8a8301e",
"status": "affected",
"version": "81033c6b584b44514cbb16fffc26ca29a0fa6270",
"versionType": "git"
},
{
"lessThan": "e644036a3e2b2c9b3eee3c61b5d31c2ca8b5ba92",
"status": "affected",
"version": "81033c6b584b44514cbb16fffc26ca29a0fa6270",
"versionType": "git"
},
{
"lessThan": "c935e72139e6d523defd60fe875c01eb1f9ea5c5",
"status": "affected",
"version": "81033c6b584b44514cbb16fffc26ca29a0fa6270",
"versionType": "git"
},
{
"lessThan": "6b8374ee2cabcf034faa34e69a855dc496a9ec12",
"status": "affected",
"version": "81033c6b584b44514cbb16fffc26ca29a0fa6270",
"versionType": "git"
},
{
"lessThan": "39381fe7394e5eafac76e7e9367e7351138a29c1",
"status": "affected",
"version": "81033c6b584b44514cbb16fffc26ca29a0fa6270",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"sound/core/init.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.9"
},
{
"lessThan": "5.9",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.10.*",
"status": "unaffected",
"version": "5.10.219",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.15.*",
"status": "unaffected",
"version": "5.15.161",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.93",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.33",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.8.*",
"status": "unaffected",
"version": "6.8.12",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.9.*",
"status": "unaffected",
"version": "6.9.3",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "6.10",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.10.219",
"versionStartIncluding": "5.9",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.15.161",
"versionStartIncluding": "5.9",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.1.93",
"versionStartIncluding": "5.9",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.6.33",
"versionStartIncluding": "5.9",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.8.12",
"versionStartIncluding": "5.9",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.9.3",
"versionStartIncluding": "5.9",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.10",
"versionStartIncluding": "5.9",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nALSA: core: Fix NULL module pointer assignment at card init\n\nThe commit 81033c6b584b (\"ALSA: core: Warn on empty module\")\nintroduced a WARN_ON() for a NULL module pointer passed at snd_card\nobject creation, and it also wraps the code around it with \u0027#ifdef\nMODULE\u0027. This works in most cases, but the devils are always in\ndetails. \"MODULE\" is defined when the target code (i.e. the sound\ncore) is built as a module; but this doesn\u0027t mean that the caller is\nalso built-in or not. Namely, when only the sound core is built-in\n(CONFIG_SND=y) while the driver is a module (CONFIG_SND_USB_AUDIO=m),\nthe passed module pointer is ignored even if it\u0027s non-NULL, and\ncard-\u003emodule remains as NULL. This would result in the missing module\nreference up/down at the device open/close, leading to a race with the\ncode execution after the module removal.\n\nFor addressing the bug, move the assignment of card-\u003emodule again out\nof ifdef. The WARN_ON() is still wrapped with ifdef because the\nmodule can be really NULL when all sound drivers are built-in.\n\nNote that we keep \u0027ifdef MODULE\u0027 for WARN_ON(), otherwise it would\nlead to a false-positive NULL module check. Admittedly it won\u0027t catch\nperfectly, i.e. no check is performed when CONFIG_SND=y. But, it\u0027s no\nreal problem as it\u0027s only for debugging, and the condition is pretty\nrare."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 7.8,
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"scenarios": [
{
"lang": "en",
"value": "AV:L - Exploitation requires opening a local ALSA device node (/dev/snd/pcmC*D*, controlC*, hwC*D*, timer, or an OSS/proc equivalent); there is no network-reachable path into snd_card_init or the affected open handlers.\nAC:L - The affected configuration (CONFIG_SND=y with a driver built as a module) is a shipped mainline defconfig, and the attacker deterministically creates the dangling state simply by holding an fd open \u2014 no memory-layout luck or unwinnable race is needed for the stale function-pointer call on release.\nPR:L - Only ordinary access to /dev/snd is needed, which is granted to the logged-in local user via session ACLs or the audio group on desktops and to the audio/media UID on Android \u2014 no capability is required to open the device and defeat the module-reference interlock.\nUI:N - No victim must be tricked into any action; the module removal that triggers the use-after-free occurs autonomously during routine driver updates, power-management, and hotplug scripts, and the attacker\u0027s own open() is what removes the safety interlock.\nS:U - The corruption and its consequences are confined to the kernel\u0027s own security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - The card, substream, kcontrol and hwdep objects retain pointers into freed module text and data, so reads through those stale pointers disclose whatever now occupies the reclaimed module region, and a use-after-free of this class is leverageable into arbitrary kernel memory disclosure.\nI:H - Release and teardown perform indirect calls through substream-\u003eops and card-\u003eprivate_free into freed module memory that can be reallocated with attacker-influenced content, yielding a control-flow hijack primitive rather than a simple fault.\nA:H - Even without weaponization, dereferencing freed module text on close reliably oopses or panics the kernel, and the attacker can arrange this repeatedly."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-05T11:33:05.452Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/d7ff29a429b56f04783152ad7bbd7233b740e434"
},
{
"url": "https://git.kernel.org/stable/c/e7e0ca200772bdb2fdc6d43d32d341e87a36f811"
},
{
"url": "https://git.kernel.org/stable/c/e007476725730c1a68387b54b7629486d8a8301e"
},
{
"url": "https://git.kernel.org/stable/c/e644036a3e2b2c9b3eee3c61b5d31c2ca8b5ba92"
},
{
"url": "https://git.kernel.org/stable/c/c935e72139e6d523defd60fe875c01eb1f9ea5c5"
},
{
"url": "https://git.kernel.org/stable/c/6b8374ee2cabcf034faa34e69a855dc496a9ec12"
},
{
"url": "https://git.kernel.org/stable/c/39381fe7394e5eafac76e7e9367e7351138a29c1"
}
],
"title": "ALSA: core: Fix NULL module pointer assignment at card init",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2024-38605",
"datePublished": "2024-06-19T13:48:15.769Z",
"dateReserved": "2024-06-18T19:36:34.934Z",
"dateUpdated": "2026-08-05T11:33:05.452Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
CERTFR-2024-AVI-0823
Vulnerability from certfr_avis - Published: 2024-09-27 - Updated: 2024-09-27
De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire, une atteinte à la confidentialité des données et une atteinte à l'intégrité des données.
Solutions
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
None| Title | Publication Time | Tags | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "Ubuntu 16.04 ESM",
"product": {
"name": "Ubuntu",
"vendor": {
"name": "Ubuntu",
"scada": false
}
}
},
{
"description": "Ubuntu 24.04 LTS",
"product": {
"name": "Ubuntu",
"vendor": {
"name": "Ubuntu",
"scada": false
}
}
},
{
"description": "Ubuntu 18.04 ESM",
"product": {
"name": "Ubuntu",
"vendor": {
"name": "Ubuntu",
"scada": false
}
}
},
{
"description": "Ubuntu 20.04 LTS",
"product": {
"name": "Ubuntu",
"vendor": {
"name": "Ubuntu",
"scada": false
}
}
},
{
"description": "Ubuntu 14.04 ESM",
"product": {
"name": "Ubuntu",
"vendor": {
"name": "Ubuntu",
"scada": false
}
}
},
{
"description": "Ubuntu 22.04 LTS",
"product": {
"name": "Ubuntu",
"vendor": {
"name": "Ubuntu",
"scada": false
}
}
}
],
"affected_systems_content": null,
"content": "## Solutions\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour l\u0027obtention des correctifs (cf. section Documentation).",
"cves": [
{
"name": "CVE-2024-39481",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39481"
},
{
"name": "CVE-2024-40986",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40986"
},
{
"name": "CVE-2024-40931",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40931"
},
{
"name": "CVE-2024-42109",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42109"
},
{
"name": "CVE-2024-38662",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38662"
},
{
"name": "CVE-2024-41001",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-41001"
},
{
"name": "CVE-2024-42070",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42070"
},
{
"name": "CVE-2024-41093",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-41093"
},
{
"name": "CVE-2024-38627",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38627"
},
{
"name": "CVE-2024-38306",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38306"
},
{
"name": "CVE-2024-38599",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38599"
},
{
"name": "CVE-2024-39298",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39298"
},
{
"name": "CVE-2024-38555",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38555"
},
{
"name": "CVE-2024-41009",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-41009"
},
{
"name": "CVE-2024-39503",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39503"
},
{
"name": "CVE-2024-36477",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-36477"
},
{
"name": "CVE-2024-38390",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38390"
},
{
"name": "CVE-2024-40903",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40903"
},
{
"name": "CVE-2024-39491",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39491"
},
{
"name": "CVE-2024-40988",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40988"
},
{
"name": "CVE-2024-42137",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42137"
},
{
"name": "CVE-2024-26984",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-26984"
},
{
"name": "CVE-2024-41004",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-41004"
},
{
"name": "CVE-2024-42098",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42098"
},
{
"name": "CVE-2024-40962",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40962"
},
{
"name": "CVE-2024-36973",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-36973"
},
{
"name": "CVE-2024-42089",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42089"
},
{
"name": "CVE-2024-38388",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38388"
},
{
"name": "CVE-2024-40919",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40919"
},
{
"name": "CVE-2024-40935",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40935"
},
{
"name": "CVE-2024-38583",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38583"
},
{
"name": "CVE-2024-40973",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40973"
},
{
"name": "CVE-2022-48851",
"url": "https://www.cve.org/CVERecord?id=CVE-2022-48851"
},
{
"name": "CVE-2024-39474",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39474"
},
{
"name": "CVE-2024-40955",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40955"
},
{
"name": "CVE-2024-41000",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-41000"
},
{
"name": "CVE-2024-36974",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-36974"
},
{
"name": "CVE-2024-39496",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39496"
},
{
"name": "CVE-2024-38384",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38384"
},
{
"name": "CVE-2024-41034",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-41034"
},
{
"name": "CVE-2024-40924",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40924"
},
{
"name": "CVE-2024-39470",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39470"
},
{
"name": "CVE-2024-38548",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38548"
},
{
"name": "CVE-2024-38664",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38664"
},
{
"name": "CVE-2022-48772",
"url": "https://www.cve.org/CVERecord?id=CVE-2022-48772"
},
{
"name": "CVE-2024-36972",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-36972"
},
{
"name": "CVE-2024-37026",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-37026"
},
{
"name": "CVE-2024-37356",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-37356"
},
{
"name": "CVE-2024-42097",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42097"
},
{
"name": "CVE-2024-36479",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-36479"
},
{
"name": "CVE-2024-38632",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38632"
},
{
"name": "CVE-2024-26677",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-26677"
},
{
"name": "CVE-2024-38659",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38659"
},
{
"name": "CVE-2024-42236",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42236"
},
{
"name": "CVE-2024-39469",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39469"
},
{
"name": "CVE-2024-39509",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39509"
},
{
"name": "CVE-2024-42157",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42157"
},
{
"name": "CVE-2024-40975",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40975"
},
{
"name": "CVE-2023-52803",
"url": "https://www.cve.org/CVERecord?id=CVE-2023-52803"
},
{
"name": "CVE-2024-27437",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-27437"
},
{
"name": "CVE-2024-39484",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39484"
},
{
"name": "CVE-2024-34030",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-34030"
},
{
"name": "CVE-2024-40971",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40971"
},
{
"name": "CVE-2024-39505",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39505"
},
{
"name": "CVE-2024-27012",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-27012"
},
{
"name": "CVE-2024-40926",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40926"
},
{
"name": "CVE-2024-38601",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38601"
},
{
"name": "CVE-2022-48857",
"url": "https://www.cve.org/CVERecord?id=CVE-2022-48857"
},
{
"name": "CVE-2024-40932",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40932"
},
{
"name": "CVE-2024-38546",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38546"
},
{
"name": "CVE-2024-41006",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-41006"
},
{
"name": "CVE-2024-38596",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38596"
},
{
"name": "CVE-2024-42068",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42068"
},
{
"name": "CVE-2024-40904",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40904"
},
{
"name": "CVE-2024-42084",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42084"
},
{
"name": "CVE-2024-40900",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40900"
},
{
"name": "CVE-2024-40920",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40920"
},
{
"name": "CVE-2024-42080",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42080"
},
{
"name": "CVE-2024-42153",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42153"
},
{
"name": "CVE-2024-38590",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38590"
},
{
"name": "CVE-2024-40960",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40960"
},
{
"name": "CVE-2024-40918",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40918"
},
{
"name": "CVE-2024-39463",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39463"
},
{
"name": "CVE-2024-40997",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40997"
},
{
"name": "CVE-2021-47181",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-47181"
},
{
"name": "CVE-2024-39480",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39480"
},
{
"name": "CVE-2024-39479",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39479"
},
{
"name": "CVE-2024-42154",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42154"
},
{
"name": "CVE-2024-42228",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42228"
},
{
"name": "CVE-2024-33847",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-33847"
},
{
"name": "CVE-2024-36484",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-36484"
},
{
"name": "CVE-2024-39488",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39488"
},
{
"name": "CVE-2024-42229",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42229"
},
{
"name": "CVE-2024-42086",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42086"
},
{
"name": "CVE-2024-41007",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-41007"
},
{
"name": "CVE-2024-41095",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-41095"
},
{
"name": "CVE-2024-40928",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40928"
},
{
"name": "CVE-2023-52887",
"url": "https://www.cve.org/CVERecord?id=CVE-2023-52887"
},
{
"name": "CVE-2024-39498",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39498"
},
{
"name": "CVE-2024-42240",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42240"
},
{
"name": "CVE-2024-38629",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38629"
},
{
"name": "CVE-2024-42076",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42076"
},
{
"name": "CVE-2024-40972",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40972"
},
{
"name": "CVE-2024-42092",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42092"
},
{
"name": "CVE-2022-48791",
"url": "https://www.cve.org/CVERecord?id=CVE-2022-48791"
},
{
"name": "CVE-2024-42093",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42093"
},
{
"name": "CVE-2024-42247",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42247"
},
{
"name": "CVE-2024-27398",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-27398"
},
{
"name": "CVE-2024-40959",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40959"
},
{
"name": "CVE-2024-39497",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39497"
},
{
"name": "CVE-2023-52527",
"url": "https://www.cve.org/CVERecord?id=CVE-2023-52527"
},
{
"name": "CVE-2024-40899",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40899"
},
{
"name": "CVE-2024-38560",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38560"
},
{
"name": "CVE-2024-25741",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-25741"
},
{
"name": "CVE-2024-40937",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40937"
},
{
"name": "CVE-2024-40916",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40916"
},
{
"name": "CVE-2024-38578",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38578"
},
{
"name": "CVE-2024-38586",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38586"
},
{
"name": "CVE-2024-26880",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-26880"
},
{
"name": "CVE-2024-41048",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-41048"
},
{
"name": "CVE-2024-42130",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42130"
},
{
"name": "CVE-2024-40976",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40976"
},
{
"name": "CVE-2024-39468",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39468"
},
{
"name": "CVE-2024-38582",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38582"
},
{
"name": "CVE-2024-39291",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39291"
},
{
"name": "CVE-2024-39490",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39490"
},
{
"name": "CVE-2024-40980",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40980"
},
{
"name": "CVE-2024-40974",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40974"
},
{
"name": "CVE-2024-38558",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38558"
},
{
"name": "CVE-2024-38613",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38613"
},
{
"name": "CVE-2024-42124",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42124"
},
{
"name": "CVE-2024-40989",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40989"
},
{
"name": "CVE-2024-36286",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-36286"
},
{
"name": "CVE-2024-34027",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-34027"
},
{
"name": "CVE-2024-39502",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39502"
},
{
"name": "CVE-2022-48863",
"url": "https://www.cve.org/CVERecord?id=CVE-2022-48863"
},
{
"name": "CVE-2024-40979",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40979"
},
{
"name": "CVE-2024-38571",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38571"
},
{
"name": "CVE-2024-42087",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42087"
},
{
"name": "CVE-2024-40977",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40977"
},
{
"name": "CVE-2024-40983",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40983"
},
{
"name": "CVE-2024-39508",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39508"
},
{
"name": "CVE-2024-38565",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38565"
},
{
"name": "CVE-2024-38612",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38612"
},
{
"name": "CVE-2024-37354",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-37354"
},
{
"name": "CVE-2024-39301",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39301"
},
{
"name": "CVE-2024-39467",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39467"
},
{
"name": "CVE-2024-40940",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40940"
},
{
"name": "CVE-2024-40963",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40963"
},
{
"name": "CVE-2024-41041",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-41041"
},
{
"name": "CVE-2024-42131",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42131"
},
{
"name": "CVE-2024-36270",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-36270"
},
{
"name": "CVE-2024-40947",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40947"
},
{
"name": "CVE-2024-42232",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42232"
},
{
"name": "CVE-2024-41005",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-41005"
},
{
"name": "CVE-2024-39507",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39507"
},
{
"name": "CVE-2023-52809",
"url": "https://www.cve.org/CVERecord?id=CVE-2023-52809"
},
{
"name": "CVE-2024-42223",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42223"
},
{
"name": "CVE-2024-41097",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-41097"
},
{
"name": "CVE-2024-39462",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39462"
},
{
"name": "CVE-2024-33621",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-33621"
},
{
"name": "CVE-2024-36978",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-36978"
},
{
"name": "CVE-2024-42225",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42225"
},
{
"name": "CVE-2024-42121",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42121"
},
{
"name": "CVE-2024-42160",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42160"
},
{
"name": "CVE-2024-38625",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38625"
},
{
"name": "CVE-2024-40905",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40905"
},
{
"name": "CVE-2024-41047",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-41047"
},
{
"name": "CVE-2024-39296",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39296"
},
{
"name": "CVE-2024-39466",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39466"
},
{
"name": "CVE-2024-34777",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-34777"
},
{
"name": "CVE-2024-42244",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42244"
},
{
"name": "CVE-2022-48836",
"url": "https://www.cve.org/CVERecord?id=CVE-2022-48836"
},
{
"name": "CVE-2024-39277",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39277"
},
{
"name": "CVE-2024-40906",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40906"
},
{
"name": "CVE-2024-39475",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39475"
},
{
"name": "CVE-2024-40902",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40902"
},
{
"name": "CVE-2024-39485",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39485"
},
{
"name": "CVE-2024-40934",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40934"
},
{
"name": "CVE-2024-40970",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40970"
},
{
"name": "CVE-2022-48850",
"url": "https://www.cve.org/CVERecord?id=CVE-2022-48850"
},
{
"name": "CVE-2024-42119",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42119"
},
{
"name": "CVE-2024-42082",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42082"
},
{
"name": "CVE-2024-40912",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40912"
},
{
"name": "CVE-2024-26733",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-26733"
},
{
"name": "CVE-2024-26851",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-26851"
},
{
"name": "CVE-2024-41089",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-41089"
},
{
"name": "CVE-2024-39487",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39487"
},
{
"name": "CVE-2024-39371",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39371"
},
{
"name": "CVE-2024-38610",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38610"
},
{
"name": "CVE-2024-38623",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38623"
},
{
"name": "CVE-2024-39489",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39489"
},
{
"name": "CVE-2024-38634",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38634"
},
{
"name": "CVE-2024-42140",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42140"
},
{
"name": "CVE-2024-31076",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-31076"
},
{
"name": "CVE-2022-48838",
"url": "https://www.cve.org/CVERecord?id=CVE-2022-48838"
},
{
"name": "CVE-2024-40998",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40998"
},
{
"name": "CVE-2024-40925",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40925"
},
{
"name": "CVE-2024-38636",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38636"
},
{
"name": "CVE-2024-38628",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38628"
},
{
"name": "CVE-2024-38547",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38547"
},
{
"name": "CVE-2024-40938",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40938"
},
{
"name": "CVE-2024-36971",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-36971"
},
{
"name": "CVE-2024-35247",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-35247"
},
{
"name": "CVE-2024-38663",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38663"
},
{
"name": "CVE-2024-42085",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42085"
},
{
"name": "CVE-2024-40948",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40948"
},
{
"name": "CVE-2024-41092",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-41092"
},
{
"name": "CVE-2024-38633",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38633"
},
{
"name": "CVE-2024-40995",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40995"
},
{
"name": "CVE-2024-39500",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39500"
},
{
"name": "CVE-2024-42270",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42270"
},
{
"name": "CVE-2024-41087",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-41087"
},
{
"name": "CVE-2024-40965",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40965"
},
{
"name": "CVE-2024-38550",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38550"
},
{
"name": "CVE-2024-42106",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42106"
},
{
"name": "CVE-2024-42095",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42095"
},
{
"name": "CVE-2024-35927",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-35927"
},
{
"name": "CVE-2024-40910",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40910"
},
{
"name": "CVE-2024-40929",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40929"
},
{
"name": "CVE-2024-26651",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-26651"
},
{
"name": "CVE-2024-39504",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39504"
},
{
"name": "CVE-2024-40922",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40922"
},
{
"name": "CVE-2024-39501",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39501"
},
{
"name": "CVE-2024-42090",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42090"
},
{
"name": "CVE-2024-38667",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38667"
},
{
"name": "CVE-2024-42104",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42104"
},
{
"name": "CVE-2024-42120",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42120"
},
{
"name": "CVE-2024-36244",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-36244"
},
{
"name": "CVE-2024-42101",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42101"
},
{
"name": "CVE-2024-36014",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-36014"
},
{
"name": "CVE-2024-42077",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42077"
},
{
"name": "CVE-2024-38570",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38570"
},
{
"name": "CVE-2024-36015",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-36015"
},
{
"name": "CVE-2024-40943",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40943"
},
{
"name": "CVE-2024-40964",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40964"
},
{
"name": "CVE-2024-36489",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-36489"
},
{
"name": "CVE-2023-52884",
"url": "https://www.cve.org/CVERecord?id=CVE-2023-52884"
},
{
"name": "CVE-2024-40901",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40901"
},
{
"name": "CVE-2024-39495",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39495"
},
{
"name": "CVE-2024-40985",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40985"
},
{
"name": "CVE-2024-39471",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39471"
},
{
"name": "CVE-2024-40923",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40923"
},
{
"name": "CVE-2024-39492",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39492"
},
{
"name": "CVE-2024-38630",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38630"
},
{
"name": "CVE-2024-39494",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39494"
},
{
"name": "CVE-2024-39473",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39473"
},
{
"name": "CVE-2024-40954",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40954"
},
{
"name": "CVE-2024-40908",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40908"
},
{
"name": "CVE-2024-40913",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40913"
},
{
"name": "CVE-2024-38549",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38549"
},
{
"name": "CVE-2024-42096",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42096"
},
{
"name": "CVE-2024-32936",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-32936"
},
{
"name": "CVE-2024-38622",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38622"
},
{
"name": "CVE-2024-41003",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-41003"
},
{
"name": "CVE-2024-38619",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38619"
},
{
"name": "CVE-2024-40956",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40956"
},
{
"name": "CVE-2024-40966",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40966"
},
{
"name": "CVE-2024-38780",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38780"
},
{
"name": "CVE-2024-38573",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38573"
},
{
"name": "CVE-2024-41027",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-41027"
},
{
"name": "CVE-2024-40957",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40957"
},
{
"name": "CVE-2024-40939",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40939"
},
{
"name": "CVE-2024-42094",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42094"
},
{
"name": "CVE-2024-40994",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40994"
},
{
"name": "CVE-2024-38567",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38567"
},
{
"name": "CVE-2024-23848",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-23848"
},
{
"name": "CVE-2024-36478",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-36478"
},
{
"name": "CVE-2024-41040",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-41040"
},
{
"name": "CVE-2024-40917",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40917"
},
{
"name": "CVE-2024-40987",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40987"
},
{
"name": "CVE-2024-40927",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40927"
},
{
"name": "CVE-2024-42115",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42115"
},
{
"name": "CVE-2024-40945",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40945"
},
{
"name": "CVE-2024-38588",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38588"
},
{
"name": "CVE-2024-40941",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40941"
},
{
"name": "CVE-2024-40949",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40949"
},
{
"name": "CVE-2024-40951",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40951"
},
{
"name": "CVE-2024-40967",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40967"
},
{
"name": "CVE-2024-36481",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-36481"
},
{
"name": "CVE-2024-41055",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-41055"
},
{
"name": "CVE-2024-38637",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38637"
},
{
"name": "CVE-2024-38635",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38635"
},
{
"name": "CVE-2024-40921",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40921"
},
{
"name": "CVE-2024-40984",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40984"
},
{
"name": "CVE-2024-42102",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42102"
},
{
"name": "CVE-2024-42224",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42224"
},
{
"name": "CVE-2024-40982",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40982"
},
{
"name": "CVE-2024-42078",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42078"
},
{
"name": "CVE-2024-38618",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38618"
},
{
"name": "CVE-2024-42161",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42161"
},
{
"name": "CVE-2024-39276",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39276"
},
{
"name": "CVE-2024-36032",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-36032"
},
{
"name": "CVE-2024-39506",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39506"
},
{
"name": "CVE-2024-40990",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40990"
},
{
"name": "CVE-2024-40978",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40978"
},
{
"name": "CVE-2024-40944",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40944"
},
{
"name": "CVE-2024-40936",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40936"
},
{
"name": "CVE-2024-40968",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40968"
},
{
"name": "CVE-2024-41035",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-41035"
},
{
"name": "CVE-2024-41049",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-41049"
},
{
"name": "CVE-2024-38624",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38624"
},
{
"name": "CVE-2024-38589",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38589"
},
{
"name": "CVE-2024-38598",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38598"
},
{
"name": "CVE-2024-38381",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38381"
},
{
"name": "CVE-2024-37078",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-37078"
},
{
"name": "CVE-2024-42127",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42127"
},
{
"name": "CVE-2024-38661",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38661"
},
{
"name": "CVE-2024-39493",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39493"
},
{
"name": "CVE-2024-42105",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42105"
},
{
"name": "CVE-2024-39478",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39478"
},
{
"name": "CVE-2024-40996",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40996"
},
{
"name": "CVE-2024-39483",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39483"
},
{
"name": "CVE-2021-47188",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-47188"
},
{
"name": "CVE-2024-41044",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-41044"
},
{
"name": "CVE-2024-40958",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40958"
},
{
"name": "CVE-2024-38559",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38559"
},
{
"name": "CVE-2024-40981",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40981"
},
{
"name": "CVE-2024-38621",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38621"
},
{
"name": "CVE-2024-37021",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-37021"
},
{
"name": "CVE-2024-40915",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40915"
},
{
"name": "CVE-2024-41046",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-41046"
},
{
"name": "CVE-2024-42152",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42152"
},
{
"name": "CVE-2024-38597",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38597"
},
{
"name": "CVE-2024-40930",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40930"
},
{
"name": "CVE-2024-40909",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40909"
},
{
"name": "CVE-2024-42148",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42148"
},
{
"name": "CVE-2024-39464",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39464"
},
{
"name": "CVE-2024-39482",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39482"
},
{
"name": "CVE-2024-36288",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-36288"
},
{
"name": "CVE-2024-39499",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39499"
},
{
"name": "CVE-2024-38579",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38579"
},
{
"name": "CVE-2024-39292",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39292"
},
{
"name": "CVE-2024-40933",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40933"
},
{
"name": "CVE-2024-38607",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38607"
},
{
"name": "CVE-2024-38587",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38587"
},
{
"name": "CVE-2024-41002",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-41002"
},
{
"name": "CVE-2024-40911",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40911"
},
{
"name": "CVE-2024-36894",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-36894"
},
{
"name": "CVE-2024-40969",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40969"
},
{
"name": "CVE-2024-40942",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40942"
},
{
"name": "CVE-2024-38605",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38605"
},
{
"name": "CVE-2024-38580",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38580"
},
{
"name": "CVE-2024-40999",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40999"
},
{
"name": "CVE-2024-42159",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42159"
},
{
"name": "CVE-2024-40992",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40992"
},
{
"name": "CVE-2024-38591",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38591"
},
{
"name": "CVE-2024-40952",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40952"
},
{
"name": "CVE-2024-36281",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-36281"
},
{
"name": "CVE-2024-39465",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39465"
},
{
"name": "CVE-2024-38552",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38552"
},
{
"name": "CVE-2024-39510",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39510"
},
{
"name": "CVE-2024-33619",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-33619"
},
{
"name": "CVE-2024-38615",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38615"
},
{
"name": "CVE-2024-40914",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40914"
},
{
"name": "CVE-2024-39461",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39461"
},
{
"name": "CVE-2024-40953",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40953"
},
{
"name": "CVE-2024-42145",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42145"
},
{
"name": "CVE-2024-40961",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40961"
},
{
"name": "CVE-2024-38385",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38385"
}
],
"initial_release_date": "2024-09-27T00:00:00",
"last_revision_date": "2024-09-27T00:00:00",
"links": [],
"reference": "CERTFR-2024-AVI-0823",
"revisions": [
{
"description": "Version initiale",
"revision_date": "2024-09-27T00:00:00.000000"
}
],
"risks": [
{
"description": "Atteinte \u00e0 l\u0027int\u00e9grit\u00e9 des donn\u00e9es"
},
{
"description": "Ex\u00e9cution de code arbitraire"
},
{
"description": "Non sp\u00e9cifi\u00e9 par l\u0027\u00e9diteur"
},
{
"description": "D\u00e9ni de service"
},
{
"description": "Contournement de la politique de s\u00e9curit\u00e9"
},
{
"description": "Atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es"
}
],
"summary": "De multiples vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 d\u00e9couvertes dans le noyau Linux d\u0027Ubuntu. Certaines d\u0027entre elles permettent \u00e0 un attaquant de provoquer une ex\u00e9cution de code arbitraire, une atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es et une atteinte \u00e0 l\u0027int\u00e9grit\u00e9 des donn\u00e9es.",
"title": "Multiples vuln\u00e9rabilit\u00e9s dans le noyau Linux d\u0027Ubuntu",
"vendor_advisories": [
{
"published_at": "2024-09-26",
"title": "Bulletin de s\u00e9curit\u00e9 Ubuntu USN-7021-3",
"url": "https://ubuntu.com/security/notices/USN-7021-3"
},
{
"published_at": "2024-09-23",
"title": "Bulletin de s\u00e9curit\u00e9 Ubuntu USN-7020-2",
"url": "https://ubuntu.com/security/notices/USN-7020-2"
},
{
"published_at": "2024-09-26",
"title": "Bulletin de s\u00e9curit\u00e9 Ubuntu USN-7039-1",
"url": "https://ubuntu.com/security/notices/USN-7039-1"
},
{
"published_at": "2024-09-26",
"title": "Bulletin de s\u00e9curit\u00e9 Ubuntu USN-7020-3",
"url": "https://ubuntu.com/security/notices/USN-7020-3"
},
{
"published_at": "2024-09-23",
"title": "Bulletin de s\u00e9curit\u00e9 Ubuntu USN-6999-2",
"url": "https://ubuntu.com/security/notices/USN-6999-2"
},
{
"published_at": "2024-09-23",
"title": "Bulletin de s\u00e9curit\u00e9 Ubuntu USN-7007-2",
"url": "https://ubuntu.com/security/notices/USN-7007-2"
},
{
"published_at": "2024-09-25",
"title": "Bulletin de s\u00e9curit\u00e9 Ubuntu USN-7009-2",
"url": "https://ubuntu.com/security/notices/USN-7009-2"
},
{
"published_at": "2024-09-26",
"title": "Bulletin de s\u00e9curit\u00e9 Ubuntu USN-7003-4",
"url": "https://ubuntu.com/security/notices/USN-7003-4"
},
{
"published_at": "2024-09-23",
"title": "Bulletin de s\u00e9curit\u00e9 Ubuntu USN-7029-1",
"url": "https://ubuntu.com/security/notices/USN-7029-1"
},
{
"published_at": "2024-09-23",
"title": "Bulletin de s\u00e9curit\u00e9 Ubuntu USN-7021-2",
"url": "https://ubuntu.com/security/notices/USN-7021-2"
},
{
"published_at": "2024-09-23",
"title": "Bulletin de s\u00e9curit\u00e9 Ubuntu USN-7007-3",
"url": "https://ubuntu.com/security/notices/USN-7007-3"
},
{
"published_at": "2024-09-23",
"title": "Bulletin de s\u00e9curit\u00e9 Ubuntu USN-7028-1",
"url": "https://ubuntu.com/security/notices/USN-7028-1"
}
]
}
OESA-2024-1766 (CVE-2024-36477)
Vulnerability from osv_openeuler – Published: 2024-06-28 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:
tpm_tis_spi: Account for SPI header when allocating TPM SPI xfer buffer
The TPM SPI transfer mechanism uses MAX_SPI_FRAMESIZE for computing the maximum transfer length and the size of the transfer buffer. As such, it does not account for the 4 bytes of header that prepends the SPI data frame. This can result in out-of-bounds accesses and was confirmed with KASAN.
Introduce SPI_HDRSIZE to account for the header and use to allocate the transfer buffer.(CVE-2024-36477)
In the Linux kernel, the following vulnerability has been resolved:
net: fix out-of-bounds access in ops_init
net_alloc_generic is called by net_alloc, which is called without any locking. It reads max_gen_ptrs, which is changed under pernet_ops_rwsem. It is read twice, first to allocate an array, then to set s.len, which is later used to limit the bounds of the array access.
It is possible that the array is allocated and another thread is registering a new pernet ops, increments max_gen_ptrs, which is then used to set s.len with a larger than allocated length for the variable array.
Fix it by reading max_gen_ptrs only once in net_alloc_generic. If max_gen_ptrs is later incremented, it will be caught in net_assign_generic.(CVE-2024-36883)
In the Linux kernel, the following vulnerability has been resolved:
gpiolib: cdev: fix uninitialised kfifo
If a line is requested with debounce, and that results in debouncing in software, and the line is subsequently reconfigured to enable edge detection then the allocation of the kfifo to contain edge events is overlooked. This results in events being written to and read from an uninitialised kfifo. Read events are returned to userspace.
Initialise the kfifo in the case where the software debounce is already active.(CVE-2024-36898)
In the Linux kernel, the following vulnerability has been resolved:
ipv6: fib6_rules: avoid possible NULL dereference in fib6_rule_action()
syzbot is able to trigger the following crash [1], caused by unsafe ip6_dst_idev() use.
Indeed ip6_dst_idev() can return NULL, and must always be checked.
[1]
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN PTI KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] CPU: 0 PID: 31648 Comm: syz-executor.0 Not tainted 6.9.0-rc4-next-20240417-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 RIP: 0010:__fib6_rule_action net/ipv6/fib6_rules.c:237 [inline] RIP: 0010:fib6_rule_action+0x241/0x7b0 net/ipv6/fib6_rules.c:267 Code: 02 00 00 49 8d 9f d8 00 00 00 48 89 d8 48 c1 e8 03 42 80 3c 20 00 74 08 48 89 df e8 f9 32 bf f7 48 8b 1b 48 89 d8 48 c1 e8 03 <42> 80 3c 20 00 74 08 48 89 df e8 e0 32 bf f7 4c 8b 03 48 89 ef 4c RSP: 0018:ffffc9000fc1f2f0 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 1a772f98c8186700 RDX: 0000000000000003 RSI: ffffffff8bcac4e0 RDI: ffffffff8c1f9760 RBP: ffff8880673fb980 R08: ffffffff8fac15ef R09: 1ffffffff1f582bd R10: dffffc0000000000 R11: fffffbfff1f582be R12: dffffc0000000000 R13: 0000000000000080 R14: ffff888076509000 R15: ffff88807a029a00 FS: 00007f55e82ca6c0(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000001b31d23000 CR3: 0000000022b66000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> fib_rules_lookup+0x62c/0xdb0 net/core/fib_rules.c:317 fib6_rule_lookup+0x1fd/0x790 net/ipv6/fib6_rules.c:108 ip6_route_output_flags_noref net/ipv6/route.c:2637 [inline] ip6_route_output_flags+0x38e/0x610 net/ipv6/route.c:2649 ip6_route_output include/net/ip6_route.h:93 [inline] ip6_dst_lookup_tail+0x189/0x11a0 net/ipv6/ip6_output.c:1120 ip6_dst_lookup_flow+0xb9/0x180 net/ipv6/ip6_output.c:1250 sctp_v6_get_dst+0x792/0x1e20 net/sctp/ipv6.c:326 sctp_transport_route+0x12c/0x2e0 net/sctp/transport.c:455 sctp_assoc_add_peer+0x614/0x15c0 net/sctp/associola.c:662 sctp_connect_new_asoc+0x31d/0x6c0 net/sctp/socket.c:1099 __sctp_connect+0x66d/0xe30 net/sctp/socket.c:1197 sctp_connect net/sctp/socket.c:4819 [inline] sctp_inet_connect+0x149/0x1f0 net/sctp/socket.c:4834 __sys_connect_file net/socket.c:2048 [inline] __sys_connect+0x2df/0x310 net/socket.c:2065 __do_sys_connect net/socket.c:2075 [inline] __se_sys_connect net/socket.c:2072 [inline] __x64_sys_connect+0x7a/0x90 net/socket.c:2072 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f(CVE-2024-36902)
In the Linux kernel, the following vulnerability has been resolved:
ipv6: Fix potential uninit-value access in __ip6_make_skb()
As it was done in commit fc1092f51567 ("ipv4: Fix uninit-value access in __ip_make_skb()") for IPv4, check FLOWI_FLAG_KNOWN_NH on fl6->flowi6_flags instead of testing HDRINCL on the socket to avoid a race condition which causes uninit-value access.(CVE-2024-36903)
In the Linux kernel, the following vulnerability has been resolved:
tcp: defer shutdown(SEND_SHUTDOWN) for TCP_SYN_RECV sockets
TCP_SYN_RECV state is really special, it is only used by cross-syn connections, mostly used by fuzzers.
In the following crash [1], syzbot managed to trigger a divide by zero in tcp_rcv_space_adjust()
A socket makes the following state transitions, without ever calling tcp_init_transfer(), meaning tcp_init_buffer_space() is also not called.
TCP_CLOSE
connect() TCP_SYN_SENT TCP_SYN_RECV shutdown() -> tcp_shutdown(sk, SEND_SHUTDOWN) TCP_FIN_WAIT1
To fix this issue, change tcp_shutdown() to not perform a TCP_SYN_RECV -> TCP_FIN_WAIT1 transition, which makes no sense anyway.
When tcp_rcv_state_process() later changes socket state from TCP_SYN_RECV to TCP_ESTABLISH, then look at sk->sk_shutdown to finally enter TCP_FIN_WAIT1 state, and send a FIN packet from a sane socket state.
This means tcp_send_fin() can now be called from BH context, and must use GFP_ATOMIC allocations.
[1] divide error: 0000 [#1] PREEMPT SMP KASAN NOPTI CPU: 1 PID: 5084 Comm: syz-executor358 Not tainted 6.9.0-rc6-syzkaller-00022-g98369dccd2f8 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 RIP: 0010:tcp_rcv_space_adjust+0x2df/0x890 net/ipv4/tcp_input.c:767 Code: e3 04 4c 01 eb 48 8b 44 24 38 0f b6 04 10 84 c0 49 89 d5 0f 85 a5 03 00 00 41 8b 8e c8 09 00 00 89 e8 29 c8 48 0f af c3 31 d2 <48> f7 f1 48 8d 1c 43 49 8d 96 76 08 00 00 48 89 d0 48 c1 e8 03 48 RSP: 0018:ffffc900031ef3f0 EFLAGS: 00010246 RAX: 0c677a10441f8f42 RBX: 000000004fb95e7e RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: 0000000027d4b11f R08: ffffffff89e535a4 R09: 1ffffffff25e6ab7 R10: dffffc0000000000 R11: ffffffff8135e920 R12: ffff88802a9f8d30 R13: dffffc0000000000 R14: ffff88802a9f8d00 R15: 1ffff1100553f2da FS: 00005555775c0380(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f1155bf2304 CR3: 000000002b9f2000 CR4: 0000000000350ef0 Call Trace: <TASK> tcp_recvmsg_locked+0x106d/0x25a0 net/ipv4/tcp.c:2513 tcp_recvmsg+0x25d/0x920 net/ipv4/tcp.c:2578 inet6_recvmsg+0x16a/0x730 net/ipv6/af_inet6.c:680 sock_recvmsg_nosec net/socket.c:1046 [inline] sock_recvmsg+0x109/0x280 net/socket.c:1068 ____sys_recvmsg+0x1db/0x470 net/socket.c:2803 ___sys_recvmsg net/socket.c:2845 [inline] do_recvmmsg+0x474/0xae0 net/socket.c:2939 __sys_recvmmsg net/socket.c:3018 [inline] __do_sys_recvmmsg net/socket.c:3041 [inline] __se_sys_recvmmsg net/socket.c:3034 [inline] __x64_sys_recvmmsg+0x199/0x250 net/socket.c:3034 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7faeb6363db9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 c1 17 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:00007ffcc1997168 EFLAGS: 00000246 ORIG_RAX: 000000000000012b RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007faeb6363db9 RDX: 0000000000000001 RSI: 0000000020000bc0 RDI: 0000000000000005 RBP: 0000000000000000 R08: 0000000000000000 R09: 000000000000001c R10: 0000000000000122 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000000001(CVE-2024-36905)
In the Linux kernel, the following vulnerability has been resolved:
scsi: bnx2fc: Remove spin_lock_bh while releasing resources after upload
The session resources are used by FW and driver when session is offloaded, once session is uploaded these resources are not used. The lock is not required as these fields won't be used any longer. The offload and upload calls are sequential, hence lock is not required.
This will suppress following BUG_ON():
[ 449.843143] ------------[ cut here ]------------ [ 449.848302] kernel BUG at mm/vmalloc.c:2727! [ 449.853072] invalid opcode: 0000 [#1] PREEMPT SMP PTI [ 449.858712] CPU: 5 PID: 1996 Comm: kworker/u24:2 Not tainted 5.14.0-118.el9.x86_64 #1 Rebooting. [ 449.867454] Hardware name: Dell Inc. PowerEdge R730/0WCJNT, BIOS 2.3.4 11/08/2016 [ 449.876966] Workqueue: fc_rport_eq fc_rport_work [libfc] [ 449.882910] RIP: 0010:vunmap+0x2e/0x30 [ 449.887098] Code: 00 65 8b 05 14 a2 f0 4a a9 00 ff ff 00 75 1b 55 48 89 fd e8 34 36 79 00 48 85 ed 74 0b 48 89 ef 31 f6 5d e9 14 fc ff ff 5d c3 <0f> 0b 0f 1f 44 00 00 41 57 41 56 49 89 ce 41 55 49 89 fd 41 54 41 [ 449.908054] RSP: 0018:ffffb83d878b3d68 EFLAGS: 00010206 [ 449.913887] RAX: 0000000080000201 RBX: ffff8f4355133550 RCX: 000000000d400005 [ 449.921843] RDX: 0000000000000001 RSI: 0000000000001000 RDI: ffffb83da53f5000 [ 449.929808] RBP: ffff8f4ac6675800 R08: ffffb83d878b3d30 R09: 00000000000efbdf [ 449.937774] R10: 0000000000000003 R11: ffff8f434573e000 R12: 0000000000001000 [ 449.945736] R13: 0000000000001000 R14: ffffb83da53f5000 R15: ffff8f43d4ea3ae0 [ 449.953701] FS: 0000000000000000(0000) GS:ffff8f529fc80000(0000) knlGS:0000000000000000 [ 449.962732] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 449.969138] CR2: 00007f8cf993e150 CR3: 0000000efbe10003 CR4: 00000000003706e0 [ 449.977102] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 449.985065] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 449.993028] Call Trace: [ 449.995756] __iommu_dma_free+0x96/0x100 [ 450.000139] bnx2fc_free_session_resc+0x67/0x240 [bnx2fc] [ 450.006171] bnx2fc_upload_session+0xce/0x100 [bnx2fc] [ 450.011910] bnx2fc_rport_event_handler+0x9f/0x240 [bnx2fc] [ 450.018136] fc_rport_work+0x103/0x5b0 [libfc] [ 450.023103] process_one_work+0x1e8/0x3c0 [ 450.027581] worker_thread+0x50/0x3b0 [ 450.031669] ? rescuer_thread+0x370/0x370 [ 450.036143] kthread+0x149/0x170 [ 450.039744] ? set_kthread_struct+0x40/0x40 [ 450.044411] ret_from_fork+0x22/0x30 [ 450.048404] Modules linked in: vfat msdos fat xfs nfs_layout_nfsv41_files rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver dm_service_time qedf qed crc8 bnx2fc libfcoe libfc scsi_transport_fc intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp dcdbas rapl intel_cstate intel_uncore mei_me pcspkr mei ipmi_ssif lpc_ich ipmi_si fuse zram ext4 mbcache jbd2 loop nfsv3 nfs_acl nfs lockd grace fscache netfs irdma ice sd_mod t10_pi sg ib_uverbs ib_core 8021q garp mrp stp llc mgag200 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt mxm_wmi fb_sys_fops cec crct10dif_pclmul ahci crc32_pclmul bnx2x drm ghash_clmulni_intel libahci rfkill i40e libata megaraid_sas mdio wmi sunrpc lrw dm_crypt dm_round_robin dm_multipath dm_snapshot dm_bufio dm_mirror dm_region_hash dm_log dm_zero dm_mod linear raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx raid6_pq libcrc32c crc32c_intel raid1 raid0 iscsi_ibft squashfs be2iscsi bnx2i cnic uio cxgb4i cxgb4 tls [ 450.048497] libcxgbi libcxgb qla4xxx iscsi_boot_sysfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi edd ipmi_devintf ipmi_msghandler [ 450.159753] ---[ end trace 712de2c57c64abc8 ]---(CVE-2024-36919)
In the Linux kernel, the following vulnerability has been resolved:
s390/qeth: Fix kernel panic after setting hsuid
Symptom: When the hsuid attribute is set for the first time on an IQD Layer3 device while the corresponding network interface is already UP, the kernel will try to execute a napi function pointer that is NULL.
Example:
[ 2057.572696] illegal operation: 0001 ilc:1 [#1] SMP [ 2057.572702] Modules linked in: af_iucv qeth_l3 zfcp scsi_transport_fc sunrpc nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nf_tables_set nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables libcrc32c nfnetlink ghash_s390 prng xts aes_s390 des_s390 de s_generic sha3_512_s390 sha3_256_s390 sha512_s390 vfio_ccw vfio_mdev mdev vfio_iommu_type1 eadm_sch vfio ext4 mbcache jbd2 qeth_l2 bridge stp llc dasd_eckd_mod qeth dasd_mod qdio ccwgroup pkey zcrypt [ 2057.572739] CPU: 6 PID: 60182 Comm: stress_client Kdump: loaded Not tainted 4.18.0-541.el8.s390x #1 [ 2057.572742] Hardware name: IBM 3931 A01 704 (LPAR) [ 2057.572744] Krnl PSW : 0704f00180000000 0000000000000002 (0x2) [ 2057.572748] R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:3 PM:0 RI:0 EA:3 [ 2057.572751] Krnl GPRS: 0000000000000004 0000000000000000 00000000a3b008d8 0000000000000000 [ 2057.572754] 00000000a3b008d8 cb923a29c779abc5 0000000000000000 00000000814cfd80 [ 2057.572756] 000000000000012c 0000000000000000 00000000a3b008d8 00000000a3b008d8 [ 2057.572758] 00000000bab6d500 00000000814cfd80 0000000091317e46 00000000814cfc68 [ 2057.572762] Krnl Code:#0000000000000000: 0000 illegal >0000000000000002: 0000 illegal 0000000000000004: 0000 illegal 0000000000000006: 0000 illegal 0000000000000008: 0000 illegal 000000000000000a: 0000 illegal 000000000000000c: 0000 illegal 000000000000000e: 0000 illegal [ 2057.572800] Call Trace: [ 2057.572801] ([<00000000ec639700>] 0xec639700) [ 2057.572803] [<00000000913183e2>] net_rx_action+0x2ba/0x398 [ 2057.572809] [<0000000091515f76>] __do_softirq+0x11e/0x3a0 [ 2057.572813] [<0000000090ce160c>] do_softirq_own_stack+0x3c/0x58 [ 2057.572817] ([<0000000090d2cbd6>] do_softirq.part.1+0x56/0x60) [ 2057.572822] [<0000000090d2cc60>] __local_bh_enable_ip+0x80/0x98 [ 2057.572825] [<0000000091314706>] __dev_queue_xmit+0x2be/0xd70 [ 2057.572827] [<000003ff803dd6d6>] afiucv_hs_send+0x24e/0x300 [af_iucv] [ 2057.572830] [<000003ff803dd88a>] iucv_send_ctrl+0x102/0x138 [af_iucv] [ 2057.572833] [<000003ff803de72a>] iucv_sock_connect+0x37a/0x468 [af_iucv] [ 2057.572835] [<00000000912e7e90>] __sys_connect+0xa0/0xd8 [ 2057.572839] [<00000000912e9580>] sys_socketcall+0x228/0x348 [ 2057.572841] [<0000000091514e1a>] system_call+0x2a6/0x2c8 [ 2057.572843] Last Breaking-Event-Address: [ 2057.572844] [<0000000091317e44>] __napi_poll+0x4c/0x1d8 [ 2057.572846] [ 2057.572847] Kernel panic - not syncing: Fatal exception in interrupt
Analysis: There is one napi structure per out_q: card->qdio.out_qs[i].napi The napi.poll functions are set during qeth_open().
Since commit 1cfef80d4c2b ("s390/qeth: Don't call dev_close/dev_open (DOWN/UP)") qeth_set_offline()/qeth_set_online() no longer call dev_close()/ dev_open(). So if qeth_free_qdio_queues() cleared card->qdio.out_qs[i].napi.poll while the network interface was UP and the card was offline, they are not set again.
Reproduction: chzdev -e $devno layer2=0 ip link set dev $network_interface up echo 0 > /sys/bus/ccw ---truncated---(CVE-2024-36928)
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: L2CAP: Fix div-by-zero in l2cap_le_flowctl_init()
l2cap_le_flowctl_init() can cause both div-by-zero and an integer overflow since hdev->le_mtu may not fall in the valid range.
Move MTU from hci_dev to hci_conn to validate MTU and stop the connection process earlier if MTU is invalid. Also, add a missing validation in read_buffer_size() and make it return an error value if the validation fails. Now hci_conn_add() returns ERR_PTR() as it can fail due to the both a kzalloc failure and invalid MTU value.
divide error: 0000 [#1] PREEMPT SMP KASAN NOPTI CPU: 0 PID: 67 Comm: kworker/u5:0 Tainted: G W 6.9.0-rc5+ #20 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 Workqueue: hci0 hci_rx_work RIP: 0010:l2cap_le_flowctl_init+0x19e/0x3f0 net/bluetooth/l2cap_core.c:547 Code: e8 17 17 0c 00 66 41 89 9f 84 00 00 00 bf 01 00 00 00 41 b8 02 00 00 00 4c 89 fe 4c 89 e2 89 d9 e8 27 17 0c 00 44 89 f0 31 d2 <66> f7 f3 89 c3 ff c3 4d 8d b7 88 00 00 00 4c 89 f0 48 c1 e8 03 42 RSP: 0018:ffff88810bc0f858 EFLAGS: 00010246 RAX: 00000000000002a0 RBX: 0000000000000000 RCX: dffffc0000000000 RDX: 0000000000000000 RSI: ffff88810bc0f7c0 RDI: ffffc90002dcb66f RBP: ffff88810bc0f880 R08: aa69db2dda70ff01 R09: 0000ffaaaaaaaaaa R10: 0084000000ffaaaa R11: 0000000000000000 R12: ffff88810d65a084 R13: dffffc0000000000 R14: 00000000000002a0 R15: ffff88810d65a000 FS: 0000000000000000(0000) GS:ffff88811ac00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020000100 CR3: 0000000103268003 CR4: 0000000000770ef0 PKRU: 55555554 Call Trace: <TASK> l2cap_le_connect_req net/bluetooth/l2cap_core.c:4902 [inline] l2cap_le_sig_cmd net/bluetooth/l2cap_core.c:5420 [inline] l2cap_le_sig_channel net/bluetooth/l2cap_core.c:5486 [inline] l2cap_recv_frame+0xe59d/0x11710 net/bluetooth/l2cap_core.c:6809 l2cap_recv_acldata+0x544/0x10a0 net/bluetooth/l2cap_core.c:7506 hci_acldata_packet net/bluetooth/hci_core.c:3939 [inline] hci_rx_work+0x5e5/0xb20 net/bluetooth/hci_core.c:4176 process_one_work kernel/workqueue.c:3254 [inline] process_scheduled_works+0x90f/0x1530 kernel/workqueue.c:3335 worker_thread+0x926/0xe70 kernel/workqueue.c:3416 kthread+0x2e3/0x380 kernel/kthread.c:388 ret_from_fork+0x5c/0x90 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 </TASK> Modules linked in: ---[ end trace 0000000000000000 ]---(CVE-2024-36968)
In the Linux kernel, the following vulnerability has been resolved:
net/sched: taprio: always validate TCA_TAPRIO_ATTR_PRIOMAP
If one TCA_TAPRIO_ATTR_PRIOMAP attribute has been provided, taprio_parse_mqprio_opt() must validate it, or userspace can inject arbitrary data to the kernel, the second time taprio_change() is called.
First call (with valid attributes) sets dev->num_tc to a non zero value.
Second call (with arbitrary mqprio attributes) returns early from taprio_parse_mqprio_opt() and bad things can happen.(CVE-2024-36974)
In the Linux kernel, the following vulnerability has been resolved:
KEYS: trusted: Do not use WARN when encode fails
When asn1_encode_sequence() fails, WARN is not the correct solution.
- asn1_encode_sequence() is not an internal function (located in lib/asn1_encode.c).
- Location is known, which makes the stack trace useless.
- Results a crash if panic_on_warn is set.
It is also noteworthy that the use of WARN is undocumented, and it should be avoided unless there is a carefully considered rationale to use it.
Replace WARN with pr_err, and print the return value instead, which is only useful piece of information.(CVE-2024-36975)
In the Linux kernel, the following vulnerability has been resolved:
usb: dwc3: Wait unconditionally after issuing EndXfer command
Currently all controller IP/revisions except DWC3_usb3 >= 310a wait 1ms unconditionally for ENDXFER completion when IOC is not set. This is because DWC_usb3 controller revisions >= 3.10a supports GUCTL2[14: Rst_actbitlater] bit which allows polling CMDACT bit to know whether ENDXFER command is completed.
Consider a case where an IN request was queued, and parallelly soft_disconnect was called (due to ffs_epfile_release). This eventually calls stop_active_transfer with IOC cleared, hence send_gadget_ep_cmd() skips waiting for CMDACT cleared during EndXfer. For DWC3 controllers with revisions >= 310a, we don't forcefully wait for 1ms either, and we proceed by unmapping the requests. If ENDXFER didn't complete by this time, it leads to SMMU faults since the controller would still be accessing those requests.
Fix this by ensuring ENDXFER completion by adding 1ms delay in __dwc3_stop_active_transfer() unconditionally.(CVE-2024-36977)
In the Linux kernel, the following vulnerability has been resolved:
net: sched: sch_multiq: fix possible OOB write in multiq_tune()
q->bands will be assigned to qopt->bands to execute subsequent code logic after kmalloc. So the old q->bands should not be used in kmalloc. Otherwise, an out-of-bounds write will occur.(CVE-2024-36978)
In the Linux kernel, the following vulnerability has been resolved:
net: bridge: xmit: make sure we have at least eth header len bytes
syzbot triggered an uninit value[1] error in bridge device's xmit path by sending a short (less than ETH_HLEN bytes) skb. To fix it check if we can actually pull that amount instead of assuming.
Tested with dropwatch: drop at: br_dev_xmit+0xb93/0x12d0 [bridge] (0xffffffffc06739b3) origin: software timestamp: Mon May 13 11:31:53 2024 778214037 nsec protocol: 0x88a8 length: 2 original length: 2 drop reason: PKT_TOO_SMALL
[1] BUG: KMSAN: uninit-value in br_dev_xmit+0x61d/0x1cb0 net/bridge/br_device.c:65 br_dev_xmit+0x61d/0x1cb0 net/bridge/br_device.c:65 __netdev_start_xmit include/linux/netdevice.h:4903 [inline] netdev_start_xmit include/linux/netdevice.h:4917 [inline] xmit_one net/core/dev.c:3531 [inline] dev_hard_start_xmit+0x247/0xa20 net/core/dev.c:3547 __dev_queue_xmit+0x34db/0x5350 net/core/dev.c:4341 dev_queue_xmit include/linux/netdevice.h:3091 [inline] __bpf_tx_skb net/core/filter.c:2136 [inline] __bpf_redirect_common net/core/filter.c:2180 [inline] __bpf_redirect+0x14a6/0x1620 net/core/filter.c:2187 ____bpf_clone_redirect net/core/filter.c:2460 [inline] bpf_clone_redirect+0x328/0x470 net/core/filter.c:2432 ___bpf_prog_run+0x13fe/0xe0f0 kernel/bpf/core.c:1997 __bpf_prog_run512+0xb5/0xe0 kernel/bpf/core.c:2238 bpf_dispatcher_nop_func include/linux/bpf.h:1234 [inline] __bpf_prog_run include/linux/filter.h:657 [inline] bpf_prog_run include/linux/filter.h:664 [inline] bpf_test_run+0x499/0xc30 net/bpf/test_run.c:425 bpf_prog_test_run_skb+0x14ea/0x1f20 net/bpf/test_run.c:1058 bpf_prog_test_run+0x6b7/0xad0 kernel/bpf/syscall.c:4269 __sys_bpf+0x6aa/0xd90 kernel/bpf/syscall.c:5678 __do_sys_bpf kernel/bpf/syscall.c:5767 [inline] __se_sys_bpf kernel/bpf/syscall.c:5765 [inline] __x64_sys_bpf+0xa0/0xe0 kernel/bpf/syscall.c:5765 x64_sys_call+0x96b/0x3b50 arch/x86/include/generated/asm/syscalls_64.h:322 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcf/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f(CVE-2024-38538)
In the Linux kernel, the following vulnerability has been resolved:
of: module: add buffer overflow check in of_modalias()
In of_modalias(), if the buffer happens to be too small even for the 1st snprintf() call, the len parameter will become negative and str parameter (if not NULL initially) will point beyond the buffer's end. Add the buffer overflow check after the 1st snprintf() call and fix such check after the strlen() call (accounting for the terminating NUL char).(CVE-2024-38541)
In the Linux kernel, the following vulnerability has been resolved:
drm/mediatek: Add 0 size check to mtk_drm_gem_obj
Add a check to mtk_drm_gem_init if we attempt to allocate a GEM object of 0 bytes. Currently, no such check exists and the kernel will panic if a userspace application attempts to allocate a 0x0 GBM buffer.
Tested by attempting to allocate a 0x0 GBM buffer on an MT8188 and verifying that we now return EINVAL.(CVE-2024-38549)
In the Linux kernel, the following vulnerability has been resolved:
speakup: Fix sizeof() vs ARRAY_SIZE() bug
The "buf" pointer is an array of u16 values. This code should be using ARRAY_SIZE() (which is 256) instead of sizeof() (which is 512), otherwise it can the still got out of bounds.(CVE-2024-38587)
In the Linux kernel, the following vulnerability has been resolved:
af_unix: Fix data races in unix_release_sock/unix_stream_sendmsg
A data-race condition has been identified in af_unix. In one data path, the write function unix_release_sock() atomically writes to sk->sk_shutdown using WRITE_ONCE. However, on the reader side, unix_stream_sendmsg() does not read it atomically. Consequently, this issue is causing the following KCSAN splat to occur:
BUG: KCSAN: data-race in unix_release_sock / unix_stream_sendmsg
write (marked) to 0xffff88867256ddbb of 1 bytes by task 7270 on cpu 28:
unix_release_sock (net/unix/af_unix.c:640)
unix_release (net/unix/af_unix.c:1050)
sock_close (net/socket.c:659 net/socket.c:1421)
__fput (fs/file_table.c:422)
__fput_sync (fs/file_table.c:508)
__se_sys_close (fs/open.c:1559 fs/open.c:1541)
__x64_sys_close (fs/open.c:1541)
x64_sys_call (arch/x86/entry/syscall_64.c:33)
do_syscall_64 (arch/x86/entry/common.c:?)
entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)
read to 0xffff88867256ddbb of 1 bytes by task 989 on cpu 14:
unix_stream_sendmsg (net/unix/af_unix.c:2273)
__sock_sendmsg (net/socket.c:730 net/socket.c:745)
____sys_sendmsg (net/socket.c:2584)
__sys_sendmmsg (net/socket.c:2638 net/socket.c:2724)
__x64_sys_sendmmsg (net/socket.c:2753 net/socket.c:2750 net/socket.c:2750)
x64_sys_call (arch/x86/entry/syscall_64.c:33)
do_syscall_64 (arch/x86/entry/common.c:?)
entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)
value changed: 0x01 -> 0x03
The line numbers are related to commit dd5a440a31fa ("Linux 6.9-rc7").
Commit e1d09c2c2f57 ("af_unix: Fix data races around sk->sk_shutdown.") addressed a comparable issue in the past regarding sk->sk_shutdown. However, it overlooked resolving this particular data path. This patch only offending unix_stream_sendmsg() function, since the other reads seem to be protected by unix_state_lock() as discussed in(CVE-2024-38596)
In the Linux kernel, the following vulnerability has been resolved:
ring-buffer: Fix a race between readers and resize checks
The reader code in rb_get_reader_page() swaps a new reader page into the ring buffer by doing cmpxchg on old->list.prev->next to point it to the new page. Following that, if the operation is successful, old->list.next->prev gets updated too. This means the underlying doubly-linked list is temporarily inconsistent, page->prev->next or page->next->prev might not be equal back to page for some page in the ring buffer.
The resize operation in ring_buffer_resize() can be invoked in parallel. It calls rb_check_pages() which can detect the described inconsistency and stop further tracing:
[ 190.271762] ------------[ cut here ]------------ [ 190.271771] WARNING: CPU: 1 PID: 6186 at kernel/trace/ring_buffer.c:1467 rb_check_pages.isra.0+0x6a/0xa0 [ 190.271789] Modules linked in: [...] [ 190.271991] Unloaded tainted modules: intel_uncore_frequency(E):1 skx_edac(E):1 [ 190.272002] CPU: 1 PID: 6186 Comm: cmd.sh Kdump: loaded Tainted: G E 6.9.0-rc6-default #5 158d3e1e6d0b091c34c3b96bfd99a1c58306d79f [ 190.272011] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.0-0-gd239552c-rebuilt.opensuse.org 04/01/2014 [ 190.272015] RIP: 0010:rb_check_pages.isra.0+0x6a/0xa0 [ 190.272023] Code: [...] [ 190.272028] RSP: 0018:ffff9c37463abb70 EFLAGS: 00010206 [ 190.272034] RAX: ffff8eba04b6cb80 RBX: 0000000000000007 RCX: ffff8eba01f13d80 [ 190.272038] RDX: ffff8eba01f130c0 RSI: ffff8eba04b6cd00 RDI: ffff8eba0004c700 [ 190.272042] RBP: ffff8eba0004c700 R08: 0000000000010002 R09: 0000000000000000 [ 190.272045] R10: 00000000ffff7f52 R11: ffff8eba7f600000 R12: ffff8eba0004c720 [ 190.272049] R13: ffff8eba00223a00 R14: 0000000000000008 R15: ffff8eba067a8000 [ 190.272053] FS: 00007f1bd64752c0(0000) GS:ffff8eba7f680000(0000) knlGS:0000000000000000 [ 190.272057] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 190.272061] CR2: 00007f1bd6662590 CR3: 000000010291e001 CR4: 0000000000370ef0 [ 190.272070] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 190.272073] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 190.272077] Call Trace: [ 190.272098] <TASK> [ 190.272189] ring_buffer_resize+0x2ab/0x460 [ 190.272199] __tracing_resize_ring_buffer.part.0+0x23/0xa0 [ 190.272206] tracing_resize_ring_buffer+0x65/0x90 [ 190.272216] tracing_entries_write+0x74/0xc0 [ 190.272225] vfs_write+0xf5/0x420 [ 190.272248] ksys_write+0x67/0xe0 [ 190.272256] do_syscall_64+0x82/0x170 [ 190.272363] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 190.272373] RIP: 0033:0x7f1bd657d263 [ 190.272381] Code: [...] [ 190.272385] RSP: 002b:00007ffe72b643f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 [ 190.272391] RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007f1bd657d263 [ 190.272395] RDX: 0000000000000002 RSI: 0000555a6eb538e0 RDI: 0000000000000001 [ 190.272398] RBP: 0000555a6eb538e0 R08: 000000000000000a R09: 0000000000000000 [ 190.272401] R10: 0000555a6eb55190 R11: 0000000000000246 R12: 00007f1bd6662500 [ 190.272404] R13: 0000000000000002 R14: 00007f1bd6667c00 R15: 0000000000000002 [ 190.272412] </TASK> [ 190.272414] ---[ end trace 0000000000000000 ]---
Note that ring_buffer_resize() calls rb_check_pages() only if the parent trace_buffer has recording disabled. Recent commit d78ab792705c ("tracing: Stop current tracer when resizing buffer") causes that it is now always the case which makes it more likely to experience this issue.
The window to hit this race is nonetheless very small. To help reproducing it, one can add a delay loop in rb_get_reader_page():
ret = rb_head_page_replace(reader, cpu_buffer->reader_page); if (!ret) goto spin; for (unsigned i = 0; i < 1U << 26; i++) /* inserted delay loop */ asm volatile ("" : : : "memory"); rb_list_head(reader->list.next)->prev = &cpu_buffer->reader_page->list;
.. ---truncated---(CVE-2024-38601)
In the Linux kernel, the following vulnerability has been resolved:
ALSA: core: Fix NULL module pointer assignment at card init
The commit 81033c6b584b ("ALSA: core: Warn on empty module") introduced a WARN_ON() for a NULL module pointer passed at snd_card object creation, and it also wraps the code around it with '#ifdef MODULE'. This works in most cases, but the devils are always in details. "MODULE" is defined when the target code (i.e. the sound core) is built as a module; but this doesn't mean that the caller is also built-in or not. Namely, when only the sound core is built-in (CONFIG_SND=y) while the driver is a module (CONFIG_SND_USB_AUDIO=m), the passed module pointer is ignored even if it's non-NULL, and card->module remains as NULL. This would result in the missing module reference up/down at the device open/close, leading to a race with the code execution after the module removal.
For addressing the bug, move the assignment of card->module again out of ifdef. The WARN_ON() is still wrapped with ifdef because the module can be really NULL when all sound drivers are built-in.
Note that we keep 'ifdef MODULE' for WARN_ON(), otherwise it would lead to a false-positive NULL module check. Admittedly it won't catch perfectly, i.e. no check is performed when CONFIG_SND=y. But, it's no real problem as it's only for debugging, and the condition is pretty rare.(CVE-2024-38605)
In the Linux kernel, the following vulnerability has been resolved:
f2fs: multidev: fix to recognize valid zero block address
As reported by Yi Zhang in mailing list [1], kernel warning was catched during zbd/010 test as below:
./check zbd/010 zbd/010 (test gap zone support with F2FS) [failed] runtime ... 3.752s something found in dmesg: [ 4378.146781] run blktests zbd/010 at 2024-02-18 11:31:13 [ 4378.192349] null_blk: module loaded [ 4378.209860] null_blk: disk nullb0 created [ 4378.413285] scsi_debug:sdebug_driver_probe: scsi_debug: trim poll_queues to 0. poll_q/nr_hw = (0/1) [ 4378.422334] scsi host15: scsi_debug: version 0191 [20210520] dev_size_mb=1024, opts=0x0, submit_queues=1, statistics=0 [ 4378.434922] scsi 15:0:0:0: Direct-Access-ZBC Linux scsi_debug 0191 PQ: 0 ANSI: 7 [ 4378.443343] scsi 15:0:0:0: Power-on or device reset occurred [ 4378.449371] sd 15:0:0:0: Attached scsi generic sg5 type 20 [ 4378.449418] sd 15:0:0:0: [sdf] Host-managed zoned block device ... (See '/mnt/tests/gitlab.com/api/v4/projects/19168116/repository/archive.zip/storage/blktests/blk/blktests/results/nodev/zbd/010.dmesg'
WARNING: CPU: 22 PID: 44011 at fs/iomap/iter.c:51 CPU: 22 PID: 44011 Comm: fio Not tainted 6.8.0-rc3+ #1 RIP: 0010:iomap_iter+0x32b/0x350 Call Trace: <TASK> __iomap_dio_rw+0x1df/0x830 f2fs_file_read_iter+0x156/0x3d0 [f2fs] aio_read+0x138/0x210 io_submit_one+0x188/0x8c0 __x64_sys_io_submit+0x8c/0x1a0 do_syscall_64+0x86/0x170 entry_SYSCALL_64_after_hwframe+0x6e/0x76
Shinichiro Kawasaki helps to analyse this issue and proposes a potential fixing patch in [2].
Quoted from reply of Shinichiro Kawasaki:
"I confirmed that the trigger commit is dbf8e63f48af as Yi reported. I took a look in the commit, but it looks fine to me. So I thought the cause is not in the commit diff.
I found the WARN is printed when the f2fs is set up with multiple devices, and read requests are mapped to the very first block of the second device in the direct read path. In this case, f2fs_map_blocks() and f2fs_map_blocks_cached() modify map->m_pblk as the physical block address from each block device. It becomes zero when it is mapped to the first block of the device. However, f2fs_iomap_begin() assumes that map->m_pblk is the physical block address of the whole f2fs, across the all block devices. It compares map->m_pblk against NULL_ADDR == 0, then go into the unexpected branch and sets the invalid iomap->length. The WARN catches the invalid iomap->length.
This WARN is printed even for non-zoned block devices, by following steps.
- Create two (non-zoned) null_blk devices memory backed with 128MB size each: nullb0 and nullb1. # mkfs.f2fs /dev/nullb0 -c /dev/nullb1 # mount -t f2fs /dev/nullb0 "${mount_dir}" # dd if=/dev/zero of="${mount_dir}/test.dat" bs=1M count=192 # dd if="${mount_dir}/test.dat" of=/dev/null bs=1M count=192 iflag=direct
..."
So, the root cause of this issue is: when multi-devices feature is on, f2fs_map_blocks() may return zero blkaddr in non-primary device, which is a verified valid block address, however, f2fs_iomap_begin() treats it as an invalid block address, and then it triggers the warning in iomap framework code.
Finally, as discussed, we decide to use a more simple and direct way that checking (map.m_flags & F2FS_MAP_MAPPED) condition instead of (map.m_pblk != NULL_ADDR) to fix this issue.
Thanks a lot for the effort of Yi Zhang and Shinichiro Kawasaki on this issue.
[1] https://lore.kernel.org/linux-f2fs-devel/CAHj4cs-kfojYC9i0G73PRkYzcxCTex=-vugRFeP40g_URGvnfQ@mail.gmail.com/ [2] https://lore.kernel.org/linux-f2fs-devel/gngdj77k4picagsfdtiaa7gpgnup6fsgwzsltx6milmhegmjff@iax2n4wvrqye/(CVE-2024-38636)
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"kernel-6.6.0-31.0.0.39.oe2403.aarch64.rpm",
"kernel-tools-devel-6.6.0-31.0.0.39.oe2403.aarch64.rpm",
"kernel-tools-6.6.0-31.0.0.39.oe2403.aarch64.rpm",
"kernel-devel-6.6.0-31.0.0.39.oe2403.aarch64.rpm",
"python3-perf-6.6.0-31.0.0.39.oe2403.aarch64.rpm",
"kernel-debuginfo-6.6.0-31.0.0.39.oe2403.aarch64.rpm",
"python3-perf-debuginfo-6.6.0-31.0.0.39.oe2403.aarch64.rpm",
"bpftool-debuginfo-6.6.0-31.0.0.39.oe2403.aarch64.rpm",
"perf-6.6.0-31.0.0.39.oe2403.aarch64.rpm",
"bpftool-6.6.0-31.0.0.39.oe2403.aarch64.rpm",
"kernel-headers-6.6.0-31.0.0.39.oe2403.aarch64.rpm",
"perf-debuginfo-6.6.0-31.0.0.39.oe2403.aarch64.rpm",
"kernel-source-6.6.0-31.0.0.39.oe2403.aarch64.rpm",
"kernel-tools-debuginfo-6.6.0-31.0.0.39.oe2403.aarch64.rpm",
"kernel-debugsource-6.6.0-31.0.0.39.oe2403.aarch64.rpm"
],
"src": [
"kernel-6.6.0-31.0.0.39.oe2403.src.rpm"
],
"x86_64": [
"bpftool-debuginfo-6.6.0-31.0.0.39.oe2403.x86_64.rpm",
"kernel-headers-6.6.0-31.0.0.39.oe2403.x86_64.rpm",
"python3-perf-6.6.0-31.0.0.39.oe2403.x86_64.rpm",
"perf-debuginfo-6.6.0-31.0.0.39.oe2403.x86_64.rpm",
"kernel-debugsource-6.6.0-31.0.0.39.oe2403.x86_64.rpm",
"perf-6.6.0-31.0.0.39.oe2403.x86_64.rpm",
"python3-perf-debuginfo-6.6.0-31.0.0.39.oe2403.x86_64.rpm",
"kernel-6.6.0-31.0.0.39.oe2403.x86_64.rpm",
"kernel-source-6.6.0-31.0.0.39.oe2403.x86_64.rpm",
"kernel-debuginfo-6.6.0-31.0.0.39.oe2403.x86_64.rpm",
"kernel-tools-6.6.0-31.0.0.39.oe2403.x86_64.rpm",
"kernel-devel-6.6.0-31.0.0.39.oe2403.x86_64.rpm",
"bpftool-6.6.0-31.0.0.39.oe2403.x86_64.rpm",
"kernel-tools-devel-6.6.0-31.0.0.39.oe2403.x86_64.rpm",
"kernel-tools-debuginfo-6.6.0-31.0.0.39.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-31.0.0.39.oe2403"
}
],
"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:\r\n\r\ntpm_tis_spi: Account for SPI header when allocating TPM SPI xfer buffer\r\n\r\nThe TPM SPI transfer mechanism uses MAX_SPI_FRAMESIZE for computing the\nmaximum transfer length and the size of the transfer buffer. As such, it\ndoes not account for the 4 bytes of header that prepends the SPI data\nframe. This can result in out-of-bounds accesses and was confirmed with\nKASAN.\r\n\r\nIntroduce SPI_HDRSIZE to account for the header and use to allocate the\ntransfer buffer.(CVE-2024-36477)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: fix out-of-bounds access in ops_init\r\n\r\nnet_alloc_generic is called by net_alloc, which is called without any\nlocking. It reads max_gen_ptrs, which is changed under pernet_ops_rwsem. It\nis read twice, first to allocate an array, then to set s.len, which is\nlater used to limit the bounds of the array access.\r\n\r\nIt is possible that the array is allocated and another thread is\nregistering a new pernet ops, increments max_gen_ptrs, which is then used\nto set s.len with a larger than allocated length for the variable array.\r\n\r\nFix it by reading max_gen_ptrs only once in net_alloc_generic. If\nmax_gen_ptrs is later incremented, it will be caught in net_assign_generic.(CVE-2024-36883)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ngpiolib: cdev: fix uninitialised kfifo\r\n\r\nIf a line is requested with debounce, and that results in debouncing\nin software, and the line is subsequently reconfigured to enable edge\ndetection then the allocation of the kfifo to contain edge events is\noverlooked. This results in events being written to and read from an\nuninitialised kfifo. Read events are returned to userspace.\r\n\r\nInitialise the kfifo in the case where the software debounce is\nalready active.(CVE-2024-36898)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nipv6: fib6_rules: avoid possible NULL dereference in fib6_rule_action()\r\n\r\nsyzbot is able to trigger the following crash [1],\ncaused by unsafe ip6_dst_idev() use.\r\n\r\nIndeed ip6_dst_idev() can return NULL, and must always be checked.\r\n\r\n[1]\r\n\r\nOops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN PTI\nKASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]\nCPU: 0 PID: 31648 Comm: syz-executor.0 Not tainted 6.9.0-rc4-next-20240417-syzkaller #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024\n RIP: 0010:__fib6_rule_action net/ipv6/fib6_rules.c:237 [inline]\n RIP: 0010:fib6_rule_action+0x241/0x7b0 net/ipv6/fib6_rules.c:267\nCode: 02 00 00 49 8d 9f d8 00 00 00 48 89 d8 48 c1 e8 03 42 80 3c 20 00 74 08 48 89 df e8 f9 32 bf f7 48 8b 1b 48 89 d8 48 c1 e8 03 \u0026lt;42\u0026gt; 80 3c 20 00 74 08 48 89 df e8 e0 32 bf f7 4c 8b 03 48 89 ef 4c\nRSP: 0018:ffffc9000fc1f2f0 EFLAGS: 00010246\nRAX: 0000000000000000 RBX: 0000000000000000 RCX: 1a772f98c8186700\nRDX: 0000000000000003 RSI: ffffffff8bcac4e0 RDI: ffffffff8c1f9760\nRBP: ffff8880673fb980 R08: ffffffff8fac15ef R09: 1ffffffff1f582bd\nR10: dffffc0000000000 R11: fffffbfff1f582be R12: dffffc0000000000\nR13: 0000000000000080 R14: ffff888076509000 R15: ffff88807a029a00\nFS: 00007f55e82ca6c0(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000001b31d23000 CR3: 0000000022b66000 CR4: 00000000003506f0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n fib_rules_lookup+0x62c/0xdb0 net/core/fib_rules.c:317\n fib6_rule_lookup+0x1fd/0x790 net/ipv6/fib6_rules.c:108\n ip6_route_output_flags_noref net/ipv6/route.c:2637 [inline]\n ip6_route_output_flags+0x38e/0x610 net/ipv6/route.c:2649\n ip6_route_output include/net/ip6_route.h:93 [inline]\n ip6_dst_lookup_tail+0x189/0x11a0 net/ipv6/ip6_output.c:1120\n ip6_dst_lookup_flow+0xb9/0x180 net/ipv6/ip6_output.c:1250\n sctp_v6_get_dst+0x792/0x1e20 net/sctp/ipv6.c:326\n sctp_transport_route+0x12c/0x2e0 net/sctp/transport.c:455\n sctp_assoc_add_peer+0x614/0x15c0 net/sctp/associola.c:662\n sctp_connect_new_asoc+0x31d/0x6c0 net/sctp/socket.c:1099\n __sctp_connect+0x66d/0xe30 net/sctp/socket.c:1197\n sctp_connect net/sctp/socket.c:4819 [inline]\n sctp_inet_connect+0x149/0x1f0 net/sctp/socket.c:4834\n __sys_connect_file net/socket.c:2048 [inline]\n __sys_connect+0x2df/0x310 net/socket.c:2065\n __do_sys_connect net/socket.c:2075 [inline]\n __se_sys_connect net/socket.c:2072 [inline]\n __x64_sys_connect+0x7a/0x90 net/socket.c:2072\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f(CVE-2024-36902)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nipv6: Fix potential uninit-value access in __ip6_make_skb()\r\n\r\nAs it was done in commit fc1092f51567 (\u0026quot;ipv4: Fix uninit-value access in\n__ip_make_skb()\u0026quot;) for IPv4, check FLOWI_FLAG_KNOWN_NH on fl6-\u0026gt;flowi6_flags\ninstead of testing HDRINCL on the socket to avoid a race condition which\ncauses uninit-value access.(CVE-2024-36903)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntcp: defer shutdown(SEND_SHUTDOWN) for TCP_SYN_RECV sockets\r\n\r\nTCP_SYN_RECV state is really special, it is only used by\ncross-syn connections, mostly used by fuzzers.\r\n\r\nIn the following crash [1], syzbot managed to trigger a divide\nby zero in tcp_rcv_space_adjust()\r\n\r\nA socket makes the following state transitions,\nwithout ever calling tcp_init_transfer(),\nmeaning tcp_init_buffer_space() is also not called.\r\n\r\n TCP_CLOSE\nconnect()\n TCP_SYN_SENT\n TCP_SYN_RECV\nshutdown() -\u0026gt; tcp_shutdown(sk, SEND_SHUTDOWN)\n TCP_FIN_WAIT1\r\n\r\nTo fix this issue, change tcp_shutdown() to not\nperform a TCP_SYN_RECV -\u0026gt; TCP_FIN_WAIT1 transition,\nwhich makes no sense anyway.\r\n\r\nWhen tcp_rcv_state_process() later changes socket state\nfrom TCP_SYN_RECV to TCP_ESTABLISH, then look at\nsk-\u0026gt;sk_shutdown to finally enter TCP_FIN_WAIT1 state,\nand send a FIN packet from a sane socket state.\r\n\r\nThis means tcp_send_fin() can now be called from BH\ncontext, and must use GFP_ATOMIC allocations.\r\n\r\n[1]\ndivide error: 0000 [#1] PREEMPT SMP KASAN NOPTI\nCPU: 1 PID: 5084 Comm: syz-executor358 Not tainted 6.9.0-rc6-syzkaller-00022-g98369dccd2f8 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024\n RIP: 0010:tcp_rcv_space_adjust+0x2df/0x890 net/ipv4/tcp_input.c:767\nCode: e3 04 4c 01 eb 48 8b 44 24 38 0f b6 04 10 84 c0 49 89 d5 0f 85 a5 03 00 00 41 8b 8e c8 09 00 00 89 e8 29 c8 48 0f af c3 31 d2 \u0026lt;48\u0026gt; f7 f1 48 8d 1c 43 49 8d 96 76 08 00 00 48 89 d0 48 c1 e8 03 48\nRSP: 0018:ffffc900031ef3f0 EFLAGS: 00010246\nRAX: 0c677a10441f8f42 RBX: 000000004fb95e7e RCX: 0000000000000000\nRDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000\nRBP: 0000000027d4b11f R08: ffffffff89e535a4 R09: 1ffffffff25e6ab7\nR10: dffffc0000000000 R11: ffffffff8135e920 R12: ffff88802a9f8d30\nR13: dffffc0000000000 R14: ffff88802a9f8d00 R15: 1ffff1100553f2da\nFS: 00005555775c0380(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f1155bf2304 CR3: 000000002b9f2000 CR4: 0000000000350ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n tcp_recvmsg_locked+0x106d/0x25a0 net/ipv4/tcp.c:2513\n tcp_recvmsg+0x25d/0x920 net/ipv4/tcp.c:2578\n inet6_recvmsg+0x16a/0x730 net/ipv6/af_inet6.c:680\n sock_recvmsg_nosec net/socket.c:1046 [inline]\n sock_recvmsg+0x109/0x280 net/socket.c:1068\n ____sys_recvmsg+0x1db/0x470 net/socket.c:2803\n ___sys_recvmsg net/socket.c:2845 [inline]\n do_recvmmsg+0x474/0xae0 net/socket.c:2939\n __sys_recvmmsg net/socket.c:3018 [inline]\n __do_sys_recvmmsg net/socket.c:3041 [inline]\n __se_sys_recvmmsg net/socket.c:3034 [inline]\n __x64_sys_recvmmsg+0x199/0x250 net/socket.c:3034\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7faeb6363db9\nCode: 28 00 00 00 75 05 48 83 c4 28 c3 e8 c1 17 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\nRSP: 002b:00007ffcc1997168 EFLAGS: 00000246 ORIG_RAX: 000000000000012b\nRAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007faeb6363db9\nRDX: 0000000000000001 RSI: 0000000020000bc0 RDI: 0000000000000005\nRBP: 0000000000000000 R08: 0000000000000000 R09: 000000000000001c\nR10: 0000000000000122 R11: 0000000000000246 R12: 0000000000000000\nR13: 0000000000000000 R14: 0000000000000001 R15: 0000000000000001(CVE-2024-36905)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nscsi: bnx2fc: Remove spin_lock_bh while releasing resources after upload\r\n\r\nThe session resources are used by FW and driver when session is offloaded,\nonce session is uploaded these resources are not used. The lock is not\nrequired as these fields won\u0026apos;t be used any longer. The offload and upload\ncalls are sequential, hence lock is not required.\r\n\r\nThis will suppress following BUG_ON():\r\n\r\n[ 449.843143] ------------[ cut here ]------------\n[ 449.848302] kernel BUG at mm/vmalloc.c:2727!\n[ 449.853072] invalid opcode: 0000 [#1] PREEMPT SMP PTI\n[ 449.858712] CPU: 5 PID: 1996 Comm: kworker/u24:2 Not tainted 5.14.0-118.el9.x86_64 #1\nRebooting.\n[ 449.867454] Hardware name: Dell Inc. PowerEdge R730/0WCJNT, BIOS 2.3.4 11/08/2016\n[ 449.876966] Workqueue: fc_rport_eq fc_rport_work [libfc]\n[ 449.882910] RIP: 0010:vunmap+0x2e/0x30\n[ 449.887098] Code: 00 65 8b 05 14 a2 f0 4a a9 00 ff ff 00 75 1b 55 48 89 fd e8 34 36 79 00 48 85 ed 74 0b 48 89 ef 31 f6 5d e9 14 fc ff ff 5d c3 \u0026lt;0f\u0026gt; 0b 0f 1f 44 00 00 41 57 41 56 49 89 ce 41 55 49 89 fd 41 54 41\n[ 449.908054] RSP: 0018:ffffb83d878b3d68 EFLAGS: 00010206\n[ 449.913887] RAX: 0000000080000201 RBX: ffff8f4355133550 RCX: 000000000d400005\n[ 449.921843] RDX: 0000000000000001 RSI: 0000000000001000 RDI: ffffb83da53f5000\n[ 449.929808] RBP: ffff8f4ac6675800 R08: ffffb83d878b3d30 R09: 00000000000efbdf\n[ 449.937774] R10: 0000000000000003 R11: ffff8f434573e000 R12: 0000000000001000\n[ 449.945736] R13: 0000000000001000 R14: ffffb83da53f5000 R15: ffff8f43d4ea3ae0\n[ 449.953701] FS: 0000000000000000(0000) GS:ffff8f529fc80000(0000) knlGS:0000000000000000\n[ 449.962732] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 449.969138] CR2: 00007f8cf993e150 CR3: 0000000efbe10003 CR4: 00000000003706e0\n[ 449.977102] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[ 449.985065] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n[ 449.993028] Call Trace:\n[ 449.995756] __iommu_dma_free+0x96/0x100\n[ 450.000139] bnx2fc_free_session_resc+0x67/0x240 [bnx2fc]\n[ 450.006171] bnx2fc_upload_session+0xce/0x100 [bnx2fc]\n[ 450.011910] bnx2fc_rport_event_handler+0x9f/0x240 [bnx2fc]\n[ 450.018136] fc_rport_work+0x103/0x5b0 [libfc]\n[ 450.023103] process_one_work+0x1e8/0x3c0\n[ 450.027581] worker_thread+0x50/0x3b0\n[ 450.031669] ? rescuer_thread+0x370/0x370\n[ 450.036143] kthread+0x149/0x170\n[ 450.039744] ? set_kthread_struct+0x40/0x40\n[ 450.044411] ret_from_fork+0x22/0x30\n[ 450.048404] Modules linked in: vfat msdos fat xfs nfs_layout_nfsv41_files rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver dm_service_time qedf qed crc8 bnx2fc libfcoe libfc scsi_transport_fc intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp dcdbas rapl intel_cstate intel_uncore mei_me pcspkr mei ipmi_ssif lpc_ich ipmi_si fuse zram ext4 mbcache jbd2 loop nfsv3 nfs_acl nfs lockd grace fscache netfs irdma ice sd_mod t10_pi sg ib_uverbs ib_core 8021q garp mrp stp llc mgag200 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt mxm_wmi fb_sys_fops cec crct10dif_pclmul ahci crc32_pclmul bnx2x drm ghash_clmulni_intel libahci rfkill i40e libata megaraid_sas mdio wmi sunrpc lrw dm_crypt dm_round_robin dm_multipath dm_snapshot dm_bufio dm_mirror dm_region_hash dm_log dm_zero dm_mod linear raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx raid6_pq libcrc32c crc32c_intel raid1 raid0 iscsi_ibft squashfs be2iscsi bnx2i cnic uio cxgb4i cxgb4 tls\n[ 450.048497] libcxgbi libcxgb qla4xxx iscsi_boot_sysfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi edd ipmi_devintf ipmi_msghandler\n[ 450.159753] ---[ end trace 712de2c57c64abc8 ]---(CVE-2024-36919)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ns390/qeth: Fix kernel panic after setting hsuid\r\n\r\nSymptom:\nWhen the hsuid attribute is set for the first time on an IQD Layer3\ndevice while the corresponding network interface is already UP,\nthe kernel will try to execute a napi function pointer that is NULL.\r\n\r\nExample:\n---------------------------------------------------------------------------\n[ 2057.572696] illegal operation: 0001 ilc:1 [#1] SMP\n[ 2057.572702] Modules linked in: af_iucv qeth_l3 zfcp scsi_transport_fc sunrpc nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6\nnft_reject nft_ct nf_tables_set nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables libcrc32c nfnetlink ghash_s390 prng xts aes_s390 des_s390 de\ns_generic sha3_512_s390 sha3_256_s390 sha512_s390 vfio_ccw vfio_mdev mdev vfio_iommu_type1 eadm_sch vfio ext4 mbcache jbd2 qeth_l2 bridge stp llc dasd_eckd_mod qeth dasd_mod\n qdio ccwgroup pkey zcrypt\n[ 2057.572739] CPU: 6 PID: 60182 Comm: stress_client Kdump: loaded Not tainted 4.18.0-541.el8.s390x #1\n[ 2057.572742] Hardware name: IBM 3931 A01 704 (LPAR)\n[ 2057.572744] Krnl PSW : 0704f00180000000 0000000000000002 (0x2)\n[ 2057.572748] R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:3 PM:0 RI:0 EA:3\n[ 2057.572751] Krnl GPRS: 0000000000000004 0000000000000000 00000000a3b008d8 0000000000000000\n[ 2057.572754] 00000000a3b008d8 cb923a29c779abc5 0000000000000000 00000000814cfd80\n[ 2057.572756] 000000000000012c 0000000000000000 00000000a3b008d8 00000000a3b008d8\n[ 2057.572758] 00000000bab6d500 00000000814cfd80 0000000091317e46 00000000814cfc68\n[ 2057.572762] Krnl Code:#0000000000000000: 0000 illegal\n \u0026gt;0000000000000002: 0000 illegal\n 0000000000000004: 0000 illegal\n 0000000000000006: 0000 illegal\n 0000000000000008: 0000 illegal\n 000000000000000a: 0000 illegal\n 000000000000000c: 0000 illegal\n 000000000000000e: 0000 illegal\n[ 2057.572800] Call Trace:\n[ 2057.572801] ([\u0026lt;00000000ec639700\u0026gt;] 0xec639700)\n[ 2057.572803] [\u0026lt;00000000913183e2\u0026gt;] net_rx_action+0x2ba/0x398\n[ 2057.572809] [\u0026lt;0000000091515f76\u0026gt;] __do_softirq+0x11e/0x3a0\n[ 2057.572813] [\u0026lt;0000000090ce160c\u0026gt;] do_softirq_own_stack+0x3c/0x58\n[ 2057.572817] ([\u0026lt;0000000090d2cbd6\u0026gt;] do_softirq.part.1+0x56/0x60)\n[ 2057.572822] [\u0026lt;0000000090d2cc60\u0026gt;] __local_bh_enable_ip+0x80/0x98\n[ 2057.572825] [\u0026lt;0000000091314706\u0026gt;] __dev_queue_xmit+0x2be/0xd70\n[ 2057.572827] [\u0026lt;000003ff803dd6d6\u0026gt;] afiucv_hs_send+0x24e/0x300 [af_iucv]\n[ 2057.572830] [\u0026lt;000003ff803dd88a\u0026gt;] iucv_send_ctrl+0x102/0x138 [af_iucv]\n[ 2057.572833] [\u0026lt;000003ff803de72a\u0026gt;] iucv_sock_connect+0x37a/0x468 [af_iucv]\n[ 2057.572835] [\u0026lt;00000000912e7e90\u0026gt;] __sys_connect+0xa0/0xd8\n[ 2057.572839] [\u0026lt;00000000912e9580\u0026gt;] sys_socketcall+0x228/0x348\n[ 2057.572841] [\u0026lt;0000000091514e1a\u0026gt;] system_call+0x2a6/0x2c8\n[ 2057.572843] Last Breaking-Event-Address:\n[ 2057.572844] [\u0026lt;0000000091317e44\u0026gt;] __napi_poll+0x4c/0x1d8\n[ 2057.572846]\n[ 2057.572847] Kernel panic - not syncing: Fatal exception in interrupt\n-------------------------------------------------------------------------------------------\r\n\r\nAnalysis:\nThere is one napi structure per out_q: card-\u0026gt;qdio.out_qs[i].napi\nThe napi.poll functions are set during qeth_open().\r\n\r\nSince\ncommit 1cfef80d4c2b (\u0026quot;s390/qeth: Don\u0026apos;t call dev_close/dev_open (DOWN/UP)\u0026quot;)\nqeth_set_offline()/qeth_set_online() no longer call dev_close()/\ndev_open(). So if qeth_free_qdio_queues() cleared\ncard-\u0026gt;qdio.out_qs[i].napi.poll while the network interface was UP and the\ncard was offline, they are not set again.\r\n\r\nReproduction:\nchzdev -e $devno layer2=0\nip link set dev $network_interface up\necho 0 \u0026gt; /sys/bus/ccw\n---truncated---(CVE-2024-36928)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nBluetooth: L2CAP: Fix div-by-zero in l2cap_le_flowctl_init()\r\n\r\nl2cap_le_flowctl_init() can cause both div-by-zero and an integer\noverflow since hdev-\u0026gt;le_mtu may not fall in the valid range.\r\n\r\nMove MTU from hci_dev to hci_conn to validate MTU and stop the connection\nprocess earlier if MTU is invalid.\nAlso, add a missing validation in read_buffer_size() and make it return\nan error value if the validation fails.\nNow hci_conn_add() returns ERR_PTR() as it can fail due to the both a\nkzalloc failure and invalid MTU value.\r\n\r\ndivide error: 0000 [#1] PREEMPT SMP KASAN NOPTI\nCPU: 0 PID: 67 Comm: kworker/u5:0 Tainted: G W 6.9.0-rc5+ #20\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014\nWorkqueue: hci0 hci_rx_work\nRIP: 0010:l2cap_le_flowctl_init+0x19e/0x3f0 net/bluetooth/l2cap_core.c:547\nCode: e8 17 17 0c 00 66 41 89 9f 84 00 00 00 bf 01 00 00 00 41 b8 02 00 00 00 4c\n89 fe 4c 89 e2 89 d9 e8 27 17 0c 00 44 89 f0 31 d2 \u0026lt;66\u0026gt; f7 f3 89 c3 ff c3 4d 8d\nb7 88 00 00 00 4c 89 f0 48 c1 e8 03 42\nRSP: 0018:ffff88810bc0f858 EFLAGS: 00010246\nRAX: 00000000000002a0 RBX: 0000000000000000 RCX: dffffc0000000000\nRDX: 0000000000000000 RSI: ffff88810bc0f7c0 RDI: ffffc90002dcb66f\nRBP: ffff88810bc0f880 R08: aa69db2dda70ff01 R09: 0000ffaaaaaaaaaa\nR10: 0084000000ffaaaa R11: 0000000000000000 R12: ffff88810d65a084\nR13: dffffc0000000000 R14: 00000000000002a0 R15: ffff88810d65a000\nFS: 0000000000000000(0000) GS:ffff88811ac00000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000020000100 CR3: 0000000103268003 CR4: 0000000000770ef0\nPKRU: 55555554\nCall Trace:\n \u0026lt;TASK\u0026gt;\n l2cap_le_connect_req net/bluetooth/l2cap_core.c:4902 [inline]\n l2cap_le_sig_cmd net/bluetooth/l2cap_core.c:5420 [inline]\n l2cap_le_sig_channel net/bluetooth/l2cap_core.c:5486 [inline]\n l2cap_recv_frame+0xe59d/0x11710 net/bluetooth/l2cap_core.c:6809\n l2cap_recv_acldata+0x544/0x10a0 net/bluetooth/l2cap_core.c:7506\n hci_acldata_packet net/bluetooth/hci_core.c:3939 [inline]\n hci_rx_work+0x5e5/0xb20 net/bluetooth/hci_core.c:4176\n process_one_work kernel/workqueue.c:3254 [inline]\n process_scheduled_works+0x90f/0x1530 kernel/workqueue.c:3335\n worker_thread+0x926/0xe70 kernel/workqueue.c:3416\n kthread+0x2e3/0x380 kernel/kthread.c:388\n ret_from_fork+0x5c/0x90 arch/x86/kernel/process.c:147\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244\n \u0026lt;/TASK\u0026gt;\nModules linked in:\n---[ end trace 0000000000000000 ]---(CVE-2024-36968)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/sched: taprio: always validate TCA_TAPRIO_ATTR_PRIOMAP\r\n\r\nIf one TCA_TAPRIO_ATTR_PRIOMAP attribute has been provided,\ntaprio_parse_mqprio_opt() must validate it, or userspace\ncan inject arbitrary data to the kernel, the second time\ntaprio_change() is called.\r\n\r\nFirst call (with valid attributes) sets dev-\u0026gt;num_tc\nto a non zero value.\r\n\r\nSecond call (with arbitrary mqprio attributes)\nreturns early from taprio_parse_mqprio_opt()\nand bad things can happen.(CVE-2024-36974)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKEYS: trusted: Do not use WARN when encode fails\r\n\r\nWhen asn1_encode_sequence() fails, WARN is not the correct solution.\r\n\r\n1. asn1_encode_sequence() is not an internal function (located\n in lib/asn1_encode.c).\n2. Location is known, which makes the stack trace useless.\n3. Results a crash if panic_on_warn is set.\r\n\r\nIt is also noteworthy that the use of WARN is undocumented, and it\nshould be avoided unless there is a carefully considered rationale to\nuse it.\r\n\r\nReplace WARN with pr_err, and print the return value instead, which is\nonly useful piece of information.(CVE-2024-36975)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nusb: dwc3: Wait unconditionally after issuing EndXfer command\r\n\r\nCurrently all controller IP/revisions except DWC3_usb3 \u0026gt;= 310a\nwait 1ms unconditionally for ENDXFER completion when IOC is not\nset. This is because DWC_usb3 controller revisions \u0026gt;= 3.10a\nsupports GUCTL2[14: Rst_actbitlater] bit which allows polling\nCMDACT bit to know whether ENDXFER command is completed.\r\n\r\nConsider a case where an IN request was queued, and parallelly\nsoft_disconnect was called (due to ffs_epfile_release). This\neventually calls stop_active_transfer with IOC cleared, hence\nsend_gadget_ep_cmd() skips waiting for CMDACT cleared during\nEndXfer. For DWC3 controllers with revisions \u0026gt;= 310a, we don\u0026apos;t\nforcefully wait for 1ms either, and we proceed by unmapping the\nrequests. If ENDXFER didn\u0026apos;t complete by this time, it leads to\nSMMU faults since the controller would still be accessing those\nrequests.\r\n\r\nFix this by ensuring ENDXFER completion by adding 1ms delay in\n__dwc3_stop_active_transfer() unconditionally.(CVE-2024-36977)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: sched: sch_multiq: fix possible OOB write in multiq_tune()\r\n\r\nq-\u0026gt;bands will be assigned to qopt-\u0026gt;bands to execute subsequent code logic\nafter kmalloc. So the old q-\u0026gt;bands should not be used in kmalloc.\nOtherwise, an out-of-bounds write will occur.(CVE-2024-36978)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: bridge: xmit: make sure we have at least eth header len bytes\r\n\r\nsyzbot triggered an uninit value[1] error in bridge device\u0026apos;s xmit path\nby sending a short (less than ETH_HLEN bytes) skb. To fix it check if\nwe can actually pull that amount instead of assuming.\r\n\r\nTested with dropwatch:\n drop at: br_dev_xmit+0xb93/0x12d0 [bridge] (0xffffffffc06739b3)\n origin: software\n timestamp: Mon May 13 11:31:53 2024 778214037 nsec\n protocol: 0x88a8\n length: 2\n original length: 2\n drop reason: PKT_TOO_SMALL\r\n\r\n[1]\nBUG: KMSAN: uninit-value in br_dev_xmit+0x61d/0x1cb0 net/bridge/br_device.c:65\n br_dev_xmit+0x61d/0x1cb0 net/bridge/br_device.c:65\n __netdev_start_xmit include/linux/netdevice.h:4903 [inline]\n netdev_start_xmit include/linux/netdevice.h:4917 [inline]\n xmit_one net/core/dev.c:3531 [inline]\n dev_hard_start_xmit+0x247/0xa20 net/core/dev.c:3547\n __dev_queue_xmit+0x34db/0x5350 net/core/dev.c:4341\n dev_queue_xmit include/linux/netdevice.h:3091 [inline]\n __bpf_tx_skb net/core/filter.c:2136 [inline]\n __bpf_redirect_common net/core/filter.c:2180 [inline]\n __bpf_redirect+0x14a6/0x1620 net/core/filter.c:2187\n ____bpf_clone_redirect net/core/filter.c:2460 [inline]\n bpf_clone_redirect+0x328/0x470 net/core/filter.c:2432\n ___bpf_prog_run+0x13fe/0xe0f0 kernel/bpf/core.c:1997\n __bpf_prog_run512+0xb5/0xe0 kernel/bpf/core.c:2238\n bpf_dispatcher_nop_func include/linux/bpf.h:1234 [inline]\n __bpf_prog_run include/linux/filter.h:657 [inline]\n bpf_prog_run include/linux/filter.h:664 [inline]\n bpf_test_run+0x499/0xc30 net/bpf/test_run.c:425\n bpf_prog_test_run_skb+0x14ea/0x1f20 net/bpf/test_run.c:1058\n bpf_prog_test_run+0x6b7/0xad0 kernel/bpf/syscall.c:4269\n __sys_bpf+0x6aa/0xd90 kernel/bpf/syscall.c:5678\n __do_sys_bpf kernel/bpf/syscall.c:5767 [inline]\n __se_sys_bpf kernel/bpf/syscall.c:5765 [inline]\n __x64_sys_bpf+0xa0/0xe0 kernel/bpf/syscall.c:5765\n x64_sys_call+0x96b/0x3b50 arch/x86/include/generated/asm/syscalls_64.h:322\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xcf/0x1e0 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f(CVE-2024-38538)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nof: module: add buffer overflow check in of_modalias()\r\n\r\nIn of_modalias(), if the buffer happens to be too small even for the 1st\nsnprintf() call, the len parameter will become negative and str parameter\n(if not NULL initially) will point beyond the buffer\u0026apos;s end. Add the buffer\noverflow check after the 1st snprintf() call and fix such check after the\nstrlen() call (accounting for the terminating NUL char).(CVE-2024-38541)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/mediatek: Add 0 size check to mtk_drm_gem_obj\r\n\r\nAdd a check to mtk_drm_gem_init if we attempt to allocate a GEM object\nof 0 bytes. Currently, no such check exists and the kernel will panic if\na userspace application attempts to allocate a 0x0 GBM buffer.\r\n\r\nTested by attempting to allocate a 0x0 GBM buffer on an MT8188 and\nverifying that we now return EINVAL.(CVE-2024-38549)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nspeakup: Fix sizeof() vs ARRAY_SIZE() bug\r\n\r\nThe \u0026quot;buf\u0026quot; pointer is an array of u16 values. This code should be\nusing ARRAY_SIZE() (which is 256) instead of sizeof() (which is 512),\notherwise it can the still got out of bounds.(CVE-2024-38587)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\naf_unix: Fix data races in unix_release_sock/unix_stream_sendmsg\r\n\r\nA data-race condition has been identified in af_unix. In one data path,\nthe write function unix_release_sock() atomically writes to\nsk-\u0026gt;sk_shutdown using WRITE_ONCE. However, on the reader side,\nunix_stream_sendmsg() does not read it atomically. Consequently, this\nissue is causing the following KCSAN splat to occur:\r\n\r\n\tBUG: KCSAN: data-race in unix_release_sock / unix_stream_sendmsg\r\n\r\n\twrite (marked) to 0xffff88867256ddbb of 1 bytes by task 7270 on cpu 28:\n\tunix_release_sock (net/unix/af_unix.c:640)\n\tunix_release (net/unix/af_unix.c:1050)\n\tsock_close (net/socket.c:659 net/socket.c:1421)\n\t__fput (fs/file_table.c:422)\n\t__fput_sync (fs/file_table.c:508)\n\t__se_sys_close (fs/open.c:1559 fs/open.c:1541)\n\t__x64_sys_close (fs/open.c:1541)\n\tx64_sys_call (arch/x86/entry/syscall_64.c:33)\n\tdo_syscall_64 (arch/x86/entry/common.c:?)\n\tentry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\r\n\r\n\tread to 0xffff88867256ddbb of 1 bytes by task 989 on cpu 14:\n\tunix_stream_sendmsg (net/unix/af_unix.c:2273)\n\t__sock_sendmsg (net/socket.c:730 net/socket.c:745)\n\t____sys_sendmsg (net/socket.c:2584)\n\t__sys_sendmmsg (net/socket.c:2638 net/socket.c:2724)\n\t__x64_sys_sendmmsg (net/socket.c:2753 net/socket.c:2750 net/socket.c:2750)\n\tx64_sys_call (arch/x86/entry/syscall_64.c:33)\n\tdo_syscall_64 (arch/x86/entry/common.c:?)\n\tentry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\r\n\r\n\tvalue changed: 0x01 -\u0026gt; 0x03\r\n\r\nThe line numbers are related to commit dd5a440a31fa (\u0026quot;Linux 6.9-rc7\u0026quot;).\r\n\r\nCommit e1d09c2c2f57 (\u0026quot;af_unix: Fix data races around sk-\u0026gt;sk_shutdown.\u0026quot;)\naddressed a comparable issue in the past regarding sk-\u0026gt;sk_shutdown.\nHowever, it overlooked resolving this particular data path.\nThis patch only offending unix_stream_sendmsg() function, since the\nother reads seem to be protected by unix_state_lock() as discussed in(CVE-2024-38596)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nring-buffer: Fix a race between readers and resize checks\r\n\r\nThe reader code in rb_get_reader_page() swaps a new reader page into the\nring buffer by doing cmpxchg on old-\u0026gt;list.prev-\u0026gt;next to point it to the\nnew page. Following that, if the operation is successful,\nold-\u0026gt;list.next-\u0026gt;prev gets updated too. This means the underlying\ndoubly-linked list is temporarily inconsistent, page-\u0026gt;prev-\u0026gt;next or\npage-\u0026gt;next-\u0026gt;prev might not be equal back to page for some page in the\nring buffer.\r\n\r\nThe resize operation in ring_buffer_resize() can be invoked in parallel.\nIt calls rb_check_pages() which can detect the described inconsistency\nand stop further tracing:\r\n\r\n[ 190.271762] ------------[ cut here ]------------\n[ 190.271771] WARNING: CPU: 1 PID: 6186 at kernel/trace/ring_buffer.c:1467 rb_check_pages.isra.0+0x6a/0xa0\n[ 190.271789] Modules linked in: [...]\n[ 190.271991] Unloaded tainted modules: intel_uncore_frequency(E):1 skx_edac(E):1\n[ 190.272002] CPU: 1 PID: 6186 Comm: cmd.sh Kdump: loaded Tainted: G E 6.9.0-rc6-default #5 158d3e1e6d0b091c34c3b96bfd99a1c58306d79f\n[ 190.272011] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.0-0-gd239552c-rebuilt.opensuse.org 04/01/2014\n[ 190.272015] RIP: 0010:rb_check_pages.isra.0+0x6a/0xa0\n[ 190.272023] Code: [...]\n[ 190.272028] RSP: 0018:ffff9c37463abb70 EFLAGS: 00010206\n[ 190.272034] RAX: ffff8eba04b6cb80 RBX: 0000000000000007 RCX: ffff8eba01f13d80\n[ 190.272038] RDX: ffff8eba01f130c0 RSI: ffff8eba04b6cd00 RDI: ffff8eba0004c700\n[ 190.272042] RBP: ffff8eba0004c700 R08: 0000000000010002 R09: 0000000000000000\n[ 190.272045] R10: 00000000ffff7f52 R11: ffff8eba7f600000 R12: ffff8eba0004c720\n[ 190.272049] R13: ffff8eba00223a00 R14: 0000000000000008 R15: ffff8eba067a8000\n[ 190.272053] FS: 00007f1bd64752c0(0000) GS:ffff8eba7f680000(0000) knlGS:0000000000000000\n[ 190.272057] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 190.272061] CR2: 00007f1bd6662590 CR3: 000000010291e001 CR4: 0000000000370ef0\n[ 190.272070] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[ 190.272073] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n[ 190.272077] Call Trace:\n[ 190.272098] \u0026lt;TASK\u0026gt;\n[ 190.272189] ring_buffer_resize+0x2ab/0x460\n[ 190.272199] __tracing_resize_ring_buffer.part.0+0x23/0xa0\n[ 190.272206] tracing_resize_ring_buffer+0x65/0x90\n[ 190.272216] tracing_entries_write+0x74/0xc0\n[ 190.272225] vfs_write+0xf5/0x420\n[ 190.272248] ksys_write+0x67/0xe0\n[ 190.272256] do_syscall_64+0x82/0x170\n[ 190.272363] entry_SYSCALL_64_after_hwframe+0x76/0x7e\n[ 190.272373] RIP: 0033:0x7f1bd657d263\n[ 190.272381] Code: [...]\n[ 190.272385] RSP: 002b:00007ffe72b643f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001\n[ 190.272391] RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007f1bd657d263\n[ 190.272395] RDX: 0000000000000002 RSI: 0000555a6eb538e0 RDI: 0000000000000001\n[ 190.272398] RBP: 0000555a6eb538e0 R08: 000000000000000a R09: 0000000000000000\n[ 190.272401] R10: 0000555a6eb55190 R11: 0000000000000246 R12: 00007f1bd6662500\n[ 190.272404] R13: 0000000000000002 R14: 00007f1bd6667c00 R15: 0000000000000002\n[ 190.272412] \u0026lt;/TASK\u0026gt;\n[ 190.272414] ---[ end trace 0000000000000000 ]---\r\n\r\nNote that ring_buffer_resize() calls rb_check_pages() only if the parent\ntrace_buffer has recording disabled. Recent commit d78ab792705c\n(\u0026quot;tracing: Stop current tracer when resizing buffer\u0026quot;) causes that it is\nnow always the case which makes it more likely to experience this issue.\r\n\r\nThe window to hit this race is nonetheless very small. To help\nreproducing it, one can add a delay loop in rb_get_reader_page():\r\n\r\n ret = rb_head_page_replace(reader, cpu_buffer-\u0026gt;reader_page);\n if (!ret)\n \tgoto spin;\n for (unsigned i = 0; i \u0026lt; 1U \u0026lt;\u0026lt; 26; i++) /* inserted delay loop */\n \t__asm__ __volatile__ (\u0026quot;\u0026quot; : : : \u0026quot;memory\u0026quot;);\n rb_list_head(reader-\u0026gt;list.next)-\u0026gt;prev = \u0026amp;cpu_buffer-\u0026gt;reader_page-\u0026gt;list;\r\n\r\n.. \n---truncated---(CVE-2024-38601)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nALSA: core: Fix NULL module pointer assignment at card init\r\n\r\nThe commit 81033c6b584b (\u0026quot;ALSA: core: Warn on empty module\u0026quot;)\nintroduced a WARN_ON() for a NULL module pointer passed at snd_card\nobject creation, and it also wraps the code around it with \u0026apos;#ifdef\nMODULE\u0026apos;. This works in most cases, but the devils are always in\ndetails. \u0026quot;MODULE\u0026quot; is defined when the target code (i.e. the sound\ncore) is built as a module; but this doesn\u0026apos;t mean that the caller is\nalso built-in or not. Namely, when only the sound core is built-in\n(CONFIG_SND=y) while the driver is a module (CONFIG_SND_USB_AUDIO=m),\nthe passed module pointer is ignored even if it\u0026apos;s non-NULL, and\ncard-\u0026gt;module remains as NULL. This would result in the missing module\nreference up/down at the device open/close, leading to a race with the\ncode execution after the module removal.\r\n\r\nFor addressing the bug, move the assignment of card-\u0026gt;module again out\nof ifdef. The WARN_ON() is still wrapped with ifdef because the\nmodule can be really NULL when all sound drivers are built-in.\r\n\r\nNote that we keep \u0026apos;ifdef MODULE\u0026apos; for WARN_ON(), otherwise it would\nlead to a false-positive NULL module check. Admittedly it won\u0026apos;t catch\nperfectly, i.e. no check is performed when CONFIG_SND=y. But, it\u0026apos;s no\nreal problem as it\u0026apos;s only for debugging, and the condition is pretty\nrare.(CVE-2024-38605)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nf2fs: multidev: fix to recognize valid zero block address\r\n\r\nAs reported by Yi Zhang in mailing list [1], kernel warning was catched\nduring zbd/010 test as below:\r\n\r\n./check zbd/010\nzbd/010 (test gap zone support with F2FS) [failed]\n runtime ... 3.752s\n something found in dmesg:\n [ 4378.146781] run blktests zbd/010 at 2024-02-18 11:31:13\n [ 4378.192349] null_blk: module loaded\n [ 4378.209860] null_blk: disk nullb0 created\n [ 4378.413285] scsi_debug:sdebug_driver_probe: scsi_debug: trim\npoll_queues to 0. poll_q/nr_hw = (0/1)\n [ 4378.422334] scsi host15: scsi_debug: version 0191 [20210520]\n dev_size_mb=1024, opts=0x0, submit_queues=1, statistics=0\n [ 4378.434922] scsi 15:0:0:0: Direct-Access-ZBC Linux\nscsi_debug 0191 PQ: 0 ANSI: 7\n [ 4378.443343] scsi 15:0:0:0: Power-on or device reset occurred\n [ 4378.449371] sd 15:0:0:0: Attached scsi generic sg5 type 20\n [ 4378.449418] sd 15:0:0:0: [sdf] Host-managed zoned block device\n ...\n (See \u0026apos;/mnt/tests/gitlab.com/api/v4/projects/19168116/repository/archive.zip/storage/blktests/blk/blktests/results/nodev/zbd/010.dmesg\u0026apos;\r\n\r\nWARNING: CPU: 22 PID: 44011 at fs/iomap/iter.c:51\nCPU: 22 PID: 44011 Comm: fio Not tainted 6.8.0-rc3+ #1\nRIP: 0010:iomap_iter+0x32b/0x350\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __iomap_dio_rw+0x1df/0x830\n f2fs_file_read_iter+0x156/0x3d0 [f2fs]\n aio_read+0x138/0x210\n io_submit_one+0x188/0x8c0\n __x64_sys_io_submit+0x8c/0x1a0\n do_syscall_64+0x86/0x170\n entry_SYSCALL_64_after_hwframe+0x6e/0x76\r\n\r\nShinichiro Kawasaki helps to analyse this issue and proposes a potential\nfixing patch in [2].\r\n\r\nQuoted from reply of Shinichiro Kawasaki:\r\n\r\n\u0026quot;I confirmed that the trigger commit is dbf8e63f48af as Yi reported. I took a\nlook in the commit, but it looks fine to me. So I thought the cause is not\nin the commit diff.\r\n\r\nI found the WARN is printed when the f2fs is set up with multiple devices,\nand read requests are mapped to the very first block of the second device in the\ndirect read path. In this case, f2fs_map_blocks() and f2fs_map_blocks_cached()\nmodify map-\u0026gt;m_pblk as the physical block address from each block device. It\nbecomes zero when it is mapped to the first block of the device. However,\nf2fs_iomap_begin() assumes that map-\u0026gt;m_pblk is the physical block address of the\nwhole f2fs, across the all block devices. It compares map-\u0026gt;m_pblk against\nNULL_ADDR == 0, then go into the unexpected branch and sets the invalid\niomap-\u0026gt;length. The WARN catches the invalid iomap-\u0026gt;length.\r\n\r\nThis WARN is printed even for non-zoned block devices, by following steps.\r\n\r\n - Create two (non-zoned) null_blk devices memory backed with 128MB size each:\n nullb0 and nullb1.\n # mkfs.f2fs /dev/nullb0 -c /dev/nullb1\n # mount -t f2fs /dev/nullb0 \u0026quot;${mount_dir}\u0026quot;\n # dd if=/dev/zero of=\u0026quot;${mount_dir}/test.dat\u0026quot; bs=1M count=192\n # dd if=\u0026quot;${mount_dir}/test.dat\u0026quot; of=/dev/null bs=1M count=192 iflag=direct\r\n\r\n...\u0026quot;\r\n\r\nSo, the root cause of this issue is: when multi-devices feature is on,\nf2fs_map_blocks() may return zero blkaddr in non-primary device, which is\na verified valid block address, however, f2fs_iomap_begin() treats it as\nan invalid block address, and then it triggers the warning in iomap\nframework code.\r\n\r\nFinally, as discussed, we decide to use a more simple and direct way that\nchecking (map.m_flags \u0026amp; F2FS_MAP_MAPPED) condition instead of\n(map.m_pblk != NULL_ADDR) to fix this issue.\r\n\r\nThanks a lot for the effort of Yi Zhang and Shinichiro Kawasaki on this\nissue.\r\n\r\n[1] https://lore.kernel.org/linux-f2fs-devel/CAHj4cs-kfojYC9i0G73PRkYzcxCTex=-vugRFeP40g_URGvnfQ@mail.gmail.com/\n[2] https://lore.kernel.org/linux-f2fs-devel/gngdj77k4picagsfdtiaa7gpgnup6fsgwzsltx6milmhegmjff@iax2n4wvrqye/(CVE-2024-38636)",
"id": "OESA-2024-1766",
"modified": "2026-08-06T11:07:14Z",
"published": "2024-06-28T11:07:14Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1766"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-36477"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-36883"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-36898"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-36902"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-36903"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-36905"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-36919"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-36928"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-36968"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-36974"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-36975"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-36977"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-36978"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38538"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38541"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38549"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38587"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38596"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38601"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38605"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38636"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "kernel security update",
"upstream": [
"CVE-2024-36477",
"CVE-2024-36883",
"CVE-2024-36898",
"CVE-2024-36902",
"CVE-2024-36903",
"CVE-2024-36905",
"CVE-2024-36919",
"CVE-2024-36928",
"CVE-2024-36968",
"CVE-2024-36974",
"CVE-2024-36975",
"CVE-2024-36977",
"CVE-2024-36978",
"CVE-2024-38538",
"CVE-2024-38541",
"CVE-2024-38549",
"CVE-2024-38587",
"CVE-2024-38596",
"CVE-2024-38601",
"CVE-2024-38605",
"CVE-2024-38636"
]
}
OESA-2024-1860 (CVE-2021-47391)
Vulnerability from osv_openeuler – Published: 2024-07-19 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:
RDMA/cma: Ensure rdma_addr_cancel() happens before issuing more requests
The FSM can run in a circle allowing rdma_resolve_ip() to be called twice on the same id_priv. While this cannot happen without going through the work, it violates the invariant that the same address resolution background request cannot be active twice.
CPU 1 CPU 2
rdma_resolve_addr(): RDMA_CM_IDLE -> RDMA_CM_ADDR_QUERY rdma_resolve_ip(addr_handler) #1
process_one_req(): for #1
addr_handler():
RDMA_CM_ADDR_QUERY -> RDMA_CM_ADDR_BOUND
mutex_unlock(&id_priv->handler_mutex);
[.. handler still running ..]
rdma_resolve_addr(): RDMA_CM_ADDR_BOUND -> RDMA_CM_ADDR_QUERY rdma_resolve_ip(addr_handler) !! two requests are now on the req_list
rdma_destroy_id(): destroy_id_handler_unlock(): _destroy_id(): cma_cancel_operation(): rdma_addr_cancel()
// process_one_req() self removes it
spin_lock_bh(&lock);
cancel_delayed_work(&req->work);
if (!list_empty(&req->list)) == true
! rdma_addr_cancel() returns after process_on_req #1 is done
kfree(id_priv)
process_one_req(): for #2
addr_handler():
mutex_lock(&id_priv->handler_mutex);
!! Use after free on id_priv
rdma_addr_cancel() expects there to be one req on the list and only cancels the first one. The self-removal behavior of the work only happens after the handler has returned. This yields a situations where the req_list can have two reqs for the same "handle" but rdma_addr_cancel() only cancels the first one.
The second req remains active beyond rdma_destroy_id() and will use-after-free id_priv once it inevitably triggers.
Fix this by remembering if the id_priv has called rdma_resolve_ip() and always cancel before calling it again. This ensures the req_list never gets more than one item in it and doesn't cost anything in the normal flow that never uses this strange error path.(CVE-2021-47391)
In the Linux kernel, the following vulnerability has been resolved:
net/smc: Forward wakeup to smc socket waitqueue after fallback
When we replace TCP with SMC and a fallback occurs, there may be some socket waitqueue entries remaining in smc socket->wq, such as eppoll_entries inserted by userspace applications.
After the fallback, data flows over TCP/IP and only clcsocket->wq will be woken up. Applications can't be notified by the entries which were inserted in smc socket->wq before fallback. So we need a mechanism to wake up smc socket->wq at the same time if some entries remaining in it.
The current workaround is to transfer the entries from smc socket->wq to clcsock->wq during the fallback. But this may cause a crash like this:
general protection fault, probably for non-canonical address 0xdead000000000100: 0000 [#1] PREEMPT SMP PTI CPU: 3 PID: 0 Comm: swapper/3 Kdump: loaded Tainted: G E 5.16.0+ #107 RIP: 0010:__wake_up_common+0x65/0x170 Call Trace: <IRQ> __wake_up_common_lock+0x7a/0xc0 sock_def_readable+0x3c/0x70 tcp_data_queue+0x4a7/0xc40 tcp_rcv_established+0x32f/0x660 ? sk_filter_trim_cap+0xcb/0x2e0 tcp_v4_do_rcv+0x10b/0x260 tcp_v4_rcv+0xd2a/0xde0 ip_protocol_deliver_rcu+0x3b/0x1d0 ip_local_deliver_finish+0x54/0x60 ip_local_deliver+0x6a/0x110 ? tcp_v4_early_demux+0xa2/0x140 ? tcp_v4_early_demux+0x10d/0x140 ip_sublist_rcv_finish+0x49/0x60 ip_sublist_rcv+0x19d/0x230 ip_list_rcv+0x13e/0x170 __netif_receive_skb_list_core+0x1c2/0x240 netif_receive_skb_list_internal+0x1e6/0x320 napi_complete_done+0x11d/0x190 mlx5e_napi_poll+0x163/0x6b0 [mlx5_core] __napi_poll+0x3c/0x1b0 net_rx_action+0x27c/0x300 __do_softirq+0x114/0x2d2 irq_exit_rcu+0xb4/0xe0 common_interrupt+0xba/0xe0 </IRQ> <TASK>
The crash is caused by privately transferring waitqueue entries from smc socket->wq to clcsock->wq. The owners of these entries, such as epoll, have no idea that the entries have been transferred to a different socket wait queue and still use original waitqueue spinlock (smc socket->wq.wait.lock) to make the entries operation exclusive, but it doesn't work. The operations to the entries, such as removing from the waitqueue (now is clcsock->wq after fallback), may cause a crash when clcsock waitqueue is being iterated over at the moment.
This patch tries to fix this by no longer transferring wait queue entries privately, but introducing own implementations of clcsock's callback functions in fallback situation. The callback functions will forward the wakeup to smc socket->wq if clcsock->wq is actually woken up and smc socket->wq has remaining entries.(CVE-2022-48721)
In the Linux kernel, the following vulnerability has been resolved:
ice: Do not use WQ_MEM_RECLAIM flag for workqueue
When both ice and the irdma driver are loaded, a warning in check_flush_dependency is being triggered. This is due to ice driver workqueue being allocated with the WQ_MEM_RECLAIM flag and the irdma one is not.
According to kernel documentation, this flag should be set if the workqueue will be involved in the kernel's memory reclamation flow. Since it is not, there is no need for the ice driver's WQ to have this flag set so remove it.
Example trace:
[ +0.000004] workqueue: WQ_MEM_RECLAIM ice:ice_service_task [ice] is flushing !WQ_MEM_RECLAIM infiniband:0x0 [ +0.000139] WARNING: CPU: 0 PID: 728 at kernel/workqueue.c:2632 check_flush_dependency+0x178/0x1a0 [ +0.000011] Modules linked in: bonding tls xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 nft_compat nft_cha in_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink bridge stp llc rfkill vfat fat intel_rapl_msr intel rapl_common isst_if_common skx_edac nfit libnvdimm x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct1 0dif_pclmul crc32_pclmul ghash_clmulni_intel rapl intel_cstate rpcrdma sunrpc rdma_ucm ib_srpt ib_isert iscsi_target_mod target core_mod ib_iser libiscsi scsi_transport_iscsi rdma_cm ib_cm iw_cm iTCO_wdt iTCO_vendor_support ipmi_ssif irdma mei_me ib_uverbs ib_core intel_uncore joydev pcspkr i2c_i801 acpi_ipmi mei lpc_ich i2c_smbus intel_pch_thermal ioatdma ipmi_si acpi_power_meter acpi_pad xfs libcrc32c sd_mod t10_pi crc64_rocksoft crc64 sg ahci ixgbe libahci ice i40e igb crc32c_intel mdio i2c_algo_bit liba ta dca wmi dm_mirror dm_region_hash dm_log dm_mod ipmi_devintf ipmi_msghandler fuse [ +0.000161] [last unloaded: bonding] [ +0.000006] CPU: 0 PID: 728 Comm: kworker/0:2 Tainted: G S 6.2.0-rc2_next-queue-13jan-00458-gc20aabd57164 #1 [ +0.000006] Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS SE5C620.86B.02.01.0010.010620200716 01/06/2020 [ +0.000003] Workqueue: ice ice_service_task [ice] [ +0.000127] RIP: 0010:check_flush_dependency+0x178/0x1a0 [ +0.000005] Code: 89 8e 02 01 e8 49 3d 40 00 49 8b 55 18 48 8d 8d d0 00 00 00 48 8d b3 d0 00 00 00 4d 89 e0 48 c7 c7 e0 3b 08 9f e8 bb d3 07 01 <0f> 0b e9 be fe ff ff 80 3d 24 89 8e 02 00 0f 85 6b ff ff ff e9 06 [ +0.000004] RSP: 0018:ffff88810a39f990 EFLAGS: 00010282 [ +0.000005] RAX: 0000000000000000 RBX: ffff888141bc2400 RCX: 0000000000000000 [ +0.000004] RDX: 0000000000000001 RSI: dffffc0000000000 RDI: ffffffffa1213a80 [ +0.000003] RBP: ffff888194bf3400 R08: ffffed117b306112 R09: ffffed117b306112 [ +0.000003] R10: ffff888bd983088b R11: ffffed117b306111 R12: 0000000000000000 [ +0.000003] R13: ffff888111f84d00 R14: ffff88810a3943ac R15: ffff888194bf3400 [ +0.000004] FS: 0000000000000000(0000) GS:ffff888bd9800000(0000) knlGS:0000000000000000 [ +0.000003] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ +0.000003] CR2: 000056035b208b60 CR3: 000000017795e005 CR4: 00000000007706f0 [ +0.000003] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ +0.000003] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ +0.000002] PKRU: 55555554 [ +0.000003] Call Trace: [ +0.000002] <TASK> [ +0.000003] __flush_workqueue+0x203/0x840 [ +0.000006] ? mutex_unlock+0x84/0xd0 [ +0.000008] ? __pfx_mutex_unlock+0x10/0x10 [ +0.000004] ? __pfx___flush_workqueue+0x10/0x10 [ +0.000006] ? mutex_lock+0xa3/0xf0 [ +0.000005] ib_cache_cleanup_one+0x39/0x190 [ib_core] [ +0.000174] __ib_unregister_device+0x84/0xf0 [ib_core] [ +0.000094] ib_unregister_device+0x25/0x30 [ib_core] [ +0.000093] irdma_ib_unregister_device+0x97/0xc0 [irdma] [ +0.000064] ? __pfx_irdma_ib_unregister_device+0x10/0x10 [irdma] [ +0.000059] ? up_write+0x5c/0x90 [ +0.000005] irdma_remove+0x36/0x90 [irdma] [ +0.000062] auxiliary_bus_remove+0x32/0x50 [ +0.000007] device_r ---truncated---(CVE-2023-52743)
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix slab out of bounds write in smb_inherit_dacl()
slab out-of-bounds write is caused by that offsets is bigger than pntsd allocation size. This patch add the check to validate 3 offsets using allocation size.(CVE-2023-52755)
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: btusb: Add date->evt_skb is NULL check
fix crash because of null pointers
[ 6104.969662] BUG: kernel NULL pointer dereference, address: 00000000000000c8 [ 6104.969667] #PF: supervisor read access in kernel mode [ 6104.969668] #PF: error_code(0x0000) - not-present page [ 6104.969670] PGD 0 P4D 0 [ 6104.969673] Oops: 0000 [#1] SMP NOPTI [ 6104.969684] RIP: 0010:btusb_mtk_hci_wmt_sync+0x144/0x220 [btusb] [ 6104.969688] RSP: 0018:ffffb8d681533d48 EFLAGS: 00010246 [ 6104.969689] RAX: 0000000000000000 RBX: ffff8ad560bb2000 RCX: 0000000000000006 [ 6104.969691] RDX: 0000000000000000 RSI: ffffb8d681533d08 RDI: 0000000000000000 [ 6104.969692] RBP: ffffb8d681533d70 R08: 0000000000000001 R09: 0000000000000001 [ 6104.969694] R10: 0000000000000001 R11: 00000000fa83b2da R12: ffff8ad461d1d7c0 [ 6104.969695] R13: 0000000000000000 R14: ffff8ad459618c18 R15: ffffb8d681533d90 [ 6104.969697] FS: 00007f5a1cab9d40(0000) GS:ffff8ad578200000(0000) knlGS:00000 [ 6104.969699] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 6104.969700] CR2: 00000000000000c8 CR3: 000000018620c001 CR4: 0000000000760ef0 [ 6104.969701] PKRU: 55555554 [ 6104.969702] Call Trace: [ 6104.969708] btusb_mtk_shutdown+0x44/0x80 [btusb] [ 6104.969732] hci_dev_do_close+0x470/0x5c0 [bluetooth] [ 6104.969748] hci_rfkill_set_block+0x56/0xa0 [bluetooth] [ 6104.969753] rfkill_set_block+0x92/0x160 [ 6104.969755] rfkill_fop_write+0x136/0x1e0 [ 6104.969759] __vfs_write+0x18/0x40 [ 6104.969761] vfs_write+0xdf/0x1c0 [ 6104.969763] ksys_write+0xb1/0xe0 [ 6104.969765] __x64_sys_write+0x1a/0x20 [ 6104.969769] do_syscall_64+0x51/0x180 [ 6104.969771] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 6104.969773] RIP: 0033:0x7f5a21f18fef [ 6104.9] RSP: 002b:00007ffeefe39010 EFLAGS: 00000293 ORIG_RAX: 0000000000000001 [ 6104.969780] RAX: ffffffffffffffda RBX: 000055c10a7560a0 RCX: 00007f5a21f18fef [ 6104.969781] RDX: 0000000000000008 RSI: 00007ffeefe39060 RDI: 0000000000000012 [ 6104.969782] RBP: 00007ffeefe39060 R08: 0000000000000000 R09: 0000000000000017 [ 6104.969784] R10: 00007ffeefe38d97 R11: 0000000000000293 R12: 0000000000000002 [ 6104.969785] R13: 00007ffeefe39220 R14: 00007ffeefe391a0 R15: 000055c10a72acf0(CVE-2023-52833)
In the Linux kernel, the following vulnerability has been resolved:
f2fs: compress: fix to cover {reserve,release}_compress_blocks() w/ cp_rwsem lock
It needs to cover {reserve,release}_compress_blocks() w/ cp_rwsem lock to avoid racing with checkpoint, otherwise, filesystem metadata including blkaddr in dnode, inode fields and .total_valid_block_count may be corrupted after SPO case.(CVE-2024-34027)
In the Linux kernel, the following vulnerability has been resolved:
null_blk: fix null-ptr-dereference while configuring 'power' and 'submit_queues'
Writing 'power' and 'submit_queues' concurrently will trigger kernel panic:
Test script:
modprobe null_blk nr_devices=0 mkdir -p /sys/kernel/config/nullb/nullb0 while true; do echo 1 > submit_queues; echo 4 > submit_queues; done & while true; do echo 1 > power; echo 0 > power; done
Test result:
BUG: kernel NULL pointer dereference, address: 0000000000000148 Oops: 0000 [#1] PREEMPT SMP RIP: 0010:__lock_acquire+0x41d/0x28f0 Call Trace: <TASK> lock_acquire+0x121/0x450 down_write+0x5f/0x1d0 simple_recursive_removal+0x12f/0x5c0 blk_mq_debugfs_unregister_hctxs+0x7c/0x100 blk_mq_update_nr_hw_queues+0x4a3/0x720 nullb_update_nr_hw_queues+0x71/0xf0 [null_blk] nullb_device_submit_queues_store+0x79/0xf0 [null_blk] configfs_write_iter+0x119/0x1e0 vfs_write+0x326/0x730 ksys_write+0x74/0x150
This is because del_gendisk() can concurrent with blk_mq_update_nr_hw_queues():
nullb_device_power_store nullb_apply_submit_queues null_del_dev del_gendisk nullb_update_nr_hw_queues if (!dev->nullb) // still set while gendisk is deleted return 0 blk_mq_update_nr_hw_queues dev->nullb = NULL
Fix this problem by resuing the global mutex to protect nullb_device_power_store() and nullb_update_nr_hw_queues() from configfs.(CVE-2024-36478)
In the Linux kernel, the following vulnerability has been resolved:
bnxt_re: avoid shift undefined behavior in bnxt_qplib_alloc_init_hwq
Undefined behavior is triggered when bnxt_qplib_alloc_init_hwq is called with hwq_attr->aux_depth != 0 and hwq_attr->aux_stride == 0. In that case, "roundup_pow_of_two(hwq_attr->aux_stride)" gets called. roundup_pow_of_two is documented as undefined for 0.
Fix it in the one caller that had this combination.
The undefined behavior was detected by UBSAN: UBSAN: shift-out-of-bounds in ./include/linux/log2.h:57:13 shift exponent 64 is too large for 64-bit type 'long unsigned int' CPU: 24 PID: 1075 Comm: (udev-worker) Not tainted 6.9.0-rc6+ #4 Hardware name: Abacus electric, s.r.o. - servis@abacus.cz Super Server/H12SSW-iN, BIOS 2.7 10/25/2023 Call Trace: <TASK> dump_stack_lvl+0x5d/0x80 ubsan_epilogue+0x5/0x30 __ubsan_handle_shift_out_of_bounds.cold+0x61/0xec __roundup_pow_of_two+0x25/0x35 [bnxt_re] bnxt_qplib_alloc_init_hwq+0xa1/0x470 [bnxt_re] bnxt_qplib_create_qp+0x19e/0x840 [bnxt_re] bnxt_re_create_qp+0x9b1/0xcd0 [bnxt_re] ? srso_alias_return_thunk+0x5/0xfbef5 ? srso_alias_return_thunk+0x5/0xfbef5 ? __kmalloc+0x1b6/0x4f0 ? create_qp.part.0+0x128/0x1c0 [ib_core] ? __pfx_bnxt_re_create_qp+0x10/0x10 [bnxt_re] create_qp.part.0+0x128/0x1c0 [ib_core] ib_create_qp_kernel+0x50/0xd0 [ib_core] create_mad_qp+0x8e/0xe0 [ib_core] ? __pfx_qp_event_handler+0x10/0x10 [ib_core] ib_mad_init_device+0x2be/0x680 [ib_core] add_client_context+0x10d/0x1a0 [ib_core] enable_device_and_get+0xe0/0x1d0 [ib_core] ib_register_device+0x53c/0x630 [ib_core] ? srso_alias_return_thunk+0x5/0xfbef5 bnxt_re_probe+0xbd8/0xe50 [bnxt_re] ? __pfx_bnxt_re_probe+0x10/0x10 [bnxt_re] auxiliary_bus_probe+0x49/0x80 ? driver_sysfs_add+0x57/0xc0 really_probe+0xde/0x340 ? pm_runtime_barrier+0x54/0x90 ? __pfx___driver_attach+0x10/0x10 __driver_probe_device+0x78/0x110 driver_probe_device+0x1f/0xa0 __driver_attach+0xba/0x1c0 bus_for_each_dev+0x8f/0xe0 bus_add_driver+0x146/0x220 driver_register+0x72/0xd0 __auxiliary_driver_register+0x6e/0xd0 ? __pfx_bnxt_re_mod_init+0x10/0x10 [bnxt_re] bnxt_re_mod_init+0x3e/0xff0 [bnxt_re] ? __pfx_bnxt_re_mod_init+0x10/0x10 [bnxt_re] do_one_initcall+0x5b/0x310 do_init_module+0x90/0x250 init_module_from_file+0x86/0xc0 idempotent_init_module+0x121/0x2b0 __x64_sys_finit_module+0x5e/0xb0 do_syscall_64+0x82/0x160 ? srso_alias_return_thunk+0x5/0xfbef5 ? syscall_exit_to_user_mode_prepare+0x149/0x170 ? srso_alias_return_thunk+0x5/0xfbef5 ? syscall_exit_to_user_mode+0x75/0x230 ? srso_alias_return_thunk+0x5/0xfbef5 ? do_syscall_64+0x8e/0x160 ? srso_alias_return_thunk+0x5/0xfbef5 ? __count_memcg_events+0x69/0x100 ? srso_alias_return_thunk+0x5/0xfbef5 ? count_memcg_events.constprop.0+0x1a/0x30 ? srso_alias_return_thunk+0x5/0xfbef5 ? handle_mm_fault+0x1f0/0x300 ? srso_alias_return_thunk+0x5/0xfbef5 ? do_user_addr_fault+0x34e/0x640 ? srso_alias_return_thunk+0x5/0xfbef5 ? srso_alias_return_thunk+0x5/0xfbef5 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7f4e5132821d Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 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 8b 0d e3 db 0c 00 f7 d8 64 89 01 48 RSP: 002b:00007ffca9c906a8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139 RAX: ffffffffffffffda RBX: 0000563ec8a8f130 RCX: 00007f4e5132821d RDX: 0000000000000000 RSI: 00007f4e518fa07d RDI: 000000000000003b RBP: 00007ffca9c90760 R08: 00007f4e513f6b20 R09: 00007ffca9c906f0 R10: 0000563ec8a8faa0 R11: 0000000000000246 R12: 00007f4e518fa07d R13: 0000000000020000 R14: 0000563ec8409e90 R15: 0000563ec8a8fa60 </TASK> ---[ end trace ]---(CVE-2024-38540)
In the Linux kernel, the following vulnerability has been resolved:
net: openvswitch: fix overwriting ct original tuple for ICMPv6
OVS_PACKET_CMD_EXECUTE has 3 main attributes: - OVS_PACKET_ATTR_KEY - Packet metadata in a netlink format. - OVS_PACKET_ATTR_PACKET - Binary packet content. - OVS_PACKET_ATTR_ACTIONS - Actions to execute on the packet.
OVS_PACKET_ATTR_KEY is parsed first to populate sw_flow_key structure with the metadata like conntrack state, input port, recirculation id, etc. Then the packet itself gets parsed to populate the rest of the keys from the packet headers.
Whenever the packet parsing code starts parsing the ICMPv6 header, it first zeroes out fields in the key corresponding to Neighbor Discovery information even if it is not an ND packet.
It is an 'ipv6.nd' field. However, the 'ipv6' is a union that shares the space between 'nd' and 'ct_orig' that holds the original tuple conntrack metadata parsed from the OVS_PACKET_ATTR_KEY.
ND packets should not normally have conntrack state, so it's fine to share the space, but normal ICMPv6 Echo packets or maybe other types of ICMPv6 can have the state attached and it should not be overwritten.
The issue results in all but the last 4 bytes of the destination address being wiped from the original conntrack tuple leading to incorrect packet matching and potentially executing wrong actions in case this packet recirculates within the datapath or goes back to userspace.
ND fields should not be accessed in non-ND packets, so not clearing them should be fine. Executing memset() only for actual ND packets to avoid the issue.
Initializing the whole thing before parsing is needed because ND packet may not contain all the options.
The issue only affects the OVS_PACKET_CMD_EXECUTE path and doesn't affect packets entering OVS datapath from network interfaces, because in this case CT metadata is populated from skb after the packet is already parsed.(CVE-2024-38558)
In the Linux kernel, the following vulnerability has been resolved:
gfs2: Fix potential glock use-after-free on unmount
When a DLM lockspace is released and there ares still locks in that lockspace, DLM will unlock those locks automatically. Commit fb6791d100d1b started exploiting this behavior to speed up filesystem unmount: gfs2 would simply free glocks it didn't want to unlock and then release the lockspace. This didn't take the bast callbacks for asynchronous lock contention notifications into account, which remain active until until a lock is unlocked or its lockspace is released.
To prevent those callbacks from accessing deallocated objects, put the glocks that should not be unlocked on the sd_dead_glocks list, release the lockspace, and only then free those glocks.
As an additional measure, ignore unexpected ast and bast callbacks if the receiving glock is dead.(CVE-2024-38570)
In the Linux kernel, the following vulnerability has been resolved:
r8169: Fix possible ring buffer corruption on fragmented Tx packets.
An issue was found on the RTL8125b when transmitting small fragmented packets, whereby invalid entries were inserted into the transmit ring buffer, subsequently leading to calls to dma_unmap_single() with a null address.
This was caused by rtl8169_start_xmit() not noticing changes to nr_frags which may occur when small packets are padded (to work around hardware quirks) in rtl8169_tso_csum_v2().
To fix this, postpone inspecting nr_frags until after any padding has been applied.(CVE-2024-38586)
In the Linux kernel, the following vulnerability has been resolved:
md: fix resync softlockup when bitmap size is less than array size
Is is reported that for dm-raid10, lvextend + lvchange --syncaction will trigger following softlockup:
kernel:watchdog: BUG: soft lockup - CPU#3 stuck for 26s! [mdX_resync:6976] CPU: 7 PID: 3588 Comm: mdX_resync Kdump: loaded Not tainted 6.9.0-rc4-next-20240419 #1 RIP: 0010:_raw_spin_unlock_irq+0x13/0x30 Call Trace: <TASK> md_bitmap_start_sync+0x6b/0xf0 raid10_sync_request+0x25c/0x1b40 [raid10] md_do_sync+0x64b/0x1020 md_thread+0xa7/0x170 kthread+0xcf/0x100 ret_from_fork+0x30/0x50 ret_from_fork_asm+0x1a/0x30
And the detailed process is as follows:
md_do_sync j = mddev->resync_min while (j < max_sectors) sectors = raid10_sync_request(mddev, j, &skipped) if (!md_bitmap_start_sync(..., &sync_blocks)) // md_bitmap_start_sync set sync_blocks to 0 return sync_blocks + sectors_skippe; // sectors = 0; j += sectors; // j never change
Root cause is that commit 301867b1c168 ("md/raid10: check slab-out-of-bounds in md_bitmap_get_counter") return early from md_bitmap_get_counter(), without setting returned blocks.
Fix this problem by always set returned blocks from md_bitmap_get_counter"(), as it used to be.
Noted that this patch just fix the softlockup problem in kernel, the case that bitmap size doesn't match array size still need to be fixed.(CVE-2024-38598)
In the Linux kernel, the following vulnerability has been resolved:
ALSA: core: Fix NULL module pointer assignment at card init
The commit 81033c6b584b ("ALSA: core: Warn on empty module") introduced a WARN_ON() for a NULL module pointer passed at snd_card object creation, and it also wraps the code around it with '#ifdef MODULE'. This works in most cases, but the devils are always in details. "MODULE" is defined when the target code (i.e. the sound core) is built as a module; but this doesn't mean that the caller is also built-in or not. Namely, when only the sound core is built-in (CONFIG_SND=y) while the driver is a module (CONFIG_SND_USB_AUDIO=m), the passed module pointer is ignored even if it's non-NULL, and card->module remains as NULL. This would result in the missing module reference up/down at the device open/close, leading to a race with the code execution after the module removal.
For addressing the bug, move the assignment of card->module again out of ifdef. The WARN_ON() is still wrapped with ifdef because the module can be really NULL when all sound drivers are built-in.
Note that we keep 'ifdef MODULE' for WARN_ON(), otherwise it would lead to a false-positive NULL module check. Admittedly it won't catch perfectly, i.e. no check is performed when CONFIG_SND=y. But, it's no real problem as it's only for debugging, and the condition is pretty rare.(CVE-2024-38605)
In the Linux kernel, the following vulnerability has been resolved:
cpufreq: exit() callback is optional
The exit() callback is optional and shouldn't be called without checking a valid pointer first.
Also, we must clear freq_table pointer even if the exit() callback isn't present.(CVE-2024-38615)
In the Linux kernel, the following vulnerability has been resolved:
vfio/pci: fix potential memory leak in vfio_intx_enable()
If vfio_irq_ctx_alloc() failed will lead to 'name' memory leak.(CVE-2024-38632)
In the Linux kernel, the following vulnerability has been resolved:
kdb: Fix buffer overflow during tab-complete
Currently, when the user attempts symbol completion with the Tab key, kdb will use strncpy() to insert the completed symbol into the command buffer. Unfortunately it passes the size of the source buffer rather than the destination to strncpy() with predictably horrible results. Most obviously if the command buffer is already full but cp, the cursor position, is in the middle of the buffer, then we will write past the end of the supplied buffer.
Fix this by replacing the dubious strncpy() calls with memmove()/memcpy() calls plus explicit boundary checks to make sure we have enough space before we start moving characters around.(CVE-2024-39480)
In the Linux kernel, the following vulnerability has been resolved:
bonding: Fix out-of-bounds read in bond_option_arp_ip_targets_set()
In function bond_option_arp_ip_targets_set(), if newval->string is an empty string, newval->string+1 will point to the byte after the string, causing an out-of-bound read.
BUG: KASAN: slab-out-of-bounds in strlen+0x7d/0xa0 lib/string.c:418 Read of size 1 at addr ffff8881119c4781 by task syz-executor665/8107 CPU: 1 PID: 8107 Comm: syz-executor665 Not tainted 6.7.0-rc7 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd9/0x150 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:364 [inline] print_report+0xc1/0x5e0 mm/kasan/report.c:475 kasan_report+0xbe/0xf0 mm/kasan/report.c:588 strlen+0x7d/0xa0 lib/string.c:418 __fortify_strlen include/linux/fortify-string.h:210 [inline] in4_pton+0xa3/0x3f0 net/core/utils.c:130 bond_option_arp_ip_targets_set+0xc2/0x910 drivers/net/bonding/bond_options.c:1201 __bond_opt_set+0x2a4/0x1030 drivers/net/bonding/bond_options.c:767 __bond_opt_set_notify+0x48/0x150 drivers/net/bonding/bond_options.c:792 bond_opt_tryset_rtnl+0xda/0x160 drivers/net/bonding/bond_options.c:817 bonding_sysfs_store_option+0xa1/0x120 drivers/net/bonding/bond_sysfs.c:156 dev_attr_store+0x54/0x80 drivers/base/core.c:2366 sysfs_kf_write+0x114/0x170 fs/sysfs/file.c:136 kernfs_fop_write_iter+0x337/0x500 fs/kernfs/file.c:334 call_write_iter include/linux/fs.h:2020 [inline] new_sync_write fs/read_write.c:491 [inline] vfs_write+0x96a/0xd80 fs/read_write.c:584 ksys_write+0x122/0x250 fs/read_write.c:637 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x40/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b ---[ end trace ]---
Fix it by adding a check of string length before using it.(CVE-2024-39487)
In the Linux kernel, the following vulnerability has been resolved:
arm64: asm-bug: Add .align 2 to the end of __BUG_ENTRY
When CONFIG_DEBUG_BUGVERBOSE=n, we fail to add necessary padding bytes to bug_table entries, and as a result the last entry in a bug table will be ignored, potentially leading to an unexpected panic(). All prior entries in the table will be handled correctly.
The arm64 ABI requires that struct fields of up to 8 bytes are naturally-aligned, with padding added within a struct such that struct are suitably aligned within arrays.
When CONFIG_DEBUG_BUGVERPOSE=y, the layout of a bug_entry is:
struct bug_entry {
signed int bug_addr_disp; // 4 bytes
signed int file_disp; // 4 bytes
unsigned short line; // 2 bytes
unsigned short flags; // 2 bytes
}
... with 12 bytes total, requiring 4-byte alignment.
When CONFIG_DEBUG_BUGVERBOSE=n, the layout of a bug_entry is:
struct bug_entry {
signed int bug_addr_disp; // 4 bytes
unsigned short flags; // 2 bytes
< implicit padding > // 2 bytes
}
... with 8 bytes total, with 6 bytes of data and 2 bytes of trailing padding, requiring 4-byte alginment.
When we create a bug_entry in assembly, we align the start of the entry to 4 bytes, which implicitly handles padding for any prior entries. However, we do not align the end of the entry, and so when CONFIG_DEBUG_BUGVERBOSE=n, the final entry lacks the trailing padding bytes.
For the main kernel image this is not a problem as find_bug() doesn't depend on the trailing padding bytes when searching for entries:
for (bug = __start___bug_table; bug < __stop___bug_table; ++bug)
if (bugaddr == bug_addr(bug))
return bug;
However for modules, module_bug_finalize() depends on the trailing bytes when calculating the number of entries:
mod->num_bugs = sechdrs[i].sh_size / sizeof(struct bug_entry);
... and as the last bug_entry lacks the necessary padding bytes, this entry will not be counted, e.g. in the case of a single entry:
sechdrs[i].sh_size == 6
sizeof(struct bug_entry) == 8;
sechdrs[i].sh_size / sizeof(struct bug_entry) == 0;
Consequently module_find_bug() will miss the last bug_entry when it does:
for (i = 0; i < mod->num_bugs; ++i, ++bug)
if (bugaddr == bug_addr(bug))
goto out;
... which can lead to a kenrel panic due to an unhandled bug.
This can be demonstrated with the following module:
static int __init buginit(void)
{
WARN(1, "hello\n");
return 0;
}
static void __exit bugexit(void)
{
}
module_init(buginit);
module_exit(bugexit);
MODULE_LICENSE("GPL");
... which will trigger a kernel panic when loaded:
------------[ cut here ]------------
hello
Unexpected kernel BRK exception at EL1
Internal error: BRK handler: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in: hello(O+)
CPU: 0 PID: 50 Comm: insmod Tainted: G O 6.9.1 #8
Hardware name: linux,dummy-virt (DT)
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : buginit+0x18/0x1000 [hello]
lr : buginit+0x18/0x1000 [hello]
sp : ffff800080533ae0
x29: ffff800080533ae0 x28: 0000000000000000 x27: 0000000000000000
x26: ffffaba8c4e70510 x25: ffff800080533c30 x24: ffffaba8c4a28a58
x23: 0000000000000000 x22: 0000000000000000 x21: ffff3947c0eab3c0
x20: ffffaba8c4e3f000 x19: ffffaba846464000 x18: 0000000000000006
x17: 0000000000000000 x16: ffffaba8c2492834 x15: 0720072007200720
x14: 0720072007200720 x13: ffffaba8c49b27c8 x12: 0000000000000312
x11: 0000000000000106 x10: ffffaba8c4a0a7c8 x9 : ffffaba8c49b27c8
x8 : 00000000ffffefff x7 : ffffaba8c4a0a7c8 x6 : 80000000fffff000
x5 : 0000000000000107 x4 : 0000000000000000 x3 : 0000000000000000
x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff3947c0eab3c0
Call trace:
buginit+0x18/0x1000 [hello]
do_one_initcall+0x80/0x1c8
do_init_module+0x60/0x218
load_module+0x1ba4/0x1d70
__do_sys_init_module+0x198/0x1d0
__arm64_sys_init_module+0x1c/0x28
invoke_syscall+0x48/0x114
el0_svc
---truncated---(CVE-2024-39488)
In the Linux kernel, the following vulnerability has been resolved:
ipv6: sr: fix memleak in seg6_hmac_init_algo
seg6_hmac_init_algo returns without cleaning up the previous allocations if one fails, so it's going to leak all that memory and the crypto tfms.
Update seg6_hmac_exit to only free the memory when allocated, so we can reuse the code directly.(CVE-2024-39489)
In the Linux kernel, the following vulnerability has been resolved:
sock_map: avoid race between sock_map_close and sk_psock_put
sk_psock_get will return NULL if the refcount of psock has gone to 0, which will happen when the last call of sk_psock_put is done. However, sk_psock_drop may not have finished yet, so the close callback will still point to sock_map_close despite psock being NULL.
This can be reproduced with a thread deleting an element from the sock map, while the second one creates a socket, adds it to the map and closes it.
That will trigger the WARN_ON_ONCE:
------------[ cut here ]------------ WARNING: CPU: 1 PID: 7220 at net/core/sock_map.c:1701 sock_map_close+0x2a2/0x2d0 net/core/sock_map.c:1701 Modules linked in: CPU: 1 PID: 7220 Comm: syz-executor380 Not tainted 6.9.0-syzkaller-07726-g3c999d1ae3c7 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024 RIP: 0010:sock_map_close+0x2a2/0x2d0 net/core/sock_map.c:1701 Code: df e8 92 29 88 f8 48 8b 1b 48 89 d8 48 c1 e8 03 42 80 3c 20 00 74 08 48 89 df e8 79 29 88 f8 4c 8b 23 eb 89 e8 4f 15 23 f8 90 <0f> 0b 90 48 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f 5d e9 13 26 3d 02 RSP: 0018:ffffc9000441fda8 EFLAGS: 00010293 RAX: ffffffff89731ae1 RBX: ffffffff94b87540 RCX: ffff888029470000 RDX: 0000000000000000 RSI: ffffffff8bcab5c0 RDI: ffffffff8c1faba0 RBP: 0000000000000000 R08: ffffffff92f9b61f R09: 1ffffffff25f36c3 R10: dffffc0000000000 R11: fffffbfff25f36c4 R12: ffffffff89731840 R13: ffff88804b587000 R14: ffff88804b587000 R15: ffffffff89731870 FS: 000055555e080380(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 00000000207d4000 CR4: 0000000000350ef0 Call Trace: <TASK> unix_release+0x87/0xc0 net/unix/af_unix.c:1048 __sock_release net/socket.c:659 [inline] sock_close+0xbe/0x240 net/socket.c:1421 __fput+0x42b/0x8a0 fs/file_table.c:422 __do_sys_close fs/open.c:1556 [inline] __se_sys_close fs/open.c:1541 [inline] __x64_sys_close+0x7f/0x110 fs/open.c:1541 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fb37d618070 Code: 00 00 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d4 e8 10 2c 00 00 80 3d 31 f0 07 00 00 74 17 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 48 c3 0f 1f 80 00 00 00 00 48 83 ec 18 89 7c RSP: 002b:00007ffcd4a525d8 EFLAGS: 00000202 ORIG_RAX: 0000000000000003 RAX: ffffffffffffffda RBX: 0000000000000005 RCX: 00007fb37d618070 RDX: 0000000000000010 RSI: 00000000200001c0 RDI: 0000000000000004 RBP: 0000000000000000 R08: 0000000100000000 R09: 0000000100000000 R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 </TASK>
Use sk_psock, which will only check that the pointer is not been set to NULL yet, which should only happen after the callbacks are restored. If, then, a reference can still be gotten, we may call sk_psock_stop and cancel psock->work.
As suggested by Paolo Abeni, reorder the condition so the control flow is less convoluted.
After that change, the reproducer does not trigger the WARN_ON_ONCE anymore.(CVE-2024-39500)
In the Linux kernel, the following vulnerability has been resolved:
mptcp: ensure snd_una is properly initialized on connect
This is strictly related to commit fb7a0d334894 ("mptcp: ensure snd_nxt is properly initialized on connect"). It turns out that syzkaller can trigger the retransmit after fallback and before processing any other incoming packet - so that snd_una is still left uninitialized.
Address the issue explicitly initializing snd_una together with snd_nxt and write_seq.(CVE-2024-40931)
In the Linux kernel, the following vulnerability has been resolved:
f2fs: remove clear SB_INLINECRYPT flag in default_options
In f2fs_remount, SB_INLINECRYPT flag will be clear and re-set. If create new file or open file during this gap, these files will not use inlinecrypt. Worse case, it may lead to data corruption if wrappedkey_v0 is enable.
Thread A: Thread B:
-f2fs_remount -f2fs_file_open or f2fs_new_inode -default_options <- clear SB_INLINECRYPT flag
-fscrypt_select_encryption_impl
-parse_options <- set SB_INLINECRYPT again(CVE-2024-40971)
| URL | Type | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"kernel-5.10.0-136.85.0.166.oe2203sp1.aarch64.rpm",
"kernel-debuginfo-5.10.0-136.85.0.166.oe2203sp1.aarch64.rpm",
"kernel-debugsource-5.10.0-136.85.0.166.oe2203sp1.aarch64.rpm",
"kernel-devel-5.10.0-136.85.0.166.oe2203sp1.aarch64.rpm",
"kernel-headers-5.10.0-136.85.0.166.oe2203sp1.aarch64.rpm",
"kernel-source-5.10.0-136.85.0.166.oe2203sp1.aarch64.rpm",
"kernel-tools-5.10.0-136.85.0.166.oe2203sp1.aarch64.rpm",
"kernel-tools-debuginfo-5.10.0-136.85.0.166.oe2203sp1.aarch64.rpm",
"kernel-tools-devel-5.10.0-136.85.0.166.oe2203sp1.aarch64.rpm",
"perf-5.10.0-136.85.0.166.oe2203sp1.aarch64.rpm",
"perf-debuginfo-5.10.0-136.85.0.166.oe2203sp1.aarch64.rpm",
"python3-perf-5.10.0-136.85.0.166.oe2203sp1.aarch64.rpm",
"python3-perf-debuginfo-5.10.0-136.85.0.166.oe2203sp1.aarch64.rpm"
],
"src": [
"kernel-5.10.0-136.85.0.166.oe2203sp1.src.rpm"
],
"x86_64": [
"kernel-5.10.0-136.85.0.166.oe2203sp1.x86_64.rpm",
"kernel-debuginfo-5.10.0-136.85.0.166.oe2203sp1.x86_64.rpm",
"kernel-debugsource-5.10.0-136.85.0.166.oe2203sp1.x86_64.rpm",
"kernel-devel-5.10.0-136.85.0.166.oe2203sp1.x86_64.rpm",
"kernel-headers-5.10.0-136.85.0.166.oe2203sp1.x86_64.rpm",
"kernel-source-5.10.0-136.85.0.166.oe2203sp1.x86_64.rpm",
"kernel-tools-5.10.0-136.85.0.166.oe2203sp1.x86_64.rpm",
"kernel-tools-debuginfo-5.10.0-136.85.0.166.oe2203sp1.x86_64.rpm",
"kernel-tools-devel-5.10.0-136.85.0.166.oe2203sp1.x86_64.rpm",
"perf-5.10.0-136.85.0.166.oe2203sp1.x86_64.rpm",
"perf-debuginfo-5.10.0-136.85.0.166.oe2203sp1.x86_64.rpm",
"python3-perf-5.10.0-136.85.0.166.oe2203sp1.x86_64.rpm",
"python3-perf-debuginfo-5.10.0-136.85.0.166.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.85.0.166.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:\r\n\r\nRDMA/cma: Ensure rdma_addr_cancel() happens before issuing more requests\r\n\r\nThe FSM can run in a circle allowing rdma_resolve_ip() to be called twice\non the same id_priv. While this cannot happen without going through the\nwork, it violates the invariant that the same address resolution\nbackground request cannot be active twice.\r\n\r\n CPU 1 CPU 2\r\n\r\nrdma_resolve_addr():\n RDMA_CM_IDLE -\u0026gt; RDMA_CM_ADDR_QUERY\n rdma_resolve_ip(addr_handler) #1\r\n\r\n\t\t\t process_one_req(): for #1\n addr_handler():\n RDMA_CM_ADDR_QUERY -\u0026gt; RDMA_CM_ADDR_BOUND\n mutex_unlock(\u0026amp;id_priv-\u0026gt;handler_mutex);\n [.. handler still running ..]\r\n\r\nrdma_resolve_addr():\n RDMA_CM_ADDR_BOUND -\u0026gt; RDMA_CM_ADDR_QUERY\n rdma_resolve_ip(addr_handler)\n !! two requests are now on the req_list\r\n\r\nrdma_destroy_id():\n destroy_id_handler_unlock():\n _destroy_id():\n cma_cancel_operation():\n rdma_addr_cancel()\r\n\r\n // process_one_req() self removes it\n\t\t spin_lock_bh(\u0026amp;lock);\n cancel_delayed_work(\u0026amp;req-\u0026gt;work);\n\t if (!list_empty(\u0026amp;req-\u0026gt;list)) == true\r\n\r\n ! rdma_addr_cancel() returns after process_on_req #1 is done\r\n\r\n kfree(id_priv)\r\n\r\n\t\t\t process_one_req(): for #2\n addr_handler():\n\t mutex_lock(\u0026amp;id_priv-\u0026gt;handler_mutex);\n !! Use after free on id_priv\r\n\r\nrdma_addr_cancel() expects there to be one req on the list and only\ncancels the first one. The self-removal behavior of the work only happens\nafter the handler has returned. This yields a situations where the\nreq_list can have two reqs for the same \u0026quot;handle\u0026quot; but rdma_addr_cancel()\nonly cancels the first one.\r\n\r\nThe second req remains active beyond rdma_destroy_id() and will\nuse-after-free id_priv once it inevitably triggers.\r\n\r\nFix this by remembering if the id_priv has called rdma_resolve_ip() and\nalways cancel before calling it again. This ensures the req_list never\ngets more than one item in it and doesn\u0026apos;t cost anything in the normal flow\nthat never uses this strange error path.(CVE-2021-47391)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/smc: Forward wakeup to smc socket waitqueue after fallback\r\n\r\nWhen we replace TCP with SMC and a fallback occurs, there may be\nsome socket waitqueue entries remaining in smc socket-\u0026gt;wq, such\nas eppoll_entries inserted by userspace applications.\r\n\r\nAfter the fallback, data flows over TCP/IP and only clcsocket-\u0026gt;wq\nwill be woken up. Applications can\u0026apos;t be notified by the entries\nwhich were inserted in smc socket-\u0026gt;wq before fallback. So we need\na mechanism to wake up smc socket-\u0026gt;wq at the same time if some\nentries remaining in it.\r\n\r\nThe current workaround is to transfer the entries from smc socket-\u0026gt;wq\nto clcsock-\u0026gt;wq during the fallback. But this may cause a crash\nlike this:\r\n\r\n general protection fault, probably for non-canonical address 0xdead000000000100: 0000 [#1] PREEMPT SMP PTI\n CPU: 3 PID: 0 Comm: swapper/3 Kdump: loaded Tainted: G E 5.16.0+ #107\n RIP: 0010:__wake_up_common+0x65/0x170\n Call Trace:\n \u0026lt;IRQ\u0026gt;\n __wake_up_common_lock+0x7a/0xc0\n sock_def_readable+0x3c/0x70\n tcp_data_queue+0x4a7/0xc40\n tcp_rcv_established+0x32f/0x660\n ? sk_filter_trim_cap+0xcb/0x2e0\n tcp_v4_do_rcv+0x10b/0x260\n tcp_v4_rcv+0xd2a/0xde0\n ip_protocol_deliver_rcu+0x3b/0x1d0\n ip_local_deliver_finish+0x54/0x60\n ip_local_deliver+0x6a/0x110\n ? tcp_v4_early_demux+0xa2/0x140\n ? tcp_v4_early_demux+0x10d/0x140\n ip_sublist_rcv_finish+0x49/0x60\n ip_sublist_rcv+0x19d/0x230\n ip_list_rcv+0x13e/0x170\n __netif_receive_skb_list_core+0x1c2/0x240\n netif_receive_skb_list_internal+0x1e6/0x320\n napi_complete_done+0x11d/0x190\n mlx5e_napi_poll+0x163/0x6b0 [mlx5_core]\n __napi_poll+0x3c/0x1b0\n net_rx_action+0x27c/0x300\n __do_softirq+0x114/0x2d2\n irq_exit_rcu+0xb4/0xe0\n common_interrupt+0xba/0xe0\n \u0026lt;/IRQ\u0026gt;\n \u0026lt;TASK\u0026gt;\r\n\r\nThe crash is caused by privately transferring waitqueue entries from\nsmc socket-\u0026gt;wq to clcsock-\u0026gt;wq. The owners of these entries, such as\nepoll, have no idea that the entries have been transferred to a\ndifferent socket wait queue and still use original waitqueue spinlock\n(smc socket-\u0026gt;wq.wait.lock) to make the entries operation exclusive,\nbut it doesn\u0026apos;t work. The operations to the entries, such as removing\nfrom the waitqueue (now is clcsock-\u0026gt;wq after fallback), may cause a\ncrash when clcsock waitqueue is being iterated over at the moment.\r\n\r\nThis patch tries to fix this by no longer transferring wait queue\nentries privately, but introducing own implementations of clcsock\u0026apos;s\ncallback functions in fallback situation. The callback functions will\nforward the wakeup to smc socket-\u0026gt;wq if clcsock-\u0026gt;wq is actually woken\nup and smc socket-\u0026gt;wq has remaining entries.(CVE-2022-48721)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nice: Do not use WQ_MEM_RECLAIM flag for workqueue\r\n\r\nWhen both ice and the irdma driver are loaded, a warning in\ncheck_flush_dependency is being triggered. This is due to ice driver\nworkqueue being allocated with the WQ_MEM_RECLAIM flag and the irdma one\nis not.\r\n\r\nAccording to kernel documentation, this flag should be set if the\nworkqueue will be involved in the kernel\u0026apos;s memory reclamation flow.\nSince it is not, there is no need for the ice driver\u0026apos;s WQ to have this\nflag set so remove it.\r\n\r\nExample trace:\r\n\r\n[ +0.000004] workqueue: WQ_MEM_RECLAIM ice:ice_service_task [ice] is flushing !WQ_MEM_RECLAIM infiniband:0x0\n[ +0.000139] WARNING: CPU: 0 PID: 728 at kernel/workqueue.c:2632 check_flush_dependency+0x178/0x1a0\n[ +0.000011] Modules linked in: bonding tls xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 nft_compat nft_cha\nin_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink bridge stp llc rfkill vfat fat intel_rapl_msr intel\n_rapl_common isst_if_common skx_edac nfit libnvdimm x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct1\n0dif_pclmul crc32_pclmul ghash_clmulni_intel rapl intel_cstate rpcrdma sunrpc rdma_ucm ib_srpt ib_isert iscsi_target_mod target_\ncore_mod ib_iser libiscsi scsi_transport_iscsi rdma_cm ib_cm iw_cm iTCO_wdt iTCO_vendor_support ipmi_ssif irdma mei_me ib_uverbs\nib_core intel_uncore joydev pcspkr i2c_i801 acpi_ipmi mei lpc_ich i2c_smbus intel_pch_thermal ioatdma ipmi_si acpi_power_meter\nacpi_pad xfs libcrc32c sd_mod t10_pi crc64_rocksoft crc64 sg ahci ixgbe libahci ice i40e igb crc32c_intel mdio i2c_algo_bit liba\nta dca wmi dm_mirror dm_region_hash dm_log dm_mod ipmi_devintf ipmi_msghandler fuse\n[ +0.000161] [last unloaded: bonding]\n[ +0.000006] CPU: 0 PID: 728 Comm: kworker/0:2 Tainted: G S 6.2.0-rc2_next-queue-13jan-00458-gc20aabd57164 #1\n[ +0.000006] Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS SE5C620.86B.02.01.0010.010620200716 01/06/2020\n[ +0.000003] Workqueue: ice ice_service_task [ice]\n[ +0.000127] RIP: 0010:check_flush_dependency+0x178/0x1a0\n[ +0.000005] Code: 89 8e 02 01 e8 49 3d 40 00 49 8b 55 18 48 8d 8d d0 00 00 00 48 8d b3 d0 00 00 00 4d 89 e0 48 c7 c7 e0 3b 08\n9f e8 bb d3 07 01 \u0026lt;0f\u0026gt; 0b e9 be fe ff ff 80 3d 24 89 8e 02 00 0f 85 6b ff ff ff e9 06\n[ +0.000004] RSP: 0018:ffff88810a39f990 EFLAGS: 00010282\n[ +0.000005] RAX: 0000000000000000 RBX: ffff888141bc2400 RCX: 0000000000000000\n[ +0.000004] RDX: 0000000000000001 RSI: dffffc0000000000 RDI: ffffffffa1213a80\n[ +0.000003] RBP: ffff888194bf3400 R08: ffffed117b306112 R09: ffffed117b306112\n[ +0.000003] R10: ffff888bd983088b R11: ffffed117b306111 R12: 0000000000000000\n[ +0.000003] R13: ffff888111f84d00 R14: ffff88810a3943ac R15: ffff888194bf3400\n[ +0.000004] FS: 0000000000000000(0000) GS:ffff888bd9800000(0000) knlGS:0000000000000000\n[ +0.000003] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ +0.000003] CR2: 000056035b208b60 CR3: 000000017795e005 CR4: 00000000007706f0\n[ +0.000003] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[ +0.000003] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n[ +0.000002] PKRU: 55555554\n[ +0.000003] Call Trace:\n[ +0.000002] \u0026lt;TASK\u0026gt;\n[ +0.000003] __flush_workqueue+0x203/0x840\n[ +0.000006] ? mutex_unlock+0x84/0xd0\n[ +0.000008] ? __pfx_mutex_unlock+0x10/0x10\n[ +0.000004] ? __pfx___flush_workqueue+0x10/0x10\n[ +0.000006] ? mutex_lock+0xa3/0xf0\n[ +0.000005] ib_cache_cleanup_one+0x39/0x190 [ib_core]\n[ +0.000174] __ib_unregister_device+0x84/0xf0 [ib_core]\n[ +0.000094] ib_unregister_device+0x25/0x30 [ib_core]\n[ +0.000093] irdma_ib_unregister_device+0x97/0xc0 [irdma]\n[ +0.000064] ? __pfx_irdma_ib_unregister_device+0x10/0x10 [irdma]\n[ +0.000059] ? up_write+0x5c/0x90\n[ +0.000005] irdma_remove+0x36/0x90 [irdma]\n[ +0.000062] auxiliary_bus_remove+0x32/0x50\n[ +0.000007] device_r\n---truncated---(CVE-2023-52743)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nksmbd: fix slab out of bounds write in smb_inherit_dacl()\r\n\r\nslab out-of-bounds write is caused by that offsets is bigger than pntsd\nallocation size. This patch add the check to validate 3 offsets using\nallocation size.(CVE-2023-52755)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nBluetooth: btusb: Add date-\u0026gt;evt_skb is NULL check\r\n\r\nfix crash because of null pointers\r\n\r\n[ 6104.969662] BUG: kernel NULL pointer dereference, address: 00000000000000c8\n[ 6104.969667] #PF: supervisor read access in kernel mode\n[ 6104.969668] #PF: error_code(0x0000) - not-present page\n[ 6104.969670] PGD 0 P4D 0\n[ 6104.969673] Oops: 0000 [#1] SMP NOPTI\n[ 6104.969684] RIP: 0010:btusb_mtk_hci_wmt_sync+0x144/0x220 [btusb]\n[ 6104.969688] RSP: 0018:ffffb8d681533d48 EFLAGS: 00010246\n[ 6104.969689] RAX: 0000000000000000 RBX: ffff8ad560bb2000 RCX: 0000000000000006\n[ 6104.969691] RDX: 0000000000000000 RSI: ffffb8d681533d08 RDI: 0000000000000000\n[ 6104.969692] RBP: ffffb8d681533d70 R08: 0000000000000001 R09: 0000000000000001\n[ 6104.969694] R10: 0000000000000001 R11: 00000000fa83b2da R12: ffff8ad461d1d7c0\n[ 6104.969695] R13: 0000000000000000 R14: ffff8ad459618c18 R15: ffffb8d681533d90\n[ 6104.969697] FS: 00007f5a1cab9d40(0000) GS:ffff8ad578200000(0000) knlGS:00000\n[ 6104.969699] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 6104.969700] CR2: 00000000000000c8 CR3: 000000018620c001 CR4: 0000000000760ef0\n[ 6104.969701] PKRU: 55555554\n[ 6104.969702] Call Trace:\n[ 6104.969708] btusb_mtk_shutdown+0x44/0x80 [btusb]\n[ 6104.969732] hci_dev_do_close+0x470/0x5c0 [bluetooth]\n[ 6104.969748] hci_rfkill_set_block+0x56/0xa0 [bluetooth]\n[ 6104.969753] rfkill_set_block+0x92/0x160\n[ 6104.969755] rfkill_fop_write+0x136/0x1e0\n[ 6104.969759] __vfs_write+0x18/0x40\n[ 6104.969761] vfs_write+0xdf/0x1c0\n[ 6104.969763] ksys_write+0xb1/0xe0\n[ 6104.969765] __x64_sys_write+0x1a/0x20\n[ 6104.969769] do_syscall_64+0x51/0x180\n[ 6104.969771] entry_SYSCALL_64_after_hwframe+0x44/0xa9\n[ 6104.969773] RIP: 0033:0x7f5a21f18fef\n[ 6104.9] RSP: 002b:00007ffeefe39010 EFLAGS: 00000293 ORIG_RAX: 0000000000000001\n[ 6104.969780] RAX: ffffffffffffffda RBX: 000055c10a7560a0 RCX: 00007f5a21f18fef\n[ 6104.969781] RDX: 0000000000000008 RSI: 00007ffeefe39060 RDI: 0000000000000012\n[ 6104.969782] RBP: 00007ffeefe39060 R08: 0000000000000000 R09: 0000000000000017\n[ 6104.969784] R10: 00007ffeefe38d97 R11: 0000000000000293 R12: 0000000000000002\n[ 6104.969785] R13: 00007ffeefe39220 R14: 00007ffeefe391a0 R15: 000055c10a72acf0(CVE-2023-52833)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nf2fs: compress: fix to cover {reserve,release}_compress_blocks() w/ cp_rwsem lock\r\n\r\nIt needs to cover {reserve,release}_compress_blocks() w/ cp_rwsem lock\nto avoid racing with checkpoint, otherwise, filesystem metadata including\nblkaddr in dnode, inode fields and .total_valid_block_count may be\ncorrupted after SPO case.(CVE-2024-34027)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnull_blk: fix null-ptr-dereference while configuring \u0026apos;power\u0026apos; and \u0026apos;submit_queues\u0026apos;\r\n\r\nWriting \u0026apos;power\u0026apos; and \u0026apos;submit_queues\u0026apos; concurrently will trigger kernel\npanic:\r\n\r\nTest script:\r\n\r\nmodprobe null_blk nr_devices=0\nmkdir -p /sys/kernel/config/nullb/nullb0\nwhile true; do echo 1 \u0026gt; submit_queues; echo 4 \u0026gt; submit_queues; done \u0026amp;\nwhile true; do echo 1 \u0026gt; power; echo 0 \u0026gt; power; done\r\n\r\nTest result:\r\n\r\nBUG: kernel NULL pointer dereference, address: 0000000000000148\nOops: 0000 [#1] PREEMPT SMP\nRIP: 0010:__lock_acquire+0x41d/0x28f0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n lock_acquire+0x121/0x450\n down_write+0x5f/0x1d0\n simple_recursive_removal+0x12f/0x5c0\n blk_mq_debugfs_unregister_hctxs+0x7c/0x100\n blk_mq_update_nr_hw_queues+0x4a3/0x720\n nullb_update_nr_hw_queues+0x71/0xf0 [null_blk]\n nullb_device_submit_queues_store+0x79/0xf0 [null_blk]\n configfs_write_iter+0x119/0x1e0\n vfs_write+0x326/0x730\n ksys_write+0x74/0x150\r\n\r\nThis is because del_gendisk() can concurrent with\nblk_mq_update_nr_hw_queues():\r\n\r\nnullb_device_power_store\tnullb_apply_submit_queues\n null_del_dev\n del_gendisk\n\t\t\t\t nullb_update_nr_hw_queues\n\t\t\t\t if (!dev-\u0026gt;nullb)\n\t\t\t\t // still set while gendisk is deleted\n\t\t\t\t return 0\n\t\t\t\t blk_mq_update_nr_hw_queues\n dev-\u0026gt;nullb = NULL\r\n\r\nFix this problem by resuing the global mutex to protect\nnullb_device_power_store() and nullb_update_nr_hw_queues() from configfs.(CVE-2024-36478)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbnxt_re: avoid shift undefined behavior in bnxt_qplib_alloc_init_hwq\r\n\r\nUndefined behavior is triggered when bnxt_qplib_alloc_init_hwq is called\nwith hwq_attr-\u0026gt;aux_depth != 0 and hwq_attr-\u0026gt;aux_stride == 0.\nIn that case, \u0026quot;roundup_pow_of_two(hwq_attr-\u0026gt;aux_stride)\u0026quot; gets called.\nroundup_pow_of_two is documented as undefined for 0.\r\n\r\nFix it in the one caller that had this combination.\r\n\r\nThe undefined behavior was detected by UBSAN:\n UBSAN: shift-out-of-bounds in ./include/linux/log2.h:57:13\n shift exponent 64 is too large for 64-bit type \u0026apos;long unsigned int\u0026apos;\n CPU: 24 PID: 1075 Comm: (udev-worker) Not tainted 6.9.0-rc6+ #4\n Hardware name: Abacus electric, s.r.o. - servis@abacus.cz Super Server/H12SSW-iN, BIOS 2.7 10/25/2023\n Call Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x5d/0x80\n ubsan_epilogue+0x5/0x30\n __ubsan_handle_shift_out_of_bounds.cold+0x61/0xec\n __roundup_pow_of_two+0x25/0x35 [bnxt_re]\n bnxt_qplib_alloc_init_hwq+0xa1/0x470 [bnxt_re]\n bnxt_qplib_create_qp+0x19e/0x840 [bnxt_re]\n bnxt_re_create_qp+0x9b1/0xcd0 [bnxt_re]\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? __kmalloc+0x1b6/0x4f0\n ? create_qp.part.0+0x128/0x1c0 [ib_core]\n ? __pfx_bnxt_re_create_qp+0x10/0x10 [bnxt_re]\n create_qp.part.0+0x128/0x1c0 [ib_core]\n ib_create_qp_kernel+0x50/0xd0 [ib_core]\n create_mad_qp+0x8e/0xe0 [ib_core]\n ? __pfx_qp_event_handler+0x10/0x10 [ib_core]\n ib_mad_init_device+0x2be/0x680 [ib_core]\n add_client_context+0x10d/0x1a0 [ib_core]\n enable_device_and_get+0xe0/0x1d0 [ib_core]\n ib_register_device+0x53c/0x630 [ib_core]\n ? srso_alias_return_thunk+0x5/0xfbef5\n bnxt_re_probe+0xbd8/0xe50 [bnxt_re]\n ? __pfx_bnxt_re_probe+0x10/0x10 [bnxt_re]\n auxiliary_bus_probe+0x49/0x80\n ? driver_sysfs_add+0x57/0xc0\n really_probe+0xde/0x340\n ? pm_runtime_barrier+0x54/0x90\n ? __pfx___driver_attach+0x10/0x10\n __driver_probe_device+0x78/0x110\n driver_probe_device+0x1f/0xa0\n __driver_attach+0xba/0x1c0\n bus_for_each_dev+0x8f/0xe0\n bus_add_driver+0x146/0x220\n driver_register+0x72/0xd0\n __auxiliary_driver_register+0x6e/0xd0\n ? __pfx_bnxt_re_mod_init+0x10/0x10 [bnxt_re]\n bnxt_re_mod_init+0x3e/0xff0 [bnxt_re]\n ? __pfx_bnxt_re_mod_init+0x10/0x10 [bnxt_re]\n do_one_initcall+0x5b/0x310\n do_init_module+0x90/0x250\n init_module_from_file+0x86/0xc0\n idempotent_init_module+0x121/0x2b0\n __x64_sys_finit_module+0x5e/0xb0\n do_syscall_64+0x82/0x160\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? syscall_exit_to_user_mode_prepare+0x149/0x170\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? syscall_exit_to_user_mode+0x75/0x230\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? do_syscall_64+0x8e/0x160\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? __count_memcg_events+0x69/0x100\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? count_memcg_events.constprop.0+0x1a/0x30\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? handle_mm_fault+0x1f0/0x300\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? do_user_addr_fault+0x34e/0x640\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? srso_alias_return_thunk+0x5/0xfbef5\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n RIP: 0033:0x7f4e5132821d\n Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 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 8b 0d e3 db 0c 00 f7 d8 64 89 01 48\n RSP: 002b:00007ffca9c906a8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139\n RAX: ffffffffffffffda RBX: 0000563ec8a8f130 RCX: 00007f4e5132821d\n RDX: 0000000000000000 RSI: 00007f4e518fa07d RDI: 000000000000003b\n RBP: 00007ffca9c90760 R08: 00007f4e513f6b20 R09: 00007ffca9c906f0\n R10: 0000563ec8a8faa0 R11: 0000000000000246 R12: 00007f4e518fa07d\n R13: 0000000000020000 R14: 0000563ec8409e90 R15: 0000563ec8a8fa60\n \u0026lt;/TASK\u0026gt;\n ---[ end trace ]---(CVE-2024-38540)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: openvswitch: fix overwriting ct original tuple for ICMPv6\r\n\r\nOVS_PACKET_CMD_EXECUTE has 3 main attributes:\n - OVS_PACKET_ATTR_KEY - Packet metadata in a netlink format.\n - OVS_PACKET_ATTR_PACKET - Binary packet content.\n - OVS_PACKET_ATTR_ACTIONS - Actions to execute on the packet.\r\n\r\nOVS_PACKET_ATTR_KEY is parsed first to populate sw_flow_key structure\nwith the metadata like conntrack state, input port, recirculation id,\netc. Then the packet itself gets parsed to populate the rest of the\nkeys from the packet headers.\r\n\r\nWhenever the packet parsing code starts parsing the ICMPv6 header, it\nfirst zeroes out fields in the key corresponding to Neighbor Discovery\ninformation even if it is not an ND packet.\r\n\r\nIt is an \u0026apos;ipv6.nd\u0026apos; field. However, the \u0026apos;ipv6\u0026apos; is a union that shares\nthe space between \u0026apos;nd\u0026apos; and \u0026apos;ct_orig\u0026apos; that holds the original tuple\nconntrack metadata parsed from the OVS_PACKET_ATTR_KEY.\r\n\r\nND packets should not normally have conntrack state, so it\u0026apos;s fine to\nshare the space, but normal ICMPv6 Echo packets or maybe other types of\nICMPv6 can have the state attached and it should not be overwritten.\r\n\r\nThe issue results in all but the last 4 bytes of the destination\naddress being wiped from the original conntrack tuple leading to\nincorrect packet matching and potentially executing wrong actions\nin case this packet recirculates within the datapath or goes back\nto userspace.\r\n\r\nND fields should not be accessed in non-ND packets, so not clearing\nthem should be fine. Executing memset() only for actual ND packets to\navoid the issue.\r\n\r\nInitializing the whole thing before parsing is needed because ND packet\nmay not contain all the options.\r\n\r\nThe issue only affects the OVS_PACKET_CMD_EXECUTE path and doesn\u0026apos;t\naffect packets entering OVS datapath from network interfaces, because\nin this case CT metadata is populated from skb after the packet is\nalready parsed.(CVE-2024-38558)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ngfs2: Fix potential glock use-after-free on unmount\r\n\r\nWhen a DLM lockspace is released and there ares still locks in that\nlockspace, DLM will unlock those locks automatically. Commit\nfb6791d100d1b started exploiting this behavior to speed up filesystem\nunmount: gfs2 would simply free glocks it didn\u0026apos;t want to unlock and then\nrelease the lockspace. This didn\u0026apos;t take the bast callbacks for\nasynchronous lock contention notifications into account, which remain\nactive until until a lock is unlocked or its lockspace is released.\r\n\r\nTo prevent those callbacks from accessing deallocated objects, put the\nglocks that should not be unlocked on the sd_dead_glocks list, release\nthe lockspace, and only then free those glocks.\r\n\r\nAs an additional measure, ignore unexpected ast and bast callbacks if\nthe receiving glock is dead.(CVE-2024-38570)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nr8169: Fix possible ring buffer corruption on fragmented Tx packets.\r\n\r\nAn issue was found on the RTL8125b when transmitting small fragmented\npackets, whereby invalid entries were inserted into the transmit ring\nbuffer, subsequently leading to calls to dma_unmap_single() with a null\naddress.\r\n\r\nThis was caused by rtl8169_start_xmit() not noticing changes to nr_frags\nwhich may occur when small packets are padded (to work around hardware\nquirks) in rtl8169_tso_csum_v2().\r\n\r\nTo fix this, postpone inspecting nr_frags until after any padding has been\napplied.(CVE-2024-38586)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmd: fix resync softlockup when bitmap size is less than array size\r\n\r\nIs is reported that for dm-raid10, lvextend + lvchange --syncaction will\ntrigger following softlockup:\r\n\r\nkernel:watchdog: BUG: soft lockup - CPU#3 stuck for 26s! [mdX_resync:6976]\nCPU: 7 PID: 3588 Comm: mdX_resync Kdump: loaded Not tainted 6.9.0-rc4-next-20240419 #1\nRIP: 0010:_raw_spin_unlock_irq+0x13/0x30\nCall Trace:\n \u0026lt;TASK\u0026gt;\n md_bitmap_start_sync+0x6b/0xf0\n raid10_sync_request+0x25c/0x1b40 [raid10]\n md_do_sync+0x64b/0x1020\n md_thread+0xa7/0x170\n kthread+0xcf/0x100\n ret_from_fork+0x30/0x50\n ret_from_fork_asm+0x1a/0x30\r\n\r\nAnd the detailed process is as follows:\r\n\r\nmd_do_sync\n j = mddev-\u0026gt;resync_min\n while (j \u0026lt; max_sectors)\n sectors = raid10_sync_request(mddev, j, \u0026amp;skipped)\n if (!md_bitmap_start_sync(..., \u0026amp;sync_blocks))\n // md_bitmap_start_sync set sync_blocks to 0\n return sync_blocks + sectors_skippe;\n // sectors = 0;\n j += sectors;\n // j never change\r\n\r\nRoot cause is that commit 301867b1c168 (\u0026quot;md/raid10: check\nslab-out-of-bounds in md_bitmap_get_counter\u0026quot;) return early from\nmd_bitmap_get_counter(), without setting returned blocks.\r\n\r\nFix this problem by always set returned blocks from\nmd_bitmap_get_counter\u0026quot;(), as it used to be.\r\n\r\nNoted that this patch just fix the softlockup problem in kernel, the\ncase that bitmap size doesn\u0026apos;t match array size still need to be fixed.(CVE-2024-38598)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nALSA: core: Fix NULL module pointer assignment at card init\r\n\r\nThe commit 81033c6b584b (\u0026quot;ALSA: core: Warn on empty module\u0026quot;)\nintroduced a WARN_ON() for a NULL module pointer passed at snd_card\nobject creation, and it also wraps the code around it with \u0026apos;#ifdef\nMODULE\u0026apos;. This works in most cases, but the devils are always in\ndetails. \u0026quot;MODULE\u0026quot; is defined when the target code (i.e. the sound\ncore) is built as a module; but this doesn\u0026apos;t mean that the caller is\nalso built-in or not. Namely, when only the sound core is built-in\n(CONFIG_SND=y) while the driver is a module (CONFIG_SND_USB_AUDIO=m),\nthe passed module pointer is ignored even if it\u0026apos;s non-NULL, and\ncard-\u0026gt;module remains as NULL. This would result in the missing module\nreference up/down at the device open/close, leading to a race with the\ncode execution after the module removal.\r\n\r\nFor addressing the bug, move the assignment of card-\u0026gt;module again out\nof ifdef. The WARN_ON() is still wrapped with ifdef because the\nmodule can be really NULL when all sound drivers are built-in.\r\n\r\nNote that we keep \u0026apos;ifdef MODULE\u0026apos; for WARN_ON(), otherwise it would\nlead to a false-positive NULL module check. Admittedly it won\u0026apos;t catch\nperfectly, i.e. no check is performed when CONFIG_SND=y. But, it\u0026apos;s no\nreal problem as it\u0026apos;s only for debugging, and the condition is pretty\nrare.(CVE-2024-38605)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncpufreq: exit() callback is optional\r\n\r\nThe exit() callback is optional and shouldn\u0026apos;t be called without checking\na valid pointer first.\r\n\r\nAlso, we must clear freq_table pointer even if the exit() callback isn\u0026apos;t\npresent.(CVE-2024-38615)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nvfio/pci: fix potential memory leak in vfio_intx_enable()\r\n\r\nIf vfio_irq_ctx_alloc() failed will lead to \u0026apos;name\u0026apos; memory leak.(CVE-2024-38632)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nkdb: Fix buffer overflow during tab-complete\r\n\r\nCurrently, when the user attempts symbol completion with the Tab key, kdb\nwill use strncpy() to insert the completed symbol into the command buffer.\nUnfortunately it passes the size of the source buffer rather than the\ndestination to strncpy() with predictably horrible results. Most obviously\nif the command buffer is already full but cp, the cursor position, is in\nthe middle of the buffer, then we will write past the end of the supplied\nbuffer.\r\n\r\nFix this by replacing the dubious strncpy() calls with memmove()/memcpy()\ncalls plus explicit boundary checks to make sure we have enough space\nbefore we start moving characters around.(CVE-2024-39480)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbonding: Fix out-of-bounds read in bond_option_arp_ip_targets_set()\r\n\r\nIn function bond_option_arp_ip_targets_set(), if newval-\u0026gt;string is an\nempty string, newval-\u0026gt;string+1 will point to the byte after the\nstring, causing an out-of-bound read.\r\n\r\nBUG: KASAN: slab-out-of-bounds in strlen+0x7d/0xa0 lib/string.c:418\nRead of size 1 at addr ffff8881119c4781 by task syz-executor665/8107\nCPU: 1 PID: 8107 Comm: syz-executor665 Not tainted 6.7.0-rc7 #1\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __dump_stack lib/dump_stack.c:88 [inline]\n dump_stack_lvl+0xd9/0x150 lib/dump_stack.c:106\n print_address_description mm/kasan/report.c:364 [inline]\n print_report+0xc1/0x5e0 mm/kasan/report.c:475\n kasan_report+0xbe/0xf0 mm/kasan/report.c:588\n strlen+0x7d/0xa0 lib/string.c:418\n __fortify_strlen include/linux/fortify-string.h:210 [inline]\n in4_pton+0xa3/0x3f0 net/core/utils.c:130\n bond_option_arp_ip_targets_set+0xc2/0x910\ndrivers/net/bonding/bond_options.c:1201\n __bond_opt_set+0x2a4/0x1030 drivers/net/bonding/bond_options.c:767\n __bond_opt_set_notify+0x48/0x150 drivers/net/bonding/bond_options.c:792\n bond_opt_tryset_rtnl+0xda/0x160 drivers/net/bonding/bond_options.c:817\n bonding_sysfs_store_option+0xa1/0x120 drivers/net/bonding/bond_sysfs.c:156\n dev_attr_store+0x54/0x80 drivers/base/core.c:2366\n sysfs_kf_write+0x114/0x170 fs/sysfs/file.c:136\n kernfs_fop_write_iter+0x337/0x500 fs/kernfs/file.c:334\n call_write_iter include/linux/fs.h:2020 [inline]\n new_sync_write fs/read_write.c:491 [inline]\n vfs_write+0x96a/0xd80 fs/read_write.c:584\n ksys_write+0x122/0x250 fs/read_write.c:637\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0x40/0x110 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x63/0x6b\n---[ end trace ]---\r\n\r\nFix it by adding a check of string length before using it.(CVE-2024-39487)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\narm64: asm-bug: Add .align 2 to the end of __BUG_ENTRY\r\n\r\nWhen CONFIG_DEBUG_BUGVERBOSE=n, we fail to add necessary padding bytes\nto bug_table entries, and as a result the last entry in a bug table will\nbe ignored, potentially leading to an unexpected panic(). All prior\nentries in the table will be handled correctly.\r\n\r\nThe arm64 ABI requires that struct fields of up to 8 bytes are\nnaturally-aligned, with padding added within a struct such that struct\nare suitably aligned within arrays.\r\n\r\nWhen CONFIG_DEBUG_BUGVERPOSE=y, the layout of a bug_entry is:\r\n\r\n\tstruct bug_entry {\n\t\tsigned int bug_addr_disp;\t// 4 bytes\n\t\tsigned int file_disp;\t// 4 bytes\n\t\tunsigned short line;\t\t// 2 bytes\n\t\tunsigned short flags;\t\t// 2 bytes\n\t}\r\n\r\n... with 12 bytes total, requiring 4-byte alignment.\r\n\r\nWhen CONFIG_DEBUG_BUGVERBOSE=n, the layout of a bug_entry is:\r\n\r\n\tstruct bug_entry {\n\t\tsigned int bug_addr_disp;\t// 4 bytes\n\t\tunsigned short flags;\t\t// 2 bytes\n\t\t\u0026lt; implicit padding \u0026gt;\t\t// 2 bytes\n\t}\r\n\r\n... with 8 bytes total, with 6 bytes of data and 2 bytes of trailing\npadding, requiring 4-byte alginment.\r\n\r\nWhen we create a bug_entry in assembly, we align the start of the entry\nto 4 bytes, which implicitly handles padding for any prior entries.\nHowever, we do not align the end of the entry, and so when\nCONFIG_DEBUG_BUGVERBOSE=n, the final entry lacks the trailing padding\nbytes.\r\n\r\nFor the main kernel image this is not a problem as find_bug() doesn\u0026apos;t\ndepend on the trailing padding bytes when searching for entries:\r\n\r\n\tfor (bug = __start___bug_table; bug \u0026lt; __stop___bug_table; ++bug)\n\t\tif (bugaddr == bug_addr(bug))\n\t\t\treturn bug;\r\n\r\nHowever for modules, module_bug_finalize() depends on the trailing\nbytes when calculating the number of entries:\r\n\r\n\tmod-\u0026gt;num_bugs = sechdrs[i].sh_size / sizeof(struct bug_entry);\r\n\r\n... and as the last bug_entry lacks the necessary padding bytes, this entry\nwill not be counted, e.g. in the case of a single entry:\r\n\r\n\tsechdrs[i].sh_size == 6\n\tsizeof(struct bug_entry) == 8;\r\n\r\n\tsechdrs[i].sh_size / sizeof(struct bug_entry) == 0;\r\n\r\nConsequently module_find_bug() will miss the last bug_entry when it does:\r\n\r\n\tfor (i = 0; i \u0026lt; mod-\u0026gt;num_bugs; ++i, ++bug)\n\t\tif (bugaddr == bug_addr(bug))\n\t\t\tgoto out;\r\n\r\n... which can lead to a kenrel panic due to an unhandled bug.\r\n\r\nThis can be demonstrated with the following module:\r\n\r\n\tstatic int __init buginit(void)\n\t{\n\t\tWARN(1, \u0026quot;hello\\n\u0026quot;);\n\t\treturn 0;\n\t}\r\n\r\n\tstatic void __exit bugexit(void)\n\t{\n\t}\r\n\r\n\tmodule_init(buginit);\n\tmodule_exit(bugexit);\n\tMODULE_LICENSE(\u0026quot;GPL\u0026quot;);\r\n\r\n... which will trigger a kernel panic when loaded:\r\n\r\n\t------------[ cut here ]------------\n\thello\n\tUnexpected kernel BRK exception at EL1\n\tInternal error: BRK handler: 00000000f2000800 [#1] PREEMPT SMP\n\tModules linked in: hello(O+)\n\tCPU: 0 PID: 50 Comm: insmod Tainted: G O 6.9.1 #8\n\tHardware name: linux,dummy-virt (DT)\n\tpstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n\tpc : buginit+0x18/0x1000 [hello]\n\tlr : buginit+0x18/0x1000 [hello]\n\tsp : ffff800080533ae0\n\tx29: ffff800080533ae0 x28: 0000000000000000 x27: 0000000000000000\n\tx26: ffffaba8c4e70510 x25: ffff800080533c30 x24: ffffaba8c4a28a58\n\tx23: 0000000000000000 x22: 0000000000000000 x21: ffff3947c0eab3c0\n\tx20: ffffaba8c4e3f000 x19: ffffaba846464000 x18: 0000000000000006\n\tx17: 0000000000000000 x16: ffffaba8c2492834 x15: 0720072007200720\n\tx14: 0720072007200720 x13: ffffaba8c49b27c8 x12: 0000000000000312\n\tx11: 0000000000000106 x10: ffffaba8c4a0a7c8 x9 : ffffaba8c49b27c8\n\tx8 : 00000000ffffefff x7 : ffffaba8c4a0a7c8 x6 : 80000000fffff000\n\tx5 : 0000000000000107 x4 : 0000000000000000 x3 : 0000000000000000\n\tx2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff3947c0eab3c0\n\tCall trace:\n\t buginit+0x18/0x1000 [hello]\n\t do_one_initcall+0x80/0x1c8\n\t do_init_module+0x60/0x218\n\t load_module+0x1ba4/0x1d70\n\t __do_sys_init_module+0x198/0x1d0\n\t __arm64_sys_init_module+0x1c/0x28\n\t invoke_syscall+0x48/0x114\n\t el0_svc\n---truncated---(CVE-2024-39488)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nipv6: sr: fix memleak in seg6_hmac_init_algo\r\n\r\nseg6_hmac_init_algo returns without cleaning up the previous allocations\nif one fails, so it\u0026apos;s going to leak all that memory and the crypto tfms.\r\n\r\nUpdate seg6_hmac_exit to only free the memory when allocated, so we can\nreuse the code directly.(CVE-2024-39489)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsock_map: avoid race between sock_map_close and sk_psock_put\r\n\r\nsk_psock_get will return NULL if the refcount of psock has gone to 0, which\nwill happen when the last call of sk_psock_put is done. However,\nsk_psock_drop may not have finished yet, so the close callback will still\npoint to sock_map_close despite psock being NULL.\r\n\r\nThis can be reproduced with a thread deleting an element from the sock map,\nwhile the second one creates a socket, adds it to the map and closes it.\r\n\r\nThat will trigger the WARN_ON_ONCE:\r\n\r\n------------[ cut here ]------------\nWARNING: CPU: 1 PID: 7220 at net/core/sock_map.c:1701 sock_map_close+0x2a2/0x2d0 net/core/sock_map.c:1701\nModules linked in:\nCPU: 1 PID: 7220 Comm: syz-executor380 Not tainted 6.9.0-syzkaller-07726-g3c999d1ae3c7 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024\nRIP: 0010:sock_map_close+0x2a2/0x2d0 net/core/sock_map.c:1701\nCode: df e8 92 29 88 f8 48 8b 1b 48 89 d8 48 c1 e8 03 42 80 3c 20 00 74 08 48 89 df e8 79 29 88 f8 4c 8b 23 eb 89 e8 4f 15 23 f8 90 \u0026lt;0f\u0026gt; 0b 90 48 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f 5d e9 13 26 3d 02\nRSP: 0018:ffffc9000441fda8 EFLAGS: 00010293\nRAX: ffffffff89731ae1 RBX: ffffffff94b87540 RCX: ffff888029470000\nRDX: 0000000000000000 RSI: ffffffff8bcab5c0 RDI: ffffffff8c1faba0\nRBP: 0000000000000000 R08: ffffffff92f9b61f R09: 1ffffffff25f36c3\nR10: dffffc0000000000 R11: fffffbfff25f36c4 R12: ffffffff89731840\nR13: ffff88804b587000 R14: ffff88804b587000 R15: ffffffff89731870\nFS: 000055555e080380(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000000 CR3: 00000000207d4000 CR4: 0000000000350ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n unix_release+0x87/0xc0 net/unix/af_unix.c:1048\n __sock_release net/socket.c:659 [inline]\n sock_close+0xbe/0x240 net/socket.c:1421\n __fput+0x42b/0x8a0 fs/file_table.c:422\n __do_sys_close fs/open.c:1556 [inline]\n __se_sys_close fs/open.c:1541 [inline]\n __x64_sys_close+0x7f/0x110 fs/open.c:1541\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7fb37d618070\nCode: 00 00 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d4 e8 10 2c 00 00 80 3d 31 f0 07 00 00 74 17 b8 03 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 48 c3 0f 1f 80 00 00 00 00 48 83 ec 18 89 7c\nRSP: 002b:00007ffcd4a525d8 EFLAGS: 00000202 ORIG_RAX: 0000000000000003\nRAX: ffffffffffffffda RBX: 0000000000000005 RCX: 00007fb37d618070\nRDX: 0000000000000010 RSI: 00000000200001c0 RDI: 0000000000000004\nRBP: 0000000000000000 R08: 0000000100000000 R09: 0000000100000000\nR10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000000\nR13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000\n \u0026lt;/TASK\u0026gt;\r\n\r\nUse sk_psock, which will only check that the pointer is not been set to\nNULL yet, which should only happen after the callbacks are restored. If,\nthen, a reference can still be gotten, we may call sk_psock_stop and cancel\npsock-\u0026gt;work.\r\n\r\nAs suggested by Paolo Abeni, reorder the condition so the control flow is\nless convoluted.\r\n\r\nAfter that change, the reproducer does not trigger the WARN_ON_ONCE\nanymore.(CVE-2024-39500)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmptcp: ensure snd_una is properly initialized on connect\r\n\r\nThis is strictly related to commit fb7a0d334894 (\u0026quot;mptcp: ensure snd_nxt\nis properly initialized on connect\u0026quot;). It turns out that syzkaller can\ntrigger the retransmit after fallback and before processing any other\nincoming packet - so that snd_una is still left uninitialized.\r\n\r\nAddress the issue explicitly initializing snd_una together with snd_nxt\nand write_seq.(CVE-2024-40931)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nf2fs: remove clear SB_INLINECRYPT flag in default_options\r\n\r\nIn f2fs_remount, SB_INLINECRYPT flag will be clear and re-set.\nIf create new file or open file during this gap, these files\nwill not use inlinecrypt. Worse case, it may lead to data\ncorruption if wrappedkey_v0 is enable.\r\n\r\nThread A: Thread B:\r\n\r\n-f2fs_remount\t\t\t\t-f2fs_file_open or f2fs_new_inode\n -default_options\n\t\u0026lt;- clear SB_INLINECRYPT flag\r\n\r\n -fscrypt_select_encryption_impl\r\n\r\n -parse_options\n\t\u0026lt;- set SB_INLINECRYPT again(CVE-2024-40971)",
"id": "OESA-2024-1860",
"modified": "2026-08-06T11:07:19Z",
"published": "2024-07-19T11:07:19Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-1860"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-47391"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48721"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-52743"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-52755"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-52833"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-34027"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-36478"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38540"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38558"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38570"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38586"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38598"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38605"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38615"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38632"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-39480"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-39487"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-39488"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-39489"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-39500"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-40931"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-40971"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "kernel security update",
"upstream": [
"CVE-2021-47391",
"CVE-2022-48721",
"CVE-2023-52743",
"CVE-2023-52755",
"CVE-2023-52833",
"CVE-2024-34027",
"CVE-2024-36478",
"CVE-2024-38540",
"CVE-2024-38558",
"CVE-2024-38570",
"CVE-2024-38586",
"CVE-2024-38598",
"CVE-2024-38605",
"CVE-2024-38615",
"CVE-2024-38632",
"CVE-2024-39480",
"CVE-2024-39487",
"CVE-2024-39488",
"CVE-2024-39489",
"CVE-2024-39500",
"CVE-2024-40931",
"CVE-2024-40971"
]
}
OESA-2024-1861 (CVE-2023-52755)
Vulnerability from osv_openeuler – Published: 2024-07-19 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:
ksmbd: fix slab out of bounds write in smb_inherit_dacl()
slab out-of-bounds write is caused by that offsets is bigger than pntsd allocation size. This patch add the check to validate 3 offsets using allocation size.(CVE-2023-52755)
In the Linux kernel, the following vulnerability has been resolved:
f2fs: compress: fix to cover {reserve,release}_compress_blocks() w/ cp_rwsem lock
It needs to cover {reserve,release}_compress_blocks() w/ cp_rwsem lock to avoid racing with checkpoint, otherwise, filesystem metadata including blkaddr in dnode, inode fields and .total_valid_block_count may be corrupted after SPO case.(CVE-2024-34027)
In the Linux kernel, the following vulnerability has been resolved:
null_blk: fix null-ptr-dereference while configuring 'power' and 'submit_queues'
Writing 'power' and 'submit_queues' concurrently will trigger kernel panic:
Test script:
modprobe null_blk nr_devices=0 mkdir -p /sys/kernel/config/nullb/nullb0 while true; do echo 1 > submit_queues; echo 4 > submit_queues; done & while true; do echo 1 > power; echo 0 > power; done
Test result:
BUG: kernel NULL pointer dereference, address: 0000000000000148 Oops: 0000 [#1] PREEMPT SMP RIP: 0010:__lock_acquire+0x41d/0x28f0 Call Trace: <TASK> lock_acquire+0x121/0x450 down_write+0x5f/0x1d0 simple_recursive_removal+0x12f/0x5c0 blk_mq_debugfs_unregister_hctxs+0x7c/0x100 blk_mq_update_nr_hw_queues+0x4a3/0x720 nullb_update_nr_hw_queues+0x71/0xf0 [null_blk] nullb_device_submit_queues_store+0x79/0xf0 [null_blk] configfs_write_iter+0x119/0x1e0 vfs_write+0x326/0x730 ksys_write+0x74/0x150
This is because del_gendisk() can concurrent with blk_mq_update_nr_hw_queues():
nullb_device_power_store nullb_apply_submit_queues null_del_dev del_gendisk nullb_update_nr_hw_queues if (!dev->nullb) // still set while gendisk is deleted return 0 blk_mq_update_nr_hw_queues dev->nullb = NULL
Fix this problem by resuing the global mutex to protect nullb_device_power_store() and nullb_update_nr_hw_queues() from configfs.(CVE-2024-36478)
In the Linux kernel, the following vulnerability has been resolved:
bnxt_re: avoid shift undefined behavior in bnxt_qplib_alloc_init_hwq
Undefined behavior is triggered when bnxt_qplib_alloc_init_hwq is called with hwq_attr->aux_depth != 0 and hwq_attr->aux_stride == 0. In that case, "roundup_pow_of_two(hwq_attr->aux_stride)" gets called. roundup_pow_of_two is documented as undefined for 0.
Fix it in the one caller that had this combination.
The undefined behavior was detected by UBSAN: UBSAN: shift-out-of-bounds in ./include/linux/log2.h:57:13 shift exponent 64 is too large for 64-bit type 'long unsigned int' CPU: 24 PID: 1075 Comm: (udev-worker) Not tainted 6.9.0-rc6+ #4 Hardware name: Abacus electric, s.r.o. - servis@abacus.cz Super Server/H12SSW-iN, BIOS 2.7 10/25/2023 Call Trace: <TASK> dump_stack_lvl+0x5d/0x80 ubsan_epilogue+0x5/0x30 __ubsan_handle_shift_out_of_bounds.cold+0x61/0xec __roundup_pow_of_two+0x25/0x35 [bnxt_re] bnxt_qplib_alloc_init_hwq+0xa1/0x470 [bnxt_re] bnxt_qplib_create_qp+0x19e/0x840 [bnxt_re] bnxt_re_create_qp+0x9b1/0xcd0 [bnxt_re] ? srso_alias_return_thunk+0x5/0xfbef5 ? srso_alias_return_thunk+0x5/0xfbef5 ? __kmalloc+0x1b6/0x4f0 ? create_qp.part.0+0x128/0x1c0 [ib_core] ? __pfx_bnxt_re_create_qp+0x10/0x10 [bnxt_re] create_qp.part.0+0x128/0x1c0 [ib_core] ib_create_qp_kernel+0x50/0xd0 [ib_core] create_mad_qp+0x8e/0xe0 [ib_core] ? __pfx_qp_event_handler+0x10/0x10 [ib_core] ib_mad_init_device+0x2be/0x680 [ib_core] add_client_context+0x10d/0x1a0 [ib_core] enable_device_and_get+0xe0/0x1d0 [ib_core] ib_register_device+0x53c/0x630 [ib_core] ? srso_alias_return_thunk+0x5/0xfbef5 bnxt_re_probe+0xbd8/0xe50 [bnxt_re] ? __pfx_bnxt_re_probe+0x10/0x10 [bnxt_re] auxiliary_bus_probe+0x49/0x80 ? driver_sysfs_add+0x57/0xc0 really_probe+0xde/0x340 ? pm_runtime_barrier+0x54/0x90 ? __pfx___driver_attach+0x10/0x10 __driver_probe_device+0x78/0x110 driver_probe_device+0x1f/0xa0 __driver_attach+0xba/0x1c0 bus_for_each_dev+0x8f/0xe0 bus_add_driver+0x146/0x220 driver_register+0x72/0xd0 __auxiliary_driver_register+0x6e/0xd0 ? __pfx_bnxt_re_mod_init+0x10/0x10 [bnxt_re] bnxt_re_mod_init+0x3e/0xff0 [bnxt_re] ? __pfx_bnxt_re_mod_init+0x10/0x10 [bnxt_re] do_one_initcall+0x5b/0x310 do_init_module+0x90/0x250 init_module_from_file+0x86/0xc0 idempotent_init_module+0x121/0x2b0 __x64_sys_finit_module+0x5e/0xb0 do_syscall_64+0x82/0x160 ? srso_alias_return_thunk+0x5/0xfbef5 ? syscall_exit_to_user_mode_prepare+0x149/0x170 ? srso_alias_return_thunk+0x5/0xfbef5 ? syscall_exit_to_user_mode+0x75/0x230 ? srso_alias_return_thunk+0x5/0xfbef5 ? do_syscall_64+0x8e/0x160 ? srso_alias_return_thunk+0x5/0xfbef5 ? __count_memcg_events+0x69/0x100 ? srso_alias_return_thunk+0x5/0xfbef5 ? count_memcg_events.constprop.0+0x1a/0x30 ? srso_alias_return_thunk+0x5/0xfbef5 ? handle_mm_fault+0x1f0/0x300 ? srso_alias_return_thunk+0x5/0xfbef5 ? do_user_addr_fault+0x34e/0x640 ? srso_alias_return_thunk+0x5/0xfbef5 ? srso_alias_return_thunk+0x5/0xfbef5 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7f4e5132821d Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 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 8b 0d e3 db 0c 00 f7 d8 64 89 01 48 RSP: 002b:00007ffca9c906a8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139 RAX: ffffffffffffffda RBX: 0000563ec8a8f130 RCX: 00007f4e5132821d RDX: 0000000000000000 RSI: 00007f4e518fa07d RDI: 000000000000003b RBP: 00007ffca9c90760 R08: 00007f4e513f6b20 R09: 00007ffca9c906f0 R10: 0000563ec8a8faa0 R11: 0000000000000246 R12: 00007f4e518fa07d R13: 0000000000020000 R14: 0000563ec8409e90 R15: 0000563ec8a8fa60 </TASK> ---[ end trace ]---(CVE-2024-38540)
In the Linux kernel, the following vulnerability has been resolved:
net: openvswitch: fix overwriting ct original tuple for ICMPv6
OVS_PACKET_CMD_EXECUTE has 3 main attributes: - OVS_PACKET_ATTR_KEY - Packet metadata in a netlink format. - OVS_PACKET_ATTR_PACKET - Binary packet content. - OVS_PACKET_ATTR_ACTIONS - Actions to execute on the packet.
OVS_PACKET_ATTR_KEY is parsed first to populate sw_flow_key structure with the metadata like conntrack state, input port, recirculation id, etc. Then the packet itself gets parsed to populate the rest of the keys from the packet headers.
Whenever the packet parsing code starts parsing the ICMPv6 header, it first zeroes out fields in the key corresponding to Neighbor Discovery information even if it is not an ND packet.
It is an 'ipv6.nd' field. However, the 'ipv6' is a union that shares the space between 'nd' and 'ct_orig' that holds the original tuple conntrack metadata parsed from the OVS_PACKET_ATTR_KEY.
ND packets should not normally have conntrack state, so it's fine to share the space, but normal ICMPv6 Echo packets or maybe other types of ICMPv6 can have the state attached and it should not be overwritten.
The issue results in all but the last 4 bytes of the destination address being wiped from the original conntrack tuple leading to incorrect packet matching and potentially executing wrong actions in case this packet recirculates within the datapath or goes back to userspace.
ND fields should not be accessed in non-ND packets, so not clearing them should be fine. Executing memset() only for actual ND packets to avoid the issue.
Initializing the whole thing before parsing is needed because ND packet may not contain all the options.
The issue only affects the OVS_PACKET_CMD_EXECUTE path and doesn't affect packets entering OVS datapath from network interfaces, because in this case CT metadata is populated from skb after the packet is already parsed.(CVE-2024-38558)
In the Linux kernel, the following vulnerability has been resolved:
gfs2: Fix potential glock use-after-free on unmount
When a DLM lockspace is released and there ares still locks in that lockspace, DLM will unlock those locks automatically. Commit fb6791d100d1b started exploiting this behavior to speed up filesystem unmount: gfs2 would simply free glocks it didn't want to unlock and then release the lockspace. This didn't take the bast callbacks for asynchronous lock contention notifications into account, which remain active until until a lock is unlocked or its lockspace is released.
To prevent those callbacks from accessing deallocated objects, put the glocks that should not be unlocked on the sd_dead_glocks list, release the lockspace, and only then free those glocks.
As an additional measure, ignore unexpected ast and bast callbacks if the receiving glock is dead.(CVE-2024-38570)
In the Linux kernel, the following vulnerability has been resolved:
r8169: Fix possible ring buffer corruption on fragmented Tx packets.
An issue was found on the RTL8125b when transmitting small fragmented packets, whereby invalid entries were inserted into the transmit ring buffer, subsequently leading to calls to dma_unmap_single() with a null address.
This was caused by rtl8169_start_xmit() not noticing changes to nr_frags which may occur when small packets are padded (to work around hardware quirks) in rtl8169_tso_csum_v2().
To fix this, postpone inspecting nr_frags until after any padding has been applied.(CVE-2024-38586)
In the Linux kernel, the following vulnerability has been resolved:
ALSA: core: Fix NULL module pointer assignment at card init
The commit 81033c6b584b ("ALSA: core: Warn on empty module") introduced a WARN_ON() for a NULL module pointer passed at snd_card object creation, and it also wraps the code around it with '#ifdef MODULE'. This works in most cases, but the devils are always in details. "MODULE" is defined when the target code (i.e. the sound core) is built as a module; but this doesn't mean that the caller is also built-in or not. Namely, when only the sound core is built-in (CONFIG_SND=y) while the driver is a module (CONFIG_SND_USB_AUDIO=m), the passed module pointer is ignored even if it's non-NULL, and card->module remains as NULL. This would result in the missing module reference up/down at the device open/close, leading to a race with the code execution after the module removal.
For addressing the bug, move the assignment of card->module again out of ifdef. The WARN_ON() is still wrapped with ifdef because the module can be really NULL when all sound drivers are built-in.
Note that we keep 'ifdef MODULE' for WARN_ON(), otherwise it would lead to a false-positive NULL module check. Admittedly it won't catch perfectly, i.e. no check is performed when CONFIG_SND=y. But, it's no real problem as it's only for debugging, and the condition is pretty rare.(CVE-2024-38605)
In the Linux kernel, the following vulnerability has been resolved:
vfio/pci: fix potential memory leak in vfio_intx_enable()
If vfio_irq_ctx_alloc() failed will lead to 'name' memory leak.(CVE-2024-38632)
In the Linux kernel, the following vulnerability has been resolved:
kdb: Fix buffer overflow during tab-complete
Currently, when the user attempts symbol completion with the Tab key, kdb will use strncpy() to insert the completed symbol into the command buffer. Unfortunately it passes the size of the source buffer rather than the destination to strncpy() with predictably horrible results. Most obviously if the command buffer is already full but cp, the cursor position, is in the middle of the buffer, then we will write past the end of the supplied buffer.
Fix this by replacing the dubious strncpy() calls with memmove()/memcpy() calls plus explicit boundary checks to make sure we have enough space before we start moving characters around.(CVE-2024-39480)
In the Linux kernel, the following vulnerability has been resolved:
bonding: Fix out-of-bounds read in bond_option_arp_ip_targets_set()
In function bond_option_arp_ip_targets_set(), if newval->string is an empty string, newval->string+1 will point to the byte after the string, causing an out-of-bound read.
BUG: KASAN: slab-out-of-bounds in strlen+0x7d/0xa0 lib/string.c:418 Read of size 1 at addr ffff8881119c4781 by task syz-executor665/8107 CPU: 1 PID: 8107 Comm: syz-executor665 Not tainted 6.7.0-rc7 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd9/0x150 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:364 [inline] print_report+0xc1/0x5e0 mm/kasan/report.c:475 kasan_report+0xbe/0xf0 mm/kasan/report.c:588 strlen+0x7d/0xa0 lib/string.c:418 __fortify_strlen include/linux/fortify-string.h:210 [inline] in4_pton+0xa3/0x3f0 net/core/utils.c:130 bond_option_arp_ip_targets_set+0xc2/0x910 drivers/net/bonding/bond_options.c:1201 __bond_opt_set+0x2a4/0x1030 drivers/net/bonding/bond_options.c:767 __bond_opt_set_notify+0x48/0x150 drivers/net/bonding/bond_options.c:792 bond_opt_tryset_rtnl+0xda/0x160 drivers/net/bonding/bond_options.c:817 bonding_sysfs_store_option+0xa1/0x120 drivers/net/bonding/bond_sysfs.c:156 dev_attr_store+0x54/0x80 drivers/base/core.c:2366 sysfs_kf_write+0x114/0x170 fs/sysfs/file.c:136 kernfs_fop_write_iter+0x337/0x500 fs/kernfs/file.c:334 call_write_iter include/linux/fs.h:2020 [inline] new_sync_write fs/read_write.c:491 [inline] vfs_write+0x96a/0xd80 fs/read_write.c:584 ksys_write+0x122/0x250 fs/read_write.c:637 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x40/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b ---[ end trace ]---
Fix it by adding a check of string length before using it.(CVE-2024-39487)
In the Linux kernel, the following vulnerability has been resolved:
arm64: asm-bug: Add .align 2 to the end of __BUG_ENTRY
When CONFIG_DEBUG_BUGVERBOSE=n, we fail to add necessary padding bytes to bug_table entries, and as a result the last entry in a bug table will be ignored, potentially leading to an unexpected panic(). All prior entries in the table will be handled correctly.
The arm64 ABI requires that struct fields of up to 8 bytes are naturally-aligned, with padding added within a struct such that struct are suitably aligned within arrays.
When CONFIG_DEBUG_BUGVERPOSE=y, the layout of a bug_entry is:
struct bug_entry {
signed int bug_addr_disp; // 4 bytes
signed int file_disp; // 4 bytes
unsigned short line; // 2 bytes
unsigned short flags; // 2 bytes
}
... with 12 bytes total, requiring 4-byte alignment.
When CONFIG_DEBUG_BUGVERBOSE=n, the layout of a bug_entry is:
struct bug_entry {
signed int bug_addr_disp; // 4 bytes
unsigned short flags; // 2 bytes
< implicit padding > // 2 bytes
}
... with 8 bytes total, with 6 bytes of data and 2 bytes of trailing padding, requiring 4-byte alginment.
When we create a bug_entry in assembly, we align the start of the entry to 4 bytes, which implicitly handles padding for any prior entries. However, we do not align the end of the entry, and so when CONFIG_DEBUG_BUGVERBOSE=n, the final entry lacks the trailing padding bytes.
For the main kernel image this is not a problem as find_bug() doesn't depend on the trailing padding bytes when searching for entries:
for (bug = __start___bug_table; bug < __stop___bug_table; ++bug)
if (bugaddr == bug_addr(bug))
return bug;
However for modules, module_bug_finalize() depends on the trailing bytes when calculating the number of entries:
mod->num_bugs = sechdrs[i].sh_size / sizeof(struct bug_entry);
... and as the last bug_entry lacks the necessary padding bytes, this entry will not be counted, e.g. in the case of a single entry:
sechdrs[i].sh_size == 6
sizeof(struct bug_entry) == 8;
sechdrs[i].sh_size / sizeof(struct bug_entry) == 0;
Consequently module_find_bug() will miss the last bug_entry when it does:
for (i = 0; i < mod->num_bugs; ++i, ++bug)
if (bugaddr == bug_addr(bug))
goto out;
... which can lead to a kenrel panic due to an unhandled bug.
This can be demonstrated with the following module:
static int __init buginit(void)
{
WARN(1, "hello\n");
return 0;
}
static void __exit bugexit(void)
{
}
module_init(buginit);
module_exit(bugexit);
MODULE_LICENSE("GPL");
... which will trigger a kernel panic when loaded:
------------[ cut here ]------------
hello
Unexpected kernel BRK exception at EL1
Internal error: BRK handler: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in: hello(O+)
CPU: 0 PID: 50 Comm: insmod Tainted: G O 6.9.1 #8
Hardware name: linux,dummy-virt (DT)
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : buginit+0x18/0x1000 [hello]
lr : buginit+0x18/0x1000 [hello]
sp : ffff800080533ae0
x29: ffff800080533ae0 x28: 0000000000000000 x27: 0000000000000000
x26: ffffaba8c4e70510 x25: ffff800080533c30 x24: ffffaba8c4a28a58
x23: 0000000000000000 x22: 0000000000000000 x21: ffff3947c0eab3c0
x20: ffffaba8c4e3f000 x19: ffffaba846464000 x18: 0000000000000006
x17: 0000000000000000 x16: ffffaba8c2492834 x15: 0720072007200720
x14: 0720072007200720 x13: ffffaba8c49b27c8 x12: 0000000000000312
x11: 0000000000000106 x10: ffffaba8c4a0a7c8 x9 : ffffaba8c49b27c8
x8 : 00000000ffffefff x7 : ffffaba8c4a0a7c8 x6 : 80000000fffff000
x5 : 0000000000000107 x4 : 0000000000000000 x3 : 0000000000000000
x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff3947c0eab3c0
Call trace:
buginit+0x18/0x1000 [hello]
do_one_initcall+0x80/0x1c8
do_init_module+0x60/0x218
load_module+0x1ba4/0x1d70
__do_sys_init_module+0x198/0x1d0
__arm64_sys_init_module+0x1c/0x28
invoke_syscall+0x48/0x114
el0_svc
---truncated---(CVE-2024-39488)
In the Linux kernel, the following vulnerability has been resolved:
ipv6: sr: fix memleak in seg6_hmac_init_algo
seg6_hmac_init_algo returns without cleaning up the previous allocations if one fails, so it's going to leak all that memory and the crypto tfms.
Update seg6_hmac_exit to only free the memory when allocated, so we can reuse the code directly.(CVE-2024-39489)
In the Linux kernel, the following vulnerability has been resolved:
sock_map: avoid race between sock_map_close and sk_psock_put
sk_psock_get will return NULL if the refcount of psock has gone to 0, which will happen when the last call of sk_psock_put is done. However, sk_psock_drop may not have finished yet, so the close callback will still point to sock_map_close despite psock being NULL.
This can be reproduced with a thread deleting an element from the sock map, while the second one creates a socket, adds it to the map and closes it.
That will trigger the WARN_ON_ONCE:
------------[ cut here ]------------ WARNING: CPU: 1 PID: 7220 at net/core/sock_map.c:1701 sock_map_close+0x2a2/0x2d0 net/core/sock_map.c:1701 Modules linked in: CPU: 1 PID: 7220 Comm: syz-executor380 Not tainted 6.9.0-syzkaller-07726-g3c999d1ae3c7 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024 RIP: 0010:sock_map_close+0x2a2/0x2d0 net/core/sock_map.c:1701 Code: df e8 92 29 88 f8 48 8b 1b 48 89 d8 48 c1 e8 03 42 80 3c 20 00 74 08 48 89 df e8 79 29 88 f8 4c 8b 23 eb 89 e8 4f 15 23 f8 90 <0f> 0b 90 48 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f 5d e9 13 26 3d 02 RSP: 0018:ffffc9000441fda8 EFLAGS: 00010293 RAX: ffffffff89731ae1 RBX: ffffffff94b87540 RCX: ffff888029470000 RDX: 0000000000000000 RSI: ffffffff8bcab5c0 RDI: ffffffff8c1faba0 RBP: 0000000000000000 R08: ffffffff92f9b61f R09: 1ffffffff25f36c3 R10: dffffc0000000000 R11: fffffbfff25f36c4 R12: ffffffff89731840 R13: ffff88804b587000 R14: ffff88804b587000 R15: ffffffff89731870 FS: 000055555e080380(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 00000000207d4000 CR4: 0000000000350ef0 Call Trace: <TASK> unix_release+0x87/0xc0 net/unix/af_unix.c:1048 __sock_release net/socket.c:659 [inline] sock_close+0xbe/0x240 net/socket.c:1421 __fput+0x42b/0x8a0 fs/file_table.c:422 __do_sys_close fs/open.c:1556 [inline] __se_sys_close fs/open.c:1541 [inline] __x64_sys_close+0x7f/0x110 fs/open.c:1541 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fb37d618070 Code: 00 00 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d4 e8 10 2c 00 00 80 3d 31 f0 07 00 00 74 17 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 48 c3 0f 1f 80 00 00 00 00 48 83 ec 18 89 7c RSP: 002b:00007ffcd4a525d8 EFLAGS: 00000202 ORIG_RAX: 0000000000000003 RAX: ffffffffffffffda RBX: 0000000000000005 RCX: 00007fb37d618070 RDX: 0000000000000010 RSI: 00000000200001c0 RDI: 0000000000000004 RBP: 0000000000000000 R08: 0000000100000000 R09: 0000000100000000 R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 </TASK>
Use sk_psock, which will only check that the pointer is not been set to NULL yet, which should only happen after the callbacks are restored. If, then, a reference can still be gotten, we may call sk_psock_stop and cancel psock->work.
As suggested by Paolo Abeni, reorder the condition so the control flow is less convoluted.
After that change, the reproducer does not trigger the WARN_ON_ONCE anymore.(CVE-2024-39500)
In the Linux kernel, the following vulnerability has been resolved:
ionic: fix use after netif_napi_del()
When queues are started, netif_napi_add() and napi_enable() are called. If there are 4 queues and only 3 queues are used for the current configuration, only 3 queues' napi should be registered and enabled. The ionic_qcq_enable() checks whether the .poll pointer is not NULL for enabling only the using queue' napi. Unused queues' napi will not be registered by netif_napi_add(), so the .poll pointer indicates NULL. But it couldn't distinguish whether the napi was unregistered or not because netif_napi_del() doesn't reset the .poll pointer to NULL. So, ionic_qcq_enable() calls napi_enable() for the queue, which was unregistered by netif_napi_del().
Reproducer: ethtool -L <interface name> rx 1 tx 1 combined 0 ethtool -L <interface name> rx 0 tx 0 combined 1 ethtool -L <interface name> rx 0 tx 0 combined 4
Splat looks like: kernel BUG at net/core/dev.c:6666! Oops: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI CPU: 3 PID: 1057 Comm: kworker/3:3 Not tainted 6.10.0-rc2+ #16 Workqueue: events ionic_lif_deferred_work [ionic] RIP: 0010:napi_enable+0x3b/0x40 Code: 48 89 c2 48 83 e2 f6 80 b9 61 09 00 00 00 74 0d 48 83 bf 60 01 00 00 00 74 03 80 ce 01 f0 4f RSP: 0018:ffffb6ed83227d48 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff97560cda0828 RCX: 0000000000000029 RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff97560cda0a28 RBP: ffffb6ed83227d50 R08: 0000000000000400 R09: 0000000000000001 R10: 0000000000000001 R11: 0000000000000001 R12: 0000000000000000 R13: ffff97560ce3c1a0 R14: 0000000000000000 R15: ffff975613ba0a20 FS: 0000000000000000(0000) GS:ffff975d5f780000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f8f734ee200 CR3: 0000000103e50000 CR4: 00000000007506f0 PKRU: 55555554 Call Trace: <TASK> ? die+0x33/0x90 ? do_trap+0xd9/0x100 ? napi_enable+0x3b/0x40 ? do_error_trap+0x83/0xb0 ? napi_enable+0x3b/0x40 ? napi_enable+0x3b/0x40 ? exc_invalid_op+0x4e/0x70 ? napi_enable+0x3b/0x40 ? asm_exc_invalid_op+0x16/0x20 ? napi_enable+0x3b/0x40 ionic_qcq_enable+0xb7/0x180 [ionic 59bdfc8a035436e1c4224ff7d10789e3f14643f8] ionic_start_queues+0xc4/0x290 [ionic 59bdfc8a035436e1c4224ff7d10789e3f14643f8] ionic_link_status_check+0x11c/0x170 [ionic 59bdfc8a035436e1c4224ff7d10789e3f14643f8] ionic_lif_deferred_work+0x129/0x280 [ionic 59bdfc8a035436e1c4224ff7d10789e3f14643f8] process_one_work+0x145/0x360 worker_thread+0x2bb/0x3d0 ? __pfx_worker_thread+0x10/0x10 kthread+0xcc/0x100 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x2d/0x50 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30(CVE-2024-39502)
In the Linux kernel, the following vulnerability has been resolved:
mptcp: ensure snd_una is properly initialized on connect
This is strictly related to commit fb7a0d334894 ("mptcp: ensure snd_nxt is properly initialized on connect"). It turns out that syzkaller can trigger the retransmit after fallback and before processing any other incoming packet - so that snd_una is still left uninitialized.
Address the issue explicitly initializing snd_una together with snd_nxt and write_seq.(CVE-2024-40931)
In the Linux kernel, the following vulnerability has been resolved:
HID: logitech-dj: Fix memory leak in logi_dj_recv_switch_to_dj_mode()
Fix a memory leak on logi_dj_recv_send_report() error path.(CVE-2024-40934)
In the Linux kernel, the following vulnerability has been resolved:
f2fs: remove clear SB_INLINECRYPT flag in default_options
In f2fs_remount, SB_INLINECRYPT flag will be clear and re-set. If create new file or open file during this gap, these files will not use inlinecrypt. Worse case, it may lead to data corruption if wrappedkey_v0 is enable.
Thread A: Thread B:
-f2fs_remount -f2fs_file_open or f2fs_new_inode -default_options <- clear SB_INLINECRYPT flag
-fscrypt_select_encryption_impl
-parse_options <- set SB_INLINECRYPT again(CVE-2024-40971)
| URL | Type | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"kernel-5.10.0-219.0.0.122.oe2203sp3.aarch64.rpm",
"kernel-debuginfo-5.10.0-219.0.0.122.oe2203sp3.aarch64.rpm",
"kernel-debugsource-5.10.0-219.0.0.122.oe2203sp3.aarch64.rpm",
"kernel-devel-5.10.0-219.0.0.122.oe2203sp3.aarch64.rpm",
"kernel-headers-5.10.0-219.0.0.122.oe2203sp3.aarch64.rpm",
"kernel-source-5.10.0-219.0.0.122.oe2203sp3.aarch64.rpm",
"kernel-tools-5.10.0-219.0.0.122.oe2203sp3.aarch64.rpm",
"kernel-tools-debuginfo-5.10.0-219.0.0.122.oe2203sp3.aarch64.rpm",
"kernel-tools-devel-5.10.0-219.0.0.122.oe2203sp3.aarch64.rpm",
"perf-5.10.0-219.0.0.122.oe2203sp3.aarch64.rpm",
"perf-debuginfo-5.10.0-219.0.0.122.oe2203sp3.aarch64.rpm",
"python3-perf-5.10.0-219.0.0.122.oe2203sp3.aarch64.rpm",
"python3-perf-debuginfo-5.10.0-219.0.0.122.oe2203sp3.aarch64.rpm"
],
"src": [
"kernel-5.10.0-219.0.0.122.oe2203sp3.src.rpm"
],
"x86_64": [
"kernel-5.10.0-219.0.0.122.oe2203sp3.x86_64.rpm",
"kernel-debuginfo-5.10.0-219.0.0.122.oe2203sp3.x86_64.rpm",
"kernel-debugsource-5.10.0-219.0.0.122.oe2203sp3.x86_64.rpm",
"kernel-devel-5.10.0-219.0.0.122.oe2203sp3.x86_64.rpm",
"kernel-headers-5.10.0-219.0.0.122.oe2203sp3.x86_64.rpm",
"kernel-source-5.10.0-219.0.0.122.oe2203sp3.x86_64.rpm",
"kernel-tools-5.10.0-219.0.0.122.oe2203sp3.x86_64.rpm",
"kernel-tools-debuginfo-5.10.0-219.0.0.122.oe2203sp3.x86_64.rpm",
"kernel-tools-devel-5.10.0-219.0.0.122.oe2203sp3.x86_64.rpm",
"perf-5.10.0-219.0.0.122.oe2203sp3.x86_64.rpm",
"perf-debuginfo-5.10.0-219.0.0.122.oe2203sp3.x86_64.rpm",
"python3-perf-5.10.0-219.0.0.122.oe2203sp3.x86_64.rpm",
"python3-perf-debuginfo-5.10.0-219.0.0.122.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-219.0.0.122.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:\r\n\r\nksmbd: fix slab out of bounds write in smb_inherit_dacl()\r\n\r\nslab out-of-bounds write is caused by that offsets is bigger than pntsd\nallocation size. This patch add the check to validate 3 offsets using\nallocation size.(CVE-2023-52755)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nf2fs: compress: fix to cover {reserve,release}_compress_blocks() w/ cp_rwsem lock\r\n\r\nIt needs to cover {reserve,release}_compress_blocks() w/ cp_rwsem lock\nto avoid racing with checkpoint, otherwise, filesystem metadata including\nblkaddr in dnode, inode fields and .total_valid_block_count may be\ncorrupted after SPO case.(CVE-2024-34027)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnull_blk: fix null-ptr-dereference while configuring \u0026apos;power\u0026apos; and \u0026apos;submit_queues\u0026apos;\r\n\r\nWriting \u0026apos;power\u0026apos; and \u0026apos;submit_queues\u0026apos; concurrently will trigger kernel\npanic:\r\n\r\nTest script:\r\n\r\nmodprobe null_blk nr_devices=0\nmkdir -p /sys/kernel/config/nullb/nullb0\nwhile true; do echo 1 \u0026gt; submit_queues; echo 4 \u0026gt; submit_queues; done \u0026amp;\nwhile true; do echo 1 \u0026gt; power; echo 0 \u0026gt; power; done\r\n\r\nTest result:\r\n\r\nBUG: kernel NULL pointer dereference, address: 0000000000000148\nOops: 0000 [#1] PREEMPT SMP\nRIP: 0010:__lock_acquire+0x41d/0x28f0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n lock_acquire+0x121/0x450\n down_write+0x5f/0x1d0\n simple_recursive_removal+0x12f/0x5c0\n blk_mq_debugfs_unregister_hctxs+0x7c/0x100\n blk_mq_update_nr_hw_queues+0x4a3/0x720\n nullb_update_nr_hw_queues+0x71/0xf0 [null_blk]\n nullb_device_submit_queues_store+0x79/0xf0 [null_blk]\n configfs_write_iter+0x119/0x1e0\n vfs_write+0x326/0x730\n ksys_write+0x74/0x150\r\n\r\nThis is because del_gendisk() can concurrent with\nblk_mq_update_nr_hw_queues():\r\n\r\nnullb_device_power_store\tnullb_apply_submit_queues\n null_del_dev\n del_gendisk\n\t\t\t\t nullb_update_nr_hw_queues\n\t\t\t\t if (!dev-\u0026gt;nullb)\n\t\t\t\t // still set while gendisk is deleted\n\t\t\t\t return 0\n\t\t\t\t blk_mq_update_nr_hw_queues\n dev-\u0026gt;nullb = NULL\r\n\r\nFix this problem by resuing the global mutex to protect\nnullb_device_power_store() and nullb_update_nr_hw_queues() from configfs.(CVE-2024-36478)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbnxt_re: avoid shift undefined behavior in bnxt_qplib_alloc_init_hwq\r\n\r\nUndefined behavior is triggered when bnxt_qplib_alloc_init_hwq is called\nwith hwq_attr-\u0026gt;aux_depth != 0 and hwq_attr-\u0026gt;aux_stride == 0.\nIn that case, \u0026quot;roundup_pow_of_two(hwq_attr-\u0026gt;aux_stride)\u0026quot; gets called.\nroundup_pow_of_two is documented as undefined for 0.\r\n\r\nFix it in the one caller that had this combination.\r\n\r\nThe undefined behavior was detected by UBSAN:\n UBSAN: shift-out-of-bounds in ./include/linux/log2.h:57:13\n shift exponent 64 is too large for 64-bit type \u0026apos;long unsigned int\u0026apos;\n CPU: 24 PID: 1075 Comm: (udev-worker) Not tainted 6.9.0-rc6+ #4\n Hardware name: Abacus electric, s.r.o. - servis@abacus.cz Super Server/H12SSW-iN, BIOS 2.7 10/25/2023\n Call Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x5d/0x80\n ubsan_epilogue+0x5/0x30\n __ubsan_handle_shift_out_of_bounds.cold+0x61/0xec\n __roundup_pow_of_two+0x25/0x35 [bnxt_re]\n bnxt_qplib_alloc_init_hwq+0xa1/0x470 [bnxt_re]\n bnxt_qplib_create_qp+0x19e/0x840 [bnxt_re]\n bnxt_re_create_qp+0x9b1/0xcd0 [bnxt_re]\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? __kmalloc+0x1b6/0x4f0\n ? create_qp.part.0+0x128/0x1c0 [ib_core]\n ? __pfx_bnxt_re_create_qp+0x10/0x10 [bnxt_re]\n create_qp.part.0+0x128/0x1c0 [ib_core]\n ib_create_qp_kernel+0x50/0xd0 [ib_core]\n create_mad_qp+0x8e/0xe0 [ib_core]\n ? __pfx_qp_event_handler+0x10/0x10 [ib_core]\n ib_mad_init_device+0x2be/0x680 [ib_core]\n add_client_context+0x10d/0x1a0 [ib_core]\n enable_device_and_get+0xe0/0x1d0 [ib_core]\n ib_register_device+0x53c/0x630 [ib_core]\n ? srso_alias_return_thunk+0x5/0xfbef5\n bnxt_re_probe+0xbd8/0xe50 [bnxt_re]\n ? __pfx_bnxt_re_probe+0x10/0x10 [bnxt_re]\n auxiliary_bus_probe+0x49/0x80\n ? driver_sysfs_add+0x57/0xc0\n really_probe+0xde/0x340\n ? pm_runtime_barrier+0x54/0x90\n ? __pfx___driver_attach+0x10/0x10\n __driver_probe_device+0x78/0x110\n driver_probe_device+0x1f/0xa0\n __driver_attach+0xba/0x1c0\n bus_for_each_dev+0x8f/0xe0\n bus_add_driver+0x146/0x220\n driver_register+0x72/0xd0\n __auxiliary_driver_register+0x6e/0xd0\n ? __pfx_bnxt_re_mod_init+0x10/0x10 [bnxt_re]\n bnxt_re_mod_init+0x3e/0xff0 [bnxt_re]\n ? __pfx_bnxt_re_mod_init+0x10/0x10 [bnxt_re]\n do_one_initcall+0x5b/0x310\n do_init_module+0x90/0x250\n init_module_from_file+0x86/0xc0\n idempotent_init_module+0x121/0x2b0\n __x64_sys_finit_module+0x5e/0xb0\n do_syscall_64+0x82/0x160\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? syscall_exit_to_user_mode_prepare+0x149/0x170\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? syscall_exit_to_user_mode+0x75/0x230\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? do_syscall_64+0x8e/0x160\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? __count_memcg_events+0x69/0x100\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? count_memcg_events.constprop.0+0x1a/0x30\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? handle_mm_fault+0x1f0/0x300\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? do_user_addr_fault+0x34e/0x640\n ? srso_alias_return_thunk+0x5/0xfbef5\n ? srso_alias_return_thunk+0x5/0xfbef5\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n RIP: 0033:0x7f4e5132821d\n Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 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 8b 0d e3 db 0c 00 f7 d8 64 89 01 48\n RSP: 002b:00007ffca9c906a8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139\n RAX: ffffffffffffffda RBX: 0000563ec8a8f130 RCX: 00007f4e5132821d\n RDX: 0000000000000000 RSI: 00007f4e518fa07d RDI: 000000000000003b\n RBP: 00007ffca9c90760 R08: 00007f4e513f6b20 R09: 00007ffca9c906f0\n R10: 0000563ec8a8faa0 R11: 0000000000000246 R12: 00007f4e518fa07d\n R13: 0000000000020000 R14: 0000563ec8409e90 R15: 0000563ec8a8fa60\n \u0026lt;/TASK\u0026gt;\n ---[ end trace ]---(CVE-2024-38540)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: openvswitch: fix overwriting ct original tuple for ICMPv6\r\n\r\nOVS_PACKET_CMD_EXECUTE has 3 main attributes:\n - OVS_PACKET_ATTR_KEY - Packet metadata in a netlink format.\n - OVS_PACKET_ATTR_PACKET - Binary packet content.\n - OVS_PACKET_ATTR_ACTIONS - Actions to execute on the packet.\r\n\r\nOVS_PACKET_ATTR_KEY is parsed first to populate sw_flow_key structure\nwith the metadata like conntrack state, input port, recirculation id,\netc. Then the packet itself gets parsed to populate the rest of the\nkeys from the packet headers.\r\n\r\nWhenever the packet parsing code starts parsing the ICMPv6 header, it\nfirst zeroes out fields in the key corresponding to Neighbor Discovery\ninformation even if it is not an ND packet.\r\n\r\nIt is an \u0026apos;ipv6.nd\u0026apos; field. However, the \u0026apos;ipv6\u0026apos; is a union that shares\nthe space between \u0026apos;nd\u0026apos; and \u0026apos;ct_orig\u0026apos; that holds the original tuple\nconntrack metadata parsed from the OVS_PACKET_ATTR_KEY.\r\n\r\nND packets should not normally have conntrack state, so it\u0026apos;s fine to\nshare the space, but normal ICMPv6 Echo packets or maybe other types of\nICMPv6 can have the state attached and it should not be overwritten.\r\n\r\nThe issue results in all but the last 4 bytes of the destination\naddress being wiped from the original conntrack tuple leading to\nincorrect packet matching and potentially executing wrong actions\nin case this packet recirculates within the datapath or goes back\nto userspace.\r\n\r\nND fields should not be accessed in non-ND packets, so not clearing\nthem should be fine. Executing memset() only for actual ND packets to\navoid the issue.\r\n\r\nInitializing the whole thing before parsing is needed because ND packet\nmay not contain all the options.\r\n\r\nThe issue only affects the OVS_PACKET_CMD_EXECUTE path and doesn\u0026apos;t\naffect packets entering OVS datapath from network interfaces, because\nin this case CT metadata is populated from skb after the packet is\nalready parsed.(CVE-2024-38558)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ngfs2: Fix potential glock use-after-free on unmount\r\n\r\nWhen a DLM lockspace is released and there ares still locks in that\nlockspace, DLM will unlock those locks automatically. Commit\nfb6791d100d1b started exploiting this behavior to speed up filesystem\nunmount: gfs2 would simply free glocks it didn\u0026apos;t want to unlock and then\nrelease the lockspace. This didn\u0026apos;t take the bast callbacks for\nasynchronous lock contention notifications into account, which remain\nactive until until a lock is unlocked or its lockspace is released.\r\n\r\nTo prevent those callbacks from accessing deallocated objects, put the\nglocks that should not be unlocked on the sd_dead_glocks list, release\nthe lockspace, and only then free those glocks.\r\n\r\nAs an additional measure, ignore unexpected ast and bast callbacks if\nthe receiving glock is dead.(CVE-2024-38570)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nr8169: Fix possible ring buffer corruption on fragmented Tx packets.\r\n\r\nAn issue was found on the RTL8125b when transmitting small fragmented\npackets, whereby invalid entries were inserted into the transmit ring\nbuffer, subsequently leading to calls to dma_unmap_single() with a null\naddress.\r\n\r\nThis was caused by rtl8169_start_xmit() not noticing changes to nr_frags\nwhich may occur when small packets are padded (to work around hardware\nquirks) in rtl8169_tso_csum_v2().\r\n\r\nTo fix this, postpone inspecting nr_frags until after any padding has been\napplied.(CVE-2024-38586)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nALSA: core: Fix NULL module pointer assignment at card init\r\n\r\nThe commit 81033c6b584b (\u0026quot;ALSA: core: Warn on empty module\u0026quot;)\nintroduced a WARN_ON() for a NULL module pointer passed at snd_card\nobject creation, and it also wraps the code around it with \u0026apos;#ifdef\nMODULE\u0026apos;. This works in most cases, but the devils are always in\ndetails. \u0026quot;MODULE\u0026quot; is defined when the target code (i.e. the sound\ncore) is built as a module; but this doesn\u0026apos;t mean that the caller is\nalso built-in or not. Namely, when only the sound core is built-in\n(CONFIG_SND=y) while the driver is a module (CONFIG_SND_USB_AUDIO=m),\nthe passed module pointer is ignored even if it\u0026apos;s non-NULL, and\ncard-\u0026gt;module remains as NULL. This would result in the missing module\nreference up/down at the device open/close, leading to a race with the\ncode execution after the module removal.\r\n\r\nFor addressing the bug, move the assignment of card-\u0026gt;module again out\nof ifdef. The WARN_ON() is still wrapped with ifdef because the\nmodule can be really NULL when all sound drivers are built-in.\r\n\r\nNote that we keep \u0026apos;ifdef MODULE\u0026apos; for WARN_ON(), otherwise it would\nlead to a false-positive NULL module check. Admittedly it won\u0026apos;t catch\nperfectly, i.e. no check is performed when CONFIG_SND=y. But, it\u0026apos;s no\nreal problem as it\u0026apos;s only for debugging, and the condition is pretty\nrare.(CVE-2024-38605)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nvfio/pci: fix potential memory leak in vfio_intx_enable()\r\n\r\nIf vfio_irq_ctx_alloc() failed will lead to \u0026apos;name\u0026apos; memory leak.(CVE-2024-38632)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nkdb: Fix buffer overflow during tab-complete\r\n\r\nCurrently, when the user attempts symbol completion with the Tab key, kdb\nwill use strncpy() to insert the completed symbol into the command buffer.\nUnfortunately it passes the size of the source buffer rather than the\ndestination to strncpy() with predictably horrible results. Most obviously\nif the command buffer is already full but cp, the cursor position, is in\nthe middle of the buffer, then we will write past the end of the supplied\nbuffer.\r\n\r\nFix this by replacing the dubious strncpy() calls with memmove()/memcpy()\ncalls plus explicit boundary checks to make sure we have enough space\nbefore we start moving characters around.(CVE-2024-39480)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbonding: Fix out-of-bounds read in bond_option_arp_ip_targets_set()\r\n\r\nIn function bond_option_arp_ip_targets_set(), if newval-\u0026gt;string is an\nempty string, newval-\u0026gt;string+1 will point to the byte after the\nstring, causing an out-of-bound read.\r\n\r\nBUG: KASAN: slab-out-of-bounds in strlen+0x7d/0xa0 lib/string.c:418\nRead of size 1 at addr ffff8881119c4781 by task syz-executor665/8107\nCPU: 1 PID: 8107 Comm: syz-executor665 Not tainted 6.7.0-rc7 #1\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __dump_stack lib/dump_stack.c:88 [inline]\n dump_stack_lvl+0xd9/0x150 lib/dump_stack.c:106\n print_address_description mm/kasan/report.c:364 [inline]\n print_report+0xc1/0x5e0 mm/kasan/report.c:475\n kasan_report+0xbe/0xf0 mm/kasan/report.c:588\n strlen+0x7d/0xa0 lib/string.c:418\n __fortify_strlen include/linux/fortify-string.h:210 [inline]\n in4_pton+0xa3/0x3f0 net/core/utils.c:130\n bond_option_arp_ip_targets_set+0xc2/0x910\ndrivers/net/bonding/bond_options.c:1201\n __bond_opt_set+0x2a4/0x1030 drivers/net/bonding/bond_options.c:767\n __bond_opt_set_notify+0x48/0x150 drivers/net/bonding/bond_options.c:792\n bond_opt_tryset_rtnl+0xda/0x160 drivers/net/bonding/bond_options.c:817\n bonding_sysfs_store_option+0xa1/0x120 drivers/net/bonding/bond_sysfs.c:156\n dev_attr_store+0x54/0x80 drivers/base/core.c:2366\n sysfs_kf_write+0x114/0x170 fs/sysfs/file.c:136\n kernfs_fop_write_iter+0x337/0x500 fs/kernfs/file.c:334\n call_write_iter include/linux/fs.h:2020 [inline]\n new_sync_write fs/read_write.c:491 [inline]\n vfs_write+0x96a/0xd80 fs/read_write.c:584\n ksys_write+0x122/0x250 fs/read_write.c:637\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0x40/0x110 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x63/0x6b\n---[ end trace ]---\r\n\r\nFix it by adding a check of string length before using it.(CVE-2024-39487)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\narm64: asm-bug: Add .align 2 to the end of __BUG_ENTRY\r\n\r\nWhen CONFIG_DEBUG_BUGVERBOSE=n, we fail to add necessary padding bytes\nto bug_table entries, and as a result the last entry in a bug table will\nbe ignored, potentially leading to an unexpected panic(). All prior\nentries in the table will be handled correctly.\r\n\r\nThe arm64 ABI requires that struct fields of up to 8 bytes are\nnaturally-aligned, with padding added within a struct such that struct\nare suitably aligned within arrays.\r\n\r\nWhen CONFIG_DEBUG_BUGVERPOSE=y, the layout of a bug_entry is:\r\n\r\n\tstruct bug_entry {\n\t\tsigned int bug_addr_disp;\t// 4 bytes\n\t\tsigned int file_disp;\t// 4 bytes\n\t\tunsigned short line;\t\t// 2 bytes\n\t\tunsigned short flags;\t\t// 2 bytes\n\t}\r\n\r\n... with 12 bytes total, requiring 4-byte alignment.\r\n\r\nWhen CONFIG_DEBUG_BUGVERBOSE=n, the layout of a bug_entry is:\r\n\r\n\tstruct bug_entry {\n\t\tsigned int bug_addr_disp;\t// 4 bytes\n\t\tunsigned short flags;\t\t// 2 bytes\n\t\t\u0026lt; implicit padding \u0026gt;\t\t// 2 bytes\n\t}\r\n\r\n... with 8 bytes total, with 6 bytes of data and 2 bytes of trailing\npadding, requiring 4-byte alginment.\r\n\r\nWhen we create a bug_entry in assembly, we align the start of the entry\nto 4 bytes, which implicitly handles padding for any prior entries.\nHowever, we do not align the end of the entry, and so when\nCONFIG_DEBUG_BUGVERBOSE=n, the final entry lacks the trailing padding\nbytes.\r\n\r\nFor the main kernel image this is not a problem as find_bug() doesn\u0026apos;t\ndepend on the trailing padding bytes when searching for entries:\r\n\r\n\tfor (bug = __start___bug_table; bug \u0026lt; __stop___bug_table; ++bug)\n\t\tif (bugaddr == bug_addr(bug))\n\t\t\treturn bug;\r\n\r\nHowever for modules, module_bug_finalize() depends on the trailing\nbytes when calculating the number of entries:\r\n\r\n\tmod-\u0026gt;num_bugs = sechdrs[i].sh_size / sizeof(struct bug_entry);\r\n\r\n... and as the last bug_entry lacks the necessary padding bytes, this entry\nwill not be counted, e.g. in the case of a single entry:\r\n\r\n\tsechdrs[i].sh_size == 6\n\tsizeof(struct bug_entry) == 8;\r\n\r\n\tsechdrs[i].sh_size / sizeof(struct bug_entry) == 0;\r\n\r\nConsequently module_find_bug() will miss the last bug_entry when it does:\r\n\r\n\tfor (i = 0; i \u0026lt; mod-\u0026gt;num_bugs; ++i, ++bug)\n\t\tif (bugaddr == bug_addr(bug))\n\t\t\tgoto out;\r\n\r\n... which can lead to a kenrel panic due to an unhandled bug.\r\n\r\nThis can be demonstrated with the following module:\r\n\r\n\tstatic int __init buginit(void)\n\t{\n\t\tWARN(1, \u0026quot;hello\\n\u0026quot;);\n\t\treturn 0;\n\t}\r\n\r\n\tstatic void __exit bugexit(void)\n\t{\n\t}\r\n\r\n\tmodule_init(buginit);\n\tmodule_exit(bugexit);\n\tMODULE_LICENSE(\u0026quot;GPL\u0026quot;);\r\n\r\n... which will trigger a kernel panic when loaded:\r\n\r\n\t------------[ cut here ]------------\n\thello\n\tUnexpected kernel BRK exception at EL1\n\tInternal error: BRK handler: 00000000f2000800 [#1] PREEMPT SMP\n\tModules linked in: hello(O+)\n\tCPU: 0 PID: 50 Comm: insmod Tainted: G O 6.9.1 #8\n\tHardware name: linux,dummy-virt (DT)\n\tpstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n\tpc : buginit+0x18/0x1000 [hello]\n\tlr : buginit+0x18/0x1000 [hello]\n\tsp : ffff800080533ae0\n\tx29: ffff800080533ae0 x28: 0000000000000000 x27: 0000000000000000\n\tx26: ffffaba8c4e70510 x25: ffff800080533c30 x24: ffffaba8c4a28a58\n\tx23: 0000000000000000 x22: 0000000000000000 x21: ffff3947c0eab3c0\n\tx20: ffffaba8c4e3f000 x19: ffffaba846464000 x18: 0000000000000006\n\tx17: 0000000000000000 x16: ffffaba8c2492834 x15: 0720072007200720\n\tx14: 0720072007200720 x13: ffffaba8c49b27c8 x12: 0000000000000312\n\tx11: 0000000000000106 x10: ffffaba8c4a0a7c8 x9 : ffffaba8c49b27c8\n\tx8 : 00000000ffffefff x7 : ffffaba8c4a0a7c8 x6 : 80000000fffff000\n\tx5 : 0000000000000107 x4 : 0000000000000000 x3 : 0000000000000000\n\tx2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff3947c0eab3c0\n\tCall trace:\n\t buginit+0x18/0x1000 [hello]\n\t do_one_initcall+0x80/0x1c8\n\t do_init_module+0x60/0x218\n\t load_module+0x1ba4/0x1d70\n\t __do_sys_init_module+0x198/0x1d0\n\t __arm64_sys_init_module+0x1c/0x28\n\t invoke_syscall+0x48/0x114\n\t el0_svc\n---truncated---(CVE-2024-39488)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nipv6: sr: fix memleak in seg6_hmac_init_algo\r\n\r\nseg6_hmac_init_algo returns without cleaning up the previous allocations\nif one fails, so it\u0026apos;s going to leak all that memory and the crypto tfms.\r\n\r\nUpdate seg6_hmac_exit to only free the memory when allocated, so we can\nreuse the code directly.(CVE-2024-39489)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsock_map: avoid race between sock_map_close and sk_psock_put\r\n\r\nsk_psock_get will return NULL if the refcount of psock has gone to 0, which\nwill happen when the last call of sk_psock_put is done. However,\nsk_psock_drop may not have finished yet, so the close callback will still\npoint to sock_map_close despite psock being NULL.\r\n\r\nThis can be reproduced with a thread deleting an element from the sock map,\nwhile the second one creates a socket, adds it to the map and closes it.\r\n\r\nThat will trigger the WARN_ON_ONCE:\r\n\r\n------------[ cut here ]------------\nWARNING: CPU: 1 PID: 7220 at net/core/sock_map.c:1701 sock_map_close+0x2a2/0x2d0 net/core/sock_map.c:1701\nModules linked in:\nCPU: 1 PID: 7220 Comm: syz-executor380 Not tainted 6.9.0-syzkaller-07726-g3c999d1ae3c7 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024\nRIP: 0010:sock_map_close+0x2a2/0x2d0 net/core/sock_map.c:1701\nCode: df e8 92 29 88 f8 48 8b 1b 48 89 d8 48 c1 e8 03 42 80 3c 20 00 74 08 48 89 df e8 79 29 88 f8 4c 8b 23 eb 89 e8 4f 15 23 f8 90 \u0026lt;0f\u0026gt; 0b 90 48 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f 5d e9 13 26 3d 02\nRSP: 0018:ffffc9000441fda8 EFLAGS: 00010293\nRAX: ffffffff89731ae1 RBX: ffffffff94b87540 RCX: ffff888029470000\nRDX: 0000000000000000 RSI: ffffffff8bcab5c0 RDI: ffffffff8c1faba0\nRBP: 0000000000000000 R08: ffffffff92f9b61f R09: 1ffffffff25f36c3\nR10: dffffc0000000000 R11: fffffbfff25f36c4 R12: ffffffff89731840\nR13: ffff88804b587000 R14: ffff88804b587000 R15: ffffffff89731870\nFS: 000055555e080380(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000000 CR3: 00000000207d4000 CR4: 0000000000350ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n unix_release+0x87/0xc0 net/unix/af_unix.c:1048\n __sock_release net/socket.c:659 [inline]\n sock_close+0xbe/0x240 net/socket.c:1421\n __fput+0x42b/0x8a0 fs/file_table.c:422\n __do_sys_close fs/open.c:1556 [inline]\n __se_sys_close fs/open.c:1541 [inline]\n __x64_sys_close+0x7f/0x110 fs/open.c:1541\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7fb37d618070\nCode: 00 00 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d4 e8 10 2c 00 00 80 3d 31 f0 07 00 00 74 17 b8 03 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 48 c3 0f 1f 80 00 00 00 00 48 83 ec 18 89 7c\nRSP: 002b:00007ffcd4a525d8 EFLAGS: 00000202 ORIG_RAX: 0000000000000003\nRAX: ffffffffffffffda RBX: 0000000000000005 RCX: 00007fb37d618070\nRDX: 0000000000000010 RSI: 00000000200001c0 RDI: 0000000000000004\nRBP: 0000000000000000 R08: 0000000100000000 R09: 0000000100000000\nR10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000000\nR13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000\n \u0026lt;/TASK\u0026gt;\r\n\r\nUse sk_psock, which will only check that the pointer is not been set to\nNULL yet, which should only happen after the callbacks are restored. If,\nthen, a reference can still be gotten, we may call sk_psock_stop and cancel\npsock-\u0026gt;work.\r\n\r\nAs suggested by Paolo Abeni, reorder the condition so the control flow is\nless convoluted.\r\n\r\nAfter that change, the reproducer does not trigger the WARN_ON_ONCE\nanymore.(CVE-2024-39500)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nionic: fix use after netif_napi_del()\r\n\r\nWhen queues are started, netif_napi_add() and napi_enable() are called.\nIf there are 4 queues and only 3 queues are used for the current\nconfiguration, only 3 queues\u0026apos; napi should be registered and enabled.\nThe ionic_qcq_enable() checks whether the .poll pointer is not NULL for\nenabling only the using queue\u0026apos; napi. Unused queues\u0026apos; napi will not be\nregistered by netif_napi_add(), so the .poll pointer indicates NULL.\nBut it couldn\u0026apos;t distinguish whether the napi was unregistered or not\nbecause netif_napi_del() doesn\u0026apos;t reset the .poll pointer to NULL.\nSo, ionic_qcq_enable() calls napi_enable() for the queue, which was\nunregistered by netif_napi_del().\r\n\r\nReproducer:\n ethtool -L \u0026lt;interface name\u0026gt; rx 1 tx 1 combined 0\n ethtool -L \u0026lt;interface name\u0026gt; rx 0 tx 0 combined 1\n ethtool -L \u0026lt;interface name\u0026gt; rx 0 tx 0 combined 4\r\n\r\nSplat looks like:\nkernel BUG at net/core/dev.c:6666!\nOops: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI\nCPU: 3 PID: 1057 Comm: kworker/3:3 Not tainted 6.10.0-rc2+ #16\nWorkqueue: events ionic_lif_deferred_work [ionic]\nRIP: 0010:napi_enable+0x3b/0x40\nCode: 48 89 c2 48 83 e2 f6 80 b9 61 09 00 00 00 74 0d 48 83 bf 60 01 00 00 00 74 03 80 ce 01 f0 4f\nRSP: 0018:ffffb6ed83227d48 EFLAGS: 00010246\nRAX: 0000000000000000 RBX: ffff97560cda0828 RCX: 0000000000000029\nRDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff97560cda0a28\nRBP: ffffb6ed83227d50 R08: 0000000000000400 R09: 0000000000000001\nR10: 0000000000000001 R11: 0000000000000001 R12: 0000000000000000\nR13: ffff97560ce3c1a0 R14: 0000000000000000 R15: ffff975613ba0a20\nFS: 0000000000000000(0000) GS:ffff975d5f780000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f8f734ee200 CR3: 0000000103e50000 CR4: 00000000007506f0\nPKRU: 55555554\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ? die+0x33/0x90\n ? do_trap+0xd9/0x100\n ? napi_enable+0x3b/0x40\n ? do_error_trap+0x83/0xb0\n ? napi_enable+0x3b/0x40\n ? napi_enable+0x3b/0x40\n ? exc_invalid_op+0x4e/0x70\n ? napi_enable+0x3b/0x40\n ? asm_exc_invalid_op+0x16/0x20\n ? napi_enable+0x3b/0x40\n ionic_qcq_enable+0xb7/0x180 [ionic 59bdfc8a035436e1c4224ff7d10789e3f14643f8]\n ionic_start_queues+0xc4/0x290 [ionic 59bdfc8a035436e1c4224ff7d10789e3f14643f8]\n ionic_link_status_check+0x11c/0x170 [ionic 59bdfc8a035436e1c4224ff7d10789e3f14643f8]\n ionic_lif_deferred_work+0x129/0x280 [ionic 59bdfc8a035436e1c4224ff7d10789e3f14643f8]\n process_one_work+0x145/0x360\n worker_thread+0x2bb/0x3d0\n ? __pfx_worker_thread+0x10/0x10\n kthread+0xcc/0x100\n ? __pfx_kthread+0x10/0x10\n ret_from_fork+0x2d/0x50\n ? __pfx_kthread+0x10/0x10\n ret_from_fork_asm+0x1a/0x30(CVE-2024-39502)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmptcp: ensure snd_una is properly initialized on connect\r\n\r\nThis is strictly related to commit fb7a0d334894 (\u0026quot;mptcp: ensure snd_nxt\nis properly initialized on connect\u0026quot;). It turns out that syzkaller can\ntrigger the retransmit after fallback and before processing any other\nincoming packet - so that snd_una is still left uninitialized.\r\n\r\nAddress the issue explicitly initializing snd_una together with snd_nxt\nand write_seq.(CVE-2024-40931)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nHID: logitech-dj: Fix memory leak in logi_dj_recv_switch_to_dj_mode()\r\n\r\nFix a memory leak on logi_dj_recv_send_report() error path.(CVE-2024-40934)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nf2fs: remove clear SB_INLINECRYPT flag in default_options\r\n\r\nIn f2fs_remount, SB_INLINECRYPT flag will be clear and re-set.\nIf create new file or open file during this gap, these files\nwill not use inlinecrypt. Worse case, it may lead to data\ncorruption if wrappedkey_v0 is enable.\r\n\r\nThread A: Thread B:\r\n\r\n-f2fs_remount\t\t\t\t-f2fs_file_open or f2fs_new_inode\n -default_options\n\t\u0026lt;- clear SB_INLINECRYPT flag\r\n\r\n -fscrypt_select_encryption_impl\r\n\r\n -parse_options\n\t\u0026lt;- set SB_INLINECRYPT again(CVE-2024-40971)",
"id": "OESA-2024-1861",
"modified": "2026-08-06T11:07:19Z",
"published": "2024-07-19T11:07:19Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-1861"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-52755"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-34027"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-36478"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38540"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38558"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38570"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38586"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38605"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38632"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-39480"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-39487"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-39488"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-39489"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-39500"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-39502"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-40931"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-40934"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-40971"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "kernel security update",
"upstream": [
"CVE-2023-52755",
"CVE-2024-34027",
"CVE-2024-36478",
"CVE-2024-38540",
"CVE-2024-38558",
"CVE-2024-38570",
"CVE-2024-38586",
"CVE-2024-38605",
"CVE-2024-38632",
"CVE-2024-39480",
"CVE-2024-39487",
"CVE-2024-39488",
"CVE-2024-39489",
"CVE-2024-39500",
"CVE-2024-39502",
"CVE-2024-40931",
"CVE-2024-40934",
"CVE-2024-40971"
]
}
OESA-2024-2321 (CVE-2022-48916)
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:
iommu/vt-d: Fix double list_add when enabling VMD in scalable mode
When enabling VMD and IOMMU scalable mode, the following kernel panic call trace/kernel log is shown in Eagle Stream platform (Sapphire Rapids CPU) during booting:
pci 0000:59:00.5: Adding to iommu group 42 ... vmd 0000:59:00.5: PCI host bridge to bus 10000:80 pci 10000:80:01.0: [8086:352a] type 01 class 0x060400 pci 10000:80:01.0: reg 0x10: [mem 0x00000000-0x0001ffff 64bit] pci 10000:80:01.0: enabling Extended Tags pci 10000:80:01.0: PME# supported from D0 D3hot D3cold pci 10000:80:01.0: DMAR: Setup RID2PASID failed pci 10000:80:01.0: Failed to add to iommu group 42: -16 pci 10000:80:03.0: [8086:352b] type 01 class 0x060400 pci 10000:80:03.0: reg 0x10: [mem 0x00000000-0x0001ffff 64bit] pci 10000:80:03.0: enabling Extended Tags pci 10000:80:03.0: PME# supported from D0 D3hot D3cold ------------[ cut here ]------------ kernel BUG at lib/list_debug.c:29! invalid opcode: 0000 [#1] PREEMPT SMP NOPTI CPU: 0 PID: 7 Comm: kworker/0:1 Not tainted 5.17.0-rc3+ #7 Hardware name: Lenovo ThinkSystem SR650V3/SB27A86647, BIOS ESE101Y-1.00 01/13/2022 Workqueue: events work_for_cpu_fn RIP: 0010:__list_add_valid.cold+0x26/0x3f Code: 9a 4a ab ff 4c 89 c1 48 c7 c7 40 0c d9 9e e8 b9 b1 fe ff 0f 0b 48 89 f2 4c 89 c1 48 89 fe 48 c7 c7 f0 0c d9 9e e8 a2 b1 fe ff <0f> 0b 48 89 d1 4c 89 c6 4c 89 ca 48 c7 c7 98 0c d9 9e e8 8b b1 fe RSP: 0000:ff5ad434865b3a40 EFLAGS: 00010246 RAX: 0000000000000058 RBX: ff4d61160b74b880 RCX: ff4d61255e1fffa8 RDX: 0000000000000000 RSI: 00000000fffeffff RDI: ffffffff9fd34f20 RBP: ff4d611d8e245c00 R08: 0000000000000000 R09: ff5ad434865b3888 R10: ff5ad434865b3880 R11: ff4d61257fdc6fe8 R12: ff4d61160b74b8a0 R13: ff4d61160b74b8a0 R14: ff4d611d8e245c10 R15: ff4d611d8001ba70 FS: 0000000000000000(0000) GS:ff4d611d5ea00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ff4d611fa1401000 CR3: 0000000aa0210001 CR4: 0000000000771ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: <TASK> intel_pasid_alloc_table+0x9c/0x1d0 dmar_insert_one_dev_info+0x423/0x540 ? device_to_iommu+0x12d/0x2f0 intel_iommu_attach_device+0x116/0x290 __iommu_attach_device+0x1a/0x90 iommu_group_add_device+0x190/0x2c0 __iommu_probe_device+0x13e/0x250 iommu_probe_device+0x24/0x150 iommu_bus_notifier+0x69/0x90 blocking_notifier_call_chain+0x5a/0x80 device_add+0x3db/0x7b0 ? arch_memremap_can_ram_remap+0x19/0x50 ? memremap+0x75/0x140 pci_device_add+0x193/0x1d0 pci_scan_single_device+0xb9/0xf0 pci_scan_slot+0x4c/0x110 pci_scan_child_bus_extend+0x3a/0x290 vmd_enable_domain.constprop.0+0x63e/0x820 vmd_probe+0x163/0x190 local_pci_probe+0x42/0x80 work_for_cpu_fn+0x13/0x20 process_one_work+0x1e2/0x3b0 worker_thread+0x1c4/0x3a0 ? rescuer_thread+0x370/0x370 kthread+0xc7/0xf0 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x1f/0x30 </TASK> Modules linked in: ---[ end trace 0000000000000000 ]--- ... Kernel panic - not syncing: Fatal exception Kernel Offset: 0x1ca00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) ---[ end Kernel panic - not syncing: Fatal exception ]---
The following 'lspci' output shows devices '10000:80:*' are subdevices of the VMD device 0000:59:00.5:
$ lspci ... 0000:59:00.5 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller (rev 20) ... 10000:80:01.0 PCI bridge: Intel Corporation Device 352a (rev 03) 10000:80:03.0 PCI bridge: Intel Corporation Device 352b (rev 03) 10000:80:05.0 PCI bridge: Intel Corporation Device 352c (rev 03) 10000:80:07.0 PCI bridge: Intel Corporation Device 352d (rev 03) 10000:81:00.0 Non-Volatile memory controller: Intel Corporation NVMe Datacenter SSD [3DNAND, Beta Rock Controller] 10000:82:00 ---truncated---(CVE-2022-48916)
In the Linux kernel, the following vulnerability has been resolved: PCI: mt7621: Add sentinel to quirks table Current driver is missing a sentinel in the struct soc_device_attribute array, which causes an oops when assessed by the soc_device_match(mt7621_pcie_quirks_match) call. This was only exposed once the CONFIG_SOC_MT7621 mt7621 soc_dev_attr was fixed to register the SOC as a device, in: commit 7c18b64bba3b ("mips: ralink: mt7621: do not use kzalloc too early") Fix it by adding the required sentinel.(CVE-2022-48952)
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:
of: module: prevent NULL pointer dereference in vsnprintf()
In of_modalias(), we can get passed the str and len parameters which would cause a kernel oops in vsnprintf() since it only allows passing a NULL ptr when the length is also 0. Also, we need to filter out the negative values of the len parameter as these will result in a really huge buffer since snprintf() takes size_t parameter while ours is ssize_t...
Found by Linux Verification Center (linuxtesting.org) with the Svace static analysis tool.(CVE-2024-35878)
In the Linux kernel, the following vulnerability has been resolved:
dma: xilinx_dpdma: Fix locking
There are several places where either chan->lock or chan->vchan.lock was not held. Add appropriate locking. This fixes lockdep warnings like
[ 31.077578] ------------[ cut here ]------------ [ 31.077831] WARNING: CPU: 2 PID: 40 at drivers/dma/xilinx/xilinx_dpdma.c:834 xilinx_dpdma_chan_queue_transfer+0x274/0x5e0 [ 31.077953] Modules linked in: [ 31.078019] CPU: 2 PID: 40 Comm: kworker/u12:1 Not tainted 6.6.20+ #98 [ 31.078102] Hardware name: xlnx,zynqmp (DT) [ 31.078169] Workqueue: events_unbound deferred_probe_work_func [ 31.078272] pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 31.078377] pc : xilinx_dpdma_chan_queue_transfer+0x274/0x5e0 [ 31.078473] lr : xilinx_dpdma_chan_queue_transfer+0x270/0x5e0 [ 31.078550] sp : ffffffc083bb2e10 [ 31.078590] x29: ffffffc083bb2e10 x28: 0000000000000000 x27: ffffff880165a168 [ 31.078754] x26: ffffff880164e920 x25: ffffff880164eab8 x24: ffffff880164d480 [ 31.078920] x23: ffffff880165a148 x22: ffffff880164e988 x21: 0000000000000000 [ 31.079132] x20: ffffffc082aa3000 x19: ffffff880164e880 x18: 0000000000000000 [ 31.079295] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000 [ 31.079453] x14: 0000000000000000 x13: ffffff8802263dc0 x12: 0000000000000001 [ 31.079613] x11: 0001ffc083bb2e34 x10: 0001ff880164e98f x9 : 0001ffc082aa3def [ 31.079824] x8 : 0001ffc082aa3dec x7 : 0000000000000000 x6 : 0000000000000516 [ 31.079982] x5 : ffffffc7f8d43000 x4 : ffffff88003c9c40 x3 : ffffffffffffffff [ 31.080147] x2 : ffffffc7f8d43000 x1 : 00000000000000c0 x0 : 0000000000000000 [ 31.080307] Call trace: [ 31.080340] xilinx_dpdma_chan_queue_transfer+0x274/0x5e0 [ 31.080518] xilinx_dpdma_issue_pending+0x11c/0x120 [ 31.080595] zynqmp_disp_layer_update+0x180/0x3ac [ 31.080712] zynqmp_dpsub_plane_atomic_update+0x11c/0x21c [ 31.080825] drm_atomic_helper_commit_planes+0x20c/0x684 [ 31.080951] drm_atomic_helper_commit_tail+0x5c/0xb0 [ 31.081139] commit_tail+0x234/0x294 [ 31.081246] drm_atomic_helper_commit+0x1f8/0x210 [ 31.081363] drm_atomic_commit+0x100/0x140 [ 31.081477] drm_client_modeset_commit_atomic+0x318/0x384 [ 31.081634] drm_client_modeset_commit_locked+0x8c/0x24c [ 31.081725] drm_client_modeset_commit+0x34/0x5c [ 31.081812] __drm_fb_helper_restore_fbdev_mode_unlocked+0x104/0x168 [ 31.081899] drm_fb_helper_set_par+0x50/0x70 [ 31.081971] fbcon_init+0x538/0xc48 [ 31.082047] visual_init+0x16c/0x23c [ 31.082207] do_bind_con_driver.isra.0+0x2d0/0x634 [ 31.082320] do_take_over_console+0x24c/0x33c [ 31.082429] do_fbcon_takeover+0xbc/0x1b0 [ 31.082503] fbcon_fb_registered+0x2d0/0x34c [ 31.082663] register_framebuffer+0x27c/0x38c [ 31.082767] __drm_fb_helper_initial_config_and_unlock+0x5c0/0x91c [ 31.082939] drm_fb_helper_initial_config+0x50/0x74 [ 31.083012] drm_fbdev_dma_client_hotplug+0xb8/0x108 [ 31.083115] drm_client_register+0xa0/0xf4 [ 31.083195] drm_fbdev_dma_setup+0xb0/0x1cc [ 31.083293] zynqmp_dpsub_drm_init+0x45c/0x4e0 [ 31.083431] zynqmp_dpsub_probe+0x444/0x5e0 [ 31.083616] platform_probe+0x8c/0x13c [ 31.083713] really_probe+0x258/0x59c [ 31.083793] __driver_probe_device+0xc4/0x224 [ 31.083878] driver_probe_device+0x70/0x1c0 [ 31.083961] __device_attach_driver+0x108/0x1e0 [ 31.084052] bus_for_each_drv+0x9c/0x100 [ 31.084125] __device_attach+0x100/0x298 [ 31.084207] device_initial_probe+0x14/0x20 [ 31.084292] bus_probe_device+0xd8/0xdc [ 31.084368] deferred_probe_work_func+0x11c/0x180 [ 31.084451] process_one_work+0x3ac/0x988 [ 31.084643] worker_thread+0x398/0x694 [ 31.084752] kthread+0x1bc/0x1c0 [ 31.084848] ret_from_fork+0x10/0x20 [ 31.084932] irq event stamp: 64549 [ 31.084970] hardirqs last enabled at (64548): [<ffffffc081adf35c>] _raw_spin_unlock_irqrestore+0x80/0x90 [ 31.085157] ---truncated---(CVE-2024-35990)
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nfnetlink_queue: acquire rcu_read_lock() in instance_destroy_rcu()
syzbot reported that nf_reinject() could be called without rcu_read_lock() :
WARNING: suspicious RCU usage 6.9.0-rc7-syzkaller-02060-g5c1672705a1a #0 Not tainted
net/netfilter/nfnetlink_queue.c:263 suspicious rcu_dereference_check() usage!
other info that might help us debug this:
rcu_scheduler_active = 2, debug_locks = 1 2 locks held by syz-executor.4/13427: #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_lock_acquire include/linux/rcupdate.h:329 [inline] #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_do_batch kernel/rcu/tree.c:2190 [inline] #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_core+0xa86/0x1830 kernel/rcu/tree.c:2471 #1: ffff88801ca92958 (&inst->lock){+.-.}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:356 [inline] #1: ffff88801ca92958 (&inst->lock){+.-.}-{2:2}, at: nfqnl_flush net/netfilter/nfnetlink_queue.c:405 [inline] #1: ffff88801ca92958 (&inst->lock){+.-.}-{2:2}, at: instance_destroy_rcu+0x30/0x220 net/netfilter/nfnetlink_queue.c:172
stack backtrace: CPU: 0 PID: 13427 Comm: syz-executor.4 Not tainted 6.9.0-rc7-syzkaller-02060-g5c1672705a1a #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024 Call Trace: <IRQ> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114 lockdep_rcu_suspicious+0x221/0x340 kernel/locking/lockdep.c:6712 nf_reinject net/netfilter/nfnetlink_queue.c:323 [inline] nfqnl_reinject+0x6ec/0x1120 net/netfilter/nfnetlink_queue.c:397 nfqnl_flush net/netfilter/nfnetlink_queue.c:410 [inline] instance_destroy_rcu+0x1ae/0x220 net/netfilter/nfnetlink_queue.c:172 rcu_do_batch kernel/rcu/tree.c:2196 [inline] rcu_core+0xafd/0x1830 kernel/rcu/tree.c:2471 handle_softirqs+0x2d6/0x990 kernel/softirq.c:554 __do_softirq kernel/softirq.c:588 [inline] invoke_softirq kernel/softirq.c:428 [inline] __irq_exit_rcu+0xf4/0x1c0 kernel/softirq.c:637 irq_exit_rcu+0x9/0x30 kernel/softirq.c:649 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1043 [inline] sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1043 </IRQ> <TASK>(CVE-2024-36286)
In the Linux kernel, the following vulnerability has been resolved:
ALSA: core: Fix NULL module pointer assignment at card init
The commit 81033c6b584b ("ALSA: core: Warn on empty module") introduced a WARN_ON() for a NULL module pointer passed at snd_card object creation, and it also wraps the code around it with '#ifdef MODULE'. This works in most cases, but the devils are always in details. "MODULE" is defined when the target code (i.e. the sound core) is built as a module; but this doesn't mean that the caller is also built-in or not. Namely, when only the sound core is built-in (CONFIG_SND=y) while the driver is a module (CONFIG_SND_USB_AUDIO=m), the passed module pointer is ignored even if it's non-NULL, and card->module remains as NULL. This would result in the missing module reference up/down at the device open/close, leading to a race with the code execution after the module removal.
For addressing the bug, move the assignment of card->module again out of ifdef. The WARN_ON() is still wrapped with ifdef because the module can be really NULL when all sound drivers are built-in.
Note that we keep 'ifdef MODULE' for WARN_ON(), otherwise it would lead to a false-positive NULL module check. Admittedly it won't catch perfectly, i.e. no check is performed when CONFIG_SND=y. But, it's no real problem as it's only for debugging, and the condition is pretty rare.(CVE-2024-38605)
In the Linux kernel, the following vulnerability has been resolved:
soundwire: cadence: fix invalid PDI offset
For some reason, we add an offset to the PDI, presumably to skip the PDI0 and PDI1 which are reserved for BPT.
This code is however completely wrong and leads to an out-of-bounds access. We were just lucky so far since we used only a couple of PDIs and remained within the PDI array bounds.
A Fixes: tag is not provided since there are no known platforms where the out-of-bounds would be accessed, and the initial code had problems as well.
A follow-up patch completely removes this useless offset.(CVE-2024-38635)
In the Linux kernel, the following vulnerability has been resolved:
riscv: prevent pt_regs corruption for secondary idle threads
Top of the kernel thread stack should be reserved for pt_regs. However this is not the case for the idle threads of the secondary boot harts. Their stacks overlap with their pt_regs, so both may get corrupted.
Similar issue has been fixed for the primary hart, see c7cdd96eca28 ("riscv: prevent stack corruption by reserving task_pt_regs(p) early"). However that fix was not propagated to the secondary harts. The problem has been noticed in some CPU hotplug tests with V enabled. The function smp_callin stored several registers on stack, corrupting top of pt_regs structure including status field. As a result, kernel attempted to save or restore inexistent V context.(CVE-2024-38667)
In the Linux kernel, the following vulnerability has been resolved:
nvmet: fix a possible leak when destroy a ctrl during qp establishment
In nvmet_sq_destroy we capture sq->ctrl early and if it is non-NULL we know that a ctrl was allocated (in the admin connect request handler) and we need to release pending AERs, clear ctrl->sqs and sq->ctrl (for nvme-loop primarily), and drop the final reference on the ctrl.
However, a small window is possible where nvmet_sq_destroy starts (as a result of the client giving up and disconnecting) concurrently with the nvme admin connect cmd (which may be in an early stage). But before kill_and_confirm of sq->ref (i.e. the admin connect managed to get an sq live reference). In this case, sq->ctrl was allocated however after it was captured in a local variable in nvmet_sq_destroy. This prevented the final reference drop on the ctrl.
Solve this by re-capturing the sq->ctrl after all inflight request has completed, where for sure sq->ctrl reference is final, and move forward based on that.
This issue was observed in an environment with many hosts connecting multiple ctrls simoutanuosly, creating a delay in allocating a ctrl leading up to this race window.(CVE-2024-42152)
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:
exfat: fix potential deadlock on __exfat_get_dentry_set
When accessing a file with more entries than ES_MAX_ENTRY_NUM, the bh-array is allocated in __exfat_get_entry_set. The problem is that the bh-array is allocated with GFP_KERNEL. It does not make sense. In the following cases, a deadlock for sbi->s_lock between the two processes may occur.
CPU0 CPU1
---- ----
kswapd balance_pgdat lock(fs_reclaim) exfat_iterate lock(&sbi->s_lock) exfat_readdir exfat_get_uniname_from_ext_entry exfat_get_dentry_set __exfat_get_dentry_set kmalloc_array ... lock(fs_reclaim) ... evict exfat_evict_inode lock(&sbi->s_lock)
To fix this, let's allocate bh-array with GFP_NOFS.(CVE-2024-42315)
In the Linux kernel, the following vulnerability has been resolved:
wifi: virt_wifi: avoid reporting connection success with wrong SSID
When user issues a connection with a different SSID than the one virt_wifi has advertised, the __cfg80211_connect_result() will trigger the warning: WARN_ON(bss_not_found).
The issue is because the connection code in virt_wifi does not check the SSID from user space (it only checks the BSSID), and virt_wifi will call cfg80211_connect_result() with WLAN_STATUS_SUCCESS even if the SSID is different from the one virt_wifi has advertised. Eventually cfg80211 won't be able to find the cfg80211_bss and generate the warning.
Fixed it by checking the SSID (from user space) in the connection code.(CVE-2024-43841)
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/client: fix null pointer dereference in drm_client_modeset_probe
In drm_client_modeset_probe(), the return value of drm_mode_duplicate() is assigned to modeset->mode, which will lead to a possible NULL pointer dereference on failure of drm_mode_duplicate(). Add a check to avoid npd.(CVE-2024-43894)
In the Linux kernel, the following vulnerability has been resolved:
mptcp: pm: only decrement add_addr_accepted for MPJ req
Adding the following warning ...
WARN_ON_ONCE(msk->pm.add_addr_accepted == 0)
... before decrementing the add_addr_accepted counter helped to find a bug when running the "remove single subflow" subtest from the mptcp_join.sh selftest.
Removing a 'subflow' endpoint will first trigger a RM_ADDR, then the subflow closure. Before this patch, and upon the reception of the RM_ADDR, the other peer will then try to decrement this add_addr_accepted. That's not correct because the attached subflows have not been created upon the reception of an ADD_ADDR.
A way to solve that is to decrement the counter only if the attached subflow was an MP_JOIN to a remote id that was not 0, and initiated by the host receiving the RM_ADDR.(CVE-2024-45009)
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:
soc: qcom: cmd-db: Map shared memory as WC, not WB
Linux does not write into cmd-db region. This region of memory is write protected by XPU. XPU may sometime falsely detect clean cache eviction as "write" into the write protected region leading to secure interrupt which causes an endless loop somewhere in Trust Zone.
The only reason it is working right now is because Qualcomm Hypervisor maps the same region as Non-Cacheable memory in Stage 2 translation tables. The issue manifests if we want to use another hypervisor (like Xen or KVM), which does not know anything about those specific mappings.
Changing the mapping of cmd-db memory from MEMREMAP_WB to MEMREMAP_WT/WC removes dependency on correct mappings in Stage 2 tables. This patch fixes the issue by updating the mapping to MEMREMAP_WC.
I tested this on SA8155P with Xen.(CVE-2024-46689)
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: fix mc_data out-of-bounds read warning
Clear warning that read mc_data[i-1] may out-of-bounds.(CVE-2024-46722)
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:
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: 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:
KVM: x86: Acquire kvm->srcu when handling KVM_SET_VCPU_EVENTS
Grab kvm->srcu when processing KVM_SET_VCPU_EVENTS, as KVM will forcibly leave nested VMX/SVM if SMM mode is being toggled, and leaving nested VMX reads guest memory.
Note, kvm_vcpu_ioctl_x86_set_vcpu_events() can also be called from KVM_RUN via sync_regs(), which already holds SRCU. I.e. trying to precisely use kvm_vcpu_srcu_read_lock() around the problematic SMM code would cause problems. Acquiring SRCU isn't all that expensive, so for simplicity, grab it unconditionally for KVM_SET_VCPU_EVENTS.
============================= WARNING: suspicious RCU usage 6.10.0-rc7-332d2c1d713e-next-vm #552 Not tainted
include/linux/kvm_host.h:1027 suspicious rcu_dereference_check() usage!
other info that might help us debug this:
rcu_scheduler_active = 2, debug_locks = 1 1 lock held by repro/1071: #0: ffff88811e424430 (&vcpu->mutex){+.+.}-{3:3}, at: kvm_vcpu_ioctl+0x7d/0x970 [kvm]
stack backtrace: CPU: 15 PID: 1071 Comm: repro Not tainted 6.10.0-rc7-332d2c1d713e-next-vm #552 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 Call Trace: <TASK> dump_stack_lvl+0x7f/0x90 lockdep_rcu_suspicious+0x13f/0x1a0 kvm_vcpu_gfn_to_memslot+0x168/0x190 [kvm] kvm_vcpu_read_guest+0x3e/0x90 [kvm] nested_vmx_load_msr+0x6b/0x1d0 [kvm_intel] load_vmcs12_host_state+0x432/0xb40 [kvm_intel] vmx_leave_nested+0x30/0x40 [kvm_intel] kvm_vcpu_ioctl_x86_set_vcpu_events+0x15d/0x2b0 [kvm] kvm_arch_vcpu_ioctl+0x1107/0x1750 [kvm] ? mark_held_locks+0x49/0x70 ? kvm_vcpu_ioctl+0x7d/0x970 [kvm] ? kvm_vcpu_ioctl+0x497/0x970 [kvm] kvm_vcpu_ioctl+0x497/0x970 [kvm] ? lock_acquire+0xba/0x2d0 ? find_held_lock+0x2b/0x80 ? do_user_addr_fault+0x40c/0x6f0 ? lock_release+0xb7/0x270 __x64_sys_ioctl+0x82/0xb0 do_syscall_64+0x6c/0x170 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x7ff11eb1b539 </TASK>(CVE-2024-46830)
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:
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:
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: 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: 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: RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled Fix missuse of spin_lock_irq()/spin_unlock_irq() when spin_lock_irqsave()/spin_lock_irqrestore() was hold. This was discovered through the lock debugging, and the corresponding log is as follows: raw_local_irq_restore() called with IRQs enabled WARNING: CPU: 96 PID: 2074 at kernel/locking/irqflag-debug.c:10 warn_bogus_irq_restore+0x30/0x40 ... Call trace: warn_bogus_irq_restore+0x30/0x40 _raw_spin_unlock_irqrestore+0x84/0xc8 add_qp_to_list+0x11c/0x148 [hns_roce_hw_v2] hns_roce_create_qp_common.constprop.0+0x240/0x780 [hns_roce_hw_v2] hns_roce_create_qp+0x98/0x160 [hns_roce_hw_v2] create_qp+0x138/0x258 ib_create_qp_kernel+0x50/0xe8 create_mad_qp+0xa8/0x128 ib_mad_port_open+0x218/0x448 ib_mad_init_device+0x70/0x1f8 add_client_context+0xfc/0x220 enable_device_and_get+0xd0/0x140 ib_register_device.part.0+0xf4/0x1c8 ib_register_device+0x34/0x50 hns_roce_register_device+0x174/0x3d0 [hns_roce_hw_v2] hns_roce_init+0xfc/0x2c0 [hns_roce_hw_v2] __hns_roce_hw_v2_init_instance+0x7c/0x1d0 [hns_roce_hw_v2] hns_roce_hw_v2_init_instance+0x9c/0x180 hns_roce_hw_v2
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: 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: 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: nfsd: map the EBADMSG to nfserr_io to avoid warning Ext4 will throw -EBADMSG through ext4_readdir when a checksum error occurs, resulting in the following WARNING. Fix it by mapping EBADMSG to nfserr_io. nfsd_buffered_readdir iterate_dir // -EBADMSG -74 ext4_readdir // .iterate_shared ext4_dx_readdir ext4_htree_fill_tree htree_dirblock_to_tree ext4_read_dirblock __ext4_read_dirblock ext4_dirblock_csum_verify warn_no_space_for_csum __warn_no_space_for_csum return ERR_PTR(-EFSBADCRC) // -EBADMSG -74 nfserrno // WARNING [ 161.115610] ------------[ cut here ]------------ [ 161.116465] nfsd: non-standard errno: -74 [ 161.117315] WARNING: CPU: 1 PID: 780 at fs/nfsd/nfsproc.c:878 nfserrno+0x9d/0xd0 [ 161.118596] Modules linked in: [ 161.119243] CPU: 1 PID: 780 Comm: nfsd Not tainted 5.10.0-00014-g79679361fd5d #138 [ 161.120684] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qe mu.org 04/01/2014 [ 161.123601] RIP: 0010:nfserrno+0x9d/0xd0 [ 161.124676] Code: 0f 87 da 30 dd 00 83 e3 01 b8 00 00 00 05 75 d7 44 89 ee 48 c7 c7 c0 57 24 98 89 44 24 04 c6 05 ce 2b 61 03 01 e8 99 20 d8 00 <0f> 0b 8b 44 24 04 eb b5 4c 89 e6 48 c7 c7 a0 6d a4 99 e8 cc 15 33 [ 161.127797] RSP: 0018:ffffc90000e2f9c0 EFLAGS: 00010286 [ 161.128794] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 [ 161.130089] RDX: 1ffff1103ee16f6d RSI: 0000000000000008 RDI: fffff520001c5f2a [ 161.131379] RBP: 0000000000000022 R08: 0000000000000001 R09: ffff8881f70c1827 [ 161.132664] R10: ffffed103ee18304 R11: 0000000000000001 R12: 0000000000000021 [ 161.133949] R13: 00000000ffffffb6 R14: ffff8881317c0000 R15: ffffc90000e2fbd8 [ 161.135244] FS: 0000000000000000(0000) GS:ffff8881f7080000(0000) knlGS:0000000000000000 [ 161.136695] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 161.137761] CR2: 00007fcaad70b348 CR3: 0000000144256006 CR4: 0000000000770ee0 [ 161.139041] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 161.140291] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 161.141519] PKRU: 55555554 [ 161.142076] Call Trace: [ 161.142575] ? __warn+0x9b/0x140 [ 161.143229] ? nfserrno+0x9d/0xd0 [ 161.143872] ? report_bug+0x125/0x150 [ 161.144595] ? handle_bug+0x41/0x90 [ 161.145284] ? exc_invalid_op+0x14/0x70 [ 161.146009] ? asm_exc_invalid_op+0x12/0x20 [ 161.146816] ? nfserrno+0x9d/0xd0 [ 161.147487] nfsd_buffered_readdir+0x28b/0x2b0 [ 161.148333] ? nfsd4_encode_dirent_fattr+0x380/0x380 [ 161.149258] ? nfsd_buffered_filldir+0xf0/0xf0 [ 161.150093] ? wait_for_concurrent_writes+0x170/0x170 [ 161.151004] ? generic_file_llseek_size+0x48/0x160 [ 161.151895] nfsd_readdir+0x132/0x190 [ 161.152606] ? nfsd4_encode_dirent_fattr+0x380/0x380 [ 161.153516] ? nfsd_unlink+0x380/0x380 [ 161.154256] ? override_creds+0x45/0x60 [ 161.155006] nfsd4_encode_readdir+0x21a/0x3d0 [ 161.155850] ? nfsd4_encode_readlink+0x210/0x210 [ 161.156731] ? write_bytes_to_xdr_buf+0x97/0xe0 [ 161.157598] ? __write_bytes_to_xdr_buf+0xd0/0xd0 [ 161.158494] ? lock_downgrade+0x90/0x90 [ 161.159232] ? nfs4svc_decode_voidarg+0x10/0x10 [ 161.160092] nfsd4_encode_operation+0x15a/0x440 [ 161.160959] nfsd4_proc_compound+0x718/0xe90 [ 161.161818] nfsd_dispatch+0x18e/0x2c0 [ 161.162586] svc_process_common+0x786/0xc50 [ 161.163403] ? nfsd_svc+0x380/0x380 [ 161.164137] ? svc_printk+0x160/0x160 [ 161.164846] ? svc_xprt_do_enqueue.part.0+0x365/0x380 [ 161.165808] ? nfsd_svc+0x380/0x380 [ 161.166523] ? rcu_is_watching+0x23/0x40 [ 161.167309] svc_process+0x1a5/0x200 [ 161.168019] nfsd+0x1f5/0x380 [ 161.168663] ? nfsd_shutdown_threads+0x260/0x260 [ 161.169554] kthread+0x1c4/0x210 [ 161.170224] ? kthread_insert_work_sanity_check+0x80/0x80 [ 161.171246] ret_from_fork+0x1f/0x30(CVE-2024-49875)
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Initialize get_bytes_per_element's default to 1 Variables, used as denominators and maybe not assigned to other values, should not be 0. bytes_per_element_y & bytes_per_element_c are initialized by get_bytes_per_element() which should never return 0. This fixes 10 DIVIDE_BY_ZERO issues reported by Coverity.(CVE-2024-49892)
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix index out of bounds in degamma hardware format translation Fixes index out of bounds issue in cm_helper_translate_curve_to_degamma_hw_format function. 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/dcn10/dcn10_cm_common.c:594 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow 'output_tf->tf_pts.red' 1025 <= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:595 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow 'output_tf->tf_pts.green' 1025 <= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:596 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow 'output_tf->tf_pts.blue' 1025 <= s32max(CVE-2024-49894)
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: 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: jbd2: stop waiting for space when jbd2_cleanup_journal_tail() returns error In __jbd2_log_wait_for_space(), we might call jbd2_cleanup_journal_tail() to recover some journal space. But if an error occurs while executing jbd2_cleanup_journal_tail() (e.g., an EIO), we don't stop waiting for free space right away, we try other branches, and if j_committing_transaction is NULL (i.e., the tid is 0), we will get the following complain: ============================================ JBD2: I/O error when updating journal superblock for sdd-8. __jbd2_log_wait_for_space: needed 256 blocks and only had 217 space available __jbd2_log_wait_for_space: no way to get more journal space in sdd-8 ------------[ cut here ]------------ WARNING: CPU: 2 PID: 139804 at fs/jbd2/checkpoint.c:109 __jbd2_log_wait_for_space+0x251/0x2e0 Modules linked in: CPU: 2 PID: 139804 Comm: kworker/u8:3 Not tainted 6.6.0+ #1 RIP: 0010:__jbd2_log_wait_for_space+0x251/0x2e0 Call Trace: <TASK> add_transaction_credits+0x5d1/0x5e0 start_this_handle+0x1ef/0x6a0 jbd2__journal_start+0x18b/0x340 ext4_dirty_inode+0x5d/0xb0 __mark_inode_dirty+0xe4/0x5d0 generic_update_time+0x60/0x70 [...] ============================================ So only if jbd2_cleanup_journal_tail() returns 1, i.e., there is nothing to clean up at the moment, continue to try to reclaim free space in other ways. Note that this fix relies on commit 6f6a6fda2945 ("jbd2: fix ocfs2 corrupt when updating journal superblock fails") to make jbd2_cleanup_journal_tail return the correct error code.(CVE-2024-49959)
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: ocfs2: cancel dqi_sync_work before freeing oinfo ocfs2_global_read_info() will initialize and schedule dqi_sync_work at the end, if error occurs after successfully reading global quota, it will trigger the following warning with CONFIG_DEBUG_OBJECTS_* enabled: ODEBUG: free active (active state 0) object: 00000000d8b0ce28 object type: timer_list hint: qsync_work_fn+0x0/0x16c This reports that there is an active delayed work when freeing oinfo in error handling, so cancel dqi_sync_work first. BTW, return status instead of -1 when .read_file_info fails.(CVE-2024-49966)
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: 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: scsi: fnic: Move flush_work initialization out of if block After commit 379a58caa199 ("scsi: fnic: Move fnic_fnic_flush_tx() to a work queue"), it can happen that a work item is sent to an uninitialized work queue. This may has the effect that the item being queued is never actually queued, and any further actions depending on it will not proceed. The following warning is observed while the fnic driver is loaded: kernel: WARNING: CPU: 11 PID: 0 at ../kernel/workqueue.c:1524 __queue_work+0x373/0x410 kernel: <IRQ> kernel: queue_work_on+0x3a/0x50 kernel: fnic_wq_copy_cmpl_handler+0x54a/0x730 [fnic 62fbff0c42e7fb825c60a55cde2fb91facb2ed24] kernel: fnic_isr_msix_wq_copy+0x2d/0x60 [fnic 62fbff0c42e7fb825c60a55cde2fb91facb2ed24] kernel: __handle_irq_event_percpu+0x36/0x1a0 kernel: handle_irq_event_percpu+0x30/0x70 kernel: handle_irq_event+0x34/0x60 kernel: handle_edge_irq+0x7e/0x1a0 kernel: __common_interrupt+0x3b/0xb0 kernel: common_interrupt+0x58/0xa0 kernel: </IRQ> It has been observed that this may break the rediscovery of Fibre Channel devices after a temporary fabric failure. This patch fixes it by moving the work queue initialization out of an if block in fnic_probe().(CVE-2024-50025)
In the Linux kernel, the following vulnerability has been resolved: net: do not delay dst_entries_add() in dst_release() dst_entries_add() uses per-cpu data that might be freed at netns dismantle from ip6_route_net_exit() calling dst_entries_destroy() Before ip6_route_net_exit() can be called, we release all the dsts associated with this netns, via calls to dst_release(), which waits an rcu grace period before calling dst_destroy() dst_entries_add() use in dst_destroy() is racy, because dst_entries_destroy() could have been called already. Decrementing the number of dsts must happen sooner. Notes: 1) in CONFIG_XFRM case, dst_destroy() can call dst_release_immediate(child), this might also cause UAF if the child does not have DST_NOCOUNT set. IPSEC maintainers might take a look and see how to address this. 2) There is also discussion about removing this count of dst, which might happen in future kernels.(CVE-2024-50036)
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)
| URL | Type | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"bpftool-5.10.0-234.0.0.133.oe2203sp4.aarch64.rpm",
"bpftool-debuginfo-5.10.0-234.0.0.133.oe2203sp4.aarch64.rpm",
"kernel-5.10.0-234.0.0.133.oe2203sp4.aarch64.rpm",
"kernel-debuginfo-5.10.0-234.0.0.133.oe2203sp4.aarch64.rpm",
"kernel-debugsource-5.10.0-234.0.0.133.oe2203sp4.aarch64.rpm",
"kernel-devel-5.10.0-234.0.0.133.oe2203sp4.aarch64.rpm",
"kernel-headers-5.10.0-234.0.0.133.oe2203sp4.aarch64.rpm",
"kernel-source-5.10.0-234.0.0.133.oe2203sp4.aarch64.rpm",
"kernel-tools-5.10.0-234.0.0.133.oe2203sp4.aarch64.rpm",
"kernel-tools-debuginfo-5.10.0-234.0.0.133.oe2203sp4.aarch64.rpm",
"kernel-tools-devel-5.10.0-234.0.0.133.oe2203sp4.aarch64.rpm",
"perf-5.10.0-234.0.0.133.oe2203sp4.aarch64.rpm",
"perf-debuginfo-5.10.0-234.0.0.133.oe2203sp4.aarch64.rpm",
"python3-perf-5.10.0-234.0.0.133.oe2203sp4.aarch64.rpm",
"python3-perf-debuginfo-5.10.0-234.0.0.133.oe2203sp4.aarch64.rpm"
],
"src": [
"kernel-5.10.0-234.0.0.133.oe2203sp4.src.rpm"
],
"x86_64": [
"bpftool-5.10.0-234.0.0.133.oe2203sp4.x86_64.rpm",
"bpftool-debuginfo-5.10.0-234.0.0.133.oe2203sp4.x86_64.rpm",
"kernel-5.10.0-234.0.0.133.oe2203sp4.x86_64.rpm",
"kernel-debuginfo-5.10.0-234.0.0.133.oe2203sp4.x86_64.rpm",
"kernel-debugsource-5.10.0-234.0.0.133.oe2203sp4.x86_64.rpm",
"kernel-devel-5.10.0-234.0.0.133.oe2203sp4.x86_64.rpm",
"kernel-headers-5.10.0-234.0.0.133.oe2203sp4.x86_64.rpm",
"kernel-source-5.10.0-234.0.0.133.oe2203sp4.x86_64.rpm",
"kernel-tools-5.10.0-234.0.0.133.oe2203sp4.x86_64.rpm",
"kernel-tools-debuginfo-5.10.0-234.0.0.133.oe2203sp4.x86_64.rpm",
"kernel-tools-devel-5.10.0-234.0.0.133.oe2203sp4.x86_64.rpm",
"perf-5.10.0-234.0.0.133.oe2203sp4.x86_64.rpm",
"perf-debuginfo-5.10.0-234.0.0.133.oe2203sp4.x86_64.rpm",
"python3-perf-5.10.0-234.0.0.133.oe2203sp4.x86_64.rpm",
"python3-perf-debuginfo-5.10.0-234.0.0.133.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-234.0.0.133.oe2203sp4"
}
],
"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:\r\n\r\niommu/vt-d: Fix double list_add when enabling VMD in scalable mode\r\n\r\nWhen enabling VMD and IOMMU scalable mode, the following kernel panic\ncall trace/kernel log is shown in Eagle Stream platform (Sapphire Rapids\nCPU) during booting:\r\n\r\npci 0000:59:00.5: Adding to iommu group 42\n...\nvmd 0000:59:00.5: PCI host bridge to bus 10000:80\npci 10000:80:01.0: [8086:352a] type 01 class 0x060400\npci 10000:80:01.0: reg 0x10: [mem 0x00000000-0x0001ffff 64bit]\npci 10000:80:01.0: enabling Extended Tags\npci 10000:80:01.0: PME# supported from D0 D3hot D3cold\npci 10000:80:01.0: DMAR: Setup RID2PASID failed\npci 10000:80:01.0: Failed to add to iommu group 42: -16\npci 10000:80:03.0: [8086:352b] type 01 class 0x060400\npci 10000:80:03.0: reg 0x10: [mem 0x00000000-0x0001ffff 64bit]\npci 10000:80:03.0: enabling Extended Tags\npci 10000:80:03.0: PME# supported from D0 D3hot D3cold\n------------[ cut here ]------------\nkernel BUG at lib/list_debug.c:29!\ninvalid opcode: 0000 [#1] PREEMPT SMP NOPTI\nCPU: 0 PID: 7 Comm: kworker/0:1 Not tainted 5.17.0-rc3+ #7\nHardware name: Lenovo ThinkSystem SR650V3/SB27A86647, BIOS ESE101Y-1.00 01/13/2022\nWorkqueue: events work_for_cpu_fn\nRIP: 0010:__list_add_valid.cold+0x26/0x3f\nCode: 9a 4a ab ff 4c 89 c1 48 c7 c7 40 0c d9 9e e8 b9 b1 fe ff 0f\n 0b 48 89 f2 4c 89 c1 48 89 fe 48 c7 c7 f0 0c d9 9e e8 a2 b1\n fe ff \u0026lt;0f\u0026gt; 0b 48 89 d1 4c 89 c6 4c 89 ca 48 c7 c7 98 0c d9\n 9e e8 8b b1 fe\nRSP: 0000:ff5ad434865b3a40 EFLAGS: 00010246\nRAX: 0000000000000058 RBX: ff4d61160b74b880 RCX: ff4d61255e1fffa8\nRDX: 0000000000000000 RSI: 00000000fffeffff RDI: ffffffff9fd34f20\nRBP: ff4d611d8e245c00 R08: 0000000000000000 R09: ff5ad434865b3888\nR10: ff5ad434865b3880 R11: ff4d61257fdc6fe8 R12: ff4d61160b74b8a0\nR13: ff4d61160b74b8a0 R14: ff4d611d8e245c10 R15: ff4d611d8001ba70\nFS: 0000000000000000(0000) GS:ff4d611d5ea00000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: ff4d611fa1401000 CR3: 0000000aa0210001 CR4: 0000000000771ef0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\nPKRU: 55555554\nCall Trace:\n \u0026lt;TASK\u0026gt;\n intel_pasid_alloc_table+0x9c/0x1d0\n dmar_insert_one_dev_info+0x423/0x540\n ? device_to_iommu+0x12d/0x2f0\n intel_iommu_attach_device+0x116/0x290\n __iommu_attach_device+0x1a/0x90\n iommu_group_add_device+0x190/0x2c0\n __iommu_probe_device+0x13e/0x250\n iommu_probe_device+0x24/0x150\n iommu_bus_notifier+0x69/0x90\n blocking_notifier_call_chain+0x5a/0x80\n device_add+0x3db/0x7b0\n ? arch_memremap_can_ram_remap+0x19/0x50\n ? memremap+0x75/0x140\n pci_device_add+0x193/0x1d0\n pci_scan_single_device+0xb9/0xf0\n pci_scan_slot+0x4c/0x110\n pci_scan_child_bus_extend+0x3a/0x290\n vmd_enable_domain.constprop.0+0x63e/0x820\n vmd_probe+0x163/0x190\n local_pci_probe+0x42/0x80\n work_for_cpu_fn+0x13/0x20\n process_one_work+0x1e2/0x3b0\n worker_thread+0x1c4/0x3a0\n ? rescuer_thread+0x370/0x370\n kthread+0xc7/0xf0\n ? kthread_complete_and_exit+0x20/0x20\n ret_from_fork+0x1f/0x30\n \u0026lt;/TASK\u0026gt;\nModules linked in:\n---[ end trace 0000000000000000 ]---\n...\nKernel panic - not syncing: Fatal exception\nKernel Offset: 0x1ca00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)\n---[ end Kernel panic - not syncing: Fatal exception ]---\r\n\r\nThe following \u0026apos;lspci\u0026apos; output shows devices \u0026apos;10000:80:*\u0026apos; are subdevices of\nthe VMD device 0000:59:00.5:\r\n\r\n $ lspci\n ...\n 0000:59:00.5 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller (rev 20)\n ...\n 10000:80:01.0 PCI bridge: Intel Corporation Device 352a (rev 03)\n 10000:80:03.0 PCI bridge: Intel Corporation Device 352b (rev 03)\n 10000:80:05.0 PCI bridge: Intel Corporation Device 352c (rev 03)\n 10000:80:07.0 PCI bridge: Intel Corporation Device 352d (rev 03)\n 10000:81:00.0 Non-Volatile memory controller: Intel Corporation NVMe Datacenter SSD [3DNAND, Beta Rock Controller]\n 10000:82:00\n---truncated---(CVE-2022-48916)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: PCI: mt7621: Add sentinel to quirks table Current driver is missing a sentinel in the struct soc_device_attribute array, which causes an oops when assessed by the soc_device_match(mt7621_pcie_quirks_match) call. This was only exposed once the CONFIG_SOC_MT7621 mt7621 soc_dev_attr was fixed to register the SOC as a device, in: commit 7c18b64bba3b (\u0026quot;mips: ralink: mt7621: do not use kzalloc too early\u0026quot;) Fix it by adding the required sentinel.(CVE-2022-48952)\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\nof: module: prevent NULL pointer dereference in vsnprintf()\r\n\r\nIn of_modalias(), we can get passed the str and len parameters which would\ncause a kernel oops in vsnprintf() since it only allows passing a NULL ptr\nwhen the length is also 0. Also, we need to filter out the negative values\nof the len parameter as these will result in a really huge buffer since\nsnprintf() takes size_t parameter while ours is ssize_t...\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with the Svace static\nanalysis tool.(CVE-2024-35878)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndma: xilinx_dpdma: Fix locking\r\n\r\nThere are several places where either chan-\u0026gt;lock or chan-\u0026gt;vchan.lock was\nnot held. Add appropriate locking. This fixes lockdep warnings like\r\n\r\n[ 31.077578] ------------[ cut here ]------------\n[ 31.077831] WARNING: CPU: 2 PID: 40 at drivers/dma/xilinx/xilinx_dpdma.c:834 xilinx_dpdma_chan_queue_transfer+0x274/0x5e0\n[ 31.077953] Modules linked in:\n[ 31.078019] CPU: 2 PID: 40 Comm: kworker/u12:1 Not tainted 6.6.20+ #98\n[ 31.078102] Hardware name: xlnx,zynqmp (DT)\n[ 31.078169] Workqueue: events_unbound deferred_probe_work_func\n[ 31.078272] pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[ 31.078377] pc : xilinx_dpdma_chan_queue_transfer+0x274/0x5e0\n[ 31.078473] lr : xilinx_dpdma_chan_queue_transfer+0x270/0x5e0\n[ 31.078550] sp : ffffffc083bb2e10\n[ 31.078590] x29: ffffffc083bb2e10 x28: 0000000000000000 x27: ffffff880165a168\n[ 31.078754] x26: ffffff880164e920 x25: ffffff880164eab8 x24: ffffff880164d480\n[ 31.078920] x23: ffffff880165a148 x22: ffffff880164e988 x21: 0000000000000000\n[ 31.079132] x20: ffffffc082aa3000 x19: ffffff880164e880 x18: 0000000000000000\n[ 31.079295] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000\n[ 31.079453] x14: 0000000000000000 x13: ffffff8802263dc0 x12: 0000000000000001\n[ 31.079613] x11: 0001ffc083bb2e34 x10: 0001ff880164e98f x9 : 0001ffc082aa3def\n[ 31.079824] x8 : 0001ffc082aa3dec x7 : 0000000000000000 x6 : 0000000000000516\n[ 31.079982] x5 : ffffffc7f8d43000 x4 : ffffff88003c9c40 x3 : ffffffffffffffff\n[ 31.080147] x2 : ffffffc7f8d43000 x1 : 00000000000000c0 x0 : 0000000000000000\n[ 31.080307] Call trace:\n[ 31.080340] xilinx_dpdma_chan_queue_transfer+0x274/0x5e0\n[ 31.080518] xilinx_dpdma_issue_pending+0x11c/0x120\n[ 31.080595] zynqmp_disp_layer_update+0x180/0x3ac\n[ 31.080712] zynqmp_dpsub_plane_atomic_update+0x11c/0x21c\n[ 31.080825] drm_atomic_helper_commit_planes+0x20c/0x684\n[ 31.080951] drm_atomic_helper_commit_tail+0x5c/0xb0\n[ 31.081139] commit_tail+0x234/0x294\n[ 31.081246] drm_atomic_helper_commit+0x1f8/0x210\n[ 31.081363] drm_atomic_commit+0x100/0x140\n[ 31.081477] drm_client_modeset_commit_atomic+0x318/0x384\n[ 31.081634] drm_client_modeset_commit_locked+0x8c/0x24c\n[ 31.081725] drm_client_modeset_commit+0x34/0x5c\n[ 31.081812] __drm_fb_helper_restore_fbdev_mode_unlocked+0x104/0x168\n[ 31.081899] drm_fb_helper_set_par+0x50/0x70\n[ 31.081971] fbcon_init+0x538/0xc48\n[ 31.082047] visual_init+0x16c/0x23c\n[ 31.082207] do_bind_con_driver.isra.0+0x2d0/0x634\n[ 31.082320] do_take_over_console+0x24c/0x33c\n[ 31.082429] do_fbcon_takeover+0xbc/0x1b0\n[ 31.082503] fbcon_fb_registered+0x2d0/0x34c\n[ 31.082663] register_framebuffer+0x27c/0x38c\n[ 31.082767] __drm_fb_helper_initial_config_and_unlock+0x5c0/0x91c\n[ 31.082939] drm_fb_helper_initial_config+0x50/0x74\n[ 31.083012] drm_fbdev_dma_client_hotplug+0xb8/0x108\n[ 31.083115] drm_client_register+0xa0/0xf4\n[ 31.083195] drm_fbdev_dma_setup+0xb0/0x1cc\n[ 31.083293] zynqmp_dpsub_drm_init+0x45c/0x4e0\n[ 31.083431] zynqmp_dpsub_probe+0x444/0x5e0\n[ 31.083616] platform_probe+0x8c/0x13c\n[ 31.083713] really_probe+0x258/0x59c\n[ 31.083793] __driver_probe_device+0xc4/0x224\n[ 31.083878] driver_probe_device+0x70/0x1c0\n[ 31.083961] __device_attach_driver+0x108/0x1e0\n[ 31.084052] bus_for_each_drv+0x9c/0x100\n[ 31.084125] __device_attach+0x100/0x298\n[ 31.084207] device_initial_probe+0x14/0x20\n[ 31.084292] bus_probe_device+0xd8/0xdc\n[ 31.084368] deferred_probe_work_func+0x11c/0x180\n[ 31.084451] process_one_work+0x3ac/0x988\n[ 31.084643] worker_thread+0x398/0x694\n[ 31.084752] kthread+0x1bc/0x1c0\n[ 31.084848] ret_from_fork+0x10/0x20\n[ 31.084932] irq event stamp: 64549\n[ 31.084970] hardirqs last enabled at (64548): [\u0026lt;ffffffc081adf35c\u0026gt;] _raw_spin_unlock_irqrestore+0x80/0x90\n[ 31.085157]\n---truncated---(CVE-2024-35990)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: nfnetlink_queue: acquire rcu_read_lock() in instance_destroy_rcu()\r\n\r\nsyzbot reported that nf_reinject() could be called without rcu_read_lock() :\r\n\r\nWARNING: suspicious RCU usage\n6.9.0-rc7-syzkaller-02060-g5c1672705a1a #0 Not tainted\r\n\r\nnet/netfilter/nfnetlink_queue.c:263 suspicious rcu_dereference_check() usage!\r\n\r\nother info that might help us debug this:\r\n\r\nrcu_scheduler_active = 2, debug_locks = 1\n2 locks held by syz-executor.4/13427:\n #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_lock_acquire include/linux/rcupdate.h:329 [inline]\n #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_do_batch kernel/rcu/tree.c:2190 [inline]\n #0: ffffffff8e334f60 (rcu_callback){....}-{0:0}, at: rcu_core+0xa86/0x1830 kernel/rcu/tree.c:2471\n #1: ffff88801ca92958 (\u0026amp;inst-\u0026gt;lock){+.-.}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:356 [inline]\n #1: ffff88801ca92958 (\u0026amp;inst-\u0026gt;lock){+.-.}-{2:2}, at: nfqnl_flush net/netfilter/nfnetlink_queue.c:405 [inline]\n #1: ffff88801ca92958 (\u0026amp;inst-\u0026gt;lock){+.-.}-{2:2}, at: instance_destroy_rcu+0x30/0x220 net/netfilter/nfnetlink_queue.c:172\r\n\r\nstack backtrace:\nCPU: 0 PID: 13427 Comm: syz-executor.4 Not tainted 6.9.0-rc7-syzkaller-02060-g5c1672705a1a #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024\nCall Trace:\n \u0026lt;IRQ\u0026gt;\n __dump_stack lib/dump_stack.c:88 [inline]\n dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114\n lockdep_rcu_suspicious+0x221/0x340 kernel/locking/lockdep.c:6712\n nf_reinject net/netfilter/nfnetlink_queue.c:323 [inline]\n nfqnl_reinject+0x6ec/0x1120 net/netfilter/nfnetlink_queue.c:397\n nfqnl_flush net/netfilter/nfnetlink_queue.c:410 [inline]\n instance_destroy_rcu+0x1ae/0x220 net/netfilter/nfnetlink_queue.c:172\n rcu_do_batch kernel/rcu/tree.c:2196 [inline]\n rcu_core+0xafd/0x1830 kernel/rcu/tree.c:2471\n handle_softirqs+0x2d6/0x990 kernel/softirq.c:554\n __do_softirq kernel/softirq.c:588 [inline]\n invoke_softirq kernel/softirq.c:428 [inline]\n __irq_exit_rcu+0xf4/0x1c0 kernel/softirq.c:637\n irq_exit_rcu+0x9/0x30 kernel/softirq.c:649\n instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1043 [inline]\n sysvec_apic_timer_interrupt+0xa6/0xc0 arch/x86/kernel/apic/apic.c:1043\n \u0026lt;/IRQ\u0026gt;\n \u0026lt;TASK\u0026gt;(CVE-2024-36286)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nALSA: core: Fix NULL module pointer assignment at card init\r\n\r\nThe commit 81033c6b584b (\u0026quot;ALSA: core: Warn on empty module\u0026quot;)\nintroduced a WARN_ON() for a NULL module pointer passed at snd_card\nobject creation, and it also wraps the code around it with \u0026apos;#ifdef\nMODULE\u0026apos;. This works in most cases, but the devils are always in\ndetails. \u0026quot;MODULE\u0026quot; is defined when the target code (i.e. the sound\ncore) is built as a module; but this doesn\u0026apos;t mean that the caller is\nalso built-in or not. Namely, when only the sound core is built-in\n(CONFIG_SND=y) while the driver is a module (CONFIG_SND_USB_AUDIO=m),\nthe passed module pointer is ignored even if it\u0026apos;s non-NULL, and\ncard-\u0026gt;module remains as NULL. This would result in the missing module\nreference up/down at the device open/close, leading to a race with the\ncode execution after the module removal.\r\n\r\nFor addressing the bug, move the assignment of card-\u0026gt;module again out\nof ifdef. The WARN_ON() is still wrapped with ifdef because the\nmodule can be really NULL when all sound drivers are built-in.\r\n\r\nNote that we keep \u0026apos;ifdef MODULE\u0026apos; for WARN_ON(), otherwise it would\nlead to a false-positive NULL module check. Admittedly it won\u0026apos;t catch\nperfectly, i.e. no check is performed when CONFIG_SND=y. But, it\u0026apos;s no\nreal problem as it\u0026apos;s only for debugging, and the condition is pretty\nrare.(CVE-2024-38605)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsoundwire: cadence: fix invalid PDI offset\r\n\r\nFor some reason, we add an offset to the PDI, presumably to skip the\nPDI0 and PDI1 which are reserved for BPT.\r\n\r\nThis code is however completely wrong and leads to an out-of-bounds\naccess. We were just lucky so far since we used only a couple of PDIs\nand remained within the PDI array bounds.\r\n\r\nA Fixes: tag is not provided since there are no known platforms where\nthe out-of-bounds would be accessed, and the initial code had problems\nas well.\r\n\r\nA follow-up patch completely removes this useless offset.(CVE-2024-38635)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nriscv: prevent pt_regs corruption for secondary idle threads\r\n\r\nTop of the kernel thread stack should be reserved for pt_regs. However\nthis is not the case for the idle threads of the secondary boot harts.\nTheir stacks overlap with their pt_regs, so both may get corrupted.\r\n\r\nSimilar issue has been fixed for the primary hart, see c7cdd96eca28\n(\u0026quot;riscv: prevent stack corruption by reserving task_pt_regs(p) early\u0026quot;).\nHowever that fix was not propagated to the secondary harts. The problem\nhas been noticed in some CPU hotplug tests with V enabled. The function\nsmp_callin stored several registers on stack, corrupting top of pt_regs\nstructure including status field. As a result, kernel attempted to save\nor restore inexistent V context.(CVE-2024-38667)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnvmet: fix a possible leak when destroy a ctrl during qp establishment\r\n\r\nIn nvmet_sq_destroy we capture sq-\u0026gt;ctrl early and if it is non-NULL we\nknow that a ctrl was allocated (in the admin connect request handler)\nand we need to release pending AERs, clear ctrl-\u0026gt;sqs and sq-\u0026gt;ctrl\n(for nvme-loop primarily), and drop the final reference on the ctrl.\r\n\r\nHowever, a small window is possible where nvmet_sq_destroy starts (as\na result of the client giving up and disconnecting) concurrently with\nthe nvme admin connect cmd (which may be in an early stage). But *before*\nkill_and_confirm of sq-\u0026gt;ref (i.e. the admin connect managed to get an sq\nlive reference). In this case, sq-\u0026gt;ctrl was allocated however after it was\ncaptured in a local variable in nvmet_sq_destroy.\nThis prevented the final reference drop on the ctrl.\r\n\r\nSolve this by re-capturing the sq-\u0026gt;ctrl after all inflight request has\ncompleted, where for sure sq-\u0026gt;ctrl reference is final, and move forward\nbased on that.\r\n\r\nThis issue was observed in an environment with many hosts connecting\nmultiple ctrls simoutanuosly, creating a delay in allocating a ctrl\nleading up to this race window.(CVE-2024-42152)\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\nexfat: fix potential deadlock on __exfat_get_dentry_set\r\n\r\nWhen accessing a file with more entries than ES_MAX_ENTRY_NUM, the bh-array\nis allocated in __exfat_get_entry_set. The problem is that the bh-array is\nallocated with GFP_KERNEL. It does not make sense. In the following cases,\na deadlock for sbi-\u0026gt;s_lock between the two processes may occur.\r\n\r\n CPU0 CPU1\n ---- ----\n kswapd\n balance_pgdat\n lock(fs_reclaim)\n exfat_iterate\n lock(\u0026amp;sbi-\u0026gt;s_lock)\n exfat_readdir\n exfat_get_uniname_from_ext_entry\n exfat_get_dentry_set\n __exfat_get_dentry_set\n kmalloc_array\n ...\n lock(fs_reclaim)\n ...\n evict\n exfat_evict_inode\n lock(\u0026amp;sbi-\u0026gt;s_lock)\r\n\r\nTo fix this, let\u0026apos;s allocate bh-array with GFP_NOFS.(CVE-2024-42315)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: virt_wifi: avoid reporting connection success with wrong SSID\r\n\r\nWhen user issues a connection with a different SSID than the one\nvirt_wifi has advertised, the __cfg80211_connect_result() will\ntrigger the warning: WARN_ON(bss_not_found).\r\n\r\nThe issue is because the connection code in virt_wifi does not\ncheck the SSID from user space (it only checks the BSSID), and\nvirt_wifi will call cfg80211_connect_result() with WLAN_STATUS_SUCCESS\neven if the SSID is different from the one virt_wifi has advertised.\nEventually cfg80211 won\u0026apos;t be able to find the cfg80211_bss and generate\nthe warning.\r\n\r\nFixed it by checking the SSID (from user space) in the connection code.(CVE-2024-43841)\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/client: fix null pointer dereference in drm_client_modeset_probe\r\n\r\nIn drm_client_modeset_probe(), the return value of drm_mode_duplicate() is\nassigned to modeset-\u0026gt;mode, which will lead to a possible NULL pointer\ndereference on failure of drm_mode_duplicate(). Add a check to avoid npd.(CVE-2024-43894)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmptcp: pm: only decrement add_addr_accepted for MPJ req\r\n\r\nAdding the following warning ...\r\n\r\n WARN_ON_ONCE(msk-\u0026gt;pm.add_addr_accepted == 0)\r\n\r\n... before decrementing the add_addr_accepted counter helped to find a\nbug when running the \u0026quot;remove single subflow\u0026quot; subtest from the\nmptcp_join.sh selftest.\r\n\r\nRemoving a \u0026apos;subflow\u0026apos; endpoint will first trigger a RM_ADDR, then the\nsubflow closure. Before this patch, and upon the reception of the\nRM_ADDR, the other peer will then try to decrement this\nadd_addr_accepted. That\u0026apos;s not correct because the attached subflows have\nnot been created upon the reception of an ADD_ADDR.\r\n\r\nA way to solve that is to decrement the counter only if the attached\nsubflow was an MP_JOIN to a remote id that was not 0, and initiated by\nthe host receiving the RM_ADDR.(CVE-2024-45009)\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\nsoc: qcom: cmd-db: Map shared memory as WC, not WB\r\n\r\nLinux does not write into cmd-db region. This region of memory is write\nprotected by XPU. XPU may sometime falsely detect clean cache eviction\nas \u0026quot;write\u0026quot; into the write protected region leading to secure interrupt\nwhich causes an endless loop somewhere in Trust Zone.\r\n\r\nThe only reason it is working right now is because Qualcomm Hypervisor\nmaps the same region as Non-Cacheable memory in Stage 2 translation\ntables. The issue manifests if we want to use another hypervisor (like\nXen or KVM), which does not know anything about those specific mappings.\r\n\r\nChanging the mapping of cmd-db memory from MEMREMAP_WB to MEMREMAP_WT/WC\nremoves dependency on correct mappings in Stage 2 tables. This patch\nfixes the issue by updating the mapping to MEMREMAP_WC.\r\n\r\nI tested this on SA8155P with Xen.(CVE-2024-46689)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amdgpu: fix mc_data out-of-bounds read warning\r\n\r\nClear warning that read mc_data[i-1] may out-of-bounds.(CVE-2024-46722)\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\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: 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\nKVM: x86: Acquire kvm-\u0026gt;srcu when handling KVM_SET_VCPU_EVENTS\r\n\r\nGrab kvm-\u0026gt;srcu when processing KVM_SET_VCPU_EVENTS, as KVM will forcibly\nleave nested VMX/SVM if SMM mode is being toggled, and leaving nested VMX\nreads guest memory.\r\n\r\nNote, kvm_vcpu_ioctl_x86_set_vcpu_events() can also be called from KVM_RUN\nvia sync_regs(), which already holds SRCU. I.e. trying to precisely use\nkvm_vcpu_srcu_read_lock() around the problematic SMM code would cause\nproblems. Acquiring SRCU isn\u0026apos;t all that expensive, so for simplicity,\ngrab it unconditionally for KVM_SET_VCPU_EVENTS.\r\n\r\n =============================\n WARNING: suspicious RCU usage\n 6.10.0-rc7-332d2c1d713e-next-vm #552 Not tainted\n -----------------------------\n include/linux/kvm_host.h:1027 suspicious rcu_dereference_check() usage!\r\n\r\n other info that might help us debug this:\r\n\r\n rcu_scheduler_active = 2, debug_locks = 1\n 1 lock held by repro/1071:\n #0: ffff88811e424430 (\u0026amp;vcpu-\u0026gt;mutex){+.+.}-{3:3}, at: kvm_vcpu_ioctl+0x7d/0x970 [kvm]\r\n\r\n stack backtrace:\n CPU: 15 PID: 1071 Comm: repro Not tainted 6.10.0-rc7-332d2c1d713e-next-vm #552\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n Call Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x7f/0x90\n lockdep_rcu_suspicious+0x13f/0x1a0\n kvm_vcpu_gfn_to_memslot+0x168/0x190 [kvm]\n kvm_vcpu_read_guest+0x3e/0x90 [kvm]\n nested_vmx_load_msr+0x6b/0x1d0 [kvm_intel]\n load_vmcs12_host_state+0x432/0xb40 [kvm_intel]\n vmx_leave_nested+0x30/0x40 [kvm_intel]\n kvm_vcpu_ioctl_x86_set_vcpu_events+0x15d/0x2b0 [kvm]\n kvm_arch_vcpu_ioctl+0x1107/0x1750 [kvm]\n ? mark_held_locks+0x49/0x70\n ? kvm_vcpu_ioctl+0x7d/0x970 [kvm]\n ? kvm_vcpu_ioctl+0x497/0x970 [kvm]\n kvm_vcpu_ioctl+0x497/0x970 [kvm]\n ? lock_acquire+0xba/0x2d0\n ? find_held_lock+0x2b/0x80\n ? do_user_addr_fault+0x40c/0x6f0\n ? lock_release+0xb7/0x270\n __x64_sys_ioctl+0x82/0xb0\n do_syscall_64+0x6c/0x170\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n RIP: 0033:0x7ff11eb1b539\n \u0026lt;/TASK\u0026gt;(CVE-2024-46830)\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\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:\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: 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: 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: RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled Fix missuse of spin_lock_irq()/spin_unlock_irq() when spin_lock_irqsave()/spin_lock_irqrestore() was hold. This was discovered through the lock debugging, and the corresponding log is as follows: raw_local_irq_restore() called with IRQs enabled WARNING: CPU: 96 PID: 2074 at kernel/locking/irqflag-debug.c:10 warn_bogus_irq_restore+0x30/0x40 ... Call trace: warn_bogus_irq_restore+0x30/0x40 _raw_spin_unlock_irqrestore+0x84/0xc8 add_qp_to_list+0x11c/0x148 [hns_roce_hw_v2] hns_roce_create_qp_common.constprop.0+0x240/0x780 [hns_roce_hw_v2] hns_roce_create_qp+0x98/0x160 [hns_roce_hw_v2] create_qp+0x138/0x258 ib_create_qp_kernel+0x50/0xe8 create_mad_qp+0xa8/0x128 ib_mad_port_open+0x218/0x448 ib_mad_init_device+0x70/0x1f8 add_client_context+0xfc/0x220 enable_device_and_get+0xd0/0x140 ib_register_device.part.0+0xf4/0x1c8 ib_register_device+0x34/0x50 hns_roce_register_device+0x174/0x3d0 [hns_roce_hw_v2] hns_roce_init+0xfc/0x2c0 [hns_roce_hw_v2] __hns_roce_hw_v2_init_instance+0x7c/0x1d0 [hns_roce_hw_v2] hns_roce_hw_v2_init_instance+0x9c/0x180 [hns_roce_hw_v2](CVE-2024-47735)\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: 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: 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: nfsd: map the EBADMSG to nfserr_io to avoid warning Ext4 will throw -EBADMSG through ext4_readdir when a checksum error occurs, resulting in the following WARNING. Fix it by mapping EBADMSG to nfserr_io. nfsd_buffered_readdir iterate_dir // -EBADMSG -74 ext4_readdir // .iterate_shared ext4_dx_readdir ext4_htree_fill_tree htree_dirblock_to_tree ext4_read_dirblock __ext4_read_dirblock ext4_dirblock_csum_verify warn_no_space_for_csum __warn_no_space_for_csum return ERR_PTR(-EFSBADCRC) // -EBADMSG -74 nfserrno // WARNING [ 161.115610] ------------[ cut here ]------------ [ 161.116465] nfsd: non-standard errno: -74 [ 161.117315] WARNING: CPU: 1 PID: 780 at fs/nfsd/nfsproc.c:878 nfserrno+0x9d/0xd0 [ 161.118596] Modules linked in: [ 161.119243] CPU: 1 PID: 780 Comm: nfsd Not tainted 5.10.0-00014-g79679361fd5d #138 [ 161.120684] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qe mu.org 04/01/2014 [ 161.123601] RIP: 0010:nfserrno+0x9d/0xd0 [ 161.124676] Code: 0f 87 da 30 dd 00 83 e3 01 b8 00 00 00 05 75 d7 44 89 ee 48 c7 c7 c0 57 24 98 89 44 24 04 c6 05 ce 2b 61 03 01 e8 99 20 d8 00 \u0026lt;0f\u0026gt; 0b 8b 44 24 04 eb b5 4c 89 e6 48 c7 c7 a0 6d a4 99 e8 cc 15 33 [ 161.127797] RSP: 0018:ffffc90000e2f9c0 EFLAGS: 00010286 [ 161.128794] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 [ 161.130089] RDX: 1ffff1103ee16f6d RSI: 0000000000000008 RDI: fffff520001c5f2a [ 161.131379] RBP: 0000000000000022 R08: 0000000000000001 R09: ffff8881f70c1827 [ 161.132664] R10: ffffed103ee18304 R11: 0000000000000001 R12: 0000000000000021 [ 161.133949] R13: 00000000ffffffb6 R14: ffff8881317c0000 R15: ffffc90000e2fbd8 [ 161.135244] FS: 0000000000000000(0000) GS:ffff8881f7080000(0000) knlGS:0000000000000000 [ 161.136695] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 161.137761] CR2: 00007fcaad70b348 CR3: 0000000144256006 CR4: 0000000000770ee0 [ 161.139041] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 161.140291] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 161.141519] PKRU: 55555554 [ 161.142076] Call Trace: [ 161.142575] ? __warn+0x9b/0x140 [ 161.143229] ? nfserrno+0x9d/0xd0 [ 161.143872] ? report_bug+0x125/0x150 [ 161.144595] ? handle_bug+0x41/0x90 [ 161.145284] ? exc_invalid_op+0x14/0x70 [ 161.146009] ? asm_exc_invalid_op+0x12/0x20 [ 161.146816] ? nfserrno+0x9d/0xd0 [ 161.147487] nfsd_buffered_readdir+0x28b/0x2b0 [ 161.148333] ? nfsd4_encode_dirent_fattr+0x380/0x380 [ 161.149258] ? nfsd_buffered_filldir+0xf0/0xf0 [ 161.150093] ? wait_for_concurrent_writes+0x170/0x170 [ 161.151004] ? generic_file_llseek_size+0x48/0x160 [ 161.151895] nfsd_readdir+0x132/0x190 [ 161.152606] ? nfsd4_encode_dirent_fattr+0x380/0x380 [ 161.153516] ? nfsd_unlink+0x380/0x380 [ 161.154256] ? override_creds+0x45/0x60 [ 161.155006] nfsd4_encode_readdir+0x21a/0x3d0 [ 161.155850] ? nfsd4_encode_readlink+0x210/0x210 [ 161.156731] ? write_bytes_to_xdr_buf+0x97/0xe0 [ 161.157598] ? __write_bytes_to_xdr_buf+0xd0/0xd0 [ 161.158494] ? lock_downgrade+0x90/0x90 [ 161.159232] ? nfs4svc_decode_voidarg+0x10/0x10 [ 161.160092] nfsd4_encode_operation+0x15a/0x440 [ 161.160959] nfsd4_proc_compound+0x718/0xe90 [ 161.161818] nfsd_dispatch+0x18e/0x2c0 [ 161.162586] svc_process_common+0x786/0xc50 [ 161.163403] ? nfsd_svc+0x380/0x380 [ 161.164137] ? svc_printk+0x160/0x160 [ 161.164846] ? svc_xprt_do_enqueue.part.0+0x365/0x380 [ 161.165808] ? nfsd_svc+0x380/0x380 [ 161.166523] ? rcu_is_watching+0x23/0x40 [ 161.167309] svc_process+0x1a5/0x200 [ 161.168019] nfsd+0x1f5/0x380 [ 161.168663] ? nfsd_shutdown_threads+0x260/0x260 [ 161.169554] kthread+0x1c4/0x210 [ 161.170224] ? kthread_insert_work_sanity_check+0x80/0x80 [ 161.171246] ret_from_fork+0x1f/0x30(CVE-2024-49875)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Initialize get_bytes_per_element\u0026apos;s default to 1 Variables, used as denominators and maybe not assigned to other values, should not be 0. bytes_per_element_y \u0026amp; bytes_per_element_c are initialized by get_bytes_per_element() which should never return 0. This fixes 10 DIVIDE_BY_ZERO issues reported by Coverity.(CVE-2024-49892)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix index out of bounds in degamma hardware format translation Fixes index out of bounds issue in `cm_helper_translate_curve_to_degamma_hw_format` function. 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/dcn10/dcn10_cm_common.c:594 cm_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/dcn10/dcn10_cm_common.c:595 cm_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/dcn10/dcn10_cm_common.c:596 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow \u0026apos;output_tf-\u0026gt;tf_pts.blue\u0026apos; 1025 \u0026lt;= s32max(CVE-2024-49894)\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: 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: jbd2: stop waiting for space when jbd2_cleanup_journal_tail() returns error In __jbd2_log_wait_for_space(), we might call jbd2_cleanup_journal_tail() to recover some journal space. But if an error occurs while executing jbd2_cleanup_journal_tail() (e.g., an EIO), we don\u0026apos;t stop waiting for free space right away, we try other branches, and if j_committing_transaction is NULL (i.e., the tid is 0), we will get the following complain: ============================================ JBD2: I/O error when updating journal superblock for sdd-8. __jbd2_log_wait_for_space: needed 256 blocks and only had 217 space available __jbd2_log_wait_for_space: no way to get more journal space in sdd-8 ------------[ cut here ]------------ WARNING: CPU: 2 PID: 139804 at fs/jbd2/checkpoint.c:109 __jbd2_log_wait_for_space+0x251/0x2e0 Modules linked in: CPU: 2 PID: 139804 Comm: kworker/u8:3 Not tainted 6.6.0+ #1 RIP: 0010:__jbd2_log_wait_for_space+0x251/0x2e0 Call Trace: \u0026lt;TASK\u0026gt; add_transaction_credits+0x5d1/0x5e0 start_this_handle+0x1ef/0x6a0 jbd2__journal_start+0x18b/0x340 ext4_dirty_inode+0x5d/0xb0 __mark_inode_dirty+0xe4/0x5d0 generic_update_time+0x60/0x70 [...] ============================================ So only if jbd2_cleanup_journal_tail() returns 1, i.e., there is nothing to clean up at the moment, continue to try to reclaim free space in other ways. Note that this fix relies on commit 6f6a6fda2945 (\u0026quot;jbd2: fix ocfs2 corrupt when updating journal superblock fails\u0026quot;) to make jbd2_cleanup_journal_tail return the correct error code.(CVE-2024-49959)\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: ocfs2: cancel dqi_sync_work before freeing oinfo ocfs2_global_read_info() will initialize and schedule dqi_sync_work at the end, if error occurs after successfully reading global quota, it will trigger the following warning with CONFIG_DEBUG_OBJECTS_* enabled: ODEBUG: free active (active state 0) object: 00000000d8b0ce28 object type: timer_list hint: qsync_work_fn+0x0/0x16c This reports that there is an active delayed work when freeing oinfo in error handling, so cancel dqi_sync_work first. BTW, return status instead of -1 when .read_file_info fails.(CVE-2024-49966)\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: 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: scsi: fnic: Move flush_work initialization out of if block After commit 379a58caa199 (\u0026quot;scsi: fnic: Move fnic_fnic_flush_tx() to a work queue\u0026quot;), it can happen that a work item is sent to an uninitialized work queue. This may has the effect that the item being queued is never actually queued, and any further actions depending on it will not proceed. The following warning is observed while the fnic driver is loaded: kernel: WARNING: CPU: 11 PID: 0 at ../kernel/workqueue.c:1524 __queue_work+0x373/0x410 kernel: \u0026lt;IRQ\u0026gt; kernel: queue_work_on+0x3a/0x50 kernel: fnic_wq_copy_cmpl_handler+0x54a/0x730 [fnic 62fbff0c42e7fb825c60a55cde2fb91facb2ed24] kernel: fnic_isr_msix_wq_copy+0x2d/0x60 [fnic 62fbff0c42e7fb825c60a55cde2fb91facb2ed24] kernel: __handle_irq_event_percpu+0x36/0x1a0 kernel: handle_irq_event_percpu+0x30/0x70 kernel: handle_irq_event+0x34/0x60 kernel: handle_edge_irq+0x7e/0x1a0 kernel: __common_interrupt+0x3b/0xb0 kernel: common_interrupt+0x58/0xa0 kernel: \u0026lt;/IRQ\u0026gt; It has been observed that this may break the rediscovery of Fibre Channel devices after a temporary fabric failure. This patch fixes it by moving the work queue initialization out of an if block in fnic_probe().(CVE-2024-50025)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved: net: do not delay dst_entries_add() in dst_release() dst_entries_add() uses per-cpu data that might be freed at netns dismantle from ip6_route_net_exit() calling dst_entries_destroy() Before ip6_route_net_exit() can be called, we release all the dsts associated with this netns, via calls to dst_release(), which waits an rcu grace period before calling dst_destroy() dst_entries_add() use in dst_destroy() is racy, because dst_entries_destroy() could have been called already. Decrementing the number of dsts must happen sooner. Notes: 1) in CONFIG_XFRM case, dst_destroy() can call dst_release_immediate(child), this might also cause UAF if the child does not have DST_NOCOUNT set. IPSEC maintainers might take a look and see how to address this. 2) There is also discussion about removing this count of dst, which might happen in future kernels.(CVE-2024-50036)\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)",
"id": "OESA-2024-2321",
"modified": "2026-08-06T11:07:47Z",
"published": "2024-11-01T11:07:47Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2321"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48916"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48952"
},
{
"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-35878"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-35990"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-36286"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38605"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38635"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38667"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42152"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42301"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42315"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43841"
},
{
"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-43894"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-45009"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-46675"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-46689"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-46722"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-46724"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-46757"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-46802"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-46830"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-46853"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47667"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47669"
},
{
"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-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-47735"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47737"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-47757"
},
{
"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-49875"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49892"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49894"
},
{
"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-49927"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49959"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49965"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49966"
},
{
"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-49985"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50025"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50036"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50046"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50049"
}
],
"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-2022-48916",
"CVE-2022-48952",
"CVE-2023-52917",
"CVE-2023-52918",
"CVE-2024-35878",
"CVE-2024-35990",
"CVE-2024-36286",
"CVE-2024-38605",
"CVE-2024-38635",
"CVE-2024-38667",
"CVE-2024-42152",
"CVE-2024-42301",
"CVE-2024-42315",
"CVE-2024-43841",
"CVE-2024-43858",
"CVE-2024-43867",
"CVE-2024-43871",
"CVE-2024-43894",
"CVE-2024-45009",
"CVE-2024-46675",
"CVE-2024-46689",
"CVE-2024-46722",
"CVE-2024-46724",
"CVE-2024-46757",
"CVE-2024-46802",
"CVE-2024-46830",
"CVE-2024-46853",
"CVE-2024-47667",
"CVE-2024-47669",
"CVE-2024-47684",
"CVE-2024-47685",
"CVE-2024-47692",
"CVE-2024-47695",
"CVE-2024-47698",
"CVE-2024-47709",
"CVE-2024-47710",
"CVE-2024-47720",
"CVE-2024-47735",
"CVE-2024-47737",
"CVE-2024-47757",
"CVE-2024-49866",
"CVE-2024-49867",
"CVE-2024-49868",
"CVE-2024-49875",
"CVE-2024-49892",
"CVE-2024-49894",
"CVE-2024-49895",
"CVE-2024-49900",
"CVE-2024-49902",
"CVE-2024-49903",
"CVE-2024-49911",
"CVE-2024-49927",
"CVE-2024-49959",
"CVE-2024-49965",
"CVE-2024-49966",
"CVE-2024-49969",
"CVE-2024-49974",
"CVE-2024-49985",
"CVE-2024-50025",
"CVE-2024-50036",
"CVE-2024-50046",
"CVE-2024-50049"
]
}
UBUNTU-CVE-2024-38605 (CVE-2024-38605)
Vulnerability from osv_ubuntu – Published: 2024-06-19 14:15 – Updated: 2026-11-12 13:29 – Source websiteIn the Linux kernel, the following vulnerability has been resolved: ALSA: core: Fix NULL module pointer assignment at card init The commit 81033c6b584b ("ALSA: core: Warn on empty module") introduced a WARN_ON() for a NULL module pointer passed at snd_card object creation, and it also wraps the code around it with '#ifdef MODULE'. This works in most cases, but the devils are always in details. "MODULE" is defined when the target code (i.e. the sound core) is built as a module; but this doesn't mean that the caller is also built-in or not. Namely, when only the sound core is built-in (CONFIG_SND=y) while the driver is a module (CONFIG_SND_USB_AUDIO=m), the passed module pointer is ignored even if it's non-NULL, and card->module remains as NULL. This would result in the missing module reference up/down at the device open/close, leading to a race with the code execution after the module removal. For addressing the bug, move the assignment of card->module again out of ifdef. The WARN_ON() is still wrapped with ifdef because the module can be really NULL when all sound drivers are built-in. Note that we keep 'ifdef MODULE' for WARN_ON(), otherwise it would lead to a false-positive NULL module check. Admittedly it won't catch perfectly, i.e. no check is performed when CONFIG_SND=y. But, it's no real problem as it's only for debugging, and the condition is pretty rare.
| URL | Type | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
{
"affected": [
{
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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": {
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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": {
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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": {
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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": {
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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": {
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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": {
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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": {
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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": {
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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": "No subscription required",
"binaries": [
{
"binary_name": "linux-aws-5.15-cloud-tools-5.15.0-1069",
"binary_version": "5.15.0-1069.75~20.04.1"
},
{
"binary_name": "linux-aws-5.15-headers-5.15.0-1069",
"binary_version": "5.15.0-1069.75~20.04.1"
},
{
"binary_name": "linux-aws-5.15-tools-5.15.0-1069",
"binary_version": "5.15.0-1069.75~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.15.0-1069-aws",
"binary_version": "5.15.0-1069.75~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1069-aws",
"binary_version": "5.15.0-1069.75~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1069-aws",
"binary_version": "5.15.0-1069.75~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1069-aws",
"binary_version": "5.15.0-1069.75~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1069-aws",
"binary_version": "5.15.0-1069.75~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1069-aws",
"binary_version": "5.15.0-1069.75~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1069-aws",
"binary_version": "5.15.0-1069.75~20.04.1"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-aws-5.15",
"purl": "pkg:deb/ubuntu/linux-aws-5.15@5.15.0-1069.75~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1069.75~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"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-azure-5.15-cloud-tools-5.15.0-1072",
"binary_version": "5.15.0-1072.81~20.04.1"
},
{
"binary_name": "linux-azure-5.15-headers-5.15.0-1072",
"binary_version": "5.15.0-1072.81~20.04.1"
},
{
"binary_name": "linux-azure-5.15-tools-5.15.0-1072",
"binary_version": "5.15.0-1072.81~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81~20.04.1"
},
{
"binary_name": "linux-modules-involflt-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81~20.04.1"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-azure-5.15",
"purl": "pkg:deb/ubuntu/linux-azure-5.15@5.15.0-1072.81~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1072.81~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"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1068-gcp",
"binary_version": "5.15.0-1068.76~20.04.1"
},
{
"binary_name": "linux-gcp-5.15-headers-5.15.0-1068",
"binary_version": "5.15.0-1068.76~20.04.1"
},
{
"binary_name": "linux-gcp-5.15-tools-5.15.0-1068",
"binary_version": "5.15.0-1068.76~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1068-gcp",
"binary_version": "5.15.0-1068.76~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1068-gcp",
"binary_version": "5.15.0-1068.76~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1068-gcp",
"binary_version": "5.15.0-1068.76~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1068-gcp",
"binary_version": "5.15.0-1068.76~20.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-1068-gcp",
"binary_version": "5.15.0-1068.76~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1068-gcp",
"binary_version": "5.15.0-1068.76~20.04.1"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-gcp-5.15",
"purl": "pkg:deb/ubuntu/linux-gcp-5.15@5.15.0-1068.76~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1068.76~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"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1052-gkeop",
"binary_version": "5.15.0-1052.59~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1052-gkeop",
"binary_version": "5.15.0-1052.59~20.04.1"
},
{
"binary_name": "linux-gkeop-5.15-cloud-tools-5.15.0-1052",
"binary_version": "5.15.0-1052.59~20.04.1"
},
{
"binary_name": "linux-gkeop-5.15-headers-5.15.0-1052",
"binary_version": "5.15.0-1052.59~20.04.1"
},
{
"binary_name": "linux-gkeop-5.15-tools-5.15.0-1052",
"binary_version": "5.15.0-1052.59~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1052-gkeop",
"binary_version": "5.15.0-1052.59~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1052-gkeop",
"binary_version": "5.15.0-1052.59~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1052-gkeop",
"binary_version": "5.15.0-1052.59~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1052-gkeop",
"binary_version": "5.15.0-1052.59~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1052-gkeop",
"binary_version": "5.15.0-1052.59~20.04.1"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-gkeop-5.15",
"purl": "pkg:deb/ubuntu/linux-gkeop-5.15@5.15.0-1052.59~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1052.59~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"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-121-generic",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.15.0-121-generic-64k",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.15.0-121-generic-lpae",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-121-generic",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-121-generic",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-121-generic-64k",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-121-generic-lpae",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-hwe-5.15-cloud-tools-5.15.0-121",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-hwe-5.15-cloud-tools-common",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-hwe-5.15-headers-5.15.0-121",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-hwe-5.15-source-5.15.0",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-hwe-5.15-tools-5.15.0-121",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-hwe-5.15-tools-common",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-hwe-5.15-tools-host",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-image-5.15.0-121-generic",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-image-5.15.0-121-generic-lpae",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-121-generic",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-121-generic-64k",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-121-generic",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-121-generic-64k",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-121-generic-lpae",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-121-generic",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-121-generic",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-121-generic",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-121-generic-64k",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-121-generic-lpae",
"binary_version": "5.15.0-121.131~20.04.1"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-hwe-5.15",
"purl": "pkg:deb/ubuntu/linux-hwe-5.15@5.15.0-121.131~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-121.131~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"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1062-ibm",
"binary_version": "5.15.0-1062.65~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1062-ibm",
"binary_version": "5.15.0-1062.65~20.04.1"
},
{
"binary_name": "linux-ibm-5.15-headers-5.15.0-1062",
"binary_version": "5.15.0-1062.65~20.04.1"
},
{
"binary_name": "linux-ibm-5.15-source-5.15.0",
"binary_version": "5.15.0-1062.65~20.04.1"
},
{
"binary_name": "linux-ibm-5.15-tools-5.15.0-1062",
"binary_version": "5.15.0-1062.65~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1062-ibm",
"binary_version": "5.15.0-1062.65~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1062-ibm",
"binary_version": "5.15.0-1062.65~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1062-ibm",
"binary_version": "5.15.0-1062.65~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1062-ibm",
"binary_version": "5.15.0-1062.65~20.04.1"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-ibm-5.15",
"purl": "pkg:deb/ubuntu/linux-ibm-5.15@5.15.0-1062.65~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1062.65~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"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70~20.04.1"
},
{
"binary_name": "linux-intel-iotg-5.15-cloud-tools-5.15.0-1064",
"binary_version": "5.15.0-1064.70~20.04.1"
},
{
"binary_name": "linux-intel-iotg-5.15-cloud-tools-common",
"binary_version": "5.15.0-1064.70~20.04.1"
},
{
"binary_name": "linux-intel-iotg-5.15-headers-5.15.0-1064",
"binary_version": "5.15.0-1064.70~20.04.1"
},
{
"binary_name": "linux-intel-iotg-5.15-tools-5.15.0-1064",
"binary_version": "5.15.0-1064.70~20.04.1"
},
{
"binary_name": "linux-intel-iotg-5.15-tools-common",
"binary_version": "5.15.0-1064.70~20.04.1"
},
{
"binary_name": "linux-intel-iotg-5.15-tools-host",
"binary_version": "5.15.0-1064.70~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70~20.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70~20.04.1"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-intel-iotg-5.15",
"purl": "pkg:deb/ubuntu/linux-intel-iotg-5.15@5.15.0-1064.70~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1064.70~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"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-121-lowlatency",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.15.0-121-lowlatency-64k",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-121-lowlatency",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-121-lowlatency",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-121-lowlatency-64k",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-121-lowlatency",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-121-lowlatency-64k",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-5.15-cloud-tools-5.15.0-121",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-5.15-cloud-tools-common",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-5.15-headers-5.15.0-121",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-5.15-tools-5.15.0-121",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-5.15-tools-common",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-5.15-tools-host",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-121-lowlatency",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-121-lowlatency-64k",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-121-lowlatency",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-121-lowlatency",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-121-lowlatency-64k",
"binary_version": "5.15.0-121.131~20.04.1"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-lowlatency-hwe-5.15",
"purl": "pkg:deb/ubuntu/linux-lowlatency-hwe-5.15@5.15.0-121.131~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-121.131~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"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1030-nvidia-tegra",
"binary_version": "5.15.0-1030.30~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.15.0-1030-nvidia-tegra-rt",
"binary_version": "5.15.0-1030.30~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1030-nvidia-tegra",
"binary_version": "5.15.0-1030.30~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1030-nvidia-tegra-rt",
"binary_version": "5.15.0-1030.30~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1030-nvidia-tegra",
"binary_version": "5.15.0-1030.30~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1030-nvidia-tegra-rt",
"binary_version": "5.15.0-1030.30~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1030-nvidia-tegra",
"binary_version": "5.15.0-1030.30~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1030-nvidia-tegra-rt",
"binary_version": "5.15.0-1030.30~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1030-nvidia-tegra",
"binary_version": "5.15.0-1030.30~20.04.1"
},
{
"binary_name": "linux-nvidia-tegra-5.15-headers-5.15.0-1030",
"binary_version": "5.15.0-1030.30~20.04.1"
},
{
"binary_name": "linux-nvidia-tegra-5.15-tools-5.15.0-1030",
"binary_version": "5.15.0-1030.30~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1030-nvidia-tegra",
"binary_version": "5.15.0-1030.30~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1030-nvidia-tegra-rt",
"binary_version": "5.15.0-1030.30~20.04.1"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-nvidia-tegra-5.15",
"purl": "pkg:deb/ubuntu/linux-nvidia-tegra-5.15@5.15.0-1030.30~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1030.30~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"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1067-oracle",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1067-oracle",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1067-oracle",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1067-oracle",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1067-oracle",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-oracle-5.15-headers-5.15.0-1067",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-oracle-5.15-tools-5.15.0-1067",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1067-oracle",
"binary_version": "5.15.0-1067.73~20.04.1"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-oracle-5.15",
"purl": "pkg:deb/ubuntu/linux-oracle-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-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"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1065-generic",
"binary_version": "5.15.0-1065.69~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1065-generic",
"binary_version": "5.15.0-1065.69~20.04.1"
},
{
"binary_name": "linux-image-5.15.0-1065-generic",
"binary_version": "5.15.0-1065.69~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1065-generic",
"binary_version": "5.15.0-1065.69~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1065-generic",
"binary_version": "5.15.0-1065.69~20.04.1"
},
{
"binary_name": "linux-riscv-5.15-headers-5.15.0-1065",
"binary_version": "5.15.0-1065.69~20.04.1"
},
{
"binary_name": "linux-riscv-5.15-tools-5.15.0-1065",
"binary_version": "5.15.0-1065.69~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1065-generic",
"binary_version": "5.15.0-1065.69~20.04.1"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-riscv-5.15",
"purl": "pkg:deb/ubuntu/linux-riscv-5.15@5.15.0-1065.69~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1065.69~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"
]
},
{
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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": {
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-121-generic",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-buildinfo-5.15.0-121-generic-64k",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-buildinfo-5.15.0-121-generic-lpae",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-cloud-tools-5.15.0-121",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-cloud-tools-5.15.0-121-generic",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-cloud-tools-common",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-headers-5.15.0-121",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-headers-5.15.0-121-generic",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-headers-5.15.0-121-generic-64k",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-headers-5.15.0-121-generic-lpae",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-image-5.15.0-121-generic",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-image-5.15.0-121-generic-lpae",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-image-unsigned-5.15.0-121-generic",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-image-unsigned-5.15.0-121-generic-64k",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-modules-5.15.0-121-generic",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-modules-5.15.0-121-generic-64k",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-modules-5.15.0-121-generic-lpae",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-modules-extra-5.15.0-121-generic",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-121-generic",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-source-5.15.0",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-tools-5.15.0-121",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-tools-5.15.0-121-generic",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-tools-5.15.0-121-generic-64k",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-tools-5.15.0-121-generic-lpae",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-tools-common",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-tools-host",
"binary_version": "5.15.0-121.131"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux",
"purl": "pkg:deb/ubuntu/linux@5.15.0-121.131?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-121.131"
}
],
"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"
]
},
{
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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-1069",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-aws-headers-5.15.0-1069",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-aws-tools-5.15.0-1069",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-buildinfo-5.15.0-1069-aws",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1069-aws",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-headers-5.15.0-1069-aws",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1069-aws",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-modules-5.15.0-1069-aws",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-modules-extra-5.15.0-1069-aws",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-tools-5.15.0-1069-aws",
"binary_version": "5.15.0-1069.75"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-aws",
"purl": "pkg:deb/ubuntu/linux-aws@5.15.0-1069.75?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1069.75"
}
],
"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"
]
},
{
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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-1013",
"binary_version": "6.8.0-1013.14~22.04.1"
},
{
"binary_name": "linux-aws-6.8-headers-6.8.0-1013",
"binary_version": "6.8.0-1013.14~22.04.1"
},
{
"binary_name": "linux-aws-6.8-tools-6.8.0-1013",
"binary_version": "6.8.0-1013.14~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.8.0-1013-aws",
"binary_version": "6.8.0-1013.14~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.8.0-1013-aws",
"binary_version": "6.8.0-1013.14~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1013-aws",
"binary_version": "6.8.0-1013.14~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1013-aws",
"binary_version": "6.8.0-1013.14~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1013-aws",
"binary_version": "6.8.0-1013.14~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1013-aws",
"binary_version": "6.8.0-1013.14~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-1013-aws",
"binary_version": "6.8.0-1013.14~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1013-aws",
"binary_version": "6.8.0-1013.14~22.04.1"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-aws-6.8",
"purl": "pkg:deb/ubuntu/linux-aws-6.8@6.8.0-1013.14~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1013.14~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"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-azure-cloud-tools-5.15.0-1072",
"binary_version": "5.15.0-1072.81"
},
{
"binary_name": "linux-azure-headers-5.15.0-1072",
"binary_version": "5.15.0-1072.81"
},
{
"binary_name": "linux-azure-tools-5.15.0-1072",
"binary_version": "5.15.0-1072.81"
},
{
"binary_name": "linux-buildinfo-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81"
},
{
"binary_name": "linux-headers-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81"
},
{
"binary_name": "linux-modules-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81"
},
{
"binary_name": "linux-modules-extra-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81"
},
{
"binary_name": "linux-modules-involflt-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81"
},
{
"binary_name": "linux-tools-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-azure",
"purl": "pkg:deb/ubuntu/linux-azure@5.15.0-1072.81?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1072.81"
}
],
"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"
]
},
{
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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-1012",
"binary_version": "6.8.0-1012.14~22.04.1"
},
{
"binary_name": "linux-azure-6.8-headers-6.8.0-1012",
"binary_version": "6.8.0-1012.14~22.04.1"
},
{
"binary_name": "linux-azure-6.8-tools-6.8.0-1012",
"binary_version": "6.8.0-1012.14~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.8.0-1012-azure",
"binary_version": "6.8.0-1012.14~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.8.0-1012-azure",
"binary_version": "6.8.0-1012.14~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1012-azure",
"binary_version": "6.8.0-1012.14~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1012-azure",
"binary_version": "6.8.0-1012.14~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1012-azure",
"binary_version": "6.8.0-1012.14~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1012-azure",
"binary_version": "6.8.0-1012.14~22.04.1"
},
{
"binary_name": "linux-modules-involflt-6.8.0-1012-azure",
"binary_version": "6.8.0-1012.14~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-1012-azure",
"binary_version": "6.8.0-1012.14~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1012-azure",
"binary_version": "6.8.0-1012.14~22.04.1"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-azure-6.8",
"purl": "pkg:deb/ubuntu/linux-azure-6.8@6.8.0-1012.14~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1012.14~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"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-image-unsigned-5.15.0-1072-azure-fde",
"binary_version": "5.15.0-1072.81.1"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-azure-fde",
"purl": "pkg:deb/ubuntu/linux-azure-fde@5.15.0-1072.81.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1072.81.1"
}
],
"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"
]
},
{
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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-1068-gcp",
"binary_version": "5.15.0-1068.76"
},
{
"binary_name": "linux-gcp-headers-5.15.0-1068",
"binary_version": "5.15.0-1068.76"
},
{
"binary_name": "linux-gcp-tools-5.15.0-1068",
"binary_version": "5.15.0-1068.76"
},
{
"binary_name": "linux-headers-5.15.0-1068-gcp",
"binary_version": "5.15.0-1068.76"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1068-gcp",
"binary_version": "5.15.0-1068.76"
},
{
"binary_name": "linux-modules-5.15.0-1068-gcp",
"binary_version": "5.15.0-1068.76"
},
{
"binary_name": "linux-modules-extra-5.15.0-1068-gcp",
"binary_version": "5.15.0-1068.76"
},
{
"binary_name": "linux-tools-5.15.0-1068-gcp",
"binary_version": "5.15.0-1068.76"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-gcp",
"purl": "pkg:deb/ubuntu/linux-gcp@5.15.0-1068.76?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1068.76"
}
],
"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"
]
},
{
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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-1012-gcp",
"binary_version": "6.8.0-1012.13~22.04.1"
},
{
"binary_name": "linux-gcp-6.8-headers-6.8.0-1012",
"binary_version": "6.8.0-1012.13~22.04.1"
},
{
"binary_name": "linux-gcp-6.8-tools-6.8.0-1012",
"binary_version": "6.8.0-1012.13~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1012-gcp",
"binary_version": "6.8.0-1012.13~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1012-gcp",
"binary_version": "6.8.0-1012.13~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1012-gcp",
"binary_version": "6.8.0-1012.13~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1012-gcp",
"binary_version": "6.8.0-1012.13~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1012-gcp",
"binary_version": "6.8.0-1012.13~22.04.1"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-gcp-6.8",
"purl": "pkg:deb/ubuntu/linux-gcp-6.8@6.8.0-1012.13~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1012.13~22.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1010.11~22.04.1",
"6.8.0-1011.12~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1066-gke",
"binary_version": "5.15.0-1066.72"
},
{
"binary_name": "linux-gke-headers-5.15.0-1066",
"binary_version": "5.15.0-1066.72"
},
{
"binary_name": "linux-gke-tools-5.15.0-1066",
"binary_version": "5.15.0-1066.72"
},
{
"binary_name": "linux-headers-5.15.0-1066-gke",
"binary_version": "5.15.0-1066.72"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1066-gke",
"binary_version": "5.15.0-1066.72"
},
{
"binary_name": "linux-modules-5.15.0-1066-gke",
"binary_version": "5.15.0-1066.72"
},
{
"binary_name": "linux-modules-extra-5.15.0-1066-gke",
"binary_version": "5.15.0-1066.72"
},
{
"binary_name": "linux-tools-5.15.0-1066-gke",
"binary_version": "5.15.0-1066.72"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-gke",
"purl": "pkg:deb/ubuntu/linux-gke@5.15.0-1066.72?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1066.72"
}
],
"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"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1052-gkeop",
"binary_version": "5.15.0-1052.59"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1052-gkeop",
"binary_version": "5.15.0-1052.59"
},
{
"binary_name": "linux-gkeop-cloud-tools-5.15.0-1052",
"binary_version": "5.15.0-1052.59"
},
{
"binary_name": "linux-gkeop-headers-5.15.0-1052",
"binary_version": "5.15.0-1052.59"
},
{
"binary_name": "linux-gkeop-tools-5.15.0-1052",
"binary_version": "5.15.0-1052.59"
},
{
"binary_name": "linux-headers-5.15.0-1052-gkeop",
"binary_version": "5.15.0-1052.59"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1052-gkeop",
"binary_version": "5.15.0-1052.59"
},
{
"binary_name": "linux-modules-5.15.0-1052-gkeop",
"binary_version": "5.15.0-1052.59"
},
{
"binary_name": "linux-modules-extra-5.15.0-1052-gkeop",
"binary_version": "5.15.0-1052.59"
},
{
"binary_name": "linux-tools-5.15.0-1052-gkeop",
"binary_version": "5.15.0-1052.59"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-gkeop",
"purl": "pkg:deb/ubuntu/linux-gkeop@5.15.0-1052.59?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1052.59"
}
],
"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"
]
},
{
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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-40-generic",
"binary_version": "6.8.0-40.40~22.04.3"
},
{
"binary_name": "linux-buildinfo-6.8.0-40-generic-64k",
"binary_version": "6.8.0-40.40~22.04.3"
},
{
"binary_name": "linux-cloud-tools-6.8.0-40-generic",
"binary_version": "6.8.0-40.40~22.04.3"
},
{
"binary_name": "linux-headers-6.8.0-40-generic",
"binary_version": "6.8.0-40.40~22.04.3"
},
{
"binary_name": "linux-headers-6.8.0-40-generic-64k",
"binary_version": "6.8.0-40.40~22.04.3"
},
{
"binary_name": "linux-hwe-6.8-cloud-tools-6.8.0-40",
"binary_version": "6.8.0-40.40~22.04.3"
},
{
"binary_name": "linux-hwe-6.8-headers-6.8.0-40",
"binary_version": "6.8.0-40.40~22.04.3"
},
{
"binary_name": "linux-hwe-6.8-tools-6.8.0-40",
"binary_version": "6.8.0-40.40~22.04.3"
},
{
"binary_name": "linux-image-6.8.0-40-generic",
"binary_version": "6.8.0-40.40~22.04.3"
},
{
"binary_name": "linux-image-unsigned-6.8.0-40-generic",
"binary_version": "6.8.0-40.40~22.04.3"
},
{
"binary_name": "linux-image-unsigned-6.8.0-40-generic-64k",
"binary_version": "6.8.0-40.40~22.04.3"
},
{
"binary_name": "linux-modules-6.8.0-40-generic",
"binary_version": "6.8.0-40.40~22.04.3"
},
{
"binary_name": "linux-modules-6.8.0-40-generic-64k",
"binary_version": "6.8.0-40.40~22.04.3"
},
{
"binary_name": "linux-modules-extra-6.8.0-40-generic",
"binary_version": "6.8.0-40.40~22.04.3"
},
{
"binary_name": "linux-modules-ipu6-6.8.0-40-generic",
"binary_version": "6.8.0-40.40~22.04.3"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-40-generic",
"binary_version": "6.8.0-40.40~22.04.3"
},
{
"binary_name": "linux-modules-usbio-6.8.0-40-generic",
"binary_version": "6.8.0-40.40~22.04.3"
},
{
"binary_name": "linux-tools-6.8.0-40-generic",
"binary_version": "6.8.0-40.40~22.04.3"
},
{
"binary_name": "linux-tools-6.8.0-40-generic-64k",
"binary_version": "6.8.0-40.40~22.04.3"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-hwe-6.8",
"purl": "pkg:deb/ubuntu/linux-hwe-6.8@6.8.0-40.40~22.04.3?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-40.40~22.04.3"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-38.38~22.04.1",
"6.8.0-39.39~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1062-ibm",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-headers-5.15.0-1062-ibm",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-ibm-cloud-tools-common",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-ibm-headers-5.15.0-1062",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-ibm-source-5.15.0",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-ibm-tools-5.15.0-1062",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-ibm-tools-common",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1062-ibm",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-modules-5.15.0-1062-ibm",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-modules-extra-5.15.0-1062-ibm",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-tools-5.15.0-1062-ibm",
"binary_version": "5.15.0-1062.65"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-ibm",
"purl": "pkg:deb/ubuntu/linux-ibm@5.15.0-1062.65?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1062.65"
}
],
"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"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1010-ibm",
"binary_version": "6.8.0-1010.10~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1010-ibm",
"binary_version": "6.8.0-1010.10~22.04.1"
},
{
"binary_name": "linux-ibm-6.8-headers-6.8.0-1010",
"binary_version": "6.8.0-1010.10~22.04.1"
},
{
"binary_name": "linux-ibm-6.8-source-6.8.0",
"binary_version": "6.8.0-1010.10~22.04.1"
},
{
"binary_name": "linux-ibm-6.8-tools-6.8.0-1010",
"binary_version": "6.8.0-1010.10~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1010-ibm",
"binary_version": "6.8.0-1010.10~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1010-ibm",
"binary_version": "6.8.0-1010.10~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1010-ibm",
"binary_version": "6.8.0-1010.10~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-1010-ibm",
"binary_version": "6.8.0-1010.10~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1010-ibm",
"binary_version": "6.8.0-1010.10~22.04.1"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-ibm-6.8",
"purl": "pkg:deb/ubuntu/linux-ibm-6.8@6.8.0-1010.10~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1010.10~22.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1008.8~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70"
},
{
"binary_name": "linux-headers-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70"
},
{
"binary_name": "linux-intel-iotg-cloud-tools-5.15.0-1064",
"binary_version": "5.15.0-1064.70"
},
{
"binary_name": "linux-intel-iotg-cloud-tools-common",
"binary_version": "5.15.0-1064.70"
},
{
"binary_name": "linux-intel-iotg-headers-5.15.0-1064",
"binary_version": "5.15.0-1064.70"
},
{
"binary_name": "linux-intel-iotg-tools-5.15.0-1064",
"binary_version": "5.15.0-1064.70"
},
{
"binary_name": "linux-intel-iotg-tools-common",
"binary_version": "5.15.0-1064.70"
},
{
"binary_name": "linux-intel-iotg-tools-host",
"binary_version": "5.15.0-1064.70"
},
{
"binary_name": "linux-modules-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70"
},
{
"binary_name": "linux-modules-extra-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70"
},
{
"binary_name": "linux-tools-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-intel-iotg",
"purl": "pkg:deb/ubuntu/linux-intel-iotg@5.15.0-1064.70?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1064.70"
}
],
"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"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1066-kvm",
"binary_version": "5.15.0-1066.71"
},
{
"binary_name": "linux-headers-5.15.0-1066-kvm",
"binary_version": "5.15.0-1066.71"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1066-kvm",
"binary_version": "5.15.0-1066.71"
},
{
"binary_name": "linux-kvm-headers-5.15.0-1066",
"binary_version": "5.15.0-1066.71"
},
{
"binary_name": "linux-kvm-tools-5.15.0-1066",
"binary_version": "5.15.0-1066.71"
},
{
"binary_name": "linux-modules-5.15.0-1066-kvm",
"binary_version": "5.15.0-1066.71"
},
{
"binary_name": "linux-tools-5.15.0-1066-kvm",
"binary_version": "5.15.0-1066.71"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-kvm",
"purl": "pkg:deb/ubuntu/linux-kvm@5.15.0-1066.71?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1066.71"
}
],
"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"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-121-lowlatency",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-buildinfo-5.15.0-121-lowlatency-64k",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-cloud-tools-5.15.0-121-lowlatency",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-headers-5.15.0-121-lowlatency",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-headers-5.15.0-121-lowlatency-64k",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-image-unsigned-5.15.0-121-lowlatency",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-image-unsigned-5.15.0-121-lowlatency-64k",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-lowlatency-cloud-tools-5.15.0-121",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-lowlatency-cloud-tools-common",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-lowlatency-headers-5.15.0-121",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-lowlatency-tools-5.15.0-121",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-lowlatency-tools-common",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-lowlatency-tools-host",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-modules-5.15.0-121-lowlatency",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-modules-5.15.0-121-lowlatency-64k",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-121-lowlatency",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-tools-5.15.0-121-lowlatency",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-tools-5.15.0-121-lowlatency-64k",
"binary_version": "5.15.0-121.131"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-lowlatency",
"purl": "pkg:deb/ubuntu/linux-lowlatency@5.15.0-121.131?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-121.131"
}
],
"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"
]
},
{
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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-40-lowlatency",
"binary_version": "6.8.0-40.40.1~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.8.0-40-lowlatency-64k",
"binary_version": "6.8.0-40.40.1~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.8.0-40-lowlatency",
"binary_version": "6.8.0-40.40.1~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-40-lowlatency",
"binary_version": "6.8.0-40.40.1~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-40-lowlatency-64k",
"binary_version": "6.8.0-40.40.1~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-40-lowlatency",
"binary_version": "6.8.0-40.40.1~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-40-lowlatency-64k",
"binary_version": "6.8.0-40.40.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.8-cloud-tools-6.8.0-40",
"binary_version": "6.8.0-40.40.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.8-headers-6.8.0-40",
"binary_version": "6.8.0-40.40.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.8-lib-rust-6.8.0-40-lowlatency",
"binary_version": "6.8.0-40.40.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.8-tools-6.8.0-40",
"binary_version": "6.8.0-40.40.1~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-40-lowlatency",
"binary_version": "6.8.0-40.40.1~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-40-lowlatency-64k",
"binary_version": "6.8.0-40.40.1~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-40-lowlatency",
"binary_version": "6.8.0-40.40.1~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-40-lowlatency",
"binary_version": "6.8.0-40.40.1~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-40-lowlatency-64k",
"binary_version": "6.8.0-40.40.1~22.04.1"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-lowlatency-hwe-6.8",
"purl": "pkg:deb/ubuntu/linux-lowlatency-hwe-6.8@6.8.0-40.40.1~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-40.40.1~22.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-38.38.1~22.04.2"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1064-nvidia",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-buildinfo-5.15.0-1064-nvidia-lowlatency",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1064-nvidia",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1064-nvidia-lowlatency",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-headers-5.15.0-1064-nvidia",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-headers-5.15.0-1064-nvidia-lowlatency",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1064-nvidia",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1064-nvidia-lowlatency",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-modules-5.15.0-1064-nvidia",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-modules-5.15.0-1064-nvidia-lowlatency",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-modules-extra-5.15.0-1064-nvidia",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-modules-nvidia-fs-5.15.0-1064-nvidia",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-modules-nvidia-fs-5.15.0-1064-nvidia-lowlatency",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-nvidia-cloud-tools-5.15.0-1064",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-nvidia-cloud-tools-common",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-nvidia-headers-5.15.0-1064",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-nvidia-tools-5.15.0-1064",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-nvidia-tools-common",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-nvidia-tools-host",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-tools-5.15.0-1064-nvidia",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-tools-5.15.0-1064-nvidia-lowlatency",
"binary_version": "5.15.0-1064.65"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-nvidia",
"purl": "pkg:deb/ubuntu/linux-nvidia@5.15.0-1064.65?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1064.65"
}
],
"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"
]
},
{
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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-1011-nvidia",
"binary_version": "6.8.0-1011.11~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.8.0-1011-nvidia-64k",
"binary_version": "6.8.0-1011.11~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1011-nvidia",
"binary_version": "6.8.0-1011.11~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1011-nvidia-64k",
"binary_version": "6.8.0-1011.11~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1011-nvidia",
"binary_version": "6.8.0-1011.11~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1011-nvidia-64k",
"binary_version": "6.8.0-1011.11~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1011-nvidia",
"binary_version": "6.8.0-1011.11~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1011-nvidia-64k",
"binary_version": "6.8.0-1011.11~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1011-nvidia",
"binary_version": "6.8.0-1011.11~22.04.1"
},
{
"binary_name": "linux-modules-nvidia-fs-6.8.0-1011-nvidia",
"binary_version": "6.8.0-1011.11~22.04.1"
},
{
"binary_name": "linux-modules-nvidia-fs-6.8.0-1011-nvidia-64k",
"binary_version": "6.8.0-1011.11~22.04.1"
},
{
"binary_name": "linux-nvidia-6.8-headers-6.8.0-1011",
"binary_version": "6.8.0-1011.11~22.04.1"
},
{
"binary_name": "linux-nvidia-6.8-tools-6.8.0-1011",
"binary_version": "6.8.0-1011.11~22.04.1"
},
{
"binary_name": "linux-nvidia-6.8-tools-host",
"binary_version": "6.8.0-1011.11~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1011-nvidia",
"binary_version": "6.8.0-1011.11~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1011-nvidia-64k",
"binary_version": "6.8.0-1011.11~22.04.1"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-nvidia-6.8",
"purl": "pkg:deb/ubuntu/linux-nvidia-6.8@6.8.0-1011.11~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1011.11~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"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1028-nvidia-tegra",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-buildinfo-5.15.0-1028-nvidia-tegra-rt",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-headers-5.15.0-1028-nvidia-tegra",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-headers-5.15.0-1028-nvidia-tegra-rt",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1028-nvidia-tegra",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1028-nvidia-tegra-rt",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-modules-5.15.0-1028-nvidia-tegra",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-modules-5.15.0-1028-nvidia-tegra-rt",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-modules-extra-5.15.0-1028-nvidia-tegra",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-nvidia-tegra-cloud-tools-common",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-nvidia-tegra-headers-5.15.0-1028",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-nvidia-tegra-tools-5.15.0-1028",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-nvidia-tegra-tools-common",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-nvidia-tegra-tools-host",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-tools-5.15.0-1028-nvidia-tegra",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-tools-5.15.0-1028-nvidia-tegra-rt",
"binary_version": "5.15.0-1028.28"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-nvidia-tegra",
"purl": "pkg:deb/ubuntu/linux-nvidia-tegra@5.15.0-1028.28?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1028.28"
}
],
"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"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1016-nvidia-tegra-igx",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-buildinfo-5.15.0-1016-nvidia-tegra-igx-rt",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-headers-5.15.0-1016-nvidia-tegra-igx",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-headers-5.15.0-1016-nvidia-tegra-igx-rt",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1016-nvidia-tegra-igx",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1016-nvidia-tegra-igx-rt",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-modules-5.15.0-1016-nvidia-tegra-igx",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-modules-5.15.0-1016-nvidia-tegra-igx-rt",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-modules-extra-5.15.0-1016-nvidia-tegra-igx",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-nvidia-tegra-igx-cloud-tools-common",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-nvidia-tegra-igx-headers-5.15.0-1016",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-nvidia-tegra-igx-tools-5.15.0-1016",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-nvidia-tegra-igx-tools-common",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-nvidia-tegra-igx-tools-host",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-tools-5.15.0-1016-nvidia-tegra-igx",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-tools-5.15.0-1016-nvidia-tegra-igx-rt",
"binary_version": "5.15.0-1016.16"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-nvidia-tegra-igx",
"purl": "pkg:deb/ubuntu/linux-nvidia-tegra-igx@5.15.0-1016.16?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1016.16"
}
],
"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"
]
},
{
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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-1067-oracle",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-headers-5.15.0-1067-oracle",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1067-oracle",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-modules-5.15.0-1067-oracle",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-modules-extra-5.15.0-1067-oracle",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-oracle-headers-5.15.0-1067",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-oracle-tools-5.15.0-1067",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-tools-5.15.0-1067-oracle",
"binary_version": "5.15.0-1067.73"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-oracle",
"purl": "pkg:deb/ubuntu/linux-oracle@5.15.0-1067.73?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1067.73"
}
],
"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"
]
},
{
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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-1010-oracle",
"binary_version": "6.8.0-1010.10~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.8.0-1010-oracle-64k",
"binary_version": "6.8.0-1010.10~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1010-oracle",
"binary_version": "6.8.0-1010.10~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1010-oracle-64k",
"binary_version": "6.8.0-1010.10~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1010-oracle",
"binary_version": "6.8.0-1010.10~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1010-oracle-64k",
"binary_version": "6.8.0-1010.10~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1010-oracle",
"binary_version": "6.8.0-1010.10~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1010-oracle-64k",
"binary_version": "6.8.0-1010.10~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1010-oracle",
"binary_version": "6.8.0-1010.10~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1010-oracle-64k",
"binary_version": "6.8.0-1010.10~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-1010-oracle",
"binary_version": "6.8.0-1010.10~22.04.1"
},
{
"binary_name": "linux-oracle-6.8-headers-6.8.0-1010",
"binary_version": "6.8.0-1010.10~22.04.1"
},
{
"binary_name": "linux-oracle-6.8-tools-6.8.0-1010",
"binary_version": "6.8.0-1010.10~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1010-oracle",
"binary_version": "6.8.0-1010.10~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1010-oracle-64k",
"binary_version": "6.8.0-1010.10~22.04.1"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-oracle-6.8",
"purl": "pkg:deb/ubuntu/linux-oracle-6.8@6.8.0-1010.10~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1010.10~22.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1006.6~22.04.3",
"6.8.0-1008.8~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1062-raspi",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-headers-5.15.0-1062-raspi",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-image-5.15.0-1062-raspi",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-modules-5.15.0-1062-raspi",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-modules-extra-5.15.0-1062-raspi",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-raspi-headers-5.15.0-1062",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-raspi-tools-5.15.0-1062",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-tools-5.15.0-1062-raspi",
"binary_version": "5.15.0-1062.65"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-raspi",
"purl": "pkg:deb/ubuntu/linux-raspi@5.15.0-1062.65?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1062.65"
}
],
"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"
]
},
{
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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-40-generic",
"binary_version": "6.8.0-40.40.1~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-40-generic",
"binary_version": "6.8.0-40.40.1~22.04.1"
},
{
"binary_name": "linux-image-6.8.0-40-generic",
"binary_version": "6.8.0-40.40.1~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-40-generic",
"binary_version": "6.8.0-40.40.1~22.04.1"
},
{
"binary_name": "linux-riscv-6.8-headers-6.8.0-40",
"binary_version": "6.8.0-40.40.1~22.04.1"
},
{
"binary_name": "linux-riscv-6.8-tools-6.8.0-40",
"binary_version": "6.8.0-40.40.1~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-40-generic",
"binary_version": "6.8.0-40.40.1~22.04.1"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-riscv-6.8",
"purl": "pkg:deb/ubuntu/linux-riscv-6.8@6.8.0-40.40.1~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-40.40.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"
]
},
{
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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-1035-xilinx-zynqmp",
"binary_version": "5.15.0-1035.39"
},
{
"binary_name": "linux-headers-5.15.0-1035-xilinx-zynqmp",
"binary_version": "5.15.0-1035.39"
},
{
"binary_name": "linux-image-5.15.0-1035-xilinx-zynqmp",
"binary_version": "5.15.0-1035.39"
},
{
"binary_name": "linux-modules-5.15.0-1035-xilinx-zynqmp",
"binary_version": "5.15.0-1035.39"
},
{
"binary_name": "linux-tools-5.15.0-1035-xilinx-zynqmp",
"binary_version": "5.15.0-1035.39"
},
{
"binary_name": "linux-xilinx-zynqmp-headers-5.15.0-1035",
"binary_version": "5.15.0-1035.39"
},
{
"binary_name": "linux-xilinx-zynqmp-tools-5.15.0-1035",
"binary_version": "5.15.0-1035.39"
},
{
"binary_name": "linux-xilinx-zynqmp-tools-common",
"binary_version": "5.15.0-1035.39"
},
{
"binary_name": "linux-xilinx-zynqmp-tools-host",
"binary_version": "5.15.0-1035.39"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-xilinx-zynqmp",
"purl": "pkg:deb/ubuntu/linux-xilinx-zynqmp@5.15.0-1035.39?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1035.39"
}
],
"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"
]
},
{
"ecosystem_specific": {
"availability": "Available for NVIDIA BlueField platforms",
"binaries": [
{
"binary_name": "linux-bluefield-cloud-tools-common",
"binary_version": "5.15.0-1052.54"
},
{
"binary_name": "linux-bluefield-headers-5.15.0-1052",
"binary_version": "5.15.0-1052.54"
},
{
"binary_name": "linux-bluefield-tools-5.15.0-1052",
"binary_version": "5.15.0-1052.54"
},
{
"binary_name": "linux-bluefield-tools-host",
"binary_version": "5.15.0-1052.54"
},
{
"binary_name": "linux-buildinfo-5.15.0-1052-bluefield",
"binary_version": "5.15.0-1052.54"
},
{
"binary_name": "linux-headers-5.15.0-1052-bluefield",
"binary_version": "5.15.0-1052.54"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1052-bluefield",
"binary_version": "5.15.0-1052.54"
},
{
"binary_name": "linux-modules-5.15.0-1052-bluefield",
"binary_version": "5.15.0-1052.54"
},
{
"binary_name": "linux-modules-extra-5.15.0-1052-bluefield",
"binary_version": "5.15.0-1052.54"
},
{
"binary_name": "linux-tools-5.15.0-1052-bluefield",
"binary_version": "5.15.0-1052.54"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:Nvidia-BlueField:22.04:LTS",
"name": "linux-bluefield",
"purl": "pkg:deb/ubuntu/linux-bluefield@5.15.0-1052.54?arch=source\u0026distro=bluefield/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1052.54"
}
],
"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"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1063-intel-iot-realtime",
"binary_version": "5.15.0-1063.65"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1063-intel-iot-realtime",
"binary_version": "5.15.0-1063.65"
},
{
"binary_name": "linux-headers-5.15.0-1063-intel-iot-realtime",
"binary_version": "5.15.0-1063.65"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1063-intel-iot-realtime",
"binary_version": "5.15.0-1063.65"
},
{
"binary_name": "linux-intel-iot-realtime-cloud-tools-5.15.0-1063",
"binary_version": "5.15.0-1063.65"
},
{
"binary_name": "linux-intel-iot-realtime-cloud-tools-common",
"binary_version": "5.15.0-1063.65"
},
{
"binary_name": "linux-intel-iot-realtime-headers-5.15.0-1063",
"binary_version": "5.15.0-1063.65"
},
{
"binary_name": "linux-intel-iot-realtime-tools-5.15.0-1063",
"binary_version": "5.15.0-1063.65"
},
{
"binary_name": "linux-intel-iot-realtime-tools-common",
"binary_version": "5.15.0-1063.65"
},
{
"binary_name": "linux-intel-iot-realtime-tools-host",
"binary_version": "5.15.0-1063.65"
},
{
"binary_name": "linux-modules-5.15.0-1063-intel-iot-realtime",
"binary_version": "5.15.0-1063.65"
},
{
"binary_name": "linux-modules-extra-5.15.0-1063-intel-iot-realtime",
"binary_version": "5.15.0-1063.65"
},
{
"binary_name": "linux-tools-5.15.0-1063-intel-iot-realtime",
"binary_version": "5.15.0-1063.65"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:Pro:Realtime:22.04:LTS",
"name": "linux-intel-iot-realtime",
"purl": "pkg:deb/ubuntu/linux-intel-iot-realtime@5.15.0-1063.65?arch=source\u0026distro=realtime/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1063.65"
}
],
"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"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1070-realtime",
"binary_version": "5.15.0-1070.78"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1070-realtime",
"binary_version": "5.15.0-1070.78"
},
{
"binary_name": "linux-headers-5.15.0-1070-realtime",
"binary_version": "5.15.0-1070.78"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1070-realtime",
"binary_version": "5.15.0-1070.78"
},
{
"binary_name": "linux-modules-5.15.0-1070-realtime",
"binary_version": "5.15.0-1070.78"
},
{
"binary_name": "linux-modules-extra-5.15.0-1070-realtime",
"binary_version": "5.15.0-1070.78"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-1070-realtime",
"binary_version": "5.15.0-1070.78"
},
{
"binary_name": "linux-realtime-cloud-tools-5.15.0-1070",
"binary_version": "5.15.0-1070.78"
},
{
"binary_name": "linux-realtime-cloud-tools-common",
"binary_version": "5.15.0-1070.78"
},
{
"binary_name": "linux-realtime-headers-5.15.0-1070",
"binary_version": "5.15.0-1070.78"
},
{
"binary_name": "linux-realtime-tools-5.15.0-1070",
"binary_version": "5.15.0-1070.78"
},
{
"binary_name": "linux-realtime-tools-common",
"binary_version": "5.15.0-1070.78"
},
{
"binary_name": "linux-realtime-tools-host",
"binary_version": "5.15.0-1070.78"
},
{
"binary_name": "linux-tools-5.15.0-1070-realtime",
"binary_version": "5.15.0-1070.78"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:Pro:Realtime:22.04:LTS",
"name": "linux-realtime",
"purl": "pkg:deb/ubuntu/linux-realtime@5.15.0-1070.78?arch=source\u0026distro=realtime/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1070.78"
}
],
"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"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.1-1006-realtime",
"binary_version": "6.8.1-1006.6~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.8.1-1006-realtime",
"binary_version": "6.8.1-1006.6~22.04.1"
},
{
"binary_name": "linux-headers-6.8.1-1006-realtime",
"binary_version": "6.8.1-1006.6~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.1-1006-realtime",
"binary_version": "6.8.1-1006.6~22.04.1"
},
{
"binary_name": "linux-modules-6.8.1-1006-realtime",
"binary_version": "6.8.1-1006.6~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.1-1006-realtime",
"binary_version": "6.8.1-1006.6~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.1-1006-realtime",
"binary_version": "6.8.1-1006.6~22.04.1"
},
{
"binary_name": "linux-realtime-6.8-cloud-tools-6.8.1-1006",
"binary_version": "6.8.1-1006.6~22.04.1"
},
{
"binary_name": "linux-realtime-6.8-headers-6.8.1-1006",
"binary_version": "6.8.1-1006.6~22.04.1"
},
{
"binary_name": "linux-realtime-6.8-tools-6.8.1-1006",
"binary_version": "6.8.1-1006.6~22.04.1"
},
{
"binary_name": "linux-tools-6.8.1-1006-realtime",
"binary_version": "6.8.1-1006.6~22.04.1"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:Pro:Realtime:22.04:LTS",
"name": "linux-realtime-6.8",
"purl": "pkg:deb/ubuntu/linux-realtime-6.8@6.8.1-1006.6~22.04.1?arch=source\u0026distro=realtime/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.1-1006.6~22.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.1-1004.4~22.04.1",
"6.8.1-1005.5~22.04.2"
]
},
{
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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-1069",
"binary_version": "5.15.0-1069.75+fips1"
},
{
"binary_name": "linux-aws-fips-headers-5.15.0-1069",
"binary_version": "5.15.0-1069.75+fips1"
},
{
"binary_name": "linux-aws-fips-tools-5.15.0-1069",
"binary_version": "5.15.0-1069.75+fips1"
},
{
"binary_name": "linux-buildinfo-5.15.0-1069-aws-fips",
"binary_version": "5.15.0-1069.75+fips1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1069-aws-fips",
"binary_version": "5.15.0-1069.75+fips1"
},
{
"binary_name": "linux-headers-5.15.0-1069-aws-fips",
"binary_version": "5.15.0-1069.75+fips1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1069-aws-fips",
"binary_version": "5.15.0-1069.75+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.15.0-1069-aws-fips",
"binary_version": "5.15.0-1069.75+fips1"
},
{
"binary_name": "linux-modules-5.15.0-1069-aws-fips",
"binary_version": "5.15.0-1069.75+fips1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1069-aws-fips",
"binary_version": "5.15.0-1069.75+fips1"
},
{
"binary_name": "linux-tools-5.15.0-1069-aws-fips",
"binary_version": "5.15.0-1069.75+fips1"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:22.04:LTS",
"name": "linux-aws-fips",
"purl": "pkg:deb/ubuntu/linux-aws-fips@5.15.0-1069.75+fips1?arch=source\u0026distro=fips-updates/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1069.75+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"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-azure-fips-cloud-tools-5.15.0-1072",
"binary_version": "5.15.0-1072.81+fips1"
},
{
"binary_name": "linux-azure-fips-headers-5.15.0-1072",
"binary_version": "5.15.0-1072.81+fips1"
},
{
"binary_name": "linux-azure-fips-tools-5.15.0-1072",
"binary_version": "5.15.0-1072.81+fips1"
},
{
"binary_name": "linux-buildinfo-5.15.0-1072-azure-fips",
"binary_version": "5.15.0-1072.81+fips1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1072-azure-fips",
"binary_version": "5.15.0-1072.81+fips1"
},
{
"binary_name": "linux-headers-5.15.0-1072-azure-fips",
"binary_version": "5.15.0-1072.81+fips1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1072-azure-fips",
"binary_version": "5.15.0-1072.81+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.15.0-1072-azure-fips",
"binary_version": "5.15.0-1072.81+fips1"
},
{
"binary_name": "linux-modules-5.15.0-1072-azure-fips",
"binary_version": "5.15.0-1072.81+fips1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1072-azure-fips",
"binary_version": "5.15.0-1072.81+fips1"
},
{
"binary_name": "linux-modules-involflt-5.15.0-1072-azure-fips",
"binary_version": "5.15.0-1072.81+fips1"
},
{
"binary_name": "linux-tools-5.15.0-1072-azure-fips",
"binary_version": "5.15.0-1072.81+fips1"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:22.04:LTS",
"name": "linux-azure-fips",
"purl": "pkg:deb/ubuntu/linux-azure-fips@5.15.0-1072.81+fips1?arch=source\u0026distro=fips-updates/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1072.81+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"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-121-fips",
"binary_version": "5.15.0-121.131+fips1"
},
{
"binary_name": "linux-fips-headers-5.15.0-121",
"binary_version": "5.15.0-121.131+fips1"
},
{
"binary_name": "linux-fips-tools-5.15.0-121",
"binary_version": "5.15.0-121.131+fips1"
},
{
"binary_name": "linux-fips-tools-host",
"binary_version": "5.15.0-121.131+fips1"
},
{
"binary_name": "linux-headers-5.15.0-121-fips",
"binary_version": "5.15.0-121.131+fips1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-121-fips",
"binary_version": "5.15.0-121.131+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.15.0-121-fips",
"binary_version": "5.15.0-121.131+fips1"
},
{
"binary_name": "linux-modules-5.15.0-121-fips",
"binary_version": "5.15.0-121.131+fips1"
},
{
"binary_name": "linux-modules-extra-5.15.0-121-fips",
"binary_version": "5.15.0-121.131+fips1"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-121-fips",
"binary_version": "5.15.0-121.131+fips1"
},
{
"binary_name": "linux-tools-5.15.0-121-fips",
"binary_version": "5.15.0-121.131+fips1"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:22.04:LTS",
"name": "linux-fips",
"purl": "pkg:deb/ubuntu/linux-fips@5.15.0-121.131+fips1?arch=source\u0026distro=fips-updates/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-121.131+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"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1068-gcp-fips",
"binary_version": "5.15.0-1068.76+fips1"
},
{
"binary_name": "linux-gcp-fips-headers-5.15.0-1068",
"binary_version": "5.15.0-1068.76+fips1"
},
{
"binary_name": "linux-gcp-fips-tools-5.15.0-1068",
"binary_version": "5.15.0-1068.76+fips1"
},
{
"binary_name": "linux-headers-5.15.0-1068-gcp-fips",
"binary_version": "5.15.0-1068.76+fips1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1068-gcp-fips",
"binary_version": "5.15.0-1068.76+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.15.0-1068-gcp-fips",
"binary_version": "5.15.0-1068.76+fips1"
},
{
"binary_name": "linux-modules-5.15.0-1068-gcp-fips",
"binary_version": "5.15.0-1068.76+fips1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1068-gcp-fips",
"binary_version": "5.15.0-1068.76+fips1"
},
{
"binary_name": "linux-tools-5.15.0-1068-gcp-fips",
"binary_version": "5.15.0-1068.76+fips1"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:22.04:LTS",
"name": "linux-gcp-fips",
"purl": "pkg:deb/ubuntu/linux-gcp-fips@5.15.0-1068.76+fips1?arch=source\u0026distro=fips-updates/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1068.76+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"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-40-generic",
"binary_version": "6.8.0-40.40"
},
{
"binary_name": "linux-buildinfo-6.8.0-40-generic-64k",
"binary_version": "6.8.0-40.40"
},
{
"binary_name": "linux-cloud-tools-6.8.0-40",
"binary_version": "6.8.0-40.40"
},
{
"binary_name": "linux-cloud-tools-6.8.0-40-generic",
"binary_version": "6.8.0-40.40"
},
{
"binary_name": "linux-cloud-tools-common",
"binary_version": "6.8.0-40.40"
},
{
"binary_name": "linux-headers-6.8.0-40",
"binary_version": "6.8.0-40.40"
},
{
"binary_name": "linux-headers-6.8.0-40-generic",
"binary_version": "6.8.0-40.40"
},
{
"binary_name": "linux-headers-6.8.0-40-generic-64k",
"binary_version": "6.8.0-40.40"
},
{
"binary_name": "linux-image-6.8.0-40-generic",
"binary_version": "6.8.0-40.40"
},
{
"binary_name": "linux-image-unsigned-6.8.0-40-generic",
"binary_version": "6.8.0-40.40"
},
{
"binary_name": "linux-image-unsigned-6.8.0-40-generic-64k",
"binary_version": "6.8.0-40.40"
},
{
"binary_name": "linux-lib-rust-6.8.0-40-generic",
"binary_version": "6.8.0-40.40"
},
{
"binary_name": "linux-modules-6.8.0-40-generic",
"binary_version": "6.8.0-40.40"
},
{
"binary_name": "linux-modules-6.8.0-40-generic-64k",
"binary_version": "6.8.0-40.40"
},
{
"binary_name": "linux-modules-extra-6.8.0-40-generic",
"binary_version": "6.8.0-40.40"
},
{
"binary_name": "linux-modules-ipu6-6.8.0-40-generic",
"binary_version": "6.8.0-40.40"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-40-generic",
"binary_version": "6.8.0-40.40"
},
{
"binary_name": "linux-modules-usbio-6.8.0-40-generic",
"binary_version": "6.8.0-40.40"
},
{
"binary_name": "linux-source-6.8.0",
"binary_version": "6.8.0-40.40"
},
{
"binary_name": "linux-tools-6.8.0-40",
"binary_version": "6.8.0-40.40"
},
{
"binary_name": "linux-tools-6.8.0-40-generic",
"binary_version": "6.8.0-40.40"
},
{
"binary_name": "linux-tools-6.8.0-40-generic-64k",
"binary_version": "6.8.0-40.40"
},
{
"binary_name": "linux-tools-common",
"binary_version": "6.8.0-40.40"
},
{
"binary_name": "linux-tools-host",
"binary_version": "6.8.0-40.40"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux",
"purl": "pkg:deb/ubuntu/linux@6.8.0-40.40?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-40.40"
}
],
"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"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-aws-cloud-tools-6.8.0-1013",
"binary_version": "6.8.0-1013.14"
},
{
"binary_name": "linux-aws-headers-6.8.0-1013",
"binary_version": "6.8.0-1013.14"
},
{
"binary_name": "linux-aws-tools-6.8.0-1013",
"binary_version": "6.8.0-1013.14"
},
{
"binary_name": "linux-buildinfo-6.8.0-1013-aws",
"binary_version": "6.8.0-1013.14"
},
{
"binary_name": "linux-cloud-tools-6.8.0-1013-aws",
"binary_version": "6.8.0-1013.14"
},
{
"binary_name": "linux-headers-6.8.0-1013-aws",
"binary_version": "6.8.0-1013.14"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1013-aws",
"binary_version": "6.8.0-1013.14"
},
{
"binary_name": "linux-modules-6.8.0-1013-aws",
"binary_version": "6.8.0-1013.14"
},
{
"binary_name": "linux-modules-extra-6.8.0-1013-aws",
"binary_version": "6.8.0-1013.14"
},
{
"binary_name": "linux-tools-6.8.0-1013-aws",
"binary_version": "6.8.0-1013.14"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-aws",
"purl": "pkg:deb/ubuntu/linux-aws@6.8.0-1013.14?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1013.14"
}
],
"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"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-azure-cloud-tools-6.8.0-1012",
"binary_version": "6.8.0-1012.14"
},
{
"binary_name": "linux-azure-headers-6.8.0-1012",
"binary_version": "6.8.0-1012.14"
},
{
"binary_name": "linux-azure-tools-6.8.0-1012",
"binary_version": "6.8.0-1012.14"
},
{
"binary_name": "linux-buildinfo-6.8.0-1012-azure",
"binary_version": "6.8.0-1012.14"
},
{
"binary_name": "linux-cloud-tools-6.8.0-1012-azure",
"binary_version": "6.8.0-1012.14"
},
{
"binary_name": "linux-headers-6.8.0-1012-azure",
"binary_version": "6.8.0-1012.14"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1012-azure",
"binary_version": "6.8.0-1012.14"
},
{
"binary_name": "linux-modules-6.8.0-1012-azure",
"binary_version": "6.8.0-1012.14"
},
{
"binary_name": "linux-modules-extra-6.8.0-1012-azure",
"binary_version": "6.8.0-1012.14"
},
{
"binary_name": "linux-modules-involflt-6.8.0-1012-azure",
"binary_version": "6.8.0-1012.14"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-1012-azure",
"binary_version": "6.8.0-1012.14"
},
{
"binary_name": "linux-tools-6.8.0-1012-azure",
"binary_version": "6.8.0-1012.14"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-azure",
"purl": "pkg:deb/ubuntu/linux-azure@6.8.0-1012.14?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1012.14"
}
],
"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"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1012-gcp",
"binary_version": "6.8.0-1012.13"
},
{
"binary_name": "linux-gcp-headers-6.8.0-1012",
"binary_version": "6.8.0-1012.13"
},
{
"binary_name": "linux-gcp-tools-6.8.0-1012",
"binary_version": "6.8.0-1012.13"
},
{
"binary_name": "linux-headers-6.8.0-1012-gcp",
"binary_version": "6.8.0-1012.13"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1012-gcp",
"binary_version": "6.8.0-1012.13"
},
{
"binary_name": "linux-modules-6.8.0-1012-gcp",
"binary_version": "6.8.0-1012.13"
},
{
"binary_name": "linux-modules-extra-6.8.0-1012-gcp",
"binary_version": "6.8.0-1012.13"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-1012-gcp",
"binary_version": "6.8.0-1012.13"
},
{
"binary_name": "linux-tools-6.8.0-1012-gcp",
"binary_version": "6.8.0-1012.13"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-gcp",
"purl": "pkg:deb/ubuntu/linux-gcp@6.8.0-1012.13?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1012.13"
}
],
"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"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1008-gke",
"binary_version": "6.8.0-1008.11"
},
{
"binary_name": "linux-gke-headers-6.8.0-1008",
"binary_version": "6.8.0-1008.11"
},
{
"binary_name": "linux-gke-tools-6.8.0-1008",
"binary_version": "6.8.0-1008.11"
},
{
"binary_name": "linux-headers-6.8.0-1008-gke",
"binary_version": "6.8.0-1008.11"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1008-gke",
"binary_version": "6.8.0-1008.11"
},
{
"binary_name": "linux-modules-6.8.0-1008-gke",
"binary_version": "6.8.0-1008.11"
},
{
"binary_name": "linux-modules-extra-6.8.0-1008-gke",
"binary_version": "6.8.0-1008.11"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-1008-gke",
"binary_version": "6.8.0-1008.11"
},
{
"binary_name": "linux-tools-6.8.0-1008-gke",
"binary_version": "6.8.0-1008.11"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-gke",
"purl": "pkg:deb/ubuntu/linux-gke@6.8.0-1008.11?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1008.11"
}
],
"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"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1010-ibm",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-headers-6.8.0-1010-ibm",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-ibm-cloud-tools-common",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-ibm-headers-6.8.0-1010",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-ibm-source-6.8.0",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-ibm-tools-6.8.0-1010",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1010-ibm",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-modules-6.8.0-1010-ibm",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-modules-extra-6.8.0-1010-ibm",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-1010-ibm",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-tools-6.8.0-1010-ibm",
"binary_version": "6.8.0-1010.10"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-ibm",
"purl": "pkg:deb/ubuntu/linux-ibm@6.8.0-1010.10?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1010.10"
}
],
"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"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-40-lowlatency",
"binary_version": "6.8.0-40.40.1"
},
{
"binary_name": "linux-buildinfo-6.8.0-40-lowlatency-64k",
"binary_version": "6.8.0-40.40.1"
},
{
"binary_name": "linux-cloud-tools-6.8.0-40-lowlatency",
"binary_version": "6.8.0-40.40.1"
},
{
"binary_name": "linux-headers-6.8.0-40-lowlatency",
"binary_version": "6.8.0-40.40.1"
},
{
"binary_name": "linux-headers-6.8.0-40-lowlatency-64k",
"binary_version": "6.8.0-40.40.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-40-lowlatency",
"binary_version": "6.8.0-40.40.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-40-lowlatency-64k",
"binary_version": "6.8.0-40.40.1"
},
{
"binary_name": "linux-lowlatency-cloud-tools-6.8.0-40",
"binary_version": "6.8.0-40.40.1"
},
{
"binary_name": "linux-lowlatency-cloud-tools-common",
"binary_version": "6.8.0-40.40.1"
},
{
"binary_name": "linux-lowlatency-headers-6.8.0-40",
"binary_version": "6.8.0-40.40.1"
},
{
"binary_name": "linux-lowlatency-lib-rust-6.8.0-40-lowlatency",
"binary_version": "6.8.0-40.40.1"
},
{
"binary_name": "linux-lowlatency-tools-6.8.0-40",
"binary_version": "6.8.0-40.40.1"
},
{
"binary_name": "linux-lowlatency-tools-common",
"binary_version": "6.8.0-40.40.1"
},
{
"binary_name": "linux-lowlatency-tools-host",
"binary_version": "6.8.0-40.40.1"
},
{
"binary_name": "linux-modules-6.8.0-40-lowlatency",
"binary_version": "6.8.0-40.40.1"
},
{
"binary_name": "linux-modules-6.8.0-40-lowlatency-64k",
"binary_version": "6.8.0-40.40.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-40-lowlatency",
"binary_version": "6.8.0-40.40.1"
},
{
"binary_name": "linux-tools-6.8.0-40-lowlatency",
"binary_version": "6.8.0-40.40.1"
},
{
"binary_name": "linux-tools-6.8.0-40-lowlatency-64k",
"binary_version": "6.8.0-40.40.1"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-lowlatency",
"purl": "pkg:deb/ubuntu/linux-lowlatency@6.8.0-40.40.1?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-40.40.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"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1011-nvidia",
"binary_version": "6.8.0-1011.11"
},
{
"binary_name": "linux-buildinfo-6.8.0-1011-nvidia-64k",
"binary_version": "6.8.0-1011.11"
},
{
"binary_name": "linux-headers-6.8.0-1011-nvidia",
"binary_version": "6.8.0-1011.11"
},
{
"binary_name": "linux-headers-6.8.0-1011-nvidia-64k",
"binary_version": "6.8.0-1011.11"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1011-nvidia",
"binary_version": "6.8.0-1011.11"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1011-nvidia-64k",
"binary_version": "6.8.0-1011.11"
},
{
"binary_name": "linux-modules-6.8.0-1011-nvidia",
"binary_version": "6.8.0-1011.11"
},
{
"binary_name": "linux-modules-6.8.0-1011-nvidia-64k",
"binary_version": "6.8.0-1011.11"
},
{
"binary_name": "linux-modules-extra-6.8.0-1011-nvidia",
"binary_version": "6.8.0-1011.11"
},
{
"binary_name": "linux-modules-nvidia-fs-6.8.0-1011-nvidia",
"binary_version": "6.8.0-1011.11"
},
{
"binary_name": "linux-modules-nvidia-fs-6.8.0-1011-nvidia-64k",
"binary_version": "6.8.0-1011.11"
},
{
"binary_name": "linux-nvidia-headers-6.8.0-1011",
"binary_version": "6.8.0-1011.11"
},
{
"binary_name": "linux-nvidia-tools-6.8.0-1011",
"binary_version": "6.8.0-1011.11"
},
{
"binary_name": "linux-nvidia-tools-host",
"binary_version": "6.8.0-1011.11"
},
{
"binary_name": "linux-tools-6.8.0-1011-nvidia",
"binary_version": "6.8.0-1011.11"
},
{
"binary_name": "linux-tools-6.8.0-1011-nvidia-64k",
"binary_version": "6.8.0-1011.11"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-nvidia",
"purl": "pkg:deb/ubuntu/linux-nvidia@6.8.0-1011.11?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1011.11"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1007.7",
"6.8.0-1008.8",
"6.8.0-1009.9",
"6.8.0-1010.10"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1011-nvidia-lowlatency",
"binary_version": "6.8.0-1011.11.1"
},
{
"binary_name": "linux-buildinfo-6.8.0-1011-nvidia-lowlatency-64k",
"binary_version": "6.8.0-1011.11.1"
},
{
"binary_name": "linux-headers-6.8.0-1011-nvidia-lowlatency",
"binary_version": "6.8.0-1011.11.1"
},
{
"binary_name": "linux-headers-6.8.0-1011-nvidia-lowlatency-64k",
"binary_version": "6.8.0-1011.11.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1011-nvidia-lowlatency",
"binary_version": "6.8.0-1011.11.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1011-nvidia-lowlatency-64k",
"binary_version": "6.8.0-1011.11.1"
},
{
"binary_name": "linux-modules-6.8.0-1011-nvidia-lowlatency",
"binary_version": "6.8.0-1011.11.1"
},
{
"binary_name": "linux-modules-6.8.0-1011-nvidia-lowlatency-64k",
"binary_version": "6.8.0-1011.11.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1011-nvidia-lowlatency",
"binary_version": "6.8.0-1011.11.1"
},
{
"binary_name": "linux-modules-nvidia-fs-6.8.0-1011-nvidia-lowlatency",
"binary_version": "6.8.0-1011.11.1"
},
{
"binary_name": "linux-modules-nvidia-fs-6.8.0-1011-nvidia-lowlatency-64k",
"binary_version": "6.8.0-1011.11.1"
},
{
"binary_name": "linux-nvidia-lowlatency-headers-6.8.0-1011",
"binary_version": "6.8.0-1011.11.1"
},
{
"binary_name": "linux-nvidia-lowlatency-tools-6.8.0-1011",
"binary_version": "6.8.0-1011.11.1"
},
{
"binary_name": "linux-nvidia-lowlatency-tools-host",
"binary_version": "6.8.0-1011.11.1"
},
{
"binary_name": "linux-tools-6.8.0-1011-nvidia-lowlatency",
"binary_version": "6.8.0-1011.11.1"
},
{
"binary_name": "linux-tools-6.8.0-1011-nvidia-lowlatency-64k",
"binary_version": "6.8.0-1011.11.1"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-nvidia-lowlatency",
"purl": "pkg:deb/ubuntu/linux-nvidia-lowlatency@6.8.0-1011.11.1?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1011.11.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1009.9.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1010-oem",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-headers-6.8.0-1010-oem",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1010-oem",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-modules-6.8.0-1010-oem",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-modules-ipu6-6.8.0-1010-oem",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-1010-oem",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-modules-usbio-6.8.0-1010-oem",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-oem-6.8-headers-6.8.0-1010",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-oem-6.8-tools-6.8.0-1010",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-tools-6.8.0-1010-oem",
"binary_version": "6.8.0-1010.10"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-oem-6.8",
"purl": "pkg:deb/ubuntu/linux-oem-6.8@6.8.0-1010.10?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1010.10"
}
],
"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"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1010-oracle",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-buildinfo-6.8.0-1010-oracle-64k",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-headers-6.8.0-1010-oracle",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-headers-6.8.0-1010-oracle-64k",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1010-oracle",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1010-oracle-64k",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-modules-6.8.0-1010-oracle",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-modules-6.8.0-1010-oracle-64k",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-modules-extra-6.8.0-1010-oracle",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-modules-extra-6.8.0-1010-oracle-64k",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-1010-oracle",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-oracle-headers-6.8.0-1010",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-oracle-tools-6.8.0-1010",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-tools-6.8.0-1010-oracle",
"binary_version": "6.8.0-1010.10"
},
{
"binary_name": "linux-tools-6.8.0-1010-oracle-64k",
"binary_version": "6.8.0-1010.10"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-oracle",
"purl": "pkg:deb/ubuntu/linux-oracle@6.8.0-1010.10?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1010.10"
}
],
"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"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1009-raspi",
"binary_version": "6.8.0-1009.10"
},
{
"binary_name": "linux-headers-6.8.0-1009-raspi",
"binary_version": "6.8.0-1009.10"
},
{
"binary_name": "linux-image-6.8.0-1009-raspi",
"binary_version": "6.8.0-1009.10"
},
{
"binary_name": "linux-modules-6.8.0-1009-raspi",
"binary_version": "6.8.0-1009.10"
},
{
"binary_name": "linux-raspi-headers-6.8.0-1009",
"binary_version": "6.8.0-1009.10"
},
{
"binary_name": "linux-raspi-tools-6.8.0-1009",
"binary_version": "6.8.0-1009.10"
},
{
"binary_name": "linux-tools-6.8.0-1009-raspi",
"binary_version": "6.8.0-1009.10"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-raspi",
"purl": "pkg:deb/ubuntu/linux-raspi@6.8.0-1009.10?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1009.10"
}
],
"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"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-40-generic",
"binary_version": "6.8.0-40.40.1"
},
{
"binary_name": "linux-headers-6.8.0-40-generic",
"binary_version": "6.8.0-40.40.1"
},
{
"binary_name": "linux-image-6.8.0-40-generic",
"binary_version": "6.8.0-40.40.1"
},
{
"binary_name": "linux-modules-6.8.0-40-generic",
"binary_version": "6.8.0-40.40.1"
},
{
"binary_name": "linux-riscv-headers-6.8.0-40",
"binary_version": "6.8.0-40.40.1"
},
{
"binary_name": "linux-riscv-tools-6.8.0-40",
"binary_version": "6.8.0-40.40.1"
},
{
"binary_name": "linux-tools-6.8.0-40-generic",
"binary_version": "6.8.0-40.40.1"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-riscv",
"purl": "pkg:deb/ubuntu/linux-riscv@6.8.0-40.40.1?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-40.40.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"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-2008-raspi-realtime",
"binary_version": "6.8.0-2008.8"
},
{
"binary_name": "linux-headers-6.8.0-2008-raspi-realtime",
"binary_version": "6.8.0-2008.8"
},
{
"binary_name": "linux-image-6.8.0-2008-raspi-realtime",
"binary_version": "6.8.0-2008.8"
},
{
"binary_name": "linux-modules-6.8.0-2008-raspi-realtime",
"binary_version": "6.8.0-2008.8"
},
{
"binary_name": "linux-raspi-realtime-headers-6.8.0-2008",
"binary_version": "6.8.0-2008.8"
},
{
"binary_name": "linux-raspi-realtime-tools-6.8.0-2008",
"binary_version": "6.8.0-2008.8"
},
{
"binary_name": "linux-tools-6.8.0-2008-raspi-realtime",
"binary_version": "6.8.0-2008.8"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:Pro:Realtime:24.04:LTS",
"name": "linux-raspi-realtime",
"purl": "pkg:deb/ubuntu/linux-raspi-realtime@6.8.0-2008.8?arch=source\u0026distro=realtime/noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-2008.8"
}
],
"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"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.1-1006-realtime",
"binary_version": "6.8.1-1006.6"
},
{
"binary_name": "linux-cloud-tools-6.8.1-1006-realtime",
"binary_version": "6.8.1-1006.6"
},
{
"binary_name": "linux-headers-6.8.1-1006-realtime",
"binary_version": "6.8.1-1006.6"
},
{
"binary_name": "linux-image-unsigned-6.8.1-1006-realtime",
"binary_version": "6.8.1-1006.6"
},
{
"binary_name": "linux-modules-6.8.1-1006-realtime",
"binary_version": "6.8.1-1006.6"
},
{
"binary_name": "linux-modules-extra-6.8.1-1006-realtime",
"binary_version": "6.8.1-1006.6"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.1-1006-realtime",
"binary_version": "6.8.1-1006.6"
},
{
"binary_name": "linux-realtime-cloud-tools-6.8.1-1006",
"binary_version": "6.8.1-1006.6"
},
{
"binary_name": "linux-realtime-headers-6.8.1-1006",
"binary_version": "6.8.1-1006.6"
},
{
"binary_name": "linux-realtime-tools-6.8.1-1006",
"binary_version": "6.8.1-1006.6"
},
{
"binary_name": "linux-tools-6.8.1-1006-realtime",
"binary_version": "6.8.1-1006.6"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"package": {
"ecosystem": "Ubuntu:Pro:Realtime:24.04:LTS",
"name": "linux-realtime",
"purl": "pkg:deb/ubuntu/linux-realtime@6.8.1-1006.6?arch=source\u0026distro=realtime/noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.1-1006.6"
}
],
"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"
]
},
{
"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"
}
],
"priority_reason": "Exploitation requires CAP_SYS_MODULE in the initial user namespace to invoke delete_module (rmmod), which is only available to root or processes with this specific capability. This is confirmed by the capable(CAP_SYS_MODULE) check at kernel/module/main.c:706."
},
"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"
]
}
],
"aliases": [],
"details": "In the Linux kernel, the following vulnerability has been resolved: ALSA: core: Fix NULL module pointer assignment at card init The commit 81033c6b584b (\"ALSA: core: Warn on empty module\") introduced a WARN_ON() for a NULL module pointer passed at snd_card object creation, and it also wraps the code around it with \u0027#ifdef MODULE\u0027. This works in most cases, but the devils are always in details. \"MODULE\" is defined when the target code (i.e. the sound core) is built as a module; but this doesn\u0027t mean that the caller is also built-in or not. Namely, when only the sound core is built-in (CONFIG_SND=y) while the driver is a module (CONFIG_SND_USB_AUDIO=m), the passed module pointer is ignored even if it\u0027s non-NULL, and card-\u003emodule remains as NULL. This would result in the missing module reference up/down at the device open/close, leading to a race with the code execution after the module removal. For addressing the bug, move the assignment of card-\u003emodule again out of ifdef. The WARN_ON() is still wrapped with ifdef because the module can be really NULL when all sound drivers are built-in. Note that we keep \u0027ifdef MODULE\u0027 for WARN_ON(), otherwise it would lead to a false-positive NULL module check. Admittedly it won\u0027t catch perfectly, i.e. no check is performed when CONFIG_SND=y. But, it\u0027s no real problem as it\u0027s only for debugging, and the condition is pretty rare.",
"id": "UBUNTU-CVE-2024-38605",
"modified": "2026-11-12T13:29:02Z",
"published": "2024-06-19T14:15:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2024-38605"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38605"
},
{
"type": "REPORT",
"url": "https://git.kernel.org/linus/39381fe7394e5eafac76e7e9367e7351138a29c1"
},
{
"type": "REPORT",
"url": "https://git.kernel.org/stable/c/d7ff29a429b56f04783152ad7bbd7233b740e434"
},
{
"type": "REPORT",
"url": "https://git.kernel.org/stable/c/e7e0ca200772bdb2fdc6d43d32d341e87a36f811"
},
{
"type": "REPORT",
"url": "https://git.kernel.org/stable/c/e007476725730c1a68387b54b7629486d8a8301e"
},
{
"type": "REPORT",
"url": "https://git.kernel.org/stable/c/e644036a3e2b2c9b3eee3c61b5d31c2ca8b5ba92"
},
{
"type": "REPORT",
"url": "https://git.kernel.org/stable/c/c935e72139e6d523defd60fe875c01eb1f9ea5c5"
},
{
"type": "REPORT",
"url": "https://git.kernel.org/stable/c/6b8374ee2cabcf034faa34e69a855dc496a9ec12"
},
{
"type": "REPORT",
"url": "https://git.kernel.org/stable/c/39381fe7394e5eafac76e7e9367e7351138a29c1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-6949-1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-6952-1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-6955-1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-6949-2"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-6952-2"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7007-1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7009-1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7019-1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7007-2"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7007-3"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7009-2"
}
],
"related": [
"USN-6949-1",
"USN-6952-1",
"USN-6955-1",
"USN-6949-2",
"USN-6952-2",
"USN-7007-1",
"USN-7009-1",
"USN-7019-1",
"USN-7007-2",
"USN-7007-3",
"USN-7009-2"
],
"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:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
},
{
"score": "low",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2024-38605"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
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.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
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.