Action not permitted
Modal body text goes here.
Modal Title
Modal Body
CVE-2024-42297 (GCVE-0-2024-42297)
Vulnerability from cvelistv5 – Published: 2024-08-17 09:09 – Updated: 2026-08-05 11:36| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
98e4da8ca301e062d79ae168c67e56f3c3de3ce4 , < 2d2916516577f2239b3377d9e8d12da5e6ccdfcf
(git)
Affected: 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 , < 54162974aea37a8cae00742470a78c7f6bd6f915 (git) Affected: 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 , < 54bc4e88447e385c4d4ffa85d93e0dce628fcfa6 (git) Affected: 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 , < ec56571b4b146a1cfbedab49d5fcaf19fe8bf4f1 (git) Affected: 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 , < 9ce8135accf103f7333af472709125878704fdd4 (git) Affected: 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 , < e62ff092a42f4a1bae3b310cf46673b4f3aac3b5 (git) Affected: 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 , < 2434344559f6743efb3ac15d11af9a0db9543bd3 (git) Affected: 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 , < 192b8fb8d1c8ca3c87366ebbef599fa80bb626b8 (git) |
guessed | |
| Linux | Linux |
Affected:
3.8
Unaffected: 0 , < 3.8 (semver) Unaffected: 4.19.320 , ≤ 4.19.* (semver) Unaffected: 5.4.282 , ≤ 5.4.* (semver) Unaffected: 5.10.224 , ≤ 5.10.* (semver) Unaffected: 5.15.165 , ≤ 5.15.* (semver) Unaffected: 6.1.103 , ≤ 6.1.* (semver) Unaffected: 6.6.44 , ≤ 6.6.* (semver) Unaffected: 6.10.3 , ≤ 6.10.* (semver) Unaffected: 6.11 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2024-42297",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2024-09-10T16:10:44.574818Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2024-09-12T17:33:28.885Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
},
{
"providerMetadata": {
"dateUpdated": "2025-11-03T22:03:58.483Z",
"orgId": "af854a3a-2127-422b-91ae-364da2661108",
"shortName": "CVE"
},
"references": [
{
"url": "https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html"
},
{
"url": "https://lists.debian.org/debian-lts-announce/2024/10/msg00003.html"
}
],
"title": "CVE Program Container"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/f2fs/inode.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "2d2916516577f2239b3377d9e8d12da5e6ccdfcf",
"status": "affected",
"version": "98e4da8ca301e062d79ae168c67e56f3c3de3ce4",
"versionType": "git"
},
{
"lessThan": "54162974aea37a8cae00742470a78c7f6bd6f915",
"status": "affected",
"version": "98e4da8ca301e062d79ae168c67e56f3c3de3ce4",
"versionType": "git"
},
{
"lessThan": "54bc4e88447e385c4d4ffa85d93e0dce628fcfa6",
"status": "affected",
"version": "98e4da8ca301e062d79ae168c67e56f3c3de3ce4",
"versionType": "git"
},
{
"lessThan": "ec56571b4b146a1cfbedab49d5fcaf19fe8bf4f1",
"status": "affected",
"version": "98e4da8ca301e062d79ae168c67e56f3c3de3ce4",
"versionType": "git"
},
{
"lessThan": "9ce8135accf103f7333af472709125878704fdd4",
"status": "affected",
"version": "98e4da8ca301e062d79ae168c67e56f3c3de3ce4",
"versionType": "git"
},
{
"lessThan": "e62ff092a42f4a1bae3b310cf46673b4f3aac3b5",
"status": "affected",
"version": "98e4da8ca301e062d79ae168c67e56f3c3de3ce4",
"versionType": "git"
},
{
"lessThan": "2434344559f6743efb3ac15d11af9a0db9543bd3",
"status": "affected",
"version": "98e4da8ca301e062d79ae168c67e56f3c3de3ce4",
"versionType": "git"
},
{
"lessThan": "192b8fb8d1c8ca3c87366ebbef599fa80bb626b8",
"status": "affected",
"version": "98e4da8ca301e062d79ae168c67e56f3c3de3ce4",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/f2fs/inode.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "3.8"
},
{
"lessThan": "3.8",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "4.19.*",
"status": "unaffected",
"version": "4.19.320",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.4.*",
"status": "unaffected",
"version": "5.4.282",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.10.*",
"status": "unaffected",
"version": "5.10.224",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.15.*",
"status": "unaffected",
"version": "5.15.165",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.103",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.44",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.10.*",
"status": "unaffected",
"version": "6.10.3",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "6.11",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "4.19.320",
"versionStartIncluding": "3.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.4.282",
"versionStartIncluding": "3.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.10.224",
"versionStartIncluding": "3.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.15.165",
"versionStartIncluding": "3.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.1.103",
"versionStartIncluding": "3.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.6.44",
"versionStartIncluding": "3.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.10.3",
"versionStartIncluding": "3.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.11",
"versionStartIncluding": "3.8",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to don\u0027t dirty inode for readonly filesystem\n\nsyzbot reports f2fs bug as below:\n\nkernel BUG at fs/f2fs/inode.c:933!\nRIP: 0010:f2fs_evict_inode+0x1576/0x1590 fs/f2fs/inode.c:933\nCall Trace:\n evict+0x2a4/0x620 fs/inode.c:664\n dispose_list fs/inode.c:697 [inline]\n evict_inodes+0x5f8/0x690 fs/inode.c:747\n generic_shutdown_super+0x9d/0x2c0 fs/super.c:675\n kill_block_super+0x44/0x90 fs/super.c:1667\n kill_f2fs_super+0x303/0x3b0 fs/f2fs/super.c:4894\n deactivate_locked_super+0xc1/0x130 fs/super.c:484\n cleanup_mnt+0x426/0x4c0 fs/namespace.c:1256\n task_work_run+0x24a/0x300 kernel/task_work.c:180\n ptrace_notify+0x2cd/0x380 kernel/signal.c:2399\n ptrace_report_syscall include/linux/ptrace.h:411 [inline]\n ptrace_report_syscall_exit include/linux/ptrace.h:473 [inline]\n syscall_exit_work kernel/entry/common.c:251 [inline]\n syscall_exit_to_user_mode_prepare kernel/entry/common.c:278 [inline]\n __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline]\n syscall_exit_to_user_mode+0x15c/0x280 kernel/entry/common.c:296\n do_syscall_64+0x50/0x110 arch/x86/entry/common.c:88\n entry_SYSCALL_64_after_hwframe+0x63/0x6b\n\nThe root cause is:\n- do_sys_open\n - f2fs_lookup\n - __f2fs_find_entry\n - f2fs_i_depth_write\n - f2fs_mark_inode_dirty_sync\n - f2fs_dirty_inode\n - set_inode_flag(inode, FI_DIRTY_INODE)\n\n- umount\n - kill_f2fs_super\n - kill_block_super\n - generic_shutdown_super\n - sync_filesystem\n : sb is readonly, skip sync_filesystem()\n - evict_inodes\n - iput\n - f2fs_evict_inode\n - f2fs_bug_on(sbi, is_inode_flag_set(inode, FI_DIRTY_INODE))\n : trigger kernel panic\n\nWhen we try to repair i_current_depth in readonly filesystem, let\u0027s\nskip dirty inode to avoid panic in later f2fs_evict_inode()."
}
],
"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 - The vulnerability is reached through local filesystem operations on a mounted f2fs volume \u2014 a path lookup, posix_fadvise(POSIX_FADV_WILLNEED), F2FS_IOC_PRECACHE_EXTENTS, or fiemap \u2014 with the assertion firing during inode eviction. There is no network-facing path into fs/f2fs/inode.c.\nAC:L - The trigger is fully deterministic with no race: one dirtying operation on a read-only f2fs mount guarantees FI_DIRTY_INODE survives to f2fs_evict_inode, since sync_filesystem() is unconditionally skipped for read-only superblocks. CONFIG_F2FS_CHECK_FS turns it into a hard BUG(), but the defect is not conditional on it \u2014 default configs still WARN and free the inode with a dangling sbi-\u003einode_list[DIRTY_META] entry.\nPR:L - An unprivileged local user with only read access to a file on a read-only f2fs mount can dirty the inode; f2fs_ioc_precache_extents() and f2fs_file_fadvise() perform no capability, ownership, or mnt_want_write check, and the __f2fs_find_entry depth-repair path needs nothing beyond stat(). Read-only f2fs volumes are routine on Android and embedded systems where any app can reach them.\nUI:N - The attacker performs the entire dirtying step alone; the eviction that fires the assertion happens during ordinary automatic system activity \u2014 volume unmount by vold/udisks2, media eject, or shutdown \u2014 rather than requiring a victim to be tricked into any action. On desktops where udisks2 permits console-user mount/unmount of removable media, the attacker controls the whole chain unaided.\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 - In default configurations f2fs_bug_on degrades to WARN_ON, so execution continues and f2fs_free_inode() releases the 1200-byte f2fs_inode_info while fi-\u003egdirty_list is still linked into sbi-\u003einode_list[DIRTY_META]; subsequent traversal of that list (f2fs_sync_inode_meta) reads through the freed, sprayable slab object. This is the same stale-gdirty_list use-after-free syzbot reported at this assertion site.\nI:H - The dangling DIRTY_META list node gives a write primitive \u2014 the next f2fs_inode_dirtied(sync=true) performs list_add_tail(), whose __list_add() writes a kernel pointer through head-\u003eprev into the freed and potentially reallocated f2fs_inode_cache object. Heap-sprayable slab corruption of this kind is exploitable for control-flow hijacking.\nA:H - With CONFIG_F2FS_CHECK_FS the f2fs_bug_on at fs/f2fs/inode.c:933 is a BUG_ON that panics the kernel mid-unmount, exactly as syzbot reported; without it the WARN_ON still panics under panic_on_warn and leaves the filesystem flagged SBI_NEED_FSCK. Either way the result is a full denial of service."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-05T11:36:27.711Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/2d2916516577f2239b3377d9e8d12da5e6ccdfcf"
},
{
"url": "https://git.kernel.org/stable/c/54162974aea37a8cae00742470a78c7f6bd6f915"
},
{
"url": "https://git.kernel.org/stable/c/54bc4e88447e385c4d4ffa85d93e0dce628fcfa6"
},
{
"url": "https://git.kernel.org/stable/c/ec56571b4b146a1cfbedab49d5fcaf19fe8bf4f1"
},
{
"url": "https://git.kernel.org/stable/c/9ce8135accf103f7333af472709125878704fdd4"
},
{
"url": "https://git.kernel.org/stable/c/e62ff092a42f4a1bae3b310cf46673b4f3aac3b5"
},
{
"url": "https://git.kernel.org/stable/c/2434344559f6743efb3ac15d11af9a0db9543bd3"
},
{
"url": "https://git.kernel.org/stable/c/192b8fb8d1c8ca3c87366ebbef599fa80bb626b8"
}
],
"title": "f2fs: fix to don\u0027t dirty inode for readonly filesystem",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2024-42297",
"datePublished": "2024-08-17T09:09:05.076Z",
"dateReserved": "2024-07-30T07:40:12.269Z",
"dateUpdated": "2026-08-05T11:36:27.711Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2024-42297",
"date": "2026-10-04",
"epss": "0.00246",
"percentile": "0.14355"
},
"fkie_nvd": {
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "5C41F9D9-FD77-4351-9E80-31CDB3FB794F",
"versionEndExcluding": "6.1.103",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "CC912330-6B41-4C6B-99AF-F3857FBACB6A",
"versionEndExcluding": "6.6.44",
"versionStartIncluding": "6.2",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "92D388F2-1EAF-4CFA-AC06-5B26D762EA7D",
"versionEndExcluding": "6.10.3",
"versionStartIncluding": "6.7",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to don\u0027t dirty inode for readonly filesystem\n\nsyzbot reports f2fs bug as below:\n\nkernel BUG at fs/f2fs/inode.c:933!\nRIP: 0010:f2fs_evict_inode+0x1576/0x1590 fs/f2fs/inode.c:933\nCall Trace:\n evict+0x2a4/0x620 fs/inode.c:664\n dispose_list fs/inode.c:697 [inline]\n evict_inodes+0x5f8/0x690 fs/inode.c:747\n generic_shutdown_super+0x9d/0x2c0 fs/super.c:675\n kill_block_super+0x44/0x90 fs/super.c:1667\n kill_f2fs_super+0x303/0x3b0 fs/f2fs/super.c:4894\n deactivate_locked_super+0xc1/0x130 fs/super.c:484\n cleanup_mnt+0x426/0x4c0 fs/namespace.c:1256\n task_work_run+0x24a/0x300 kernel/task_work.c:180\n ptrace_notify+0x2cd/0x380 kernel/signal.c:2399\n ptrace_report_syscall include/linux/ptrace.h:411 [inline]\n ptrace_report_syscall_exit include/linux/ptrace.h:473 [inline]\n syscall_exit_work kernel/entry/common.c:251 [inline]\n syscall_exit_to_user_mode_prepare kernel/entry/common.c:278 [inline]\n __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline]\n syscall_exit_to_user_mode+0x15c/0x280 kernel/entry/common.c:296\n do_syscall_64+0x50/0x110 arch/x86/entry/common.c:88\n entry_SYSCALL_64_after_hwframe+0x63/0x6b\n\nThe root cause is:\n- do_sys_open\n - f2fs_lookup\n - __f2fs_find_entry\n - f2fs_i_depth_write\n - f2fs_mark_inode_dirty_sync\n - f2fs_dirty_inode\n - set_inode_flag(inode, FI_DIRTY_INODE)\n\n- umount\n - kill_f2fs_super\n - kill_block_super\n - generic_shutdown_super\n - sync_filesystem\n : sb is readonly, skip sync_filesystem()\n - evict_inodes\n - iput\n - f2fs_evict_inode\n - f2fs_bug_on(sbi, is_inode_flag_set(inode, FI_DIRTY_INODE))\n : trigger kernel panic\n\nWhen we try to repair i_current_depth in readonly filesystem, let\u0027s\nskip dirty inode to avoid panic in later f2fs_evict_inode()."
},
{
"lang": "es",
"value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: f2fs: soluci\u00f3n para no ensuciar el inodo para el sistema de archivos de solo lectura syzbot informa el error de f2fs como se muestra a continuaci\u00f3n: \u00a1ERROR del kernel en fs/f2fs/inode.c:933! RIP: 0010:f2fs_evict_inode+0x1576/0x1590 fs/f2fs/inode.c:933 Seguimiento de llamadas: desalojar+0x2a4/0x620 fs/inode.c:664 dispose_list fs/inode.c:697 [en l\u00ednea] evict_inodes+0x5f8/0x690 fs /inode.c:747 generic_shutdown_super+0x9d/0x2c0 fs/super.c:675 kill_block_super+0x44/0x90 fs/super.c:1667 kill_f2fs_super+0x303/0x3b0 fs/f2fs/super.c:4894 desactivar_locked_super+0xc1/0x130 fs /super.c:484 cleanup_mnt+0x426/0x4c0 fs/namespace.c:1256 task_work_run+0x24a/0x300 kernel/task_work.c:180 ptrace_notify+0x2cd/0x380 kernel/signal.c:2399 ptrace_report_syscall include/linux/ptrace.h :411 [en l\u00ednea] ptrace_report_syscall_exit include/linux/ptrace.h:473 [en l\u00ednea] syscall_exit_work kernel/entry/common.c:251 [en l\u00ednea] syscall_exit_to_user_mode_prepare kernel/entry/common.c:278 [en l\u00ednea] __syscall_exit_to_user_mode_work kernel/entry/common .c:283 [inline] syscall_exit_to_user_mode+0x15c/0x280 kernel/entry/common.c:296 do_syscall_64+0x50/0x110 arch/x86/entry/common.c:88 entry_SYSCALL_64_after_hwframe+0x63/0x6b The root cause is: - do_sys_open - f2fs_lookup - __f2fs_find_entry - f2fs_i_ Depth_write - f2fs_mark_inode_dirty_sync - f2fs_dirty_inode - set_inode_flag(inode, FI_DIRTY_INODE) - umount - kill_f2fs_super - kill_block_super - generic_shutdown_super - sync_filesystem: sb es de solo lectura, omitir sync_file sistema() - evict_inodes - iput - f2fs_evict_inode - f2fs_bug_on(sbi, is_inode_flag_set(inodo, FI_DIRTY_INODE)): desencadena el p\u00e1nico en el kernel Cuando intentamos reparar i_current_ Depth en un sistema de archivos de solo lectura, omitamos el inodo sucio para evitar el p\u00e1nico en f2fs_evict_inode()."
}
],
"id": "CVE-2024-42297",
"lastModified": "2024-09-30T13:41:26.463",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
}
]
},
"published": "2024-08-17T09:15:10.147",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/192b8fb8d1c8ca3c87366ebbef599fa80bb626b8"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/2434344559f6743efb3ac15d11af9a0db9543bd3"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/2d2916516577f2239b3377d9e8d12da5e6ccdfcf"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/54162974aea37a8cae00742470a78c7f6bd6f915"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/54bc4e88447e385c4d4ffa85d93e0dce628fcfa6"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/9ce8135accf103f7333af472709125878704fdd4"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/e62ff092a42f4a1bae3b310cf46673b4f3aac3b5"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/ec56571b4b146a1cfbedab49d5fcaf19fe8bf4f1"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Analyzed",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "NVD-CWE-noinfo"
}
],
"source": "nvd@nist.gov",
"type": "Primary"
}
]
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/f2fs/inode.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "2d2916516577f2239b3377d9e8d12da5e6ccdfcf",
"status": "affected",
"version": "98e4da8ca301e062d79ae168c67e56f3c3de3ce4",
"versionType": "git"
},
{
"lessThan": "54162974aea37a8cae00742470a78c7f6bd6f915",
"status": "affected",
"version": "98e4da8ca301e062d79ae168c67e56f3c3de3ce4",
"versionType": "git"
},
{
"lessThan": "54bc4e88447e385c4d4ffa85d93e0dce628fcfa6",
"status": "affected",
"version": "98e4da8ca301e062d79ae168c67e56f3c3de3ce4",
"versionType": "git"
},
{
"lessThan": "ec56571b4b146a1cfbedab49d5fcaf19fe8bf4f1",
"status": "affected",
"version": "98e4da8ca301e062d79ae168c67e56f3c3de3ce4",
"versionType": "git"
},
{
"lessThan": "9ce8135accf103f7333af472709125878704fdd4",
"status": "affected",
"version": "98e4da8ca301e062d79ae168c67e56f3c3de3ce4",
"versionType": "git"
},
{
"lessThan": "e62ff092a42f4a1bae3b310cf46673b4f3aac3b5",
"status": "affected",
"version": "98e4da8ca301e062d79ae168c67e56f3c3de3ce4",
"versionType": "git"
},
{
"lessThan": "2434344559f6743efb3ac15d11af9a0db9543bd3",
"status": "affected",
"version": "98e4da8ca301e062d79ae168c67e56f3c3de3ce4",
"versionType": "git"
},
{
"lessThan": "192b8fb8d1c8ca3c87366ebbef599fa80bb626b8",
"status": "affected",
"version": "98e4da8ca301e062d79ae168c67e56f3c3de3ce4",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/f2fs/inode.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "3.8"
},
{
"lessThan": "3.8",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "4.19.*",
"status": "unaffected",
"version": "4.19.320",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.4.*",
"status": "unaffected",
"version": "5.4.282",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.10.*",
"status": "unaffected",
"version": "5.10.224",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.15.*",
"status": "unaffected",
"version": "5.15.165",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.103",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.44",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.10.*",
"status": "unaffected",
"version": "6.10.3",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "6.11",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "5C41F9D9-FD77-4351-9E80-31CDB3FB794F",
"versionEndExcluding": "6.1.103",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "CC912330-6B41-4C6B-99AF-F3857FBACB6A",
"versionEndExcluding": "6.6.44",
"versionStartIncluding": "6.2",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "92D388F2-1EAF-4CFA-AC06-5B26D762EA7D",
"versionEndExcluding": "6.10.3",
"versionStartIncluding": "6.7",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to don\u0027t dirty inode for readonly filesystem\n\nsyzbot reports f2fs bug as below:\n\nkernel BUG at fs/f2fs/inode.c:933!\nRIP: 0010:f2fs_evict_inode+0x1576/0x1590 fs/f2fs/inode.c:933\nCall Trace:\n evict+0x2a4/0x620 fs/inode.c:664\n dispose_list fs/inode.c:697 [inline]\n evict_inodes+0x5f8/0x690 fs/inode.c:747\n generic_shutdown_super+0x9d/0x2c0 fs/super.c:675\n kill_block_super+0x44/0x90 fs/super.c:1667\n kill_f2fs_super+0x303/0x3b0 fs/f2fs/super.c:4894\n deactivate_locked_super+0xc1/0x130 fs/super.c:484\n cleanup_mnt+0x426/0x4c0 fs/namespace.c:1256\n task_work_run+0x24a/0x300 kernel/task_work.c:180\n ptrace_notify+0x2cd/0x380 kernel/signal.c:2399\n ptrace_report_syscall include/linux/ptrace.h:411 [inline]\n ptrace_report_syscall_exit include/linux/ptrace.h:473 [inline]\n syscall_exit_work kernel/entry/common.c:251 [inline]\n syscall_exit_to_user_mode_prepare kernel/entry/common.c:278 [inline]\n __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline]\n syscall_exit_to_user_mode+0x15c/0x280 kernel/entry/common.c:296\n do_syscall_64+0x50/0x110 arch/x86/entry/common.c:88\n entry_SYSCALL_64_after_hwframe+0x63/0x6b\n\nThe root cause is:\n- do_sys_open\n - f2fs_lookup\n - __f2fs_find_entry\n - f2fs_i_depth_write\n - f2fs_mark_inode_dirty_sync\n - f2fs_dirty_inode\n - set_inode_flag(inode, FI_DIRTY_INODE)\n\n- umount\n - kill_f2fs_super\n - kill_block_super\n - generic_shutdown_super\n - sync_filesystem\n : sb is readonly, skip sync_filesystem()\n - evict_inodes\n - iput\n - f2fs_evict_inode\n - f2fs_bug_on(sbi, is_inode_flag_set(inode, FI_DIRTY_INODE))\n : trigger kernel panic\n\nWhen we try to repair i_current_depth in readonly filesystem, let\u0027s\nskip dirty inode to avoid panic in later f2fs_evict_inode()."
},
{
"lang": "es",
"value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: f2fs: soluci\u00f3n para no ensuciar el inodo para el sistema de archivos de solo lectura syzbot informa el error de f2fs como se muestra a continuaci\u00f3n: \u00a1ERROR del kernel en fs/f2fs/inode.c:933! RIP: 0010:f2fs_evict_inode+0x1576/0x1590 fs/f2fs/inode.c:933 Seguimiento de llamadas: desalojar+0x2a4/0x620 fs/inode.c:664 dispose_list fs/inode.c:697 [en l\u00ednea] evict_inodes+0x5f8/0x690 fs /inode.c:747 generic_shutdown_super+0x9d/0x2c0 fs/super.c:675 kill_block_super+0x44/0x90 fs/super.c:1667 kill_f2fs_super+0x303/0x3b0 fs/f2fs/super.c:4894 desactivar_locked_super+0xc1/0x130 fs /super.c:484 cleanup_mnt+0x426/0x4c0 fs/namespace.c:1256 task_work_run+0x24a/0x300 kernel/task_work.c:180 ptrace_notify+0x2cd/0x380 kernel/signal.c:2399 ptrace_report_syscall include/linux/ptrace.h :411 [en l\u00ednea] ptrace_report_syscall_exit include/linux/ptrace.h:473 [en l\u00ednea] syscall_exit_work kernel/entry/common.c:251 [en l\u00ednea] syscall_exit_to_user_mode_prepare kernel/entry/common.c:278 [en l\u00ednea] __syscall_exit_to_user_mode_work kernel/entry/common .c:283 [inline] syscall_exit_to_user_mode+0x15c/0x280 kernel/entry/common.c:296 do_syscall_64+0x50/0x110 arch/x86/entry/common.c:88 entry_SYSCALL_64_after_hwframe+0x63/0x6b The root cause is: - do_sys_open - f2fs_lookup - __f2fs_find_entry - f2fs_i_ Depth_write - f2fs_mark_inode_dirty_sync - f2fs_dirty_inode - set_inode_flag(inode, FI_DIRTY_INODE) - umount - kill_f2fs_super - kill_block_super - generic_shutdown_super - sync_filesystem: sb es de solo lectura, omitir sync_file sistema() - evict_inodes - iput - f2fs_evict_inode - f2fs_bug_on(sbi, is_inode_flag_set(inodo, FI_DIRTY_INODE)): desencadena el p\u00e1nico en el kernel Cuando intentamos reparar i_current_ Depth en un sistema de archivos de solo lectura, omitamos el inodo sucio para evitar el p\u00e1nico en f2fs_evict_inode()."
}
],
"id": "CVE-2024-42297",
"lastModified": "2026-08-04T11:19:49.133",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 5.9,
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"type": "Secondary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2024-42297",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2024-09-10T16:10:44.574818Z",
"version": "2.0.3"
}
}
]
},
"published": "2024-08-17T09:15:10.147",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/192b8fb8d1c8ca3c87366ebbef599fa80bb626b8"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/2434344559f6743efb3ac15d11af9a0db9543bd3"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/2d2916516577f2239b3377d9e8d12da5e6ccdfcf"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/54162974aea37a8cae00742470a78c7f6bd6f915"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/54bc4e88447e385c4d4ffa85d93e0dce628fcfa6"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/9ce8135accf103f7333af472709125878704fdd4"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/e62ff092a42f4a1bae3b310cf46673b4f3aac3b5"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/ec56571b4b146a1cfbedab49d5fcaf19fe8bf4f1"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"url": "https://lists.debian.org/debian-lts-announce/2024/10/msg00003.html"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"url": "https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Modified",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "NVD-CWE-noinfo"
}
],
"source": "nvd@nist.gov",
"type": "Primary"
}
]
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-08-04T18:28:05+00:00",
"cve": "CVE-2024-42297",
"id": "CVE-2024-42297",
"initial_release_date": "2024-08-17T00:00:00+00:00",
"product_status:known_not_affected": "198",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: f2fs: fix to don\u0027t dirty inode for readonly filesystem",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2024/cve-2024-42297.json",
"version": "3"
},
"suse_vex": {
"aggregate_severity": "moderate",
"current_release_date": "2026-08-31T13:53:59Z",
"cve": "CVE-2024-42297",
"id": "CVE-2024-42297",
"initial_release_date": "2024-08-18T02:02:27Z",
"product_status:known_not_affected": "610",
"source": "SUSE CSAF VEX",
"status": "interim",
"title": "SUSE CVE CVE-2024-42297",
"url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2024-42297.json",
"version": "37"
},
"vulnrichment": {
"containers": {
"adp": [
{
"providerMetadata": {
"dateUpdated": "2025-11-03T22:03:58.483Z",
"orgId": "af854a3a-2127-422b-91ae-364da2661108",
"shortName": "CVE"
},
"references": [
{
"url": "https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html"
},
{
"url": "https://lists.debian.org/debian-lts-announce/2024/10/msg00003.html"
}
],
"title": "CVE Program Container"
},
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2024-42297",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2024-09-10T16:10:44.574818Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2024-09-11T12:42:23.615Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/f2fs/inode.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "2d2916516577f2239b3377d9e8d12da5e6ccdfcf",
"status": "affected",
"version": "98e4da8ca301e062d79ae168c67e56f3c3de3ce4",
"versionType": "git"
},
{
"lessThan": "54162974aea37a8cae00742470a78c7f6bd6f915",
"status": "affected",
"version": "98e4da8ca301e062d79ae168c67e56f3c3de3ce4",
"versionType": "git"
},
{
"lessThan": "54bc4e88447e385c4d4ffa85d93e0dce628fcfa6",
"status": "affected",
"version": "98e4da8ca301e062d79ae168c67e56f3c3de3ce4",
"versionType": "git"
},
{
"lessThan": "ec56571b4b146a1cfbedab49d5fcaf19fe8bf4f1",
"status": "affected",
"version": "98e4da8ca301e062d79ae168c67e56f3c3de3ce4",
"versionType": "git"
},
{
"lessThan": "9ce8135accf103f7333af472709125878704fdd4",
"status": "affected",
"version": "98e4da8ca301e062d79ae168c67e56f3c3de3ce4",
"versionType": "git"
},
{
"lessThan": "e62ff092a42f4a1bae3b310cf46673b4f3aac3b5",
"status": "affected",
"version": "98e4da8ca301e062d79ae168c67e56f3c3de3ce4",
"versionType": "git"
},
{
"lessThan": "2434344559f6743efb3ac15d11af9a0db9543bd3",
"status": "affected",
"version": "98e4da8ca301e062d79ae168c67e56f3c3de3ce4",
"versionType": "git"
},
{
"lessThan": "192b8fb8d1c8ca3c87366ebbef599fa80bb626b8",
"status": "affected",
"version": "98e4da8ca301e062d79ae168c67e56f3c3de3ce4",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/f2fs/inode.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "3.8"
},
{
"lessThan": "3.8",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "4.19.*",
"status": "unaffected",
"version": "4.19.320",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.4.*",
"status": "unaffected",
"version": "5.4.282",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.10.*",
"status": "unaffected",
"version": "5.10.224",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.15.*",
"status": "unaffected",
"version": "5.15.165",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.103",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.44",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.10.*",
"status": "unaffected",
"version": "6.10.3",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "6.11",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "4.19.320",
"versionStartIncluding": "3.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.4.282",
"versionStartIncluding": "3.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.10.224",
"versionStartIncluding": "3.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.15.165",
"versionStartIncluding": "3.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.1.103",
"versionStartIncluding": "3.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.6.44",
"versionStartIncluding": "3.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.10.3",
"versionStartIncluding": "3.8",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.11",
"versionStartIncluding": "3.8",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to don\u0027t dirty inode for readonly filesystem\n\nsyzbot reports f2fs bug as below:\n\nkernel BUG at fs/f2fs/inode.c:933!\nRIP: 0010:f2fs_evict_inode+0x1576/0x1590 fs/f2fs/inode.c:933\nCall Trace:\n evict+0x2a4/0x620 fs/inode.c:664\n dispose_list fs/inode.c:697 [inline]\n evict_inodes+0x5f8/0x690 fs/inode.c:747\n generic_shutdown_super+0x9d/0x2c0 fs/super.c:675\n kill_block_super+0x44/0x90 fs/super.c:1667\n kill_f2fs_super+0x303/0x3b0 fs/f2fs/super.c:4894\n deactivate_locked_super+0xc1/0x130 fs/super.c:484\n cleanup_mnt+0x426/0x4c0 fs/namespace.c:1256\n task_work_run+0x24a/0x300 kernel/task_work.c:180\n ptrace_notify+0x2cd/0x380 kernel/signal.c:2399\n ptrace_report_syscall include/linux/ptrace.h:411 [inline]\n ptrace_report_syscall_exit include/linux/ptrace.h:473 [inline]\n syscall_exit_work kernel/entry/common.c:251 [inline]\n syscall_exit_to_user_mode_prepare kernel/entry/common.c:278 [inline]\n __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline]\n syscall_exit_to_user_mode+0x15c/0x280 kernel/entry/common.c:296\n do_syscall_64+0x50/0x110 arch/x86/entry/common.c:88\n entry_SYSCALL_64_after_hwframe+0x63/0x6b\n\nThe root cause is:\n- do_sys_open\n - f2fs_lookup\n - __f2fs_find_entry\n - f2fs_i_depth_write\n - f2fs_mark_inode_dirty_sync\n - f2fs_dirty_inode\n - set_inode_flag(inode, FI_DIRTY_INODE)\n\n- umount\n - kill_f2fs_super\n - kill_block_super\n - generic_shutdown_super\n - sync_filesystem\n : sb is readonly, skip sync_filesystem()\n - evict_inodes\n - iput\n - f2fs_evict_inode\n - f2fs_bug_on(sbi, is_inode_flag_set(inode, FI_DIRTY_INODE))\n : trigger kernel panic\n\nWhen we try to repair i_current_depth in readonly filesystem, let\u0027s\nskip dirty inode to avoid panic in later f2fs_evict_inode()."
}
],
"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 - The vulnerability is reached through local filesystem operations on a mounted f2fs volume \u2014 a path lookup, posix_fadvise(POSIX_FADV_WILLNEED), F2FS_IOC_PRECACHE_EXTENTS, or fiemap \u2014 with the assertion firing during inode eviction. There is no network-facing path into fs/f2fs/inode.c.\nAC:L - The trigger is fully deterministic with no race: one dirtying operation on a read-only f2fs mount guarantees FI_DIRTY_INODE survives to f2fs_evict_inode, since sync_filesystem() is unconditionally skipped for read-only superblocks. CONFIG_F2FS_CHECK_FS turns it into a hard BUG(), but the defect is not conditional on it \u2014 default configs still WARN and free the inode with a dangling sbi-\u003einode_list[DIRTY_META] entry.\nPR:L - An unprivileged local user with only read access to a file on a read-only f2fs mount can dirty the inode; f2fs_ioc_precache_extents() and f2fs_file_fadvise() perform no capability, ownership, or mnt_want_write check, and the __f2fs_find_entry depth-repair path needs nothing beyond stat(). Read-only f2fs volumes are routine on Android and embedded systems where any app can reach them.\nUI:N - The attacker performs the entire dirtying step alone; the eviction that fires the assertion happens during ordinary automatic system activity \u2014 volume unmount by vold/udisks2, media eject, or shutdown \u2014 rather than requiring a victim to be tricked into any action. On desktops where udisks2 permits console-user mount/unmount of removable media, the attacker controls the whole chain unaided.\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 - In default configurations f2fs_bug_on degrades to WARN_ON, so execution continues and f2fs_free_inode() releases the 1200-byte f2fs_inode_info while fi-\u003egdirty_list is still linked into sbi-\u003einode_list[DIRTY_META]; subsequent traversal of that list (f2fs_sync_inode_meta) reads through the freed, sprayable slab object. This is the same stale-gdirty_list use-after-free syzbot reported at this assertion site.\nI:H - The dangling DIRTY_META list node gives a write primitive \u2014 the next f2fs_inode_dirtied(sync=true) performs list_add_tail(), whose __list_add() writes a kernel pointer through head-\u003eprev into the freed and potentially reallocated f2fs_inode_cache object. Heap-sprayable slab corruption of this kind is exploitable for control-flow hijacking.\nA:H - With CONFIG_F2FS_CHECK_FS the f2fs_bug_on at fs/f2fs/inode.c:933 is a BUG_ON that panics the kernel mid-unmount, exactly as syzbot reported; without it the WARN_ON still panics under panic_on_warn and leaves the filesystem flagged SBI_NEED_FSCK. Either way the result is a full denial of service."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-05T11:36:27.711Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/2d2916516577f2239b3377d9e8d12da5e6ccdfcf"
},
{
"url": "https://git.kernel.org/stable/c/54162974aea37a8cae00742470a78c7f6bd6f915"
},
{
"url": "https://git.kernel.org/stable/c/54bc4e88447e385c4d4ffa85d93e0dce628fcfa6"
},
{
"url": "https://git.kernel.org/stable/c/ec56571b4b146a1cfbedab49d5fcaf19fe8bf4f1"
},
{
"url": "https://git.kernel.org/stable/c/9ce8135accf103f7333af472709125878704fdd4"
},
{
"url": "https://git.kernel.org/stable/c/e62ff092a42f4a1bae3b310cf46673b4f3aac3b5"
},
{
"url": "https://git.kernel.org/stable/c/2434344559f6743efb3ac15d11af9a0db9543bd3"
},
{
"url": "https://git.kernel.org/stable/c/192b8fb8d1c8ca3c87366ebbef599fa80bb626b8"
}
],
"title": "f2fs: fix to don\u0027t dirty inode for readonly filesystem",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2024-42297",
"datePublished": "2024-08-17T09:09:05.076Z",
"dateReserved": "2024-07-30T07:40:12.269Z",
"dateUpdated": "2026-08-05T11:36:27.711Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
OESA-2024-2078 (CVE-2022-48920)
Vulnerability from osv_openeuler – Published: 2024-08-30 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:
btrfs: get rid of warning on transaction commit when using flushoncommit
When using the flushoncommit mount option, during almost every transaction commit we trigger a warning from __writeback_inodes_sb_nr():
$ cat fs/fs-writeback.c: (...) static void __writeback_inodes_sb_nr(struct super_block *sb, ... { (...) WARN_ON(!rwsem_is_locked(&sb->s_umount)); (...) } (...)
The trace produced in dmesg looks like the following:
[947.473890] WARNING: CPU: 5 PID: 930 at fs/fs-writeback.c:2610 __writeback_inodes_sb_nr+0x7e/0xb3 [947.481623] Modules linked in: nfsd nls_cp437 cifs asn1_decoder cifs_arc4 fscache cifs_md4 ipmi_ssif [947.489571] CPU: 5 PID: 930 Comm: btrfs-transacti Not tainted 95.16.3-srb-asrock-00001-g36437ad63879 #186 [947.497969] RIP: 0010:__writeback_inodes_sb_nr+0x7e/0xb3 [947.502097] Code: 24 10 4c 89 44 24 18 c6 (...) [947.519760] RSP: 0018:ffffc90000777e10 EFLAGS: 00010246 [947.523818] RAX: 0000000000000000 RBX: 0000000000963300 RCX: 0000000000000000 [947.529765] RDX: 0000000000000000 RSI: 000000000000fa51 RDI: ffffc90000777e50 [947.535740] RBP: ffff888101628a90 R08: ffff888100955800 R09: ffff888100956000 [947.541701] R10: 0000000000000002 R11: 0000000000000001 R12: ffff888100963488 [947.547645] R13: ffff888100963000 R14: ffff888112fb7200 R15: ffff888100963460 [947.553621] FS: 0000000000000000(0000) GS:ffff88841fd40000(0000) knlGS:0000000000000000 [947.560537] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [947.565122] CR2: 0000000008be50c4 CR3: 000000000220c000 CR4: 00000000001006e0 [947.571072] Call Trace: [947.572354] <TASK> [947.573266] btrfs_commit_transaction+0x1f1/0x998 [947.576785] ? start_transaction+0x3ab/0x44e [947.579867] ? schedule_timeout+0x8a/0xdd [947.582716] transaction_kthread+0xe9/0x156 [947.585721] ? btrfs_cleanup_transaction.isra.0+0x407/0x407 [947.590104] kthread+0x131/0x139 [947.592168] ? set_kthread_struct+0x32/0x32 [947.595174] ret_from_fork+0x22/0x30 [947.597561] </TASK> [947.598553] ---[ end trace 644721052755541c ]---
This is because we started using writeback_inodes_sb() to flush delalloc when committing a transaction (when using -o flushoncommit), in order to avoid deadlocks with filesystem freeze operations. This change was made by commit ce8ea7cc6eb313 ("btrfs: don't call btrfs_start_delalloc_roots in flushoncommit"). After that change we started producing that warning, and every now and then a user reports this since the warning happens too often, it spams dmesg/syslog, and a user is unsure if this reflects any problem that might compromise the filesystem's reliability.
We can not just lock the sb->s_umount semaphore before calling writeback_inodes_sb(), because that would at least deadlock with filesystem freezing, since at fs/super.c:freeze_super() sync_filesystem() is called while we are holding that semaphore in write mode, and that can trigger a transaction commit, resulting in a deadlock. It would also trigger the same type of deadlock in the unmount path. Possibly, it could also introduce some other locking dependencies that lockdep would report.
To fix this call try_to_writeback_inodes_sb() instead of writeback_inodes_sb(), because that will try to read lock sb->s_umount and then will only call writeback_inodes_sb() if it was able to lock it. This is fine because the cases where it can't read lock sb->s_umount are during a filesystem unmount or during a filesystem freeze - in those cases sb->s_umount is write locked and sync_filesystem() is called, which calls writeback_inodes_sb(). In other words, in all cases where we can't take a read lock on sb->s_umount, writeback is already being triggered elsewhere.
An alternative would be to call btrfs_start_delalloc_roots() with a number of pages different from LONG_MAX, for example matching the number of delalloc bytes we currently have, in ---truncated---(CVE-2022-48920)
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nf_tables: unregister flowtable hooks on netns exit
Unregister flowtable hooks before they are releases via nf_tables_flowtable_destroy() otherwise hook core reports UAF.
BUG: KASAN: use-after-free in nf_hook_entries_grow+0x5a7/0x700 net/netfilter/core.c:142 net/netfilter/core.c:142 Read of size 4 at addr ffff8880736f7438 by task syz-executor579/3666
CPU: 0 PID: 3666 Comm: syz-executor579 Not tainted 5.16.0-rc5-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] __dump_stack lib/dump_stack.c:88 [inline] lib/dump_stack.c:106 dump_stack_lvl+0x1dc/0x2d8 lib/dump_stack.c:106 lib/dump_stack.c:106 print_address_description+0x65/0x380 mm/kasan/report.c:247 mm/kasan/report.c:247 __kasan_report mm/kasan/report.c:433 [inline] __kasan_report mm/kasan/report.c:433 [inline] mm/kasan/report.c:450 kasan_report+0x19a/0x1f0 mm/kasan/report.c:450 mm/kasan/report.c:450 nf_hook_entries_grow+0x5a7/0x700 net/netfilter/core.c:142 net/netfilter/core.c:142 __nf_register_net_hook+0x27e/0x8d0 net/netfilter/core.c:429 net/netfilter/core.c:429 nf_register_net_hook+0xaa/0x180 net/netfilter/core.c:571 net/netfilter/core.c:571 nft_register_flowtable_net_hooks+0x3c5/0x730 net/netfilter/nf_tables_api.c:7232 net/netfilter/nf_tables_api.c:7232 nf_tables_newflowtable+0x2022/0x2cf0 net/netfilter/nf_tables_api.c:7430 net/netfilter/nf_tables_api.c:7430 nfnetlink_rcv_batch net/netfilter/nfnetlink.c:513 [inline] nfnetlink_rcv_skb_batch net/netfilter/nfnetlink.c:634 [inline] nfnetlink_rcv_batch net/netfilter/nfnetlink.c:513 [inline] net/netfilter/nfnetlink.c:652 nfnetlink_rcv_skb_batch net/netfilter/nfnetlink.c:634 [inline] net/netfilter/nfnetlink.c:652 nfnetlink_rcv+0x10e6/0x2550 net/netfilter/nfnetlink.c:652 net/netfilter/nfnetlink.c:652
__nft_release_hook() calls nft_unregister_flowtable_net_hooks() which only unregisters the hooks, then after RCU grace period, it is guaranteed that no packets add new entries to the flowtable (no flow offload rules and flowtable hooks are reachable from packet path), so it is safe to call nf_flow_table_free() which cleans up the remaining entries from the flowtable (both software and hardware) and it unbinds the flow_block.(CVE-2022-48935)
In the Linux kernel, the following vulnerability has been resolved:
phonet: fix rtm_phonet_notify() skb allocation
fill_route() stores three components in the skb:
- struct rtmsg
- RTA_DST (u8)
- RTA_OIF (u32)
Therefore, rtm_phonet_notify() should use
NLMSG_ALIGN(sizeof(struct rtmsg)) + nla_total_size(1) + nla_total_size(4)(CVE-2024-36946)
In the Linux kernel, the following vulnerability has been resolved:
m68k: Fix spinlock race in kernel thread creation
Context switching does take care to retain the correct lock owner across the switch from 'prev' to 'next' tasks. This does rely on interrupts remaining disabled for the entire duration of the switch.
This condition is guaranteed for normal process creation and context switching between already running processes, because both 'prev' and 'next' already have interrupts disabled in their saved copies of the status register.
The situation is different for newly created kernel threads. The status register is set to PS_S in copy_thread(), which does leave the IPL at 0. Upon restoring the 'next' thread's status register in switch_to() aka resume(), interrupts then become enabled prematurely. resume() then returns via ret_from_kernel_thread() and schedule_tail() where run queue lock is released (see finish_task_switch() and finish_lock_switch()).
A timer interrupt calling scheduler_tick() before the lock is released in finish_task_switch() will find the lock already taken, with the current task as lock owner. This causes a spinlock recursion warning as reported by Guenter Roeck.
As far as I can ascertain, this race has been opened in commit 533e6903bea0 ("m68k: split ret_from_fork(), simplify kernel_thread()") but I haven't done a detailed study of kernel history so it may well predate that commit.
Interrupts cannot be disabled in the saved status register copy for kernel threads (init will complain about interrupts disabled when finally starting user space). Disable interrupts temporarily when switching the tasks' register sets in resume().
Note that a simple oriw 0x700,%sr after restoring sr is not enough here - this leaves enough of a race for the 'spinlock recursion' warning to still be observed.
Tested on ARAnyM and qemu (Quadra 800 emulation).(CVE-2024-38613)
In the Linux kernel, the following vulnerability has been resolved:
ipv6: sr: fix missing sk_buff release in seg6_input_core
The seg6_input() function is responsible for adding the SRH into a packet, delegating the operation to the seg6_input_core(). This function uses the skb_cow_head() to ensure that there is sufficient headroom in the sk_buff for accommodating the link-layer header. In the event that the skb_cow_header() function fails, the seg6_input_core() catches the error but it does not release the sk_buff, which will result in a memory leak.
This issue was introduced in commit af3b5158b89d ("ipv6: sr: fix BUG due to headroom too small after SRH push") and persists even after commit 7a3f5b0de364 ("netfilter: add netfilter hooks to SRv6 data plane"), where the entire seg6_input() code was refactored to deal with netfilter hooks.
The proposed patch addresses the identified memory leak by requiring the seg6_input_core() function to release the sk_buff in the event that skb_cow_head() fails.(CVE-2024-39490)
In the Linux kernel, the following vulnerability has been resolved:
crypto: hisilicon/sec - Fix memory leak for sec resource release
The AIV is one of the SEC resources. When releasing resources, it need to release the AIV resources at the same time. Otherwise, memory leakage occurs.
The aiv resource release is added to the sec resource release function.(CVE-2024-41002)
In the Linux kernel, the following vulnerability has been resolved:
ocfs2: add bounds checking to ocfs2_check_dir_entry()
This adds sanity checks for ocfs2_dir_entry to make sure all members of ocfs2_dir_entry don't stray beyond valid memory region.(CVE-2024-41015)
In the Linux kernel, the following vulnerability has been resolved:
hfsplus: fix uninit-value in copy_name
[syzbot reported] BUG: KMSAN: uninit-value in sized_strscpy+0xc4/0x160 sized_strscpy+0xc4/0x160 copy_name+0x2af/0x320 fs/hfsplus/xattr.c:411 hfsplus_listxattr+0x11e9/0x1a50 fs/hfsplus/xattr.c:750 vfs_listxattr fs/xattr.c:493 [inline] listxattr+0x1f3/0x6b0 fs/xattr.c:840 path_listxattr fs/xattr.c:864 [inline] __do_sys_listxattr fs/xattr.c:876 [inline] __se_sys_listxattr fs/xattr.c:873 [inline] __x64_sys_listxattr+0x16b/0x2f0 fs/xattr.c:873 x64_sys_call+0x2ba0/0x3b50 arch/x86/include/generated/asm/syscalls_64.h:195 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
Uninit was created at: slab_post_alloc_hook mm/slub.c:3877 [inline] slab_alloc_node mm/slub.c:3918 [inline] kmalloc_trace+0x57b/0xbe0 mm/slub.c:4065 kmalloc include/linux/slab.h:628 [inline] hfsplus_listxattr+0x4cc/0x1a50 fs/hfsplus/xattr.c:699 vfs_listxattr fs/xattr.c:493 [inline] listxattr+0x1f3/0x6b0 fs/xattr.c:840 path_listxattr fs/xattr.c:864 [inline] __do_sys_listxattr fs/xattr.c:876 [inline] __se_sys_listxattr fs/xattr.c:873 [inline] __x64_sys_listxattr+0x16b/0x2f0 fs/xattr.c:873 x64_sys_call+0x2ba0/0x3b50 arch/x86/include/generated/asm/syscalls_64.h:195 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 [Fix] When allocating memory to strbuf, initialize memory to 0.(CVE-2024-41059)
In the Linux kernel, the following vulnerability has been resolved:
s390/sclp: Fix sclp_init() cleanup on failure
If sclp_init() fails it only partially cleans up: if there are multiple failing calls to sclp_init() sclp_state_change_event will be added several times to sclp_reg_list, which results in the following warning:
------------[ cut here ]------------ list_add double add: new=000003ffe1598c10, prev=000003ffe1598bf0, next=000003ffe1598c10. WARNING: CPU: 0 PID: 1 at lib/list_debug.c:35 __list_add_valid_or_report+0xde/0xf8 CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.10.0-rc3 Krnl PSW : 0404c00180000000 000003ffe0d6076a (__list_add_valid_or_report+0xe2/0xf8) R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 ... Call Trace: [<000003ffe0d6076a>] __list_add_valid_or_report+0xe2/0xf8 ([<000003ffe0d60766>] __list_add_valid_or_report+0xde/0xf8) [<000003ffe0a8d37e>] sclp_init+0x40e/0x450 [<000003ffe00009f2>] do_one_initcall+0x42/0x1e0 [<000003ffe15b77a6>] do_initcalls+0x126/0x150 [<000003ffe15b7a0a>] kernel_init_freeable+0x1ba/0x1f8 [<000003ffe0d6650e>] kernel_init+0x2e/0x180 [<000003ffe000301c>] __ret_from_fork+0x3c/0x60 [<000003ffe0d759ca>] ret_from_fork+0xa/0x30
Fix this by removing sclp_state_change_event from sclp_reg_list when sclp_init() fails.(CVE-2024-41068)
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Check pipe offset before setting vblank
pipe_ctx has a size of MAX_PIPES so checking its index before accessing the array.
This fixes an OVERRUN issue reported by Coverity.(CVE-2024-42120)
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Add NULL pointer check for kzalloc
[Why & How] Check return pointer of kzalloc before using it.(CVE-2024-42122)
In the Linux kernel, the following vulnerability has been resolved:
protect the fetch of ->fd[fd] in do_dup2() from mispredictions
both callers have verified that fd is not greater than ->max_fds; however, misprediction might end up with tofree = fdt->fd[fd]; being speculatively executed. That's wrong for the same reasons why it's wrong in close_fd()/file_close_fd_locked(); the same solution applies - array_index_nospec(fd, fdt->max_fds) could differ from fd only in case of speculative execution on mispredicted path.(CVE-2024-42265)
In the Linux kernel, the following vulnerability has been resolved:
net/iucv: fix use after free in iucv_sock_close()
iucv_sever_path() is called from process context and from bh context. iucv->path is used as indicator whether somebody else is taking care of severing the path (or it is already removed / never existed). This needs to be done with atomic compare and swap, otherwise there is a small window where iucv_sock_close() will try to work with a path that has already been severed and freed by iucv_callback_connrej() called by iucv_tasklet_fn().
Example: [452744.123844] Call Trace: [452744.123845] ([<0000001e87f03880>] 0x1e87f03880) [452744.123966] [<00000000d593001e>] iucv_path_sever+0x96/0x138 [452744.124330] [<000003ff801ddbca>] iucv_sever_path+0xc2/0xd0 [af_iucv] [452744.124336] [<000003ff801e01b6>] iucv_sock_close+0xa6/0x310 [af_iucv] [452744.124341] [<000003ff801e08cc>] iucv_sock_release+0x3c/0xd0 [af_iucv] [452744.124345] [<00000000d574794e>] __sock_release+0x5e/0xe8 [452744.124815] [<00000000d5747a0c>] sock_close+0x34/0x48 [452744.124820] [<00000000d5421642>] __fput+0xba/0x268 [452744.124826] [<00000000d51b382c>] task_work_run+0xbc/0xf0 [452744.124832] [<00000000d5145710>] do_notify_resume+0x88/0x90 [452744.124841] [<00000000d5978096>] system_call+0xe2/0x2c8 [452744.125319] Last Breaking-Event-Address: [452744.125321] [<00000000d5930018>] iucv_path_sever+0x90/0x138 [452744.125324] [452744.125325] Kernel panic - not syncing: Fatal exception in interrupt
Note that bh_lock_sock() is not serializing the tasklet context against process context, because the check for sock_owned_by_user() and corresponding handling is missing.
Ideas for a future clean-up patch: A) Correct usage of bh_lock_sock() in tasklet context, as described in Re-enqueue, if needed. This may require adding return values to the tasklet functions and thus changes to all users of iucv.
B) Change iucv tasklet into worker and use only lock_sock() in af_iucv.(CVE-2024-42271)
In the Linux kernel, the following vulnerability has been resolved:
mISDN: Fix a use after free in hfcmulti_tx()
Don't dereference sp after calling dev_kfree_skb(sp).(CVE-2024-42280)
In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix a segment issue when downgrading gso_size
Linearize the skb when downgrading gso_size because it may trigger a BUG_ON() later when the skb is segmented as described in [1,2].(CVE-2024-42281)
In the Linux kernel, the following vulnerability has been resolved:
tipc: Return non-zero value from tipc_udp_addr2str() on error
tipc_udp_addr2str() should return non-zero value if the UDP media address is invalid. Otherwise, a buffer overflow access can occur in tipc_media_addr_printf(). Fix this by returning 1 on an invalid UDP media address.(CVE-2024-42284)
In the Linux kernel, the following vulnerability has been resolved:
RDMA/iwcm: Fix a use-after-free related to destroying CM IDs
iw_conn_req_handler() associates a new struct rdma_id_private (conn_id) with an existing struct iw_cm_id (cm_id) as follows:
conn_id->cm_id.iw = cm_id;
cm_id->context = conn_id;
cm_id->cm_handler = cma_iw_handler;
rdma_destroy_id() frees both the cm_id and the struct rdma_id_private. Make sure that cm_work_handler() does not trigger a use-after-free by only freeing of the struct rdma_id_private after all pending work has finished.(CVE-2024-42285)
In the Linux kernel, the following vulnerability has been resolved:
scsi: qla2xxx: Fix for possible memory corruption
Init Control Block is dereferenced incorrectly. Correctly dereference ICB(CVE-2024-42288)
In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix to don't dirty inode for readonly filesystem
syzbot reports f2fs bug as below:
kernel BUG at fs/f2fs/inode.c:933! RIP: 0010:f2fs_evict_inode+0x1576/0x1590 fs/f2fs/inode.c:933 Call Trace: evict+0x2a4/0x620 fs/inode.c:664 dispose_list fs/inode.c:697 [inline] evict_inodes+0x5f8/0x690 fs/inode.c:747 generic_shutdown_super+0x9d/0x2c0 fs/super.c:675 kill_block_super+0x44/0x90 fs/super.c:1667 kill_f2fs_super+0x303/0x3b0 fs/f2fs/super.c:4894 deactivate_locked_super+0xc1/0x130 fs/super.c:484 cleanup_mnt+0x426/0x4c0 fs/namespace.c:1256 task_work_run+0x24a/0x300 kernel/task_work.c:180 ptrace_notify+0x2cd/0x380 kernel/signal.c:2399 ptrace_report_syscall include/linux/ptrace.h:411 [inline] ptrace_report_syscall_exit include/linux/ptrace.h:473 [inline] syscall_exit_work kernel/entry/common.c:251 [inline] syscall_exit_to_user_mode_prepare kernel/entry/common.c:278 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline] syscall_exit_to_user_mode+0x15c/0x280 kernel/entry/common.c:296 do_syscall_64+0x50/0x110 arch/x86/entry/common.c:88 entry_SYSCALL_64_after_hwframe+0x63/0x6b
The root cause is: - do_sys_open - f2fs_lookup - __f2fs_find_entry - f2fs_i_depth_write - f2fs_mark_inode_dirty_sync - f2fs_dirty_inode - set_inode_flag(inode, FI_DIRTY_INODE)
- umount
- kill_f2fs_super
- kill_block_super
- generic_shutdown_super
- sync_filesystem : sb is readonly, skip sync_filesystem()
- evict_inodes
- iput
- f2fs_evict_inode
- f2fs_bug_on(sbi, is_inode_flag_set(inode, FI_DIRTY_INODE)) : trigger kernel panic
When we try to repair i_current_depth in readonly filesystem, let's skip dirty inode to avoid panic in later f2fs_evict_inode().(CVE-2024-42297)
In the Linux kernel, the following vulnerability has been resolved:
PCI/DPC: Fix use-after-free on concurrent DPC and hot-removal
Keith reports a use-after-free when a DPC event occurs concurrently to hot-removal of the same portion of the hierarchy:
The dpc_handler() awaits readiness of the secondary bus below the Downstream Port where the DPC event occurred. To do so, it polls the config space of the first child device on the secondary bus. If that child device is concurrently removed, accesses to its struct pci_dev cause the kernel to oops.
That's because pci_bridge_wait_for_secondary_bus() neglects to hold a reference on the child device. Before v6.3, the function was only called on resume from system sleep or on runtime resume. Holding a reference wasn't necessary back then because the pciehp IRQ thread could never run concurrently. (On resume from system sleep, IRQs are not enabled until after the resume_noirq phase. And runtime resume is always awaited before a PCI device is removed.)
However starting with v6.3, pci_bridge_wait_for_secondary_bus() is also called on a DPC event. Commit 53b54ad074de ("PCI/DPC: Await readiness of secondary bus after reset"), which introduced that, failed to appreciate that pci_bridge_wait_for_secondary_bus() now needs to hold a reference on the child device because dpc_handler() and pciehp may indeed run concurrently. The commit was backported to v5.10+ stable kernels, so that's the oldest one affected.
Add the missing reference acquisition.
Abridged stack trace:
BUG: unable to handle page fault for address: 00000000091400c0 CPU: 15 PID: 2464 Comm: irq/53-pcie-dpc 6.9.0 RIP: pci_bus_read_config_dword+0x17/0x50 pci_dev_wait() pci_bridge_wait_for_secondary_bus() dpc_reset_link() pcie_do_recovery() dpc_handler()(CVE-2024-42302)
In the Linux kernel, the following vulnerability has been resolved:
ext4: check dot and dotdot of dx_root before making dir indexed
Syzbot reports a issue as follows:
BUG: unable to handle page fault for address: ffffed11022e24fe PGD 23ffee067 P4D 23ffee067 PUD 0 Oops: Oops: 0000 [#1] PREEMPT SMP KASAN PTI CPU: 0 PID: 5079 Comm: syz-executor306 Not tainted 6.10.0-rc5-g55027e689933 #0 Call Trace: <TASK> make_indexed_dir+0xdaf/0x13c0 fs/ext4/namei.c:2341 ext4_add_entry+0x222a/0x25d0 fs/ext4/namei.c:2451 ext4_rename fs/ext4/namei.c:3936 [inline] ext4_rename2+0x26e5/0x4370 fs/ext4/namei.c:4214 [...] ============================================
The immediate cause of this problem is that there is only one valid dentry for the block to be split during do_split, so split==0 results in out of bounds accesses to the map triggering the issue.
do_split
unsigned split
dx_make_map
count = 1
split = count/2 = 0;
continued = hash2 == map[split - 1].hash;
---> map[4294967295]
The maximum length of a filename is 255 and the minimum block size is 1024, so it is always guaranteed that the number of entries is greater than or equal to 2 when do_split() is called.
But syzbot's crafted image has no dot and dotdot in dir, and the dentry distribution in dirblock is as follows:
bus dentry1 hole dentry2 free |xx--|xx-------------|...............|xx-------------|...............| 0 12 (8+248)=256 268 256 524 (8+256)=264 788 236 1024
So when renaming dentry1 increases its name_len length by 1, neither hole nor free is sufficient to hold the new dentry, and make_indexed_dir() is called.
In make_indexed_dir() it is assumed that the first two entries of the dirblock must be dot and dotdot, so bus and dentry1 are left in dx_root because they are treated as dot and dotdot, and only dentry2 is moved to the new leaf block. That's why count is equal to 1.
Therefore add the ext4_check_dx_root() helper function to add more sanity checks to dot and dotdot before starting the conversion to avoid the above issue.(CVE-2024-42305)
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Check for NULL pointer
[why & how] Need to make sure plane_state is initialized before accessing its members.
(cherry picked from commit 295d91cbc700651782a60572f83c24861607b648)(CVE-2024-42308)
In the Linux kernel, the following vulnerability has been resolved:
landlock: Don't lose track of restrictions on cred_transfer
When a process' cred struct is replaced, this almost always invokes the cred_prepare LSM hook; but in one special case (when KEYCTL_SESSION_TO_PARENT updates the parent's credentials), the cred_transfer LSM hook is used instead. Landlock only implements the cred_prepare hook, not cred_transfer, so KEYCTL_SESSION_TO_PARENT causes all information on Landlock restrictions to be lost.
This basically means that a process with the ability to use the fork() and keyctl() syscalls can get rid of all Landlock restrictions on itself.
Fix it by adding a cred_transfer hook that does the same thing as the existing cred_prepare hook. (Implemented by having hook_cred_prepare() call hook_cred_transfer() so that the two functions are less likely to accidentally diverge in the future.)(CVE-2024-42318)
In the Linux kernel, the following vulnerability has been resolved:
kvm: s390: Reject memory region operations for ucontrol VMs
This change rejects the KVM_SET_USER_MEMORY_REGION and KVM_SET_USER_MEMORY_REGION2 ioctls when called on a ucontrol VM. This is necessary since ucontrol VMs have kvm->arch.gmap set to 0 and would thus result in a null pointer dereference further in. Memory management needs to be performed in userspace and using the ioctls KVM_S390_UCAS_MAP and KVM_S390_UCAS_UNMAP.
Also improve s390 specific documentation for KVM_SET_USER_MEMORY_REGION and KVM_SET_USER_MEMORY_REGION2.
frankja@linux.ibm.com: commit message spelling fix, subject prefix fix
In the Linux kernel, the following vulnerability has been resolved:
ext4: fix infinite loop when replaying fast_commit
When doing fast_commit replay an infinite loop may occur due to an uninitialized extent_status struct. ext4_ext_determine_insert_hole() does not detect the replay and calls ext4_es_find_extent_range(), which will return immediately without initializing the 'es' variable.
Because 'es' contains garbage, an integer overflow may happen causing an infinite loop in this function, easily reproducible using fstest generic/039.
This commit fixes this issue by unconditionally initializing the structure in function ext4_es_find_extent_range().
Thanks to Zhang Yi, for figuring out the real problem!(CVE-2024-43828)
In the Linux kernel, the following vulnerability has been resolved:
media: mediatek: vcodec: Handle invalid decoder vsi
Handle an invalid decoder vsi in vpu_dec_init to ensure the decoder vsi is valid for future use.(CVE-2024-43831)
In the Linux kernel, the following vulnerability has been resolved:
cgroup/cpuset: Prevent UAF in proc_cpuset_show()
An UAF can happen when /proc/cpuset is read as reported in [1].
This can be reproduced by the following methods: 1.add an mdelay(1000) before acquiring the cgroup_lock In the cgroup_path_ns function. 2.$cat /proc/<pid>/cpuset repeatly. 3.$mount -t cgroup -o cpuset cpuset /sys/fs/cgroup/cpuset/ $umount /sys/fs/cgroup/cpuset/ repeatly.
The race that cause this bug can be shown as below:
(umount) | (cat /proc/<pid>/cpuset) css_release | proc_cpuset_show css_release_work_fn | css = task_get_css(tsk, cpuset_cgrp_id); css_free_rwork_fn | cgroup_path_ns(css->cgroup, ...); cgroup_destroy_root | mutex_lock(&cgroup_mutex); rebind_subsystems | cgroup_free_root | | // cgrp was freed, UAF | cgroup_path_ns_locked(cgrp,..);
When the cpuset is initialized, the root node top_cpuset.css.cgrp will point to &cgrp_dfl_root.cgrp. In cgroup v1, the mount operation will allocate cgroup_root, and top_cpuset.css.cgrp will point to the allocated &cgroup_root.cgrp. When the umount operation is executed, top_cpuset.css.cgrp will be rebound to &cgrp_dfl_root.cgrp.
The problem is that when rebinding to cgrp_dfl_root, there are cases where the cgroup_root allocated by setting up the root for cgroup v1 is cached. This could lead to a Use-After-Free (UAF) if it is subsequently freed. The descendant cgroups of cgroup v1 can only be freed after the css is released. However, the css of the root will never be released, yet the cgroup_root should be freed when it is unmounted. This means that obtaining a reference to the css of the root does not guarantee that css.cgrp->root will not be freed.
Fix this problem by using rcu_read_lock in proc_cpuset_show(). As cgroup_root is kfree_rcu after commit d23b5c577715 ("cgroup: Make operations on the cgroup root_list RCU safe"), css->cgroup won't be freed during the critical section. To call cgroup_path_ns_locked, css_set_lock is needed, so it is safe to replace task_get_css with task_css.
[1] https://syzkaller.appspot.com/bug?extid=9b1ff7be974a403aa4cd(CVE-2024-43853)
In the Linux kernel, the following vulnerability has been resolved:
remoteproc: imx_rproc: Skip over memory region when node value is NULL
In imx_rproc_addr_init() "nph = of_count_phandle_with_args()" just counts number of phandles. But phandles may be empty. So of_parse_phandle() in the parsing loop (0 < a < nph) may return NULL which is later dereferenced. Adjust this issue by adding NULL-return check.
Found by Linux Verification Center (linuxtesting.org) with SVACE.
Fixed title to fit within the prescribed 70-75 charcters
In the Linux kernel, the following vulnerability has been resolved:
net: usb: qmi_wwan: fix memory leak for not ip packets
Free the unused skb when not ip packets arrive.(CVE-2024-43861)
In the Linux kernel, the following vulnerability has been resolved:
net/mlx5: Always drain health in shutdown callback
There is no point in recovery during device shutdown. if health work started need to wait for it to avoid races and NULL pointer access.
Hence, drain health WQ on shutdown callback.(CVE-2024-43866)
In the Linux kernel, the following vulnerability has been resolved:
wifi: cfg80211: handle 2x996 RU allocation in cfg80211_calculate_bitrate_he()
Currently NL80211_RATE_INFO_HE_RU_ALLOC_2x996 is not handled in cfg80211_calculate_bitrate_he(), leading to below warning:
kernel: invalid HE MCS: bw:6, ru:6 kernel: WARNING: CPU: 0 PID: 2312 at net/wireless/util.c:1501 cfg80211_calculate_bitrate_he+0x22b/0x270 [cfg80211]
Fix it by handling 2x996 RU allocation in the same way as 160 MHz bandwidth.(CVE-2024-43879)
In the Linux kernel, the following vulnerability has been resolved:
exec: Fix ToCToU between perm check and set-uid/gid usage
When opening a file for exec via do_filp_open(), permission checking is done against the file's metadata at that moment, and on success, a file pointer is passed back. Much later in the execve() code path, the file metadata (specifically mode, uid, and gid) is used to determine if/how to set the uid and gid. However, those values may have changed since the permissions check, meaning the execution may gain unintended privileges.
For example, if a file could change permissions from executable and not set-id:
---------x 1 root root 16048 Aug 7 13:16 target
to set-id and non-executable:
---S------ 1 root root 16048 Aug 7 13:16 target
it is possible to gain root privileges when execution should have been disallowed.
While this race condition is rare in real-world scenarios, it has been observed (and proven exploitable) when package managers are updating the setuid bits of installed programs. Such files start with being world-executable but then are adjusted to be group-exec with a set-uid bit. For example, "chmod o-x,u+s target" makes "target" executable only by uid "root" and gid "cdrom", while also becoming setuid-root:
-rwxr-xr-x 1 root cdrom 16048 Aug 7 13:16 target
becomes:
-rwsr-xr-- 1 root cdrom 16048 Aug 7 13:16 target
But racing the chmod means users without group "cdrom" membership can get the permission to execute "target" just before the chmod, and when the chmod finishes, the exec reaches brpm_fill_uid(), and performs the setuid to root, violating the expressed authorization of "only cdrom group members can setuid to root".
Re-check that we still have execute permissions in case the metadata has changed. It would be better to keep a copy from the perm-check time, but until we can do that refactoring, the least-bad option is to do a full inode_permission() call (under inode lock). It is understood that this is safe against dead-locks, but hardly optimal.(CVE-2024-43882)
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"kernel-5.10.0-225.0.0.128.oe2203sp3.aarch64.rpm",
"kernel-debuginfo-5.10.0-225.0.0.128.oe2203sp3.aarch64.rpm",
"kernel-debugsource-5.10.0-225.0.0.128.oe2203sp3.aarch64.rpm",
"kernel-devel-5.10.0-225.0.0.128.oe2203sp3.aarch64.rpm",
"kernel-headers-5.10.0-225.0.0.128.oe2203sp3.aarch64.rpm",
"kernel-source-5.10.0-225.0.0.128.oe2203sp3.aarch64.rpm",
"kernel-tools-5.10.0-225.0.0.128.oe2203sp3.aarch64.rpm",
"kernel-tools-debuginfo-5.10.0-225.0.0.128.oe2203sp3.aarch64.rpm",
"kernel-tools-devel-5.10.0-225.0.0.128.oe2203sp3.aarch64.rpm",
"perf-5.10.0-225.0.0.128.oe2203sp3.aarch64.rpm",
"perf-debuginfo-5.10.0-225.0.0.128.oe2203sp3.aarch64.rpm",
"python3-perf-5.10.0-225.0.0.128.oe2203sp3.aarch64.rpm",
"python3-perf-debuginfo-5.10.0-225.0.0.128.oe2203sp3.aarch64.rpm"
],
"src": [
"kernel-5.10.0-225.0.0.128.oe2203sp3.src.rpm"
],
"x86_64": [
"kernel-5.10.0-225.0.0.128.oe2203sp3.x86_64.rpm",
"kernel-debuginfo-5.10.0-225.0.0.128.oe2203sp3.x86_64.rpm",
"kernel-debugsource-5.10.0-225.0.0.128.oe2203sp3.x86_64.rpm",
"kernel-devel-5.10.0-225.0.0.128.oe2203sp3.x86_64.rpm",
"kernel-headers-5.10.0-225.0.0.128.oe2203sp3.x86_64.rpm",
"kernel-source-5.10.0-225.0.0.128.oe2203sp3.x86_64.rpm",
"kernel-tools-5.10.0-225.0.0.128.oe2203sp3.x86_64.rpm",
"kernel-tools-debuginfo-5.10.0-225.0.0.128.oe2203sp3.x86_64.rpm",
"kernel-tools-devel-5.10.0-225.0.0.128.oe2203sp3.x86_64.rpm",
"perf-5.10.0-225.0.0.128.oe2203sp3.x86_64.rpm",
"perf-debuginfo-5.10.0-225.0.0.128.oe2203sp3.x86_64.rpm",
"python3-perf-5.10.0-225.0.0.128.oe2203sp3.x86_64.rpm",
"python3-perf-debuginfo-5.10.0-225.0.0.128.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-225.0.0.128.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\nbtrfs: get rid of warning on transaction commit when using flushoncommit\r\n\r\nWhen using the flushoncommit mount option, during almost every transaction\ncommit we trigger a warning from __writeback_inodes_sb_nr():\r\n\r\n $ cat fs/fs-writeback.c:\n (...)\n static void __writeback_inodes_sb_nr(struct super_block *sb, ...\n {\n (...)\n WARN_ON(!rwsem_is_locked(\u0026amp;sb-\u0026gt;s_umount));\n (...)\n }\n (...)\r\n\r\nThe trace produced in dmesg looks like the following:\r\n\r\n [947.473890] WARNING: CPU: 5 PID: 930 at fs/fs-writeback.c:2610 __writeback_inodes_sb_nr+0x7e/0xb3\n [947.481623] Modules linked in: nfsd nls_cp437 cifs asn1_decoder cifs_arc4 fscache cifs_md4 ipmi_ssif\n [947.489571] CPU: 5 PID: 930 Comm: btrfs-transacti Not tainted 95.16.3-srb-asrock-00001-g36437ad63879 #186\n [947.497969] RIP: 0010:__writeback_inodes_sb_nr+0x7e/0xb3\n [947.502097] Code: 24 10 4c 89 44 24 18 c6 (...)\n [947.519760] RSP: 0018:ffffc90000777e10 EFLAGS: 00010246\n [947.523818] RAX: 0000000000000000 RBX: 0000000000963300 RCX: 0000000000000000\n [947.529765] RDX: 0000000000000000 RSI: 000000000000fa51 RDI: ffffc90000777e50\n [947.535740] RBP: ffff888101628a90 R08: ffff888100955800 R09: ffff888100956000\n [947.541701] R10: 0000000000000002 R11: 0000000000000001 R12: ffff888100963488\n [947.547645] R13: ffff888100963000 R14: ffff888112fb7200 R15: ffff888100963460\n [947.553621] FS: 0000000000000000(0000) GS:ffff88841fd40000(0000) knlGS:0000000000000000\n [947.560537] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n [947.565122] CR2: 0000000008be50c4 CR3: 000000000220c000 CR4: 00000000001006e0\n [947.571072] Call Trace:\n [947.572354] \u0026lt;TASK\u0026gt;\n [947.573266] btrfs_commit_transaction+0x1f1/0x998\n [947.576785] ? start_transaction+0x3ab/0x44e\n [947.579867] ? schedule_timeout+0x8a/0xdd\n [947.582716] transaction_kthread+0xe9/0x156\n [947.585721] ? btrfs_cleanup_transaction.isra.0+0x407/0x407\n [947.590104] kthread+0x131/0x139\n [947.592168] ? set_kthread_struct+0x32/0x32\n [947.595174] ret_from_fork+0x22/0x30\n [947.597561] \u0026lt;/TASK\u0026gt;\n [947.598553] ---[ end trace 644721052755541c ]---\r\n\r\nThis is because we started using writeback_inodes_sb() to flush delalloc\nwhen committing a transaction (when using -o flushoncommit), in order to\navoid deadlocks with filesystem freeze operations. This change was made\nby commit ce8ea7cc6eb313 (\u0026quot;btrfs: don\u0026apos;t call btrfs_start_delalloc_roots\nin flushoncommit\u0026quot;). After that change we started producing that warning,\nand every now and then a user reports this since the warning happens too\noften, it spams dmesg/syslog, and a user is unsure if this reflects any\nproblem that might compromise the filesystem\u0026apos;s reliability.\r\n\r\nWe can not just lock the sb-\u0026gt;s_umount semaphore before calling\nwriteback_inodes_sb(), because that would at least deadlock with\nfilesystem freezing, since at fs/super.c:freeze_super() sync_filesystem()\nis called while we are holding that semaphore in write mode, and that can\ntrigger a transaction commit, resulting in a deadlock. It would also\ntrigger the same type of deadlock in the unmount path. Possibly, it could\nalso introduce some other locking dependencies that lockdep would report.\r\n\r\nTo fix this call try_to_writeback_inodes_sb() instead of\nwriteback_inodes_sb(), because that will try to read lock sb-\u0026gt;s_umount\nand then will only call writeback_inodes_sb() if it was able to lock it.\nThis is fine because the cases where it can\u0026apos;t read lock sb-\u0026gt;s_umount\nare during a filesystem unmount or during a filesystem freeze - in those\ncases sb-\u0026gt;s_umount is write locked and sync_filesystem() is called, which\ncalls writeback_inodes_sb(). In other words, in all cases where we can\u0026apos;t\ntake a read lock on sb-\u0026gt;s_umount, writeback is already being triggered\nelsewhere.\r\n\r\nAn alternative would be to call btrfs_start_delalloc_roots() with a\nnumber of pages different from LONG_MAX, for example matching the number\nof delalloc bytes we currently have, in \n---truncated---(CVE-2022-48920)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: nf_tables: unregister flowtable hooks on netns exit\r\n\r\nUnregister flowtable hooks before they are releases via\nnf_tables_flowtable_destroy() otherwise hook core reports UAF.\r\n\r\nBUG: KASAN: use-after-free in nf_hook_entries_grow+0x5a7/0x700 net/netfilter/core.c:142 net/netfilter/core.c:142\nRead of size 4 at addr ffff8880736f7438 by task syz-executor579/3666\r\n\r\nCPU: 0 PID: 3666 Comm: syz-executor579 Not tainted 5.16.0-rc5-syzkaller #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __dump_stack lib/dump_stack.c:88 [inline]\n __dump_stack lib/dump_stack.c:88 [inline] lib/dump_stack.c:106\n dump_stack_lvl+0x1dc/0x2d8 lib/dump_stack.c:106 lib/dump_stack.c:106\n print_address_description+0x65/0x380 mm/kasan/report.c:247 mm/kasan/report.c:247\n __kasan_report mm/kasan/report.c:433 [inline]\n __kasan_report mm/kasan/report.c:433 [inline] mm/kasan/report.c:450\n kasan_report+0x19a/0x1f0 mm/kasan/report.c:450 mm/kasan/report.c:450\n nf_hook_entries_grow+0x5a7/0x700 net/netfilter/core.c:142 net/netfilter/core.c:142\n __nf_register_net_hook+0x27e/0x8d0 net/netfilter/core.c:429 net/netfilter/core.c:429\n nf_register_net_hook+0xaa/0x180 net/netfilter/core.c:571 net/netfilter/core.c:571\n nft_register_flowtable_net_hooks+0x3c5/0x730 net/netfilter/nf_tables_api.c:7232 net/netfilter/nf_tables_api.c:7232\n nf_tables_newflowtable+0x2022/0x2cf0 net/netfilter/nf_tables_api.c:7430 net/netfilter/nf_tables_api.c:7430\n nfnetlink_rcv_batch net/netfilter/nfnetlink.c:513 [inline]\n nfnetlink_rcv_skb_batch net/netfilter/nfnetlink.c:634 [inline]\n nfnetlink_rcv_batch net/netfilter/nfnetlink.c:513 [inline] net/netfilter/nfnetlink.c:652\n nfnetlink_rcv_skb_batch net/netfilter/nfnetlink.c:634 [inline] net/netfilter/nfnetlink.c:652\n nfnetlink_rcv+0x10e6/0x2550 net/netfilter/nfnetlink.c:652 net/netfilter/nfnetlink.c:652\r\n\r\n__nft_release_hook() calls nft_unregister_flowtable_net_hooks() which\nonly unregisters the hooks, then after RCU grace period, it is\nguaranteed that no packets add new entries to the flowtable (no flow\noffload rules and flowtable hooks are reachable from packet path), so it\nis safe to call nf_flow_table_free() which cleans up the remaining\nentries from the flowtable (both software and hardware) and it unbinds\nthe flow_block.(CVE-2022-48935)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nphonet: fix rtm_phonet_notify() skb allocation\r\n\r\nfill_route() stores three components in the skb:\r\n\r\n- struct rtmsg\n- RTA_DST (u8)\n- RTA_OIF (u32)\r\n\r\nTherefore, rtm_phonet_notify() should use\r\n\r\nNLMSG_ALIGN(sizeof(struct rtmsg)) +\nnla_total_size(1) +\nnla_total_size(4)(CVE-2024-36946)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nm68k: Fix spinlock race in kernel thread creation\r\n\r\nContext switching does take care to retain the correct lock owner across\nthe switch from \u0026apos;prev\u0026apos; to \u0026apos;next\u0026apos; tasks. This does rely on interrupts\nremaining disabled for the entire duration of the switch.\r\n\r\nThis condition is guaranteed for normal process creation and context\nswitching between already running processes, because both \u0026apos;prev\u0026apos; and\n\u0026apos;next\u0026apos; already have interrupts disabled in their saved copies of the\nstatus register.\r\n\r\nThe situation is different for newly created kernel threads. The status\nregister is set to PS_S in copy_thread(), which does leave the IPL at 0.\nUpon restoring the \u0026apos;next\u0026apos; thread\u0026apos;s status register in switch_to() aka\nresume(), interrupts then become enabled prematurely. resume() then\nreturns via ret_from_kernel_thread() and schedule_tail() where run queue\nlock is released (see finish_task_switch() and finish_lock_switch()).\r\n\r\nA timer interrupt calling scheduler_tick() before the lock is released\nin finish_task_switch() will find the lock already taken, with the\ncurrent task as lock owner. This causes a spinlock recursion warning as\nreported by Guenter Roeck.\r\n\r\nAs far as I can ascertain, this race has been opened in commit\n533e6903bea0 (\u0026quot;m68k: split ret_from_fork(), simplify kernel_thread()\u0026quot;)\nbut I haven\u0026apos;t done a detailed study of kernel history so it may well\npredate that commit.\r\n\r\nInterrupts cannot be disabled in the saved status register copy for\nkernel threads (init will complain about interrupts disabled when\nfinally starting user space). Disable interrupts temporarily when\nswitching the tasks\u0026apos; register sets in resume().\r\n\r\nNote that a simple oriw 0x700,%sr after restoring sr is not enough here\n- this leaves enough of a race for the \u0026apos;spinlock recursion\u0026apos; warning to\nstill be observed.\r\n\r\nTested on ARAnyM and qemu (Quadra 800 emulation).(CVE-2024-38613)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nipv6: sr: fix missing sk_buff release in seg6_input_core\r\n\r\nThe seg6_input() function is responsible for adding the SRH into a\npacket, delegating the operation to the seg6_input_core(). This function\nuses the skb_cow_head() to ensure that there is sufficient headroom in\nthe sk_buff for accommodating the link-layer header.\nIn the event that the skb_cow_header() function fails, the\nseg6_input_core() catches the error but it does not release the sk_buff,\nwhich will result in a memory leak.\r\n\r\nThis issue was introduced in commit af3b5158b89d (\u0026quot;ipv6: sr: fix BUG due\nto headroom too small after SRH push\u0026quot;) and persists even after commit\n7a3f5b0de364 (\u0026quot;netfilter: add netfilter hooks to SRv6 data plane\u0026quot;),\nwhere the entire seg6_input() code was refactored to deal with netfilter\nhooks.\r\n\r\nThe proposed patch addresses the identified memory leak by requiring the\nseg6_input_core() function to release the sk_buff in the event that\nskb_cow_head() fails.(CVE-2024-39490)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncrypto: hisilicon/sec - Fix memory leak for sec resource release\r\n\r\nThe AIV is one of the SEC resources. When releasing resources,\nit need to release the AIV resources at the same time.\nOtherwise, memory leakage occurs.\r\n\r\nThe aiv resource release is added to the sec resource release\nfunction.(CVE-2024-41002)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nocfs2: add bounds checking to ocfs2_check_dir_entry()\r\n\r\nThis adds sanity checks for ocfs2_dir_entry to make sure all members of\nocfs2_dir_entry don\u0026apos;t stray beyond valid memory region.(CVE-2024-41015)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nhfsplus: fix uninit-value in copy_name\r\n\r\n[syzbot reported]\nBUG: KMSAN: uninit-value in sized_strscpy+0xc4/0x160\n sized_strscpy+0xc4/0x160\n copy_name+0x2af/0x320 fs/hfsplus/xattr.c:411\n hfsplus_listxattr+0x11e9/0x1a50 fs/hfsplus/xattr.c:750\n vfs_listxattr fs/xattr.c:493 [inline]\n listxattr+0x1f3/0x6b0 fs/xattr.c:840\n path_listxattr fs/xattr.c:864 [inline]\n __do_sys_listxattr fs/xattr.c:876 [inline]\n __se_sys_listxattr fs/xattr.c:873 [inline]\n __x64_sys_listxattr+0x16b/0x2f0 fs/xattr.c:873\n x64_sys_call+0x2ba0/0x3b50 arch/x86/include/generated/asm/syscalls_64.h:195\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\r\n\r\nUninit was created at:\n slab_post_alloc_hook mm/slub.c:3877 [inline]\n slab_alloc_node mm/slub.c:3918 [inline]\n kmalloc_trace+0x57b/0xbe0 mm/slub.c:4065\n kmalloc include/linux/slab.h:628 [inline]\n hfsplus_listxattr+0x4cc/0x1a50 fs/hfsplus/xattr.c:699\n vfs_listxattr fs/xattr.c:493 [inline]\n listxattr+0x1f3/0x6b0 fs/xattr.c:840\n path_listxattr fs/xattr.c:864 [inline]\n __do_sys_listxattr fs/xattr.c:876 [inline]\n __se_sys_listxattr fs/xattr.c:873 [inline]\n __x64_sys_listxattr+0x16b/0x2f0 fs/xattr.c:873\n x64_sys_call+0x2ba0/0x3b50 arch/x86/include/generated/asm/syscalls_64.h:195\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\n[Fix]\nWhen allocating memory to strbuf, initialize memory to 0.(CVE-2024-41059)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ns390/sclp: Fix sclp_init() cleanup on failure\r\n\r\nIf sclp_init() fails it only partially cleans up: if there are multiple\nfailing calls to sclp_init() sclp_state_change_event will be added several\ntimes to sclp_reg_list, which results in the following warning:\r\n\r\n------------[ cut here ]------------\nlist_add double add: new=000003ffe1598c10, prev=000003ffe1598bf0, next=000003ffe1598c10.\nWARNING: CPU: 0 PID: 1 at lib/list_debug.c:35 __list_add_valid_or_report+0xde/0xf8\nCPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.10.0-rc3\nKrnl PSW : 0404c00180000000 000003ffe0d6076a (__list_add_valid_or_report+0xe2/0xf8)\n R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3\n...\nCall Trace:\n [\u0026lt;000003ffe0d6076a\u0026gt;] __list_add_valid_or_report+0xe2/0xf8\n([\u0026lt;000003ffe0d60766\u0026gt;] __list_add_valid_or_report+0xde/0xf8)\n [\u0026lt;000003ffe0a8d37e\u0026gt;] sclp_init+0x40e/0x450\n [\u0026lt;000003ffe00009f2\u0026gt;] do_one_initcall+0x42/0x1e0\n [\u0026lt;000003ffe15b77a6\u0026gt;] do_initcalls+0x126/0x150\n [\u0026lt;000003ffe15b7a0a\u0026gt;] kernel_init_freeable+0x1ba/0x1f8\n [\u0026lt;000003ffe0d6650e\u0026gt;] kernel_init+0x2e/0x180\n [\u0026lt;000003ffe000301c\u0026gt;] __ret_from_fork+0x3c/0x60\n [\u0026lt;000003ffe0d759ca\u0026gt;] ret_from_fork+0xa/0x30\r\n\r\nFix this by removing sclp_state_change_event from sclp_reg_list when\nsclp_init() fails.(CVE-2024-41068)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Check pipe offset before setting vblank\r\n\r\npipe_ctx has a size of MAX_PIPES so checking its index before accessing\nthe array.\r\n\r\nThis fixes an OVERRUN issue reported by Coverity.(CVE-2024-42120)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Add NULL pointer check for kzalloc\r\n\r\n[Why \u0026amp; How]\nCheck return pointer of kzalloc before using it.(CVE-2024-42122)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nprotect the fetch of -\u0026gt;fd[fd] in do_dup2() from mispredictions\r\n\r\nboth callers have verified that fd is not greater than -\u0026gt;max_fds;\nhowever, misprediction might end up with\n tofree = fdt-\u0026gt;fd[fd];\nbeing speculatively executed. That\u0026apos;s wrong for the same reasons\nwhy it\u0026apos;s wrong in close_fd()/file_close_fd_locked(); the same\nsolution applies - array_index_nospec(fd, fdt-\u0026gt;max_fds) could differ\nfrom fd only in case of speculative execution on mispredicted path.(CVE-2024-42265)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/iucv: fix use after free in iucv_sock_close()\r\n\r\niucv_sever_path() is called from process context and from bh context.\niucv-\u0026gt;path is used as indicator whether somebody else is taking care of\nsevering the path (or it is already removed / never existed).\nThis needs to be done with atomic compare and swap, otherwise there is a\nsmall window where iucv_sock_close() will try to work with a path that has\nalready been severed and freed by iucv_callback_connrej() called by\niucv_tasklet_fn().\r\n\r\nExample:\n[452744.123844] Call Trace:\n[452744.123845] ([\u0026lt;0000001e87f03880\u0026gt;] 0x1e87f03880)\n[452744.123966] [\u0026lt;00000000d593001e\u0026gt;] iucv_path_sever+0x96/0x138\n[452744.124330] [\u0026lt;000003ff801ddbca\u0026gt;] iucv_sever_path+0xc2/0xd0 [af_iucv]\n[452744.124336] [\u0026lt;000003ff801e01b6\u0026gt;] iucv_sock_close+0xa6/0x310 [af_iucv]\n[452744.124341] [\u0026lt;000003ff801e08cc\u0026gt;] iucv_sock_release+0x3c/0xd0 [af_iucv]\n[452744.124345] [\u0026lt;00000000d574794e\u0026gt;] __sock_release+0x5e/0xe8\n[452744.124815] [\u0026lt;00000000d5747a0c\u0026gt;] sock_close+0x34/0x48\n[452744.124820] [\u0026lt;00000000d5421642\u0026gt;] __fput+0xba/0x268\n[452744.124826] [\u0026lt;00000000d51b382c\u0026gt;] task_work_run+0xbc/0xf0\n[452744.124832] [\u0026lt;00000000d5145710\u0026gt;] do_notify_resume+0x88/0x90\n[452744.124841] [\u0026lt;00000000d5978096\u0026gt;] system_call+0xe2/0x2c8\n[452744.125319] Last Breaking-Event-Address:\n[452744.125321] [\u0026lt;00000000d5930018\u0026gt;] iucv_path_sever+0x90/0x138\n[452744.125324]\n[452744.125325] Kernel panic - not syncing: Fatal exception in interrupt\r\n\r\nNote that bh_lock_sock() is not serializing the tasklet context against\nprocess context, because the check for sock_owned_by_user() and\ncorresponding handling is missing.\r\n\r\nIdeas for a future clean-up patch:\nA) Correct usage of bh_lock_sock() in tasklet context, as described in\nRe-enqueue, if needed. This may require adding return values to the\ntasklet functions and thus changes to all users of iucv.\r\n\r\nB) Change iucv tasklet into worker and use only lock_sock() in af_iucv.(CVE-2024-42271)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmISDN: Fix a use after free in hfcmulti_tx()\r\n\r\nDon\u0026apos;t dereference *sp after calling dev_kfree_skb(*sp).(CVE-2024-42280)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbpf: Fix a segment issue when downgrading gso_size\r\n\r\nLinearize the skb when downgrading gso_size because it may trigger a\nBUG_ON() later when the skb is segmented as described in [1,2].(CVE-2024-42281)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntipc: Return non-zero value from tipc_udp_addr2str() on error\r\n\r\ntipc_udp_addr2str() should return non-zero value if the UDP media\naddress is invalid. Otherwise, a buffer overflow access can occur in\ntipc_media_addr_printf(). Fix this by returning 1 on an invalid UDP\nmedia address.(CVE-2024-42284)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nRDMA/iwcm: Fix a use-after-free related to destroying CM IDs\r\n\r\niw_conn_req_handler() associates a new struct rdma_id_private (conn_id) with\nan existing struct iw_cm_id (cm_id) as follows:\r\n\r\n conn_id-\u0026gt;cm_id.iw = cm_id;\n cm_id-\u0026gt;context = conn_id;\n cm_id-\u0026gt;cm_handler = cma_iw_handler;\r\n\r\nrdma_destroy_id() frees both the cm_id and the struct rdma_id_private. Make\nsure that cm_work_handler() does not trigger a use-after-free by only\nfreeing of the struct rdma_id_private after all pending work has finished.(CVE-2024-42285)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nscsi: qla2xxx: Fix for possible memory corruption\r\n\r\nInit Control Block is dereferenced incorrectly. Correctly dereference ICB(CVE-2024-42288)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nf2fs: fix to don\u0026apos;t dirty inode for readonly filesystem\r\n\r\nsyzbot reports f2fs bug as below:\r\n\r\nkernel BUG at fs/f2fs/inode.c:933!\nRIP: 0010:f2fs_evict_inode+0x1576/0x1590 fs/f2fs/inode.c:933\nCall Trace:\n evict+0x2a4/0x620 fs/inode.c:664\n dispose_list fs/inode.c:697 [inline]\n evict_inodes+0x5f8/0x690 fs/inode.c:747\n generic_shutdown_super+0x9d/0x2c0 fs/super.c:675\n kill_block_super+0x44/0x90 fs/super.c:1667\n kill_f2fs_super+0x303/0x3b0 fs/f2fs/super.c:4894\n deactivate_locked_super+0xc1/0x130 fs/super.c:484\n cleanup_mnt+0x426/0x4c0 fs/namespace.c:1256\n task_work_run+0x24a/0x300 kernel/task_work.c:180\n ptrace_notify+0x2cd/0x380 kernel/signal.c:2399\n ptrace_report_syscall include/linux/ptrace.h:411 [inline]\n ptrace_report_syscall_exit include/linux/ptrace.h:473 [inline]\n syscall_exit_work kernel/entry/common.c:251 [inline]\n syscall_exit_to_user_mode_prepare kernel/entry/common.c:278 [inline]\n __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline]\n syscall_exit_to_user_mode+0x15c/0x280 kernel/entry/common.c:296\n do_syscall_64+0x50/0x110 arch/x86/entry/common.c:88\n entry_SYSCALL_64_after_hwframe+0x63/0x6b\r\n\r\nThe root cause is:\n- do_sys_open\n - f2fs_lookup\n - __f2fs_find_entry\n - f2fs_i_depth_write\n - f2fs_mark_inode_dirty_sync\n - f2fs_dirty_inode\n - set_inode_flag(inode, FI_DIRTY_INODE)\r\n\r\n- umount\n - kill_f2fs_super\n - kill_block_super\n - generic_shutdown_super\n - sync_filesystem\n : sb is readonly, skip sync_filesystem()\n - evict_inodes\n - iput\n - f2fs_evict_inode\n - f2fs_bug_on(sbi, is_inode_flag_set(inode, FI_DIRTY_INODE))\n : trigger kernel panic\r\n\r\nWhen we try to repair i_current_depth in readonly filesystem, let\u0026apos;s\nskip dirty inode to avoid panic in later f2fs_evict_inode().(CVE-2024-42297)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nPCI/DPC: Fix use-after-free on concurrent DPC and hot-removal\r\n\r\nKeith reports a use-after-free when a DPC event occurs concurrently to\nhot-removal of the same portion of the hierarchy:\r\n\r\nThe dpc_handler() awaits readiness of the secondary bus below the\nDownstream Port where the DPC event occurred. To do so, it polls the\nconfig space of the first child device on the secondary bus. If that\nchild device is concurrently removed, accesses to its struct pci_dev\ncause the kernel to oops.\r\n\r\nThat\u0026apos;s because pci_bridge_wait_for_secondary_bus() neglects to hold a\nreference on the child device. Before v6.3, the function was only\ncalled on resume from system sleep or on runtime resume. Holding a\nreference wasn\u0026apos;t necessary back then because the pciehp IRQ thread\ncould never run concurrently. (On resume from system sleep, IRQs are\nnot enabled until after the resume_noirq phase. And runtime resume is\nalways awaited before a PCI device is removed.)\r\n\r\nHowever starting with v6.3, pci_bridge_wait_for_secondary_bus() is also\ncalled on a DPC event. Commit 53b54ad074de (\u0026quot;PCI/DPC: Await readiness\nof secondary bus after reset\u0026quot;), which introduced that, failed to\nappreciate that pci_bridge_wait_for_secondary_bus() now needs to hold a\nreference on the child device because dpc_handler() and pciehp may\nindeed run concurrently. The commit was backported to v5.10+ stable\nkernels, so that\u0026apos;s the oldest one affected.\r\n\r\nAdd the missing reference acquisition.\r\n\r\nAbridged stack trace:\r\n\r\n BUG: unable to handle page fault for address: 00000000091400c0\n CPU: 15 PID: 2464 Comm: irq/53-pcie-dpc 6.9.0\n RIP: pci_bus_read_config_dword+0x17/0x50\n pci_dev_wait()\n pci_bridge_wait_for_secondary_bus()\n dpc_reset_link()\n pcie_do_recovery()\n dpc_handler()(CVE-2024-42302)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\next4: check dot and dotdot of dx_root before making dir indexed\r\n\r\nSyzbot reports a issue as follows:\n============================================\nBUG: unable to handle page fault for address: ffffed11022e24fe\nPGD 23ffee067 P4D 23ffee067 PUD 0\nOops: Oops: 0000 [#1] PREEMPT SMP KASAN PTI\nCPU: 0 PID: 5079 Comm: syz-executor306 Not tainted 6.10.0-rc5-g55027e689933 #0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n make_indexed_dir+0xdaf/0x13c0 fs/ext4/namei.c:2341\n ext4_add_entry+0x222a/0x25d0 fs/ext4/namei.c:2451\n ext4_rename fs/ext4/namei.c:3936 [inline]\n ext4_rename2+0x26e5/0x4370 fs/ext4/namei.c:4214\n[...]\n============================================\r\n\r\nThe immediate cause of this problem is that there is only one valid dentry\nfor the block to be split during do_split, so split==0 results in out of\nbounds accesses to the map triggering the issue.\r\n\r\n do_split\n unsigned split\n dx_make_map\n count = 1\n split = count/2 = 0;\n continued = hash2 == map[split - 1].hash;\n ---\u0026gt; map[4294967295]\r\n\r\nThe maximum length of a filename is 255 and the minimum block size is 1024,\nso it is always guaranteed that the number of entries is greater than or\nequal to 2 when do_split() is called.\r\n\r\nBut syzbot\u0026apos;s crafted image has no dot and dotdot in dir, and the dentry\ndistribution in dirblock is as follows:\r\n\r\n bus dentry1 hole dentry2 free\n|xx--|xx-------------|...............|xx-------------|...............|\n0 12 (8+248)=256 268 256 524 (8+256)=264 788 236 1024\r\n\r\nSo when renaming dentry1 increases its name_len length by 1, neither hole\nnor free is sufficient to hold the new dentry, and make_indexed_dir() is\ncalled.\r\n\r\nIn make_indexed_dir() it is assumed that the first two entries of the\ndirblock must be dot and dotdot, so bus and dentry1 are left in dx_root\nbecause they are treated as dot and dotdot, and only dentry2 is moved\nto the new leaf block. That\u0026apos;s why count is equal to 1.\r\n\r\nTherefore add the ext4_check_dx_root() helper function to add more sanity\nchecks to dot and dotdot before starting the conversion to avoid the above\nissue.(CVE-2024-42305)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Check for NULL pointer\r\n\r\n[why \u0026amp; how]\nNeed to make sure plane_state is initialized\nbefore accessing its members.\r\n\r\n(cherry picked from commit 295d91cbc700651782a60572f83c24861607b648)(CVE-2024-42308)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nlandlock: Don\u0026apos;t lose track of restrictions on cred_transfer\r\n\r\nWhen a process\u0026apos; cred struct is replaced, this _almost_ always invokes\nthe cred_prepare LSM hook; but in one special case (when\nKEYCTL_SESSION_TO_PARENT updates the parent\u0026apos;s credentials), the\ncred_transfer LSM hook is used instead. Landlock only implements the\ncred_prepare hook, not cred_transfer, so KEYCTL_SESSION_TO_PARENT causes\nall information on Landlock restrictions to be lost.\r\n\r\nThis basically means that a process with the ability to use the fork()\nand keyctl() syscalls can get rid of all Landlock restrictions on\nitself.\r\n\r\nFix it by adding a cred_transfer hook that does the same thing as the\nexisting cred_prepare hook. (Implemented by having hook_cred_prepare()\ncall hook_cred_transfer() so that the two functions are less likely to\naccidentally diverge in the future.)(CVE-2024-42318)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nkvm: s390: Reject memory region operations for ucontrol VMs\r\n\r\nThis change rejects the KVM_SET_USER_MEMORY_REGION and\nKVM_SET_USER_MEMORY_REGION2 ioctls when called on a ucontrol VM.\nThis is necessary since ucontrol VMs have kvm-\u0026gt;arch.gmap set to 0 and\nwould thus result in a null pointer dereference further in.\nMemory management needs to be performed in userspace and using the\nioctls KVM_S390_UCAS_MAP and KVM_S390_UCAS_UNMAP.\r\n\r\nAlso improve s390 specific documentation for KVM_SET_USER_MEMORY_REGION\nand KVM_SET_USER_MEMORY_REGION2.\r\n\r\n[frankja@linux.ibm.com: commit message spelling fix, subject prefix fix](CVE-2024-43819)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\next4: fix infinite loop when replaying fast_commit\r\n\r\nWhen doing fast_commit replay an infinite loop may occur due to an\nuninitialized extent_status struct. ext4_ext_determine_insert_hole() does\nnot detect the replay and calls ext4_es_find_extent_range(), which will\nreturn immediately without initializing the \u0026apos;es\u0026apos; variable.\r\n\r\nBecause \u0026apos;es\u0026apos; contains garbage, an integer overflow may happen causing an\ninfinite loop in this function, easily reproducible using fstest generic/039.\r\n\r\nThis commit fixes this issue by unconditionally initializing the structure\nin function ext4_es_find_extent_range().\r\n\r\nThanks to Zhang Yi, for figuring out the real problem!(CVE-2024-43828)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmedia: mediatek: vcodec: Handle invalid decoder vsi\r\n\r\nHandle an invalid decoder vsi in vpu_dec_init to ensure the decoder vsi\nis valid for future use.(CVE-2024-43831)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncgroup/cpuset: Prevent UAF in proc_cpuset_show()\r\n\r\nAn UAF can happen when /proc/cpuset is read as reported in [1].\r\n\r\nThis can be reproduced by the following methods:\n1.add an mdelay(1000) before acquiring the cgroup_lock In the\n cgroup_path_ns function.\n2.$cat /proc/\u0026lt;pid\u0026gt;/cpuset repeatly.\n3.$mount -t cgroup -o cpuset cpuset /sys/fs/cgroup/cpuset/\n$umount /sys/fs/cgroup/cpuset/ repeatly.\r\n\r\nThe race that cause this bug can be shown as below:\r\n\r\n(umount)\t\t|\t(cat /proc/\u0026lt;pid\u0026gt;/cpuset)\ncss_release\t\t|\tproc_cpuset_show\ncss_release_work_fn\t|\tcss = task_get_css(tsk, cpuset_cgrp_id);\ncss_free_rwork_fn\t|\tcgroup_path_ns(css-\u0026gt;cgroup, ...);\ncgroup_destroy_root\t|\tmutex_lock(\u0026amp;cgroup_mutex);\nrebind_subsystems\t|\ncgroup_free_root \t|\n\t\t\t|\t// cgrp was freed, UAF\n\t\t\t|\tcgroup_path_ns_locked(cgrp,..);\r\n\r\nWhen the cpuset is initialized, the root node top_cpuset.css.cgrp\nwill point to \u0026amp;cgrp_dfl_root.cgrp. In cgroup v1, the mount operation will\nallocate cgroup_root, and top_cpuset.css.cgrp will point to the allocated\n\u0026amp;cgroup_root.cgrp. When the umount operation is executed,\ntop_cpuset.css.cgrp will be rebound to \u0026amp;cgrp_dfl_root.cgrp.\r\n\r\nThe problem is that when rebinding to cgrp_dfl_root, there are cases\nwhere the cgroup_root allocated by setting up the root for cgroup v1\nis cached. This could lead to a Use-After-Free (UAF) if it is\nsubsequently freed. The descendant cgroups of cgroup v1 can only be\nfreed after the css is released. However, the css of the root will never\nbe released, yet the cgroup_root should be freed when it is unmounted.\nThis means that obtaining a reference to the css of the root does\nnot guarantee that css.cgrp-\u0026gt;root will not be freed.\r\n\r\nFix this problem by using rcu_read_lock in proc_cpuset_show().\nAs cgroup_root is kfree_rcu after commit d23b5c577715\n(\u0026quot;cgroup: Make operations on the cgroup root_list RCU safe\u0026quot;),\ncss-\u0026gt;cgroup won\u0026apos;t be freed during the critical section.\nTo call cgroup_path_ns_locked, css_set_lock is needed, so it is safe to\nreplace task_get_css with task_css.\r\n\r\n[1] https://syzkaller.appspot.com/bug?extid=9b1ff7be974a403aa4cd(CVE-2024-43853)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nremoteproc: imx_rproc: Skip over memory region when node value is NULL\r\n\r\nIn imx_rproc_addr_init() \u0026quot;nph = of_count_phandle_with_args()\u0026quot; just counts\nnumber of phandles. But phandles may be empty. So of_parse_phandle() in\nthe parsing loop (0 \u0026lt; a \u0026lt; nph) may return NULL which is later dereferenced.\nAdjust this issue by adding NULL-return check.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.\r\n\r\n[Fixed title to fit within the prescribed 70-75 charcters](CVE-2024-43860)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: usb: qmi_wwan: fix memory leak for not ip packets\r\n\r\nFree the unused skb when not ip packets arrive.(CVE-2024-43861)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/mlx5: Always drain health in shutdown callback\r\n\r\nThere is no point in recovery during device shutdown. if health\nwork started need to wait for it to avoid races and NULL pointer\naccess.\r\n\r\nHence, drain health WQ on shutdown callback.(CVE-2024-43866)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: cfg80211: handle 2x996 RU allocation in cfg80211_calculate_bitrate_he()\r\n\r\nCurrently NL80211_RATE_INFO_HE_RU_ALLOC_2x996 is not handled in\ncfg80211_calculate_bitrate_he(), leading to below warning:\r\n\r\nkernel: invalid HE MCS: bw:6, ru:6\nkernel: WARNING: CPU: 0 PID: 2312 at net/wireless/util.c:1501 cfg80211_calculate_bitrate_he+0x22b/0x270 [cfg80211]\r\n\r\nFix it by handling 2x996 RU allocation in the same way as 160 MHz bandwidth.(CVE-2024-43879)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nexec: Fix ToCToU between perm check and set-uid/gid usage\r\n\r\nWhen opening a file for exec via do_filp_open(), permission checking is\ndone against the file\u0026apos;s metadata at that moment, and on success, a file\npointer is passed back. Much later in the execve() code path, the file\nmetadata (specifically mode, uid, and gid) is used to determine if/how\nto set the uid and gid. However, those values may have changed since the\npermissions check, meaning the execution may gain unintended privileges.\r\n\r\nFor example, if a file could change permissions from executable and not\nset-id:\r\n\r\n---------x 1 root root 16048 Aug 7 13:16 target\r\n\r\nto set-id and non-executable:\r\n\r\n---S------ 1 root root 16048 Aug 7 13:16 target\r\n\r\nit is possible to gain root privileges when execution should have been\ndisallowed.\r\n\r\nWhile this race condition is rare in real-world scenarios, it has been\nobserved (and proven exploitable) when package managers are updating\nthe setuid bits of installed programs. Such files start with being\nworld-executable but then are adjusted to be group-exec with a set-uid\nbit. For example, \u0026quot;chmod o-x,u+s target\u0026quot; makes \u0026quot;target\u0026quot; executable only\nby uid \u0026quot;root\u0026quot; and gid \u0026quot;cdrom\u0026quot;, while also becoming setuid-root:\r\n\r\n-rwxr-xr-x 1 root cdrom 16048 Aug 7 13:16 target\r\n\r\nbecomes:\r\n\r\n-rwsr-xr-- 1 root cdrom 16048 Aug 7 13:16 target\r\n\r\nBut racing the chmod means users without group \u0026quot;cdrom\u0026quot; membership can\nget the permission to execute \u0026quot;target\u0026quot; just before the chmod, and when\nthe chmod finishes, the exec reaches brpm_fill_uid(), and performs the\nsetuid to root, violating the expressed authorization of \u0026quot;only cdrom\ngroup members can setuid to root\u0026quot;.\r\n\r\nRe-check that we still have execute permissions in case the metadata\nhas changed. It would be better to keep a copy from the perm-check time,\nbut until we can do that refactoring, the least-bad option is to do a\nfull inode_permission() call (under inode lock). It is understood that\nthis is safe against dead-locks, but hardly optimal.(CVE-2024-43882)",
"id": "OESA-2024-2078",
"modified": "2026-08-06T11:07:33Z",
"published": "2024-08-30T11:07:33Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2078"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48920"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48935"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-36946"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38613"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-39490"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-41002"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-41015"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-41059"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-41068"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42120"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42122"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42265"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42271"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42280"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42281"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42284"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42285"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42288"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42297"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42302"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42305"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42308"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42318"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43819"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43828"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43831"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43853"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43860"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43861"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43866"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43879"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43882"
}
],
"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-2022-48920",
"CVE-2022-48935",
"CVE-2024-36946",
"CVE-2024-38613",
"CVE-2024-39490",
"CVE-2024-41002",
"CVE-2024-41015",
"CVE-2024-41059",
"CVE-2024-41068",
"CVE-2024-42120",
"CVE-2024-42122",
"CVE-2024-42265",
"CVE-2024-42271",
"CVE-2024-42280",
"CVE-2024-42281",
"CVE-2024-42284",
"CVE-2024-42285",
"CVE-2024-42288",
"CVE-2024-42297",
"CVE-2024-42302",
"CVE-2024-42305",
"CVE-2024-42308",
"CVE-2024-42318",
"CVE-2024-43819",
"CVE-2024-43828",
"CVE-2024-43831",
"CVE-2024-43853",
"CVE-2024-43860",
"CVE-2024-43861",
"CVE-2024-43866",
"CVE-2024-43879",
"CVE-2024-43882"
]
}
OESA-2024-2079 (CVE-2022-48795)
Vulnerability from osv_openeuler – Published: 2024-08-30 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:
parisc: Fix data TLB miss in sba_unmap_sg
Rolf Eike Beer reported the following bug:
[1274934.746891] Bad Address (null pointer deref?): Code=15 (Data TLB miss fault) at addr 0000004140000018 [1274934.746891] CPU: 3 PID: 5549 Comm: cmake Not tainted 5.15.4-gentoo-parisc64 #4 [1274934.746891] Hardware name: 9000/785/C8000 [1274934.746891] [1274934.746891] YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI [1274934.746891] PSW: 00001000000001001111111000001110 Not tainted [1274934.746891] r00-03 000000ff0804fe0e 0000000040bc9bc0 00000000406760e4 0000004140000000 [1274934.746891] r04-07 0000000040b693c0 0000004140000000 000000004a2b08b0 0000000000000001 [1274934.746891] r08-11 0000000041f98810 0000000000000000 000000004a0a7000 0000000000000001 [1274934.746891] r12-15 0000000040bddbc0 0000000040c0cbc0 0000000040bddbc0 0000000040bddbc0 [1274934.746891] r16-19 0000000040bde3c0 0000000040bddbc0 0000000040bde3c0 0000000000000007 [1274934.746891] r20-23 0000000000000006 000000004a368950 0000000000000000 0000000000000001 [1274934.746891] r24-27 0000000000001fff 000000000800000e 000000004a1710f0 0000000040b693c0 [1274934.746891] r28-31 0000000000000001 0000000041f988b0 0000000041f98840 000000004a171118 [1274934.746891] sr00-03 00000000066e5800 0000000000000000 0000000000000000 00000000066e5800 [1274934.746891] sr04-07 0000000000000000 0000000000000000 0000000000000000 0000000000000000 [1274934.746891] [1274934.746891] IASQ: 0000000000000000 0000000000000000 IAOQ: 00000000406760e8 00000000406760ec [1274934.746891] IIR: 48780030 ISR: 0000000000000000 IOR: 0000004140000018 [1274934.746891] CPU: 3 CR30: 00000040e3a9c000 CR31: ffffffffffffffff [1274934.746891] ORIG_R28: 0000000040acdd58 [1274934.746891] IAOQ[0]: sba_unmap_sg+0xb0/0x118 [1274934.746891] IAOQ[1]: sba_unmap_sg+0xb4/0x118 [1274934.746891] RP(r2): sba_unmap_sg+0xac/0x118 [1274934.746891] Backtrace: [1274934.746891] [<00000000402740cc>] dma_unmap_sg_attrs+0x6c/0x70 [1274934.746891] [<000000004074d6bc>] scsi_dma_unmap+0x54/0x60 [1274934.746891] [<00000000407a3488>] mptscsih_io_done+0x150/0xd70 [1274934.746891] [<0000000040798600>] mpt_interrupt+0x168/0xa68 [1274934.746891] [<0000000040255a48>] __handle_irq_event_percpu+0xc8/0x278 [1274934.746891] [<0000000040255c34>] handle_irq_event_percpu+0x3c/0xd8 [1274934.746891] [<000000004025ecb4>] handle_percpu_irq+0xb4/0xf0 [1274934.746891] [<00000000402548e0>] generic_handle_irq+0x50/0x70 [1274934.746891] [<000000004019a254>] call_on_stack+0x18/0x24 [1274934.746891] [1274934.746891] Kernel panic - not syncing: Bad Address (null pointer deref?)
The bug is caused by overrunning the sglist and incorrectly testing sg_dma_len(sglist) before nents. Normally this doesn't cause a crash, but in this case sglist crossed a page boundary. This occurs in the following code:
while (sg_dma_len(sglist) && nents--) {
The fix is simply to test nents first and move the decrement of nents into the loop.(CVE-2022-48795)
In the Linux kernel, the following vulnerability has been resolved:
drm/virtio: Fix GEM handle creation UAF
Userspace can guess the handle value and try to race GEM object creation with handle close, resulting in a use-after-free if we dereference the object after dropping the handle's reference. For that reason, dropping the handle's reference must be done after we are done dereferencing the object.(CVE-2022-48899)
In the Linux kernel, the following vulnerability has been resolved:
thermal: int340x: fix memory leak in int3400_notify()
It is easy to hit the below memory leaks in my TigerLake platform:
unreferenced object 0xffff927c8b91dbc0 (size 32): comm "kworker/0:2", pid 112, jiffies 4294893323 (age 83.604s) hex dump (first 32 bytes): 4e 41 4d 45 3d 49 4e 54 33 34 30 30 20 54 68 65 NAME=INT3400 The 72 6d 61 6c 00 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b a5 rmal.kkkkkkkkkk. backtrace: [<ffffffff9c502c3e>] __kmalloc_track_caller+0x2fe/0x4a0 [<ffffffff9c7b7c15>] kvasprintf+0x65/0xd0 [<ffffffff9c7b7d6e>] kasprintf+0x4e/0x70 [<ffffffffc04cb662>] int3400_notify+0x82/0x120 [int3400_thermal] [<ffffffff9c8b7358>] acpi_ev_notify_dispatch+0x54/0x71 [<ffffffff9c88f1a7>] acpi_os_execute_deferred+0x17/0x30 [<ffffffff9c2c2c0a>] process_one_work+0x21a/0x3f0 [<ffffffff9c2c2e2a>] worker_thread+0x4a/0x3b0 [<ffffffff9c2cb4dd>] kthread+0xfd/0x130 [<ffffffff9c201c1f>] ret_from_fork+0x1f/0x30
Fix it by calling kfree() accordingly.(CVE-2022-48924)
In the Linux kernel, the following vulnerability has been resolved:
iio: adc: men_z188_adc: Fix a resource leak in an error handling path
If iio_device_register() fails, a previous ioremap() is left unbalanced.
Update the error handling path and add the missing iounmap() call, as already done in the remove function.(CVE-2022-48928)
In the Linux kernel, the following vulnerability has been resolved:
KVM: x86/mmu: make apf token non-zero to fix bug
In current async pagefault logic, when a page is ready, KVM relies on kvm_arch_can_dequeue_async_page_present() to determine whether to deliver a READY event to the Guest. This function test token value of struct kvm_vcpu_pv_apf_data, which must be reset to zero by Guest kernel when a READY event is finished by Guest. If value is zero meaning that a READY event is done, so the KVM can deliver another. But the kvm_arch_setup_async_pf() may produce a valid token with zero value, which is confused with previous mention and may lead the loss of this READY event.
This bug may cause task blocked forever in Guest: INFO: task stress:7532 blocked for more than 1254 seconds. Not tainted 5.10.0 #16 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:stress state:D stack: 0 pid: 7532 ppid: 1409 flags:0x00000080 Call Trace: __schedule+0x1e7/0x650 schedule+0x46/0xb0 kvm_async_pf_task_wait_schedule+0xad/0xe0 ? exit_to_user_mode_prepare+0x60/0x70 __kvm_handle_async_pf+0x4f/0xb0 ? asm_exc_page_fault+0x8/0x30 exc_page_fault+0x6f/0x110 ? asm_exc_page_fault+0x8/0x30 asm_exc_page_fault+0x1e/0x30 RIP: 0033:0x402d00 RSP: 002b:00007ffd31912500 EFLAGS: 00010206 RAX: 0000000000071000 RBX: ffffffffffffffff RCX: 00000000021a32b0 RDX: 000000000007d011 RSI: 000000000007d000 RDI: 00000000021262b0 RBP: 00000000021262b0 R08: 0000000000000003 R09: 0000000000000086 R10: 00000000000000eb R11: 00007fefbdf2baa0 R12: 0000000000000000 R13: 0000000000000002 R14: 000000000007d000 R15: 0000000000001000(CVE-2022-48943)
In the Linux kernel, the following vulnerability has been resolved:
gsmi: fix null-deref in gsmi_get_variable
We can get EFI variables without fetching the attribute, so we must allow for that in gsmi.
commit 859748255b43 ("efi: pstore: Omit efivars caching EFI varstore access layer") added a new get_variable call with attr=NULL, which triggers panic in gsmi.(CVE-2023-52893)
In the Linux kernel, the following vulnerability has been resolved:
xhci: Fix null pointer dereference when host dies
Make sure xhci_free_dev() and xhci_kill_endpoint_urbs() do not race and cause null pointer dereference when host suddenly dies.
Usb core may call xhci_free_dev() which frees the xhci->devs[slot_id] virt device at the same time that xhci_kill_endpoint_urbs() tries to loop through all the device's endpoints, checking if there are any cancelled urbs left to give back.
hold the xhci spinlock while freeing the virt device(CVE-2023-52898)
In the Linux kernel, the following vulnerability has been resolved:
nilfs2: fix general protection fault in nilfs_btree_insert()
If nilfs2 reads a corrupted disk image and tries to reads a b-tree node block by calling __nilfs_btree_get_block() against an invalid virtual block address, it returns -ENOENT because conversion of the virtual block address to a disk block address fails. However, this return value is the same as the internal code that b-tree lookup routines return to indicate that the block being searched does not exist, so functions that operate on that b-tree may misbehave.
When nilfs_btree_insert() receives this spurious 'not found' code from nilfs_btree_do_lookup(), it misunderstands that the 'not found' check was successful and continues the insert operation using incomplete lookup path data, causing the following crash:
general protection fault, probably for non-canonical address 0xdffffc0000000005: 0000 [#1] PREEMPT SMP KASAN KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f] ... RIP: 0010:nilfs_btree_get_nonroot_node fs/nilfs2/btree.c:418 [inline] RIP: 0010:nilfs_btree_prepare_insert fs/nilfs2/btree.c:1077 [inline] RIP: 0010:nilfs_btree_insert+0x6d3/0x1c10 fs/nilfs2/btree.c:1238 Code: bc 24 80 00 00 00 4c 89 f8 48 c1 e8 03 42 80 3c 28 00 74 08 4c 89 ff e8 4b 02 92 fe 4d 8b 3f 49 83 c7 28 4c 89 f8 48 c1 e8 03 <42> 80 3c 28 00 74 08 4c 89 ff e8 2e 02 92 fe 4d 8b 3f 49 83 c7 02 ... Call Trace: <TASK> nilfs_bmap_do_insert fs/nilfs2/bmap.c:121 [inline] nilfs_bmap_insert+0x20d/0x360 fs/nilfs2/bmap.c:147 nilfs_get_block+0x414/0x8d0 fs/nilfs2/inode.c:101 __block_write_begin_int+0x54c/0x1a80 fs/buffer.c:1991 __block_write_begin fs/buffer.c:2041 [inline] block_write_begin+0x93/0x1e0 fs/buffer.c:2102 nilfs_write_begin+0x9c/0x110 fs/nilfs2/inode.c:261 generic_perform_write+0x2e4/0x5e0 mm/filemap.c:3772 __generic_file_write_iter+0x176/0x400 mm/filemap.c:3900 generic_file_write_iter+0xab/0x310 mm/filemap.c:3932 call_write_iter include/linux/fs.h:2186 [inline] new_sync_write fs/read_write.c:491 [inline] vfs_write+0x7dc/0xc50 fs/read_write.c:584 ksys_write+0x177/0x2a0 fs/read_write.c:637 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd ... </TASK>
This patch fixes the root cause of this problem by replacing the error code that __nilfs_btree_get_block() returns on block address conversion failure from -ENOENT to another internal code -EINVAL which means that the b-tree metadata is corrupted.
By returning -EINVAL, it propagates without glitches, and for all relevant b-tree operations, functions in the upper bmap layer output an error message indicating corrupted b-tree metadata via nilfs_bmap_convert_error(), and code -EIO will be eventually returned as it should be.(CVE-2023-52900)
In the Linux kernel, the following vulnerability has been resolved:
drivers: core: synchronize really_probe() and dev_uevent()
Synchronize the dev->driver usage in really_probe() and dev_uevent(). These can run in different threads, what can result in the following race condition for dev->driver uninitialization:
Thread #1:
really_probe() { ... probe_failed: ... device_unbind_cleanup(dev) { ... dev->driver = NULL; // <= Failed probe sets dev->driver to NULL ... } ... }
Thread #2:
dev_uevent() { ... if (dev->driver) // If dev->driver is NULLed from really_probe() from here on, // after above check, the system crashes add_uevent_var(env, "DRIVER=%s", dev->driver->name); ... }
really_probe() holds the lock, already. So nothing needs to be done there. dev_uevent() is called with lock held, often, too. But not always. What implies that we can't add any locking in dev_uevent() itself. So fix this race by adding the lock to the non-protected path. This is the path where above race is observed:
dev_uevent+0x235/0x380 uevent_show+0x10c/0x1f0 <= Add lock here dev_attr_show+0x3a/0xa0 sysfs_kf_seq_show+0x17c/0x250 kernfs_seq_show+0x7c/0x90 seq_read_iter+0x2d7/0x940 kernfs_fop_read_iter+0xc6/0x310 vfs_read+0x5bc/0x6b0 ksys_read+0xeb/0x1b0 __x64_sys_read+0x42/0x50 x64_sys_call+0x27ad/0x2d30 do_syscall_64+0xcd/0x1d0 entry_SYSCALL_64_after_hwframe+0x77/0x7f
Similar cases are reported by syzkaller in
https://syzkaller.appspot.com/bug?extid=ffa8143439596313a85a
But these are regarding the initialization of dev->driver
dev->driver = drv;
As this switches dev->driver to non-NULL these reports can be considered to be false-positives (which should be "fixed" by this commit, as well, though).
The same issue was reported and tried to be fixed back in 2015 in
https://lore.kernel.org/lkml/1421259054-2574-1-git-send-email-a.sangwan@samsung.com/
already.(CVE-2024-39501)
In the Linux kernel, the following vulnerability has been resolved:
ocfs2: add bounds checking to ocfs2_check_dir_entry()
This adds sanity checks for ocfs2_dir_entry to make sure all members of ocfs2_dir_entry don't stray beyond valid memory region.(CVE-2024-41015)
In the Linux kernel, the following vulnerability has been resolved:
s390/sclp: Fix sclp_init() cleanup on failure
If sclp_init() fails it only partially cleans up: if there are multiple failing calls to sclp_init() sclp_state_change_event will be added several times to sclp_reg_list, which results in the following warning:
------------[ cut here ]------------ list_add double add: new=000003ffe1598c10, prev=000003ffe1598bf0, next=000003ffe1598c10. WARNING: CPU: 0 PID: 1 at lib/list_debug.c:35 __list_add_valid_or_report+0xde/0xf8 CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.10.0-rc3 Krnl PSW : 0404c00180000000 000003ffe0d6076a (__list_add_valid_or_report+0xe2/0xf8) R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 ... Call Trace: [<000003ffe0d6076a>] __list_add_valid_or_report+0xe2/0xf8 ([<000003ffe0d60766>] __list_add_valid_or_report+0xde/0xf8) [<000003ffe0a8d37e>] sclp_init+0x40e/0x450 [<000003ffe00009f2>] do_one_initcall+0x42/0x1e0 [<000003ffe15b77a6>] do_initcalls+0x126/0x150 [<000003ffe15b7a0a>] kernel_init_freeable+0x1ba/0x1f8 [<000003ffe0d6650e>] kernel_init+0x2e/0x180 [<000003ffe000301c>] __ret_from_fork+0x3c/0x60 [<000003ffe0d759ca>] ret_from_fork+0xa/0x30
Fix this by removing sclp_state_change_event from sclp_reg_list when sclp_init() fails.(CVE-2024-41068)
In the Linux kernel, the following vulnerability has been resolved:
i2c: pnx: Fix potential deadlock warning from del_timer_sync() call in isr
When del_timer_sync() is called in an interrupt context it throws a warning because of potential deadlock. The timer is used only to exit from wait_for_completion() after a timeout so replacing the call with wait_for_completion_timeout() allows to remove the problematic timer and its related functions altogether.(CVE-2024-42153)
In the Linux kernel, the following vulnerability has been resolved:
protect the fetch of ->fd[fd] in do_dup2() from mispredictions
both callers have verified that fd is not greater than ->max_fds; however, misprediction might end up with tofree = fdt->fd[fd]; being speculatively executed. That's wrong for the same reasons why it's wrong in close_fd()/file_close_fd_locked(); the same solution applies - array_index_nospec(fd, fdt->max_fds) could differ from fd only in case of speculative execution on mispredicted path.(CVE-2024-42265)
In the Linux kernel, the following vulnerability has been resolved:
net/iucv: fix use after free in iucv_sock_close()
iucv_sever_path() is called from process context and from bh context. iucv->path is used as indicator whether somebody else is taking care of severing the path (or it is already removed / never existed). This needs to be done with atomic compare and swap, otherwise there is a small window where iucv_sock_close() will try to work with a path that has already been severed and freed by iucv_callback_connrej() called by iucv_tasklet_fn().
Example: [452744.123844] Call Trace: [452744.123845] ([<0000001e87f03880>] 0x1e87f03880) [452744.123966] [<00000000d593001e>] iucv_path_sever+0x96/0x138 [452744.124330] [<000003ff801ddbca>] iucv_sever_path+0xc2/0xd0 [af_iucv] [452744.124336] [<000003ff801e01b6>] iucv_sock_close+0xa6/0x310 [af_iucv] [452744.124341] [<000003ff801e08cc>] iucv_sock_release+0x3c/0xd0 [af_iucv] [452744.124345] [<00000000d574794e>] __sock_release+0x5e/0xe8 [452744.124815] [<00000000d5747a0c>] sock_close+0x34/0x48 [452744.124820] [<00000000d5421642>] __fput+0xba/0x268 [452744.124826] [<00000000d51b382c>] task_work_run+0xbc/0xf0 [452744.124832] [<00000000d5145710>] do_notify_resume+0x88/0x90 [452744.124841] [<00000000d5978096>] system_call+0xe2/0x2c8 [452744.125319] Last Breaking-Event-Address: [452744.125321] [<00000000d5930018>] iucv_path_sever+0x90/0x138 [452744.125324] [452744.125325] Kernel panic - not syncing: Fatal exception in interrupt
Note that bh_lock_sock() is not serializing the tasklet context against process context, because the check for sock_owned_by_user() and corresponding handling is missing.
Ideas for a future clean-up patch: A) Correct usage of bh_lock_sock() in tasklet context, as described in Re-enqueue, if needed. This may require adding return values to the tasklet functions and thus changes to all users of iucv.
B) Change iucv tasklet into worker and use only lock_sock() in af_iucv.(CVE-2024-42271)
In the Linux kernel, the following vulnerability has been resolved:
mISDN: Fix a use after free in hfcmulti_tx()
Don't dereference sp after calling dev_kfree_skb(sp).(CVE-2024-42280)
In the Linux kernel, the following vulnerability has been resolved:
tipc: Return non-zero value from tipc_udp_addr2str() on error
tipc_udp_addr2str() should return non-zero value if the UDP media address is invalid. Otherwise, a buffer overflow access can occur in tipc_media_addr_printf(). Fix this by returning 1 on an invalid UDP media address.(CVE-2024-42284)
In the Linux kernel, the following vulnerability has been resolved:
RDMA/iwcm: Fix a use-after-free related to destroying CM IDs
iw_conn_req_handler() associates a new struct rdma_id_private (conn_id) with an existing struct iw_cm_id (cm_id) as follows:
conn_id->cm_id.iw = cm_id;
cm_id->context = conn_id;
cm_id->cm_handler = cma_iw_handler;
rdma_destroy_id() frees both the cm_id and the struct rdma_id_private. Make sure that cm_work_handler() does not trigger a use-after-free by only freeing of the struct rdma_id_private after all pending work has finished.(CVE-2024-42285)
In the Linux kernel, the following vulnerability has been resolved:
scsi: qla2xxx: During vport delete send async logout explicitly
During vport delete, it is observed that during unload we hit a crash because of stale entries in outstanding command array. For all these stale I/O entries, eh_abort was issued and aborted (fast_fail_io = 2009h) but I/Os could not complete while vport delete is in process of deleting.
BUG: kernel NULL pointer dereference, address: 000000000000001c #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP NOPTI Workqueue: qla2xxx_wq qla_do_work [qla2xxx] RIP: 0010:dma_direct_unmap_sg+0x51/0x1e0 RSP: 0018:ffffa1e1e150fc68 EFLAGS: 00010046 RAX: 0000000000000000 RBX: 0000000000000021 RCX: 0000000000000001 RDX: 0000000000000021 RSI: 0000000000000000 RDI: ffff8ce208a7a0d0 RBP: ffff8ce208a7a0d0 R08: 0000000000000000 R09: ffff8ce378aac9c8 R10: ffff8ce378aac8a0 R11: ffffa1e1e150f9d8 R12: 0000000000000000 R13: 0000000000000000 R14: ffff8ce378aac9c8 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff8d217f000000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000000000001c CR3: 0000002089acc000 CR4: 0000000000350ee0 Call Trace: <TASK> qla2xxx_qpair_sp_free_dma+0x417/0x4e0 ? qla2xxx_qpair_sp_compl+0x10d/0x1a0 ? qla2x00_status_entry+0x768/0x2830 ? newidle_balance+0x2f0/0x430 ? dequeue_entity+0x100/0x3c0 ? qla24xx_process_response_queue+0x6a1/0x19e0 ? __schedule+0x2d5/0x1140 ? qla_do_work+0x47/0x60 ? process_one_work+0x267/0x440 ? process_one_work+0x440/0x440 ? worker_thread+0x2d/0x3d0 ? process_one_work+0x440/0x440 ? kthread+0x156/0x180 ? set_kthread_struct+0x50/0x50 ? ret_from_fork+0x22/0x30 </TASK>
Send out async logout explicitly for all the ports during vport delete.(CVE-2024-42289)
In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix to don't dirty inode for readonly filesystem
syzbot reports f2fs bug as below:
kernel BUG at fs/f2fs/inode.c:933! RIP: 0010:f2fs_evict_inode+0x1576/0x1590 fs/f2fs/inode.c:933 Call Trace: evict+0x2a4/0x620 fs/inode.c:664 dispose_list fs/inode.c:697 [inline] evict_inodes+0x5f8/0x690 fs/inode.c:747 generic_shutdown_super+0x9d/0x2c0 fs/super.c:675 kill_block_super+0x44/0x90 fs/super.c:1667 kill_f2fs_super+0x303/0x3b0 fs/f2fs/super.c:4894 deactivate_locked_super+0xc1/0x130 fs/super.c:484 cleanup_mnt+0x426/0x4c0 fs/namespace.c:1256 task_work_run+0x24a/0x300 kernel/task_work.c:180 ptrace_notify+0x2cd/0x380 kernel/signal.c:2399 ptrace_report_syscall include/linux/ptrace.h:411 [inline] ptrace_report_syscall_exit include/linux/ptrace.h:473 [inline] syscall_exit_work kernel/entry/common.c:251 [inline] syscall_exit_to_user_mode_prepare kernel/entry/common.c:278 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline] syscall_exit_to_user_mode+0x15c/0x280 kernel/entry/common.c:296 do_syscall_64+0x50/0x110 arch/x86/entry/common.c:88 entry_SYSCALL_64_after_hwframe+0x63/0x6b
The root cause is: - do_sys_open - f2fs_lookup - __f2fs_find_entry - f2fs_i_depth_write - f2fs_mark_inode_dirty_sync - f2fs_dirty_inode - set_inode_flag(inode, FI_DIRTY_INODE)
- umount
- kill_f2fs_super
- kill_block_super
- generic_shutdown_super
- sync_filesystem : sb is readonly, skip sync_filesystem()
- evict_inodes
- iput
- f2fs_evict_inode
- f2fs_bug_on(sbi, is_inode_flag_set(inode, FI_DIRTY_INODE)) : trigger kernel panic
When we try to repair i_current_depth in readonly filesystem, let's skip dirty inode to avoid panic in later f2fs_evict_inode().(CVE-2024-42297)
In the Linux kernel, the following vulnerability has been resolved:
ext4: check dot and dotdot of dx_root before making dir indexed
Syzbot reports a issue as follows:
BUG: unable to handle page fault for address: ffffed11022e24fe PGD 23ffee067 P4D 23ffee067 PUD 0 Oops: Oops: 0000 [#1] PREEMPT SMP KASAN PTI CPU: 0 PID: 5079 Comm: syz-executor306 Not tainted 6.10.0-rc5-g55027e689933 #0 Call Trace: <TASK> make_indexed_dir+0xdaf/0x13c0 fs/ext4/namei.c:2341 ext4_add_entry+0x222a/0x25d0 fs/ext4/namei.c:2451 ext4_rename fs/ext4/namei.c:3936 [inline] ext4_rename2+0x26e5/0x4370 fs/ext4/namei.c:4214 [...] ============================================
The immediate cause of this problem is that there is only one valid dentry for the block to be split during do_split, so split==0 results in out of bounds accesses to the map triggering the issue.
do_split
unsigned split
dx_make_map
count = 1
split = count/2 = 0;
continued = hash2 == map[split - 1].hash;
---> map[4294967295]
The maximum length of a filename is 255 and the minimum block size is 1024, so it is always guaranteed that the number of entries is greater than or equal to 2 when do_split() is called.
But syzbot's crafted image has no dot and dotdot in dir, and the dentry distribution in dirblock is as follows:
bus dentry1 hole dentry2 free |xx--|xx-------------|...............|xx-------------|...............| 0 12 (8+248)=256 268 256 524 (8+256)=264 788 236 1024
So when renaming dentry1 increases its name_len length by 1, neither hole nor free is sufficient to hold the new dentry, and make_indexed_dir() is called.
In make_indexed_dir() it is assumed that the first two entries of the dirblock must be dot and dotdot, so bus and dentry1 are left in dx_root because they are treated as dot and dotdot, and only dentry2 is moved to the new leaf block. That's why count is equal to 1.
Therefore add the ext4_check_dx_root() helper function to add more sanity checks to dot and dotdot before starting the conversion to avoid the above issue.(CVE-2024-42305)
In the Linux kernel, the following vulnerability has been resolved:
net: usb: qmi_wwan: fix memory leak for not ip packets
Free the unused skb when not ip packets arrive.(CVE-2024-43861)
In the Linux kernel, the following vulnerability has been resolved:
wifi: cfg80211: handle 2x996 RU allocation in cfg80211_calculate_bitrate_he()
Currently NL80211_RATE_INFO_HE_RU_ALLOC_2x996 is not handled in cfg80211_calculate_bitrate_he(), leading to below warning:
kernel: invalid HE MCS: bw:6, ru:6 kernel: WARNING: CPU: 0 PID: 2312 at net/wireless/util.c:1501 cfg80211_calculate_bitrate_he+0x22b/0x270 [cfg80211]
Fix it by handling 2x996 RU allocation in the same way as 160 MHz bandwidth.(CVE-2024-43879)
In the Linux kernel, the following vulnerability has been resolved:
exec: Fix ToCToU between perm check and set-uid/gid usage
When opening a file for exec via do_filp_open(), permission checking is done against the file's metadata at that moment, and on success, a file pointer is passed back. Much later in the execve() code path, the file metadata (specifically mode, uid, and gid) is used to determine if/how to set the uid and gid. However, those values may have changed since the permissions check, meaning the execution may gain unintended privileges.
For example, if a file could change permissions from executable and not set-id:
---------x 1 root root 16048 Aug 7 13:16 target
to set-id and non-executable:
---S------ 1 root root 16048 Aug 7 13:16 target
it is possible to gain root privileges when execution should have been disallowed.
While this race condition is rare in real-world scenarios, it has been observed (and proven exploitable) when package managers are updating the setuid bits of installed programs. Such files start with being world-executable but then are adjusted to be group-exec with a set-uid bit. For example, "chmod o-x,u+s target" makes "target" executable only by uid "root" and gid "cdrom", while also becoming setuid-root:
-rwxr-xr-x 1 root cdrom 16048 Aug 7 13:16 target
becomes:
-rwsr-xr-- 1 root cdrom 16048 Aug 7 13:16 target
But racing the chmod means users without group "cdrom" membership can get the permission to execute "target" just before the chmod, and when the chmod finishes, the exec reaches brpm_fill_uid(), and performs the setuid to root, violating the expressed authorization of "only cdrom group members can setuid to root".
Re-check that we still have execute permissions in case the metadata has changed. It would be better to keep a copy from the perm-check time, but until we can do that refactoring, the least-bad option is to do a full inode_permission() call (under inode lock). It is understood that this is safe against dead-locks, but hardly optimal.(CVE-2024-43882)
| URL | Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"bpftool-4.19.90-2408.5.0.0292.oe2003sp4.aarch64.rpm",
"bpftool-debuginfo-4.19.90-2408.5.0.0292.oe2003sp4.aarch64.rpm",
"kernel-4.19.90-2408.5.0.0292.oe2003sp4.aarch64.rpm",
"kernel-debuginfo-4.19.90-2408.5.0.0292.oe2003sp4.aarch64.rpm",
"kernel-debugsource-4.19.90-2408.5.0.0292.oe2003sp4.aarch64.rpm",
"kernel-devel-4.19.90-2408.5.0.0292.oe2003sp4.aarch64.rpm",
"kernel-source-4.19.90-2408.5.0.0292.oe2003sp4.aarch64.rpm",
"kernel-tools-4.19.90-2408.5.0.0292.oe2003sp4.aarch64.rpm",
"kernel-tools-debuginfo-4.19.90-2408.5.0.0292.oe2003sp4.aarch64.rpm",
"kernel-tools-devel-4.19.90-2408.5.0.0292.oe2003sp4.aarch64.rpm",
"perf-4.19.90-2408.5.0.0292.oe2003sp4.aarch64.rpm",
"perf-debuginfo-4.19.90-2408.5.0.0292.oe2003sp4.aarch64.rpm",
"python2-perf-4.19.90-2408.5.0.0292.oe2003sp4.aarch64.rpm",
"python2-perf-debuginfo-4.19.90-2408.5.0.0292.oe2003sp4.aarch64.rpm",
"python3-perf-4.19.90-2408.5.0.0292.oe2003sp4.aarch64.rpm",
"python3-perf-debuginfo-4.19.90-2408.5.0.0292.oe2003sp4.aarch64.rpm"
],
"src": [
"kernel-4.19.90-2408.5.0.0292.oe2003sp4.src.rpm"
],
"x86_64": [
"bpftool-4.19.90-2408.5.0.0292.oe2003sp4.x86_64.rpm",
"bpftool-debuginfo-4.19.90-2408.5.0.0292.oe2003sp4.x86_64.rpm",
"kernel-4.19.90-2408.5.0.0292.oe2003sp4.x86_64.rpm",
"kernel-debuginfo-4.19.90-2408.5.0.0292.oe2003sp4.x86_64.rpm",
"kernel-debugsource-4.19.90-2408.5.0.0292.oe2003sp4.x86_64.rpm",
"kernel-devel-4.19.90-2408.5.0.0292.oe2003sp4.x86_64.rpm",
"kernel-source-4.19.90-2408.5.0.0292.oe2003sp4.x86_64.rpm",
"kernel-tools-4.19.90-2408.5.0.0292.oe2003sp4.x86_64.rpm",
"kernel-tools-debuginfo-4.19.90-2408.5.0.0292.oe2003sp4.x86_64.rpm",
"kernel-tools-devel-4.19.90-2408.5.0.0292.oe2003sp4.x86_64.rpm",
"perf-4.19.90-2408.5.0.0292.oe2003sp4.x86_64.rpm",
"perf-debuginfo-4.19.90-2408.5.0.0292.oe2003sp4.x86_64.rpm",
"python2-perf-4.19.90-2408.5.0.0292.oe2003sp4.x86_64.rpm",
"python2-perf-debuginfo-4.19.90-2408.5.0.0292.oe2003sp4.x86_64.rpm",
"python3-perf-4.19.90-2408.5.0.0292.oe2003sp4.x86_64.rpm",
"python3-perf-debuginfo-4.19.90-2408.5.0.0292.oe2003sp4.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS-SP4",
"name": "kernel",
"purl": "pkg:rpm/openEuler/kernel\u0026distro=openEuler-20.03-LTS-SP4"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.19.90-2408.5.0.0292.oe2003sp4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nparisc: Fix data TLB miss in sba_unmap_sg\r\n\r\nRolf Eike Beer reported the following bug:\r\n\r\n[1274934.746891] Bad Address (null pointer deref?): Code=15 (Data TLB miss fault) at addr 0000004140000018\n[1274934.746891] CPU: 3 PID: 5549 Comm: cmake Not tainted 5.15.4-gentoo-parisc64 #4\n[1274934.746891] Hardware name: 9000/785/C8000\n[1274934.746891]\n[1274934.746891] YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI\n[1274934.746891] PSW: 00001000000001001111111000001110 Not tainted\n[1274934.746891] r00-03 000000ff0804fe0e 0000000040bc9bc0 00000000406760e4 0000004140000000\n[1274934.746891] r04-07 0000000040b693c0 0000004140000000 000000004a2b08b0 0000000000000001\n[1274934.746891] r08-11 0000000041f98810 0000000000000000 000000004a0a7000 0000000000000001\n[1274934.746891] r12-15 0000000040bddbc0 0000000040c0cbc0 0000000040bddbc0 0000000040bddbc0\n[1274934.746891] r16-19 0000000040bde3c0 0000000040bddbc0 0000000040bde3c0 0000000000000007\n[1274934.746891] r20-23 0000000000000006 000000004a368950 0000000000000000 0000000000000001\n[1274934.746891] r24-27 0000000000001fff 000000000800000e 000000004a1710f0 0000000040b693c0\n[1274934.746891] r28-31 0000000000000001 0000000041f988b0 0000000041f98840 000000004a171118\n[1274934.746891] sr00-03 00000000066e5800 0000000000000000 0000000000000000 00000000066e5800\n[1274934.746891] sr04-07 0000000000000000 0000000000000000 0000000000000000 0000000000000000\n[1274934.746891]\n[1274934.746891] IASQ: 0000000000000000 0000000000000000 IAOQ: 00000000406760e8 00000000406760ec\n[1274934.746891] IIR: 48780030 ISR: 0000000000000000 IOR: 0000004140000018\n[1274934.746891] CPU: 3 CR30: 00000040e3a9c000 CR31: ffffffffffffffff\n[1274934.746891] ORIG_R28: 0000000040acdd58\n[1274934.746891] IAOQ[0]: sba_unmap_sg+0xb0/0x118\n[1274934.746891] IAOQ[1]: sba_unmap_sg+0xb4/0x118\n[1274934.746891] RP(r2): sba_unmap_sg+0xac/0x118\n[1274934.746891] Backtrace:\n[1274934.746891] [\u0026lt;00000000402740cc\u0026gt;] dma_unmap_sg_attrs+0x6c/0x70\n[1274934.746891] [\u0026lt;000000004074d6bc\u0026gt;] scsi_dma_unmap+0x54/0x60\n[1274934.746891] [\u0026lt;00000000407a3488\u0026gt;] mptscsih_io_done+0x150/0xd70\n[1274934.746891] [\u0026lt;0000000040798600\u0026gt;] mpt_interrupt+0x168/0xa68\n[1274934.746891] [\u0026lt;0000000040255a48\u0026gt;] __handle_irq_event_percpu+0xc8/0x278\n[1274934.746891] [\u0026lt;0000000040255c34\u0026gt;] handle_irq_event_percpu+0x3c/0xd8\n[1274934.746891] [\u0026lt;000000004025ecb4\u0026gt;] handle_percpu_irq+0xb4/0xf0\n[1274934.746891] [\u0026lt;00000000402548e0\u0026gt;] generic_handle_irq+0x50/0x70\n[1274934.746891] [\u0026lt;000000004019a254\u0026gt;] call_on_stack+0x18/0x24\n[1274934.746891]\n[1274934.746891] Kernel panic - not syncing: Bad Address (null pointer deref?)\r\n\r\nThe bug is caused by overrunning the sglist and incorrectly testing\nsg_dma_len(sglist) before nents. Normally this doesn\u0026apos;t cause a crash,\nbut in this case sglist crossed a page boundary. This occurs in the\nfollowing code:\r\n\r\n\twhile (sg_dma_len(sglist) \u0026amp;\u0026amp; nents--) {\r\n\r\nThe fix is simply to test nents first and move the decrement of nents\ninto the loop.(CVE-2022-48795)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/virtio: Fix GEM handle creation UAF\r\n\r\nUserspace can guess the handle value and try to race GEM object creation\nwith handle close, resulting in a use-after-free if we dereference the\nobject after dropping the handle\u0026apos;s reference. For that reason, dropping\nthe handle\u0026apos;s reference must be done *after* we are done dereferencing\nthe object.(CVE-2022-48899)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nthermal: int340x: fix memory leak in int3400_notify()\r\n\r\nIt is easy to hit the below memory leaks in my TigerLake platform:\r\n\r\nunreferenced object 0xffff927c8b91dbc0 (size 32):\n comm \u0026quot;kworker/0:2\u0026quot;, pid 112, jiffies 4294893323 (age 83.604s)\n hex dump (first 32 bytes):\n 4e 41 4d 45 3d 49 4e 54 33 34 30 30 20 54 68 65 NAME=INT3400 The\n 72 6d 61 6c 00 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b a5 rmal.kkkkkkkkkk.\n backtrace:\n [\u0026lt;ffffffff9c502c3e\u0026gt;] __kmalloc_track_caller+0x2fe/0x4a0\n [\u0026lt;ffffffff9c7b7c15\u0026gt;] kvasprintf+0x65/0xd0\n [\u0026lt;ffffffff9c7b7d6e\u0026gt;] kasprintf+0x4e/0x70\n [\u0026lt;ffffffffc04cb662\u0026gt;] int3400_notify+0x82/0x120 [int3400_thermal]\n [\u0026lt;ffffffff9c8b7358\u0026gt;] acpi_ev_notify_dispatch+0x54/0x71\n [\u0026lt;ffffffff9c88f1a7\u0026gt;] acpi_os_execute_deferred+0x17/0x30\n [\u0026lt;ffffffff9c2c2c0a\u0026gt;] process_one_work+0x21a/0x3f0\n [\u0026lt;ffffffff9c2c2e2a\u0026gt;] worker_thread+0x4a/0x3b0\n [\u0026lt;ffffffff9c2cb4dd\u0026gt;] kthread+0xfd/0x130\n [\u0026lt;ffffffff9c201c1f\u0026gt;] ret_from_fork+0x1f/0x30\r\n\r\nFix it by calling kfree() accordingly.(CVE-2022-48924)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\niio: adc: men_z188_adc: Fix a resource leak in an error handling path\r\n\r\nIf iio_device_register() fails, a previous ioremap() is left unbalanced.\r\n\r\nUpdate the error handling path and add the missing iounmap() call, as\nalready done in the remove function.(CVE-2022-48928)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nKVM: x86/mmu: make apf token non-zero to fix bug\r\n\r\nIn current async pagefault logic, when a page is ready, KVM relies on\nkvm_arch_can_dequeue_async_page_present() to determine whether to deliver\na READY event to the Guest. This function test token value of struct\nkvm_vcpu_pv_apf_data, which must be reset to zero by Guest kernel when a\nREADY event is finished by Guest. If value is zero meaning that a READY\nevent is done, so the KVM can deliver another.\nBut the kvm_arch_setup_async_pf() may produce a valid token with zero\nvalue, which is confused with previous mention and may lead the loss of\nthis READY event.\r\n\r\nThis bug may cause task blocked forever in Guest:\n INFO: task stress:7532 blocked for more than 1254 seconds.\n Not tainted 5.10.0 #16\n \u0026quot;echo 0 \u0026gt; /proc/sys/kernel/hung_task_timeout_secs\u0026quot; disables this message.\n task:stress state:D stack: 0 pid: 7532 ppid: 1409\n flags:0x00000080\n Call Trace:\n __schedule+0x1e7/0x650\n schedule+0x46/0xb0\n kvm_async_pf_task_wait_schedule+0xad/0xe0\n ? exit_to_user_mode_prepare+0x60/0x70\n __kvm_handle_async_pf+0x4f/0xb0\n ? asm_exc_page_fault+0x8/0x30\n exc_page_fault+0x6f/0x110\n ? asm_exc_page_fault+0x8/0x30\n asm_exc_page_fault+0x1e/0x30\n RIP: 0033:0x402d00\n RSP: 002b:00007ffd31912500 EFLAGS: 00010206\n RAX: 0000000000071000 RBX: ffffffffffffffff RCX: 00000000021a32b0\n RDX: 000000000007d011 RSI: 000000000007d000 RDI: 00000000021262b0\n RBP: 00000000021262b0 R08: 0000000000000003 R09: 0000000000000086\n R10: 00000000000000eb R11: 00007fefbdf2baa0 R12: 0000000000000000\n R13: 0000000000000002 R14: 000000000007d000 R15: 0000000000001000(CVE-2022-48943)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ngsmi: fix null-deref in gsmi_get_variable\r\n\r\nWe can get EFI variables without fetching the attribute, so we must\nallow for that in gsmi.\r\n\r\ncommit 859748255b43 (\u0026quot;efi: pstore: Omit efivars caching EFI varstore\naccess layer\u0026quot;) added a new get_variable call with attr=NULL, which\ntriggers panic in gsmi.(CVE-2023-52893)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nxhci: Fix null pointer dereference when host dies\r\n\r\nMake sure xhci_free_dev() and xhci_kill_endpoint_urbs() do not race\nand cause null pointer dereference when host suddenly dies.\r\n\r\nUsb core may call xhci_free_dev() which frees the xhci-\u0026gt;devs[slot_id]\nvirt device at the same time that xhci_kill_endpoint_urbs() tries to\nloop through all the device\u0026apos;s endpoints, checking if there are any\ncancelled urbs left to give back.\r\n\r\nhold the xhci spinlock while freeing the virt device(CVE-2023-52898)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnilfs2: fix general protection fault in nilfs_btree_insert()\r\n\r\nIf nilfs2 reads a corrupted disk image and tries to reads a b-tree node\nblock by calling __nilfs_btree_get_block() against an invalid virtual\nblock address, it returns -ENOENT because conversion of the virtual block\naddress to a disk block address fails. However, this return value is the\nsame as the internal code that b-tree lookup routines return to indicate\nthat the block being searched does not exist, so functions that operate on\nthat b-tree may misbehave.\r\n\r\nWhen nilfs_btree_insert() receives this spurious \u0026apos;not found\u0026apos; code from\nnilfs_btree_do_lookup(), it misunderstands that the \u0026apos;not found\u0026apos; check was\nsuccessful and continues the insert operation using incomplete lookup path\ndata, causing the following crash:\r\n\r\n general protection fault, probably for non-canonical address\n 0xdffffc0000000005: 0000 [#1] PREEMPT SMP KASAN\n KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f]\n ...\n RIP: 0010:nilfs_btree_get_nonroot_node fs/nilfs2/btree.c:418 [inline]\n RIP: 0010:nilfs_btree_prepare_insert fs/nilfs2/btree.c:1077 [inline]\n RIP: 0010:nilfs_btree_insert+0x6d3/0x1c10 fs/nilfs2/btree.c:1238\n Code: bc 24 80 00 00 00 4c 89 f8 48 c1 e8 03 42 80 3c 28 00 74 08 4c 89\n ff e8 4b 02 92 fe 4d 8b 3f 49 83 c7 28 4c 89 f8 48 c1 e8 03 \u0026lt;42\u0026gt; 80 3c\n 28 00 74 08 4c 89 ff e8 2e 02 92 fe 4d 8b 3f 49 83 c7 02\n ...\n Call Trace:\n \u0026lt;TASK\u0026gt;\n nilfs_bmap_do_insert fs/nilfs2/bmap.c:121 [inline]\n nilfs_bmap_insert+0x20d/0x360 fs/nilfs2/bmap.c:147\n nilfs_get_block+0x414/0x8d0 fs/nilfs2/inode.c:101\n __block_write_begin_int+0x54c/0x1a80 fs/buffer.c:1991\n __block_write_begin fs/buffer.c:2041 [inline]\n block_write_begin+0x93/0x1e0 fs/buffer.c:2102\n nilfs_write_begin+0x9c/0x110 fs/nilfs2/inode.c:261\n generic_perform_write+0x2e4/0x5e0 mm/filemap.c:3772\n __generic_file_write_iter+0x176/0x400 mm/filemap.c:3900\n generic_file_write_iter+0xab/0x310 mm/filemap.c:3932\n call_write_iter include/linux/fs.h:2186 [inline]\n new_sync_write fs/read_write.c:491 [inline]\n vfs_write+0x7dc/0xc50 fs/read_write.c:584\n ksys_write+0x177/0x2a0 fs/read_write.c:637\n do_syscall_x64 arch/x86/entry/common.c:50 [inline]\n do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80\n entry_SYSCALL_64_after_hwframe+0x63/0xcd\n ...\n \u0026lt;/TASK\u0026gt;\r\n\r\nThis patch fixes the root cause of this problem by replacing the error\ncode that __nilfs_btree_get_block() returns on block address conversion\nfailure from -ENOENT to another internal code -EINVAL which means that the\nb-tree metadata is corrupted.\r\n\r\nBy returning -EINVAL, it propagates without glitches, and for all relevant\nb-tree operations, functions in the upper bmap layer output an error\nmessage indicating corrupted b-tree metadata via\nnilfs_bmap_convert_error(), and code -EIO will be eventually returned as\nit should be.(CVE-2023-52900)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrivers: core: synchronize really_probe() and dev_uevent()\r\n\r\nSynchronize the dev-\u0026gt;driver usage in really_probe() and dev_uevent().\nThese can run in different threads, what can result in the following\nrace condition for dev-\u0026gt;driver uninitialization:\r\n\r\nThread #1:\n==========\r\n\r\nreally_probe() {\n...\nprobe_failed:\n...\ndevice_unbind_cleanup(dev) {\n ...\n dev-\u0026gt;driver = NULL; // \u0026lt;= Failed probe sets dev-\u0026gt;driver to NULL\n ...\n }\n...\n}\r\n\r\nThread #2:\n==========\r\n\r\ndev_uevent() {\n...\nif (dev-\u0026gt;driver)\n // If dev-\u0026gt;driver is NULLed from really_probe() from here on,\n // after above check, the system crashes\n add_uevent_var(env, \u0026quot;DRIVER=%s\u0026quot;, dev-\u0026gt;driver-\u0026gt;name);\n...\n}\r\n\r\nreally_probe() holds the lock, already. So nothing needs to be done\nthere. dev_uevent() is called with lock held, often, too. But not\nalways. What implies that we can\u0026apos;t add any locking in dev_uevent()\nitself. So fix this race by adding the lock to the non-protected\npath. This is the path where above race is observed:\r\n\r\n dev_uevent+0x235/0x380\n uevent_show+0x10c/0x1f0 \u0026lt;= Add lock here\n dev_attr_show+0x3a/0xa0\n sysfs_kf_seq_show+0x17c/0x250\n kernfs_seq_show+0x7c/0x90\n seq_read_iter+0x2d7/0x940\n kernfs_fop_read_iter+0xc6/0x310\n vfs_read+0x5bc/0x6b0\n ksys_read+0xeb/0x1b0\n __x64_sys_read+0x42/0x50\n x64_sys_call+0x27ad/0x2d30\n do_syscall_64+0xcd/0x1d0\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\r\n\r\nSimilar cases are reported by syzkaller in\r\n\r\nhttps://syzkaller.appspot.com/bug?extid=ffa8143439596313a85a\r\n\r\nBut these are regarding the *initialization* of dev-\u0026gt;driver\r\n\r\ndev-\u0026gt;driver = drv;\r\n\r\nAs this switches dev-\u0026gt;driver to non-NULL these reports can be considered\nto be false-positives (which should be \u0026quot;fixed\u0026quot; by this commit, as well,\nthough).\r\n\r\nThe same issue was reported and tried to be fixed back in 2015 in\r\n\r\nhttps://lore.kernel.org/lkml/1421259054-2574-1-git-send-email-a.sangwan@samsung.com/\r\n\r\nalready.(CVE-2024-39501)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nocfs2: add bounds checking to ocfs2_check_dir_entry()\r\n\r\nThis adds sanity checks for ocfs2_dir_entry to make sure all members of\nocfs2_dir_entry don\u0026apos;t stray beyond valid memory region.(CVE-2024-41015)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ns390/sclp: Fix sclp_init() cleanup on failure\r\n\r\nIf sclp_init() fails it only partially cleans up: if there are multiple\nfailing calls to sclp_init() sclp_state_change_event will be added several\ntimes to sclp_reg_list, which results in the following warning:\r\n\r\n------------[ cut here ]------------\nlist_add double add: new=000003ffe1598c10, prev=000003ffe1598bf0, next=000003ffe1598c10.\nWARNING: CPU: 0 PID: 1 at lib/list_debug.c:35 __list_add_valid_or_report+0xde/0xf8\nCPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.10.0-rc3\nKrnl PSW : 0404c00180000000 000003ffe0d6076a (__list_add_valid_or_report+0xe2/0xf8)\n R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3\n...\nCall Trace:\n [\u0026lt;000003ffe0d6076a\u0026gt;] __list_add_valid_or_report+0xe2/0xf8\n([\u0026lt;000003ffe0d60766\u0026gt;] __list_add_valid_or_report+0xde/0xf8)\n [\u0026lt;000003ffe0a8d37e\u0026gt;] sclp_init+0x40e/0x450\n [\u0026lt;000003ffe00009f2\u0026gt;] do_one_initcall+0x42/0x1e0\n [\u0026lt;000003ffe15b77a6\u0026gt;] do_initcalls+0x126/0x150\n [\u0026lt;000003ffe15b7a0a\u0026gt;] kernel_init_freeable+0x1ba/0x1f8\n [\u0026lt;000003ffe0d6650e\u0026gt;] kernel_init+0x2e/0x180\n [\u0026lt;000003ffe000301c\u0026gt;] __ret_from_fork+0x3c/0x60\n [\u0026lt;000003ffe0d759ca\u0026gt;] ret_from_fork+0xa/0x30\r\n\r\nFix this by removing sclp_state_change_event from sclp_reg_list when\nsclp_init() fails.(CVE-2024-41068)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ni2c: pnx: Fix potential deadlock warning from del_timer_sync() call in isr\r\n\r\nWhen del_timer_sync() is called in an interrupt context it throws a warning\nbecause of potential deadlock. The timer is used only to exit from\nwait_for_completion() after a timeout so replacing the call with\nwait_for_completion_timeout() allows to remove the problematic timer and\nits related functions altogether.(CVE-2024-42153)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nprotect the fetch of -\u0026gt;fd[fd] in do_dup2() from mispredictions\r\n\r\nboth callers have verified that fd is not greater than -\u0026gt;max_fds;\nhowever, misprediction might end up with\n tofree = fdt-\u0026gt;fd[fd];\nbeing speculatively executed. That\u0026apos;s wrong for the same reasons\nwhy it\u0026apos;s wrong in close_fd()/file_close_fd_locked(); the same\nsolution applies - array_index_nospec(fd, fdt-\u0026gt;max_fds) could differ\nfrom fd only in case of speculative execution on mispredicted path.(CVE-2024-42265)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/iucv: fix use after free in iucv_sock_close()\r\n\r\niucv_sever_path() is called from process context and from bh context.\niucv-\u0026gt;path is used as indicator whether somebody else is taking care of\nsevering the path (or it is already removed / never existed).\nThis needs to be done with atomic compare and swap, otherwise there is a\nsmall window where iucv_sock_close() will try to work with a path that has\nalready been severed and freed by iucv_callback_connrej() called by\niucv_tasklet_fn().\r\n\r\nExample:\n[452744.123844] Call Trace:\n[452744.123845] ([\u0026lt;0000001e87f03880\u0026gt;] 0x1e87f03880)\n[452744.123966] [\u0026lt;00000000d593001e\u0026gt;] iucv_path_sever+0x96/0x138\n[452744.124330] [\u0026lt;000003ff801ddbca\u0026gt;] iucv_sever_path+0xc2/0xd0 [af_iucv]\n[452744.124336] [\u0026lt;000003ff801e01b6\u0026gt;] iucv_sock_close+0xa6/0x310 [af_iucv]\n[452744.124341] [\u0026lt;000003ff801e08cc\u0026gt;] iucv_sock_release+0x3c/0xd0 [af_iucv]\n[452744.124345] [\u0026lt;00000000d574794e\u0026gt;] __sock_release+0x5e/0xe8\n[452744.124815] [\u0026lt;00000000d5747a0c\u0026gt;] sock_close+0x34/0x48\n[452744.124820] [\u0026lt;00000000d5421642\u0026gt;] __fput+0xba/0x268\n[452744.124826] [\u0026lt;00000000d51b382c\u0026gt;] task_work_run+0xbc/0xf0\n[452744.124832] [\u0026lt;00000000d5145710\u0026gt;] do_notify_resume+0x88/0x90\n[452744.124841] [\u0026lt;00000000d5978096\u0026gt;] system_call+0xe2/0x2c8\n[452744.125319] Last Breaking-Event-Address:\n[452744.125321] [\u0026lt;00000000d5930018\u0026gt;] iucv_path_sever+0x90/0x138\n[452744.125324]\n[452744.125325] Kernel panic - not syncing: Fatal exception in interrupt\r\n\r\nNote that bh_lock_sock() is not serializing the tasklet context against\nprocess context, because the check for sock_owned_by_user() and\ncorresponding handling is missing.\r\n\r\nIdeas for a future clean-up patch:\nA) Correct usage of bh_lock_sock() in tasklet context, as described in\nRe-enqueue, if needed. This may require adding return values to the\ntasklet functions and thus changes to all users of iucv.\r\n\r\nB) Change iucv tasklet into worker and use only lock_sock() in af_iucv.(CVE-2024-42271)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmISDN: Fix a use after free in hfcmulti_tx()\r\n\r\nDon\u0026apos;t dereference *sp after calling dev_kfree_skb(*sp).(CVE-2024-42280)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntipc: Return non-zero value from tipc_udp_addr2str() on error\r\n\r\ntipc_udp_addr2str() should return non-zero value if the UDP media\naddress is invalid. Otherwise, a buffer overflow access can occur in\ntipc_media_addr_printf(). Fix this by returning 1 on an invalid UDP\nmedia address.(CVE-2024-42284)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nRDMA/iwcm: Fix a use-after-free related to destroying CM IDs\r\n\r\niw_conn_req_handler() associates a new struct rdma_id_private (conn_id) with\nan existing struct iw_cm_id (cm_id) as follows:\r\n\r\n conn_id-\u0026gt;cm_id.iw = cm_id;\n cm_id-\u0026gt;context = conn_id;\n cm_id-\u0026gt;cm_handler = cma_iw_handler;\r\n\r\nrdma_destroy_id() frees both the cm_id and the struct rdma_id_private. Make\nsure that cm_work_handler() does not trigger a use-after-free by only\nfreeing of the struct rdma_id_private after all pending work has finished.(CVE-2024-42285)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nscsi: qla2xxx: During vport delete send async logout explicitly\r\n\r\nDuring vport delete, it is observed that during unload we hit a crash\nbecause of stale entries in outstanding command array. For all these stale\nI/O entries, eh_abort was issued and aborted (fast_fail_io = 2009h) but\nI/Os could not complete while vport delete is in process of deleting.\r\n\r\n BUG: kernel NULL pointer dereference, address: 000000000000001c\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\n PGD 0 P4D 0\n Oops: 0000 [#1] PREEMPT SMP NOPTI\n Workqueue: qla2xxx_wq qla_do_work [qla2xxx]\n RIP: 0010:dma_direct_unmap_sg+0x51/0x1e0\n RSP: 0018:ffffa1e1e150fc68 EFLAGS: 00010046\n RAX: 0000000000000000 RBX: 0000000000000021 RCX: 0000000000000001\n RDX: 0000000000000021 RSI: 0000000000000000 RDI: ffff8ce208a7a0d0\n RBP: ffff8ce208a7a0d0 R08: 0000000000000000 R09: ffff8ce378aac9c8\n R10: ffff8ce378aac8a0 R11: ffffa1e1e150f9d8 R12: 0000000000000000\n R13: 0000000000000000 R14: ffff8ce378aac9c8 R15: 0000000000000000\n FS: 0000000000000000(0000) GS:ffff8d217f000000(0000) knlGS:0000000000000000\n CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 000000000000001c CR3: 0000002089acc000 CR4: 0000000000350ee0\n Call Trace:\n \u0026lt;TASK\u0026gt;\n qla2xxx_qpair_sp_free_dma+0x417/0x4e0\n ? qla2xxx_qpair_sp_compl+0x10d/0x1a0\n ? qla2x00_status_entry+0x768/0x2830\n ? newidle_balance+0x2f0/0x430\n ? dequeue_entity+0x100/0x3c0\n ? qla24xx_process_response_queue+0x6a1/0x19e0\n ? __schedule+0x2d5/0x1140\n ? qla_do_work+0x47/0x60\n ? process_one_work+0x267/0x440\n ? process_one_work+0x440/0x440\n ? worker_thread+0x2d/0x3d0\n ? process_one_work+0x440/0x440\n ? kthread+0x156/0x180\n ? set_kthread_struct+0x50/0x50\n ? ret_from_fork+0x22/0x30\n \u0026lt;/TASK\u0026gt;\r\n\r\nSend out async logout explicitly for all the ports during vport delete.(CVE-2024-42289)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nf2fs: fix to don\u0026apos;t dirty inode for readonly filesystem\r\n\r\nsyzbot reports f2fs bug as below:\r\n\r\nkernel BUG at fs/f2fs/inode.c:933!\nRIP: 0010:f2fs_evict_inode+0x1576/0x1590 fs/f2fs/inode.c:933\nCall Trace:\n evict+0x2a4/0x620 fs/inode.c:664\n dispose_list fs/inode.c:697 [inline]\n evict_inodes+0x5f8/0x690 fs/inode.c:747\n generic_shutdown_super+0x9d/0x2c0 fs/super.c:675\n kill_block_super+0x44/0x90 fs/super.c:1667\n kill_f2fs_super+0x303/0x3b0 fs/f2fs/super.c:4894\n deactivate_locked_super+0xc1/0x130 fs/super.c:484\n cleanup_mnt+0x426/0x4c0 fs/namespace.c:1256\n task_work_run+0x24a/0x300 kernel/task_work.c:180\n ptrace_notify+0x2cd/0x380 kernel/signal.c:2399\n ptrace_report_syscall include/linux/ptrace.h:411 [inline]\n ptrace_report_syscall_exit include/linux/ptrace.h:473 [inline]\n syscall_exit_work kernel/entry/common.c:251 [inline]\n syscall_exit_to_user_mode_prepare kernel/entry/common.c:278 [inline]\n __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline]\n syscall_exit_to_user_mode+0x15c/0x280 kernel/entry/common.c:296\n do_syscall_64+0x50/0x110 arch/x86/entry/common.c:88\n entry_SYSCALL_64_after_hwframe+0x63/0x6b\r\n\r\nThe root cause is:\n- do_sys_open\n - f2fs_lookup\n - __f2fs_find_entry\n - f2fs_i_depth_write\n - f2fs_mark_inode_dirty_sync\n - f2fs_dirty_inode\n - set_inode_flag(inode, FI_DIRTY_INODE)\r\n\r\n- umount\n - kill_f2fs_super\n - kill_block_super\n - generic_shutdown_super\n - sync_filesystem\n : sb is readonly, skip sync_filesystem()\n - evict_inodes\n - iput\n - f2fs_evict_inode\n - f2fs_bug_on(sbi, is_inode_flag_set(inode, FI_DIRTY_INODE))\n : trigger kernel panic\r\n\r\nWhen we try to repair i_current_depth in readonly filesystem, let\u0026apos;s\nskip dirty inode to avoid panic in later f2fs_evict_inode().(CVE-2024-42297)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\next4: check dot and dotdot of dx_root before making dir indexed\r\n\r\nSyzbot reports a issue as follows:\n============================================\nBUG: unable to handle page fault for address: ffffed11022e24fe\nPGD 23ffee067 P4D 23ffee067 PUD 0\nOops: Oops: 0000 [#1] PREEMPT SMP KASAN PTI\nCPU: 0 PID: 5079 Comm: syz-executor306 Not tainted 6.10.0-rc5-g55027e689933 #0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n make_indexed_dir+0xdaf/0x13c0 fs/ext4/namei.c:2341\n ext4_add_entry+0x222a/0x25d0 fs/ext4/namei.c:2451\n ext4_rename fs/ext4/namei.c:3936 [inline]\n ext4_rename2+0x26e5/0x4370 fs/ext4/namei.c:4214\n[...]\n============================================\r\n\r\nThe immediate cause of this problem is that there is only one valid dentry\nfor the block to be split during do_split, so split==0 results in out of\nbounds accesses to the map triggering the issue.\r\n\r\n do_split\n unsigned split\n dx_make_map\n count = 1\n split = count/2 = 0;\n continued = hash2 == map[split - 1].hash;\n ---\u0026gt; map[4294967295]\r\n\r\nThe maximum length of a filename is 255 and the minimum block size is 1024,\nso it is always guaranteed that the number of entries is greater than or\nequal to 2 when do_split() is called.\r\n\r\nBut syzbot\u0026apos;s crafted image has no dot and dotdot in dir, and the dentry\ndistribution in dirblock is as follows:\r\n\r\n bus dentry1 hole dentry2 free\n|xx--|xx-------------|...............|xx-------------|...............|\n0 12 (8+248)=256 268 256 524 (8+256)=264 788 236 1024\r\n\r\nSo when renaming dentry1 increases its name_len length by 1, neither hole\nnor free is sufficient to hold the new dentry, and make_indexed_dir() is\ncalled.\r\n\r\nIn make_indexed_dir() it is assumed that the first two entries of the\ndirblock must be dot and dotdot, so bus and dentry1 are left in dx_root\nbecause they are treated as dot and dotdot, and only dentry2 is moved\nto the new leaf block. That\u0026apos;s why count is equal to 1.\r\n\r\nTherefore add the ext4_check_dx_root() helper function to add more sanity\nchecks to dot and dotdot before starting the conversion to avoid the above\nissue.(CVE-2024-42305)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: usb: qmi_wwan: fix memory leak for not ip packets\r\n\r\nFree the unused skb when not ip packets arrive.(CVE-2024-43861)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: cfg80211: handle 2x996 RU allocation in cfg80211_calculate_bitrate_he()\r\n\r\nCurrently NL80211_RATE_INFO_HE_RU_ALLOC_2x996 is not handled in\ncfg80211_calculate_bitrate_he(), leading to below warning:\r\n\r\nkernel: invalid HE MCS: bw:6, ru:6\nkernel: WARNING: CPU: 0 PID: 2312 at net/wireless/util.c:1501 cfg80211_calculate_bitrate_he+0x22b/0x270 [cfg80211]\r\n\r\nFix it by handling 2x996 RU allocation in the same way as 160 MHz bandwidth.(CVE-2024-43879)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nexec: Fix ToCToU between perm check and set-uid/gid usage\r\n\r\nWhen opening a file for exec via do_filp_open(), permission checking is\ndone against the file\u0026apos;s metadata at that moment, and on success, a file\npointer is passed back. Much later in the execve() code path, the file\nmetadata (specifically mode, uid, and gid) is used to determine if/how\nto set the uid and gid. However, those values may have changed since the\npermissions check, meaning the execution may gain unintended privileges.\r\n\r\nFor example, if a file could change permissions from executable and not\nset-id:\r\n\r\n---------x 1 root root 16048 Aug 7 13:16 target\r\n\r\nto set-id and non-executable:\r\n\r\n---S------ 1 root root 16048 Aug 7 13:16 target\r\n\r\nit is possible to gain root privileges when execution should have been\ndisallowed.\r\n\r\nWhile this race condition is rare in real-world scenarios, it has been\nobserved (and proven exploitable) when package managers are updating\nthe setuid bits of installed programs. Such files start with being\nworld-executable but then are adjusted to be group-exec with a set-uid\nbit. For example, \u0026quot;chmod o-x,u+s target\u0026quot; makes \u0026quot;target\u0026quot; executable only\nby uid \u0026quot;root\u0026quot; and gid \u0026quot;cdrom\u0026quot;, while also becoming setuid-root:\r\n\r\n-rwxr-xr-x 1 root cdrom 16048 Aug 7 13:16 target\r\n\r\nbecomes:\r\n\r\n-rwsr-xr-- 1 root cdrom 16048 Aug 7 13:16 target\r\n\r\nBut racing the chmod means users without group \u0026quot;cdrom\u0026quot; membership can\nget the permission to execute \u0026quot;target\u0026quot; just before the chmod, and when\nthe chmod finishes, the exec reaches brpm_fill_uid(), and performs the\nsetuid to root, violating the expressed authorization of \u0026quot;only cdrom\ngroup members can setuid to root\u0026quot;.\r\n\r\nRe-check that we still have execute permissions in case the metadata\nhas changed. It would be better to keep a copy from the perm-check time,\nbut until we can do that refactoring, the least-bad option is to do a\nfull inode_permission() call (under inode lock). It is understood that\nthis is safe against dead-locks, but hardly optimal.(CVE-2024-43882)",
"id": "OESA-2024-2079",
"modified": "2026-08-06T11:07:33Z",
"published": "2024-08-30T11:07:33Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2079"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48795"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48899"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48924"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48928"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48943"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-52893"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-52898"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-52900"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-39501"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-41015"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-41068"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42153"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42265"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42271"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42280"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42284"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42285"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42289"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42297"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42305"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43861"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43879"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43882"
}
],
"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-2022-48795",
"CVE-2022-48899",
"CVE-2022-48924",
"CVE-2022-48928",
"CVE-2022-48943",
"CVE-2023-52893",
"CVE-2023-52898",
"CVE-2023-52900",
"CVE-2024-39501",
"CVE-2024-41015",
"CVE-2024-41068",
"CVE-2024-42153",
"CVE-2024-42265",
"CVE-2024-42271",
"CVE-2024-42280",
"CVE-2024-42284",
"CVE-2024-42285",
"CVE-2024-42289",
"CVE-2024-42297",
"CVE-2024-42305",
"CVE-2024-43861",
"CVE-2024-43879",
"CVE-2024-43882"
]
}
OESA-2024-2080 (CVE-2021-47292)
Vulnerability from osv_openeuler – Published: 2024-08-30 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:
io_uring: fix memleak in io_init_wq_offload()
I got memory leak report when doing fuzz test:
BUG: memory leak unreferenced object 0xffff888107310a80 (size 96): comm "syz-executor.6", pid 4610, jiffies 4295140240 (age 20.135s) hex dump (first 32 bytes): 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00 .....N.......... backtrace: [<000000001974933b>] kmalloc include/linux/slab.h:591 [inline] [<000000001974933b>] kzalloc include/linux/slab.h:721 [inline] [<000000001974933b>] io_init_wq_offload fs/io_uring.c:7920 [inline] [<000000001974933b>] io_uring_alloc_task_context+0x466/0x640 fs/io_uring.c:7955 [<0000000039d0800d>] __io_uring_add_tctx_node+0x256/0x360 fs/io_uring.c:9016 [<000000008482e78c>] io_uring_add_tctx_node fs/io_uring.c:9052 [inline] [<000000008482e78c>] __do_sys_io_uring_enter fs/io_uring.c:9354 [inline] [<000000008482e78c>] __se_sys_io_uring_enter fs/io_uring.c:9301 [inline] [<000000008482e78c>] __x64_sys_io_uring_enter+0xabc/0xc20 fs/io_uring.c:9301 [<00000000b875f18f>] do_syscall_x64 arch/x86/entry/common.c:50 [inline] [<00000000b875f18f>] do_syscall_64+0x3b/0x90 arch/x86/entry/common.c:80 [<000000006b0a8484>] entry_SYSCALL_64_after_hwframe+0x44/0xae
CPU0 CPU1 io_uring_enter io_uring_enter io_uring_add_tctx_node io_uring_add_tctx_node __io_uring_add_tctx_node __io_uring_add_tctx_node io_uring_alloc_task_context io_uring_alloc_task_context io_init_wq_offload io_init_wq_offload hash = kzalloc hash = kzalloc ctx->hash_map = hash ctx->hash_map = hash <- one of the hash is leaked
When calling io_uring_enter() in parallel, the 'hash_map' will be leaked, add uring_lock to protect 'hash_map'.(CVE-2021-47292)
In the Linux kernel, the following vulnerability has been resolved:
io_uring: ensure task_work gets run as part of cancelations
If we successfully cancel a work item but that work item needs to be processed through task_work, then we can be sleeping uninterruptibly in io_uring_cancel_generic() and never process it. Hence we don't make forward progress and we end up with an uninterruptible sleep warning.
While in there, correct a comment that should be IFF, not IIF.(CVE-2021-47504)
In the Linux kernel, the following vulnerability has been resolved:
ethtool: ioctl: fix potential NULL deref in ethtool_set_coalesce()
ethtool_set_coalesce() now uses both the .get_coalesce() and .set_coalesce() callbacks. But the check for their availability is buggy, so changing the coalesce settings on a device where the driver provides only one of the callbacks results in a NULL pointer dereference instead of an -EOPNOTSUPP.
Fix the condition so that the availability of both callbacks is ensured. This also matches the netlink code.
Note that reproducing this requires some effort - it only affects the legacy ioctl path, and needs a specific combination of driver options: - have .get_coalesce() and .coalesce_supported but no .set_coalesce(), or - have .set_coalesce() but no .get_coalesce(). Here eg. ethtool doesn't cause the crash as it first attempts to call ethtool_get_coalesce() and bails out on error.(CVE-2021-47556)
In the Linux kernel, the following vulnerability has been resolved:
drm/gma500: Fix BUG: sleeping function called from invalid context errors
gma_crtc_page_flip() was holding the event_lock spinlock while calling crtc_funcs->mode_set_base() which takes ww_mutex.
The only reason to hold event_lock is to clear gma_crtc->page_flip_event on mode_set_base() errors.
Instead unlock it after setting gma_crtc->page_flip_event and on errors re-take the lock and clear gma_crtc->page_flip_event it it is still set.
This fixes the following WARN/stacktrace:
[ 512.122953] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:870 [ 512.123004] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 1253, name: gnome-shell [ 512.123031] preempt_count: 1, expected: 0 [ 512.123048] RCU nest depth: 0, expected: 0 [ 512.123066] INFO: lockdep is turned off. [ 512.123080] irq event stamp: 0 [ 512.123094] hardirqs last enabled at (0): [<0000000000000000>] 0x0 [ 512.123134] hardirqs last disabled at (0): [<ffffffff8d0ec28c>] copy_process+0x9fc/0x1de0 [ 512.123176] softirqs last enabled at (0): [<ffffffff8d0ec28c>] copy_process+0x9fc/0x1de0 [ 512.123207] softirqs last disabled at (0): [<0000000000000000>] 0x0 [ 512.123233] Preemption disabled at: [ 512.123241] [<0000000000000000>] 0x0 [ 512.123275] CPU: 3 PID: 1253 Comm: gnome-shell Tainted: G W 5.19.0+ #1 [ 512.123304] Hardware name: Packard Bell dot s/SJE01_CT, BIOS V1.10 07/23/2013 [ 512.123323] Call Trace: [ 512.123346] <TASK> [ 512.123370] dump_stack_lvl+0x5b/0x77 [ 512.123412] __might_resched.cold+0xff/0x13a [ 512.123458] ww_mutex_lock+0x1e/0xa0 [ 512.123495] psb_gem_pin+0x2c/0x150 [gma500_gfx] [ 512.123601] gma_pipe_set_base+0x76/0x240 [gma500_gfx] [ 512.123708] gma_crtc_page_flip+0x95/0x130 [gma500_gfx] [ 512.123808] drm_mode_page_flip_ioctl+0x57d/0x5d0 [ 512.123897] ? drm_mode_cursor2_ioctl+0x10/0x10 [ 512.123936] drm_ioctl_kernel+0xa1/0x150 [ 512.123984] drm_ioctl+0x21f/0x420 [ 512.124025] ? drm_mode_cursor2_ioctl+0x10/0x10 [ 512.124070] ? rcu_read_lock_bh_held+0xb/0x60 [ 512.124104] ? lock_release+0x1ef/0x2d0 [ 512.124161] __x64_sys_ioctl+0x8d/0xd0 [ 512.124203] do_syscall_64+0x58/0x80 [ 512.124239] ? do_syscall_64+0x67/0x80 [ 512.124267] ? trace_hardirqs_on_prepare+0x55/0xe0 [ 512.124300] ? do_syscall_64+0x67/0x80 [ 512.124340] ? rcu_read_lock_sched_held+0x10/0x80 [ 512.124377] entry_SYSCALL_64_after_hwframe+0x63/0xcd [ 512.124411] RIP: 0033:0x7fcc4a70740f [ 512.124442] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 [ 512.124470] RSP: 002b:00007ffda73f5390 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 512.124503] RAX: ffffffffffffffda RBX: 000055cc9e474500 RCX: 00007fcc4a70740f [ 512.124524] RDX: 00007ffda73f5420 RSI: 00000000c01864b0 RDI: 0000000000000009 [ 512.124544] RBP: 00007ffda73f5420 R08: 000055cc9c0b0cb0 R09: 0000000000000034 [ 512.124564] R10: 0000000000000000 R11: 0000000000000246 R12: 00000000c01864b0 [ 512.124584] R13: 0000000000000009 R14: 000055cc9df484d0 R15: 000055cc9af5d0c0 [ 512.124647] </TASK>(CVE-2022-48634)
In the Linux kernel, the following vulnerability has been resolved:
net: sched: fix possible refcount leak in tc_new_tfilter()
tfilter_put need to be called to put the refount got by tp->ops->get to avoid possible refcount leak when chain->tmplt_ops != NULL and chain->tmplt_ops != tp->ops.(CVE-2022-48639)
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nf_tables: fix percpu memory leak at nf_tables_addchain()
It seems to me that percpu memory for chain stats started leaking since commit 3bc158f8d0330f0a ("netfilter: nf_tables: map basechain priority to hardware priority") when nft_chain_offload_priority() returned an error.(CVE-2022-48642)
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nf_tables: fix nft_counters_enabled underflow at nf_tables_addchain()
syzbot is reporting underflow of nft_counters_enabled counter at nf_tables_addchain() [1], for commit 43eb8949cfdffa76 ("netfilter: nf_tables: do not leave chain stats enabled on error") missed that nf_tables_chain_destroy() after nft_basechain_init() in the error path of nf_tables_addchain() decrements the counter because nft_basechain_init() makes nft_is_base_chain() return true by setting NFT_CHAIN_BASE flag.
Increment the counter immediately after returning from nft_basechain_init().(CVE-2022-48643)
In the Linux kernel, the following vulnerability has been resolved:
net/sched: taprio: avoid disabling offload when it was never enabled
In an incredibly strange API design decision, qdisc->destroy() gets called even if qdisc->init() never succeeded, not exclusively since commit 87b60cfacf9f ("net_sched: fix error recovery at qdisc creation"), but apparently also earlier (in the case of qdisc_create_dflt()).
The taprio qdisc does not fully acknowledge this when it attempts full offload, because it starts off with q->flags = TAPRIO_FLAGS_INVALID in taprio_init(), then it replaces q->flags with TCA_TAPRIO_ATTR_FLAGS parsed from netlink (in taprio_change(), tail called from taprio_init()).
But in taprio_destroy(), we call taprio_disable_offload(), and this determines what to do based on FULL_OFFLOAD_IS_ENABLED(q->flags).
But looking at the implementation of FULL_OFFLOAD_IS_ENABLED() (a bitwise check of bit 1 in q->flags), it is invalid to call this macro on q->flags when it contains TAPRIO_FLAGS_INVALID, because that is set to U32_MAX, and therefore FULL_OFFLOAD_IS_ENABLED() will return true on an invalid set of flags.
As a result, it is possible to crash the kernel if user space forces an error between setting q->flags = TAPRIO_FLAGS_INVALID, and the calling of taprio_enable_offload(). This is because drivers do not expect the offload to be disabled when it was never enabled.
The error that we force here is to attach taprio as a non-root qdisc, but instead as child of an mqprio root qdisc:
$ tc qdisc add dev swp0 root handle 1: \ mqprio num_tc 8 map 0 1 2 3 4 5 6 7 \ queues 1@0 1@1 1@2 1@3 1@4 1@5 1@6 1@7 hw 0 $ tc qdisc replace dev swp0 parent 1:1 \ taprio num_tc 8 map 0 1 2 3 4 5 6 7 \ queues 1@0 1@1 1@2 1@3 1@4 1@5 1@6 1@7 base-time 0 \ sched-entry S 0x7f 990000 sched-entry S 0x80 100000 \ flags 0x0 clockid CLOCK_TAI Unable to handle kernel paging request at virtual address fffffffffffffff8 [fffffffffffffff8] pgd=0000000000000000, p4d=0000000000000000 Internal error: Oops: 96000004 [#1] PREEMPT SMP Call trace: taprio_dump+0x27c/0x310 vsc9959_port_setup_tc+0x1f4/0x460 felix_port_setup_tc+0x24/0x3c dsa_slave_setup_tc+0x54/0x27c taprio_disable_offload.isra.0+0x58/0xe0 taprio_destroy+0x80/0x104 qdisc_create+0x240/0x470 tc_modify_qdisc+0x1fc/0x6b0 rtnetlink_rcv_msg+0x12c/0x390 netlink_rcv_skb+0x5c/0x130 rtnetlink_rcv+0x1c/0x2c
Fix this by keeping track of the operations we made, and undo the offload only if we actually did it.
I've added "bool offloaded" inside a 4 byte hole between "int clockid" and "atomic64_t picos_per_byte". Now the first cache line looks like below:
$ pahole -C taprio_sched net/sched/sch_taprio.o struct taprio_sched { struct Qdisc * * qdiscs; / 0 8 / struct Qdisc * root; / 8 8 / u32 flags; / 16 4 / enum tk_offsets tk_offset; / 20 4 / int clockid; / 24 4 / bool offloaded; / 28 1 /
/* XXX 3 bytes hole, try to pack */
atomic64_t picos_per_byte; /* 32 0 */
/* XXX 8 bytes hole, try to pack */
spinlock_t current_entry_lock; /* 40 0 */
/* XXX 8 bytes hole, try to pack */
struct sched_entry * current_entry; /* 48 8 */
struct sched_gate_list * oper_sched; /* 56 8 */
/* --- cacheline 1 boundary (64 bytes) --- */(CVE-2022-48644)
In the Linux kernel, the following vulnerability has been resolved:
sfc: fix TX channel offset when using legacy interrupts
In legacy interrupt mode the tx_channel_offset was hardcoded to 1, but that's not correct if efx_sepparate_tx_channels is false. In that case, the offset is 0 because the tx queues are in the single existing channel at index 0, together with the rx queue.
Without this fix, as soon as you try to send any traffic, it tries to get the tx queues from an uninitialized channel getting these errors: WARNING: CPU: 1 PID: 0 at drivers/net/ethernet/sfc/tx.c:540 efx_hard_start_xmit+0x12e/0x170 [sfc] [...] RIP: 0010:efx_hard_start_xmit+0x12e/0x170 [sfc] [...] Call Trace: <IRQ> dev_hard_start_xmit+0xd7/0x230 sch_direct_xmit+0x9f/0x360 __dev_queue_xmit+0x890/0xa40 [...] BUG: unable to handle kernel NULL pointer dereference at 0000000000000020 [...] RIP: 0010:efx_hard_start_xmit+0x153/0x170 [sfc] [...] Call Trace: <IRQ> dev_hard_start_xmit+0xd7/0x230 sch_direct_xmit+0x9f/0x360 __dev_queue_xmit+0x890/0xa40 ...
In the Linux kernel, the following vulnerability has been resolved:
sfc: fix null pointer dereference in efx_hard_start_xmit
Trying to get the channel from the tx_queue variable here is wrong because we can only be here if tx_queue is NULL, so we shouldn't dereference it. As the above comment in the code says, this is very unlikely to happen, but it's wrong anyway so let's fix it.
I hit this issue because of a different bug that caused tx_queue to be NULL. If that happens, this is the error message that we get here: BUG: unable to handle kernel NULL pointer dereference at 0000000000000020 [...] RIP: 0010:efx_hard_start_xmit+0x153/0x170 sfc
In the Linux kernel, the following vulnerability has been resolved:
dmaengine: ti: k3-udma-private: Fix refcount leak bug in of_xudma_dev_get()
We should call of_node_put() for the reference returned by of_parse_phandle() in fail path or when it is not used anymore. Here we only need to move the of_node_put() before the check.(CVE-2022-48656)
In the Linux kernel, the following vulnerability has been resolved:
gpio: mockup: fix NULL pointer dereference when removing debugfs
We now remove the device's debugfs entries when unbinding the driver. This now causes a NULL-pointer dereference on module exit because the platform devices are unregistered after the global debugfs directory has been recursively removed. Fix it by unregistering the devices first.(CVE-2022-48663)
In the Linux kernel, the following vulnerability has been resolved:
cgroup: Add missing cpus_read_lock() to cgroup_attach_task_all()
syzbot is hitting percpu_rwsem_assert_held(&cpu_hotplug_lock) warning at cpuset_attach() [1], for commit 4f7e7236435ca0ab ("cgroup: Fix threadgroup_rwsem <-> cpus_read_lock() deadlock") missed that cpuset_attach() is also called from cgroup_attach_task_all(). Add cpus_read_lock() like what cgroup_procs_write_start() does.(CVE-2022-48671)
In the Linux kernel, the following vulnerability has been resolved:
of: fdt: fix off-by-one error in unflatten_dt_nodes()
Commit 78c44d910d3e ("drivers/of: Fix depth when unflattening devicetree") forgot to fix up the depth check in the loop body in unflatten_dt_nodes() which makes it possible to overflow the nps[] buffer...
Found by Linux Verification Center (linuxtesting.org) with the SVACE static analysis tool.(CVE-2022-48672)
In the Linux kernel, the following vulnerability has been resolved:
IB/core: Fix a nested dead lock as part of ODP flow
Fix a nested dead lock as part of ODP flow by using mmput_async().
From the below call trace [1] can see that calling mmput() once we have the umem_odp->umem_mutex locked as required by ib_umem_odp_map_dma_and_lock() might trigger in the same task the exit_mmap()->__mmu_notifier_release()->mlx5_ib_invalidate_range() which may dead lock when trying to lock the same mutex.
Moving to use mmput_async() will solve the problem as the above exit_mmap() flow will be called in other task and will be executed once the lock will be available.
[1] [64843.077665] task:kworker/u133:2 state:D stack: 0 pid:80906 ppid: 2 flags:0x00004000 [64843.077672] Workqueue: mlx5_ib_page_fault mlx5_ib_eqe_pf_action [mlx5_ib] [64843.077719] Call Trace: [64843.077722] <TASK> [64843.077724] __schedule+0x23d/0x590 [64843.077729] schedule+0x4e/0xb0 [64843.077735] schedule_preempt_disabled+0xe/0x10 [64843.077740] __mutex_lock.constprop.0+0x263/0x490 [64843.077747] __mutex_lock_slowpath+0x13/0x20 [64843.077752] mutex_lock+0x34/0x40 [64843.077758] mlx5_ib_invalidate_range+0x48/0x270 [mlx5_ib] [64843.077808] __mmu_notifier_release+0x1a4/0x200 [64843.077816] exit_mmap+0x1bc/0x200 [64843.077822] ? walk_page_range+0x9c/0x120 [64843.077828] ? __cond_resched+0x1a/0x50 [64843.077833] ? mutex_lock+0x13/0x40 [64843.077839] ? uprobe_clear_state+0xac/0x120 [64843.077860] mmput+0x5f/0x140 [64843.077867] ib_umem_odp_map_dma_and_lock+0x21b/0x580 [ib_core] [64843.077931] pagefault_real_mr+0x9a/0x140 [mlx5_ib] [64843.077962] pagefault_mr+0xb4/0x550 [mlx5_ib] [64843.077992] pagefault_single_data_segment.constprop.0+0x2ac/0x560 [mlx5_ib] [64843.078022] mlx5_ib_eqe_pf_action+0x528/0x780 [mlx5_ib] [64843.078051] process_one_work+0x22b/0x3d0 [64843.078059] worker_thread+0x53/0x410 [64843.078065] ? process_one_work+0x3d0/0x3d0 [64843.078073] kthread+0x12a/0x150 [64843.078079] ? set_kthread_struct+0x50/0x50 [64843.078085] ret_from_fork+0x22/0x30 [64843.078093] </TASK>(CVE-2022-48675)
In the Linux kernel, the following vulnerability has been resolved:
nvme-tcp: fix UAF when detecting digest errors
We should also bail from the io_work loop when we set rd_enabled to true, so we don't attempt to read data from the socket when the TCP stream is already out-of-sync or corrupted.(CVE-2022-48686)
In the Linux kernel, the following vulnerability has been resolved:
ipv6: sr: fix out-of-bounds read when setting HMAC data.
The SRv6 layer allows defining HMAC data that can later be used to sign IPv6 Segment Routing Headers. This configuration is realised via netlink through four attributes: SEG6_ATTR_HMACKEYID, SEG6_ATTR_SECRET, SEG6_ATTR_SECRETLEN and SEG6_ATTR_ALGID. Because the SECRETLEN attribute is decoupled from the actual length of the SECRET attribute, it is possible to provide invalid combinations (e.g., secret = "", secretlen = 64). This case is not checked in the code and with an appropriately crafted netlink message, an out-of-bounds read of up to 64 bytes (max secret length) can occur past the skb end pointer and into skb_shared_info:
Breakpoint 1, seg6_genl_sethmac (skb=<optimized out>, info=<optimized out>) at net/ipv6/seg6.c:208 208 memcpy(hinfo->secret, secret, slen); (gdb) bt #0 seg6_genl_sethmac (skb=<optimized out>, info=<optimized out>) at net/ipv6/seg6.c:208 #1 0xffffffff81e012e9 in genl_family_rcv_msg_doit (skb=skb@entry=0xffff88800b1f9f00, nlh=nlh@entry=0xffff88800b1b7600, extack=extack@entry=0xffffc90000ba7af0, ops=ops@entry=0xffffc90000ba7a80, hdrlen=4, net=0xffffffff84237580 <init_net>, family=<optimized out>, family=<optimized out>) at net/netlink/genetlink.c:731 #2 0xffffffff81e01435 in genl_family_rcv_msg (extack=0xffffc90000ba7af0, nlh=0xffff88800b1b7600, skb=0xffff88800b1f9f00, family=0xffffffff82fef6c0 <seg6_genl_family>) at net/netlink/genetlink.c:775 #3 genl_rcv_msg (skb=0xffff88800b1f9f00, nlh=0xffff88800b1b7600, extack=0xffffc90000ba7af0) at net/netlink/genetlink.c:792 #4 0xffffffff81dfffc3 in netlink_rcv_skb (skb=skb@entry=0xffff88800b1f9f00, cb=cb@entry=0xffffffff81e01350 <genl_rcv_msg>) at net/netlink/af_netlink.c:2501 #5 0xffffffff81e00919 in genl_rcv (skb=0xffff88800b1f9f00) at net/netlink/genetlink.c:803 #6 0xffffffff81dff6ae in netlink_unicast_kernel (ssk=0xffff888010eec800, skb=0xffff88800b1f9f00, sk=0xffff888004aed000) at net/netlink/af_netlink.c:1319 #7 netlink_unicast (ssk=ssk@entry=0xffff888010eec800, skb=skb@entry=0xffff88800b1f9f00, portid=portid@entry=0, nonblock=<optimized out>) at net/netlink/af_netlink.c:1345 #8 0xffffffff81dff9a4 in netlink_sendmsg (sock=<optimized out>, msg=0xffffc90000ba7e48, len=<optimized out>) at net/netlink/af_netlink.c:1921 ... (gdb) p/x ((struct sk_buff )0xffff88800b1f9f00)->head + ((struct sk_buff )0xffff88800b1f9f00)->end $1 = 0xffff88800b1b76c0 (gdb) p/x secret $2 = 0xffff88800b1b76c0 (gdb) p slen $3 = 64 '@'
The OOB data can then be read back from userspace by dumping HMAC state. This commit fixes this by ensuring SECRETLEN cannot exceed the actual length of SECRET.(CVE-2022-48687)
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nf_tables: clean up hook list when offload flags check fails
splice back the hook list so nft_chain_release_hook() has a chance to release the hooks.
BUG: memory leak unreferenced object 0xffff88810180b100 (size 96): comm "syz-executor133", pid 3619, jiffies 4294945714 (age 12.690s) hex dump (first 32 bytes): 28 64 23 02 81 88 ff ff 28 64 23 02 81 88 ff ff (d#.....(d#..... 90 a8 aa 83 ff ff ff ff 00 00 b5 0f 81 88 ff ff ................ backtrace: [<ffffffff83a8c59b>] kmalloc include/linux/slab.h:600 [inline] [<ffffffff83a8c59b>] nft_netdev_hook_alloc+0x3b/0xc0 net/netfilter/nf_tables_api.c:1901 [<ffffffff83a9239a>] nft_chain_parse_netdev net/netfilter/nf_tables_api.c:1998 [inline] [<ffffffff83a9239a>] nft_chain_parse_hook+0x33a/0x530 net/netfilter/nf_tables_api.c:2073 [<ffffffff83a9b14b>] nf_tables_addchain.constprop.0+0x10b/0x950 net/netfilter/nf_tables_api.c:2218 [<ffffffff83a9c41b>] nf_tables_newchain+0xa8b/0xc60 net/netfilter/nf_tables_api.c:2593 [<ffffffff83a3d6a6>] nfnetlink_rcv_batch+0xa46/0xd20 net/netfilter/nfnetlink.c:517 [<ffffffff83a3db79>] nfnetlink_rcv_skb_batch net/netfilter/nfnetlink.c:638 [inline] [<ffffffff83a3db79>] nfnetlink_rcv+0x1f9/0x220 net/netfilter/nfnetlink.c:656 [<ffffffff83a13b17>] netlink_unicast_kernel net/netlink/af_netlink.c:1319 [inline] [<ffffffff83a13b17>] netlink_unicast+0x397/0x4c0 net/netlink/af_netlink.c:1345 [<ffffffff83a13fd6>] netlink_sendmsg+0x396/0x710 net/netlink/af_netlink.c:1921 [<ffffffff83865ab6>] sock_sendmsg_nosec net/socket.c:714 [inline] [<ffffffff83865ab6>] sock_sendmsg+0x56/0x80 net/socket.c:734 [<ffffffff8386601c>] _syssendmsg+0x36c/0x390 net/socket.c:2482 [<ffffffff8386a918>] _sys_sendmsg+0xa8/0x110 net/socket.c:2536 [<ffffffff8386aaa8>] __sys_sendmsg+0x88/0x100 net/socket.c:2565 [<ffffffff845e5955>] do_syscall_x64 arch/x86/entry/common.c:50 [inline] [<ffffffff845e5955>] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 [<ffffffff84800087>] entry_SYSCALL_64_after_hwframe+0x63/0xcd(CVE-2022-48691)
In the Linux kernel, the following vulnerability has been resolved:
misc: fastrpc: Don't remove map on creater_process and device_release
Do not remove the map from the list on error path in fastrpc_init_create_process, instead call fastrpc_map_put, to avoid use-after-free. Do not remove it on fastrpc_device_release either, call fastrpc_map_put instead.
The fastrpc_free_map is the only proper place to remove the map. This is called only after the reference count is 0.(CVE-2022-48873)
In the Linux kernel, the following vulnerability has been resolved:
ixgbe: fix pci device refcount leak
As the comment of pci_get_domain_bus_and_slot() says, it returns a PCI device with refcount incremented, when finish using it, the caller must decrement the reference count by calling pci_dev_put().
In ixgbe_get_first_secondary_devfn() and ixgbe_x550em_a_has_mii(), pci_dev_put() is called to avoid leak.(CVE-2022-48896)
In the Linux kernel, the following vulnerability has been resolved:
drm/msm/dp: do not complete dp_aux_cmd_fifo_tx() if irq is not for aux transfer
There are 3 possible interrupt sources are handled by DP controller, HPDstatus, Controller state changes and Aux read/write transaction. At every irq, DP controller have to check isr status of every interrupt sources and service the interrupt if its isr status bits shows interrupts are pending. There is potential race condition may happen at current aux isr handler implementation since it is always complete dp_aux_cmd_fifo_tx() even irq is not for aux read or write transaction. This may cause aux read transaction return premature if host aux data read is in the middle of waiting for sink to complete transferring data to host while irq happen. This will cause host's receiving buffer contains unexpected data. This patch fixes this problem by checking aux isr and return immediately at aux isr handler if there are no any isr status bits set.
Current there is a bug report regrading eDP edid corruption happen during system booting up. After lengthy debugging to found that VIDEO_READY interrupt was continuously firing during system booting up which cause dp_aux_isr() to complete dp_aux_cmd_fifo_tx() prematurely to retrieve data from aux hardware buffer which is not yet contains complete data transfer from sink. This cause edid corruption.
Follows are the signature at kernel logs when problem happen, EDID has corrupt header panel-simple-dp-aux aux-aea0000.edp: Couldn't identify panel via EDID
Changes in v2: -- do complete if (ret == IRQ_HANDLED) ay dp-aux_isr() -- add more commit text
Changes in v3: -- add Stephen suggested -- dp_aux_isr() return IRQ_XXX back to caller -- dp_ctrl_isr() return IRQ_XXX back to caller
Changes in v4: -- split into two patches
Changes in v5: -- delete empty line between tags
Changes in v6: -- remove extra "that" and fixed line more than 75 char at commit text
Patchwork: https://patchwork.freedesktop.org/patch/516121/(CVE-2022-48898)
In the Linux kernel, the following vulnerability has been resolved:
drm/virtio: Fix GEM handle creation UAF
Userspace can guess the handle value and try to race GEM object creation with handle close, resulting in a use-after-free if we dereference the object after dropping the handle's reference. For that reason, dropping the handle's reference must be done after we are done dereferencing the object.(CVE-2022-48899)
In the Linux kernel, the following vulnerability has been resolved:
btrfs: get rid of warning on transaction commit when using flushoncommit
When using the flushoncommit mount option, during almost every transaction commit we trigger a warning from __writeback_inodes_sb_nr():
$ cat fs/fs-writeback.c: (...) static void __writeback_inodes_sb_nr(struct super_block *sb, ... { (...) WARN_ON(!rwsem_is_locked(&sb->s_umount)); (...) } (...)
The trace produced in dmesg looks like the following:
[947.473890] WARNING: CPU: 5 PID: 930 at fs/fs-writeback.c:2610 __writeback_inodes_sb_nr+0x7e/0xb3 [947.481623] Modules linked in: nfsd nls_cp437 cifs asn1_decoder cifs_arc4 fscache cifs_md4 ipmi_ssif [947.489571] CPU: 5 PID: 930 Comm: btrfs-transacti Not tainted 95.16.3-srb-asrock-00001-g36437ad63879 #186 [947.497969] RIP: 0010:__writeback_inodes_sb_nr+0x7e/0xb3 [947.502097] Code: 24 10 4c 89 44 24 18 c6 (...) [947.519760] RSP: 0018:ffffc90000777e10 EFLAGS: 00010246 [947.523818] RAX: 0000000000000000 RBX: 0000000000963300 RCX: 0000000000000000 [947.529765] RDX: 0000000000000000 RSI: 000000000000fa51 RDI: ffffc90000777e50 [947.535740] RBP: ffff888101628a90 R08: ffff888100955800 R09: ffff888100956000 [947.541701] R10: 0000000000000002 R11: 0000000000000001 R12: ffff888100963488 [947.547645] R13: ffff888100963000 R14: ffff888112fb7200 R15: ffff888100963460 [947.553621] FS: 0000000000000000(0000) GS:ffff88841fd40000(0000) knlGS:0000000000000000 [947.560537] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [947.565122] CR2: 0000000008be50c4 CR3: 000000000220c000 CR4: 00000000001006e0 [947.571072] Call Trace: [947.572354] <TASK> [947.573266] btrfs_commit_transaction+0x1f1/0x998 [947.576785] ? start_transaction+0x3ab/0x44e [947.579867] ? schedule_timeout+0x8a/0xdd [947.582716] transaction_kthread+0xe9/0x156 [947.585721] ? btrfs_cleanup_transaction.isra.0+0x407/0x407 [947.590104] kthread+0x131/0x139 [947.592168] ? set_kthread_struct+0x32/0x32 [947.595174] ret_from_fork+0x22/0x30 [947.597561] </TASK> [947.598553] ---[ end trace 644721052755541c ]---
This is because we started using writeback_inodes_sb() to flush delalloc when committing a transaction (when using -o flushoncommit), in order to avoid deadlocks with filesystem freeze operations. This change was made by commit ce8ea7cc6eb313 ("btrfs: don't call btrfs_start_delalloc_roots in flushoncommit"). After that change we started producing that warning, and every now and then a user reports this since the warning happens too often, it spams dmesg/syslog, and a user is unsure if this reflects any problem that might compromise the filesystem's reliability.
We can not just lock the sb->s_umount semaphore before calling writeback_inodes_sb(), because that would at least deadlock with filesystem freezing, since at fs/super.c:freeze_super() sync_filesystem() is called while we are holding that semaphore in write mode, and that can trigger a transaction commit, resulting in a deadlock. It would also trigger the same type of deadlock in the unmount path. Possibly, it could also introduce some other locking dependencies that lockdep would report.
To fix this call try_to_writeback_inodes_sb() instead of writeback_inodes_sb(), because that will try to read lock sb->s_umount and then will only call writeback_inodes_sb() if it was able to lock it. This is fine because the cases where it can't read lock sb->s_umount are during a filesystem unmount or during a filesystem freeze - in those cases sb->s_umount is write locked and sync_filesystem() is called, which calls writeback_inodes_sb(). In other words, in all cases where we can't take a read lock on sb->s_umount, writeback is already being triggered elsewhere.
An alternative would be to call btrfs_start_delalloc_roots() with a number of pages different from LONG_MAX, for example matching the number of delalloc bytes we currently have, in ---truncated---(CVE-2022-48920)
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nf_tables: unregister flowtable hooks on netns exit
Unregister flowtable hooks before they are releases via nf_tables_flowtable_destroy() otherwise hook core reports UAF.
BUG: KASAN: use-after-free in nf_hook_entries_grow+0x5a7/0x700 net/netfilter/core.c:142 net/netfilter/core.c:142 Read of size 4 at addr ffff8880736f7438 by task syz-executor579/3666
CPU: 0 PID: 3666 Comm: syz-executor579 Not tainted 5.16.0-rc5-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] __dump_stack lib/dump_stack.c:88 [inline] lib/dump_stack.c:106 dump_stack_lvl+0x1dc/0x2d8 lib/dump_stack.c:106 lib/dump_stack.c:106 print_address_description+0x65/0x380 mm/kasan/report.c:247 mm/kasan/report.c:247 __kasan_report mm/kasan/report.c:433 [inline] __kasan_report mm/kasan/report.c:433 [inline] mm/kasan/report.c:450 kasan_report+0x19a/0x1f0 mm/kasan/report.c:450 mm/kasan/report.c:450 nf_hook_entries_grow+0x5a7/0x700 net/netfilter/core.c:142 net/netfilter/core.c:142 __nf_register_net_hook+0x27e/0x8d0 net/netfilter/core.c:429 net/netfilter/core.c:429 nf_register_net_hook+0xaa/0x180 net/netfilter/core.c:571 net/netfilter/core.c:571 nft_register_flowtable_net_hooks+0x3c5/0x730 net/netfilter/nf_tables_api.c:7232 net/netfilter/nf_tables_api.c:7232 nf_tables_newflowtable+0x2022/0x2cf0 net/netfilter/nf_tables_api.c:7430 net/netfilter/nf_tables_api.c:7430 nfnetlink_rcv_batch net/netfilter/nfnetlink.c:513 [inline] nfnetlink_rcv_skb_batch net/netfilter/nfnetlink.c:634 [inline] nfnetlink_rcv_batch net/netfilter/nfnetlink.c:513 [inline] net/netfilter/nfnetlink.c:652 nfnetlink_rcv_skb_batch net/netfilter/nfnetlink.c:634 [inline] net/netfilter/nfnetlink.c:652 nfnetlink_rcv+0x10e6/0x2550 net/netfilter/nfnetlink.c:652 net/netfilter/nfnetlink.c:652
__nft_release_hook() calls nft_unregister_flowtable_net_hooks() which only unregisters the hooks, then after RCU grace period, it is guaranteed that no packets add new entries to the flowtable (no flow offload rules and flowtable hooks are reachable from packet path), so it is safe to call nf_flow_table_free() which cleans up the remaining entries from the flowtable (both software and hardware) and it unbinds the flow_block.(CVE-2022-48935)
In the Linux kernel, the following vulnerability has been resolved:
gsmi: fix null-deref in gsmi_get_variable
We can get EFI variables without fetching the attribute, so we must allow for that in gsmi.
commit 859748255b43 ("efi: pstore: Omit efivars caching EFI varstore access layer") added a new get_variable call with attr=NULL, which triggers panic in gsmi.(CVE-2023-52893)
In the Linux kernel, the following vulnerability has been resolved:
xhci: Fix null pointer dereference when host dies
Make sure xhci_free_dev() and xhci_kill_endpoint_urbs() do not race and cause null pointer dereference when host suddenly dies.
Usb core may call xhci_free_dev() which frees the xhci->devs[slot_id] virt device at the same time that xhci_kill_endpoint_urbs() tries to loop through all the device's endpoints, checking if there are any cancelled urbs left to give back.
hold the xhci spinlock while freeing the virt device(CVE-2023-52898)
In the Linux kernel, the following vulnerability has been resolved:
usb: xhci: Check endpoint is valid before dereferencing it
When the host controller is not responding, all URBs queued to all endpoints need to be killed. This can cause a kernel panic if we dereference an invalid endpoint.
Fix this by using xhci_get_virt_ep() helper to find the endpoint and checking if the endpoint is valid before dereferencing it.
[233311.853271] xhci-hcd xhci-hcd.1.auto: xHCI host controller not responding, assume dead [233311.853393] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000e8
[233311.853964] pc : xhci_hc_died+0x10c/0x270 [233311.853971] lr : xhci_hc_died+0x1ac/0x270
[233311.854077] Call trace: [233311.854085] xhci_hc_died+0x10c/0x270 [233311.854093] xhci_stop_endpoint_command_watchdog+0x100/0x1a4 [233311.854105] call_timer_fn+0x50/0x2d4 [233311.854112] expire_timers+0xac/0x2e4 [233311.854118] run_timer_softirq+0x300/0xabc [233311.854127] __do_softirq+0x148/0x528 [233311.854135] irq_exit+0x194/0x1a8 [233311.854143] __handle_domain_irq+0x164/0x1d0 [233311.854149] gic_handle_irq.22273+0x10c/0x188 [233311.854156] el1_irq+0xfc/0x1a8 [233311.854175] lpm_cpuidle_enter+0x25c/0x418 [msm_pm] [233311.854185] cpuidle_enter_state+0x1f0/0x764 [233311.854194] do_idle+0x594/0x6ac [233311.854201] cpu_startup_entry+0x7c/0x80 [233311.854209] secondary_start_kernel+0x170/0x198(CVE-2023-52901)
In the Linux kernel, the following vulnerability has been resolved:
io_uring: lock overflowing for IOPOLL
syzbot reports an issue with overflow filling for IOPOLL:
WARNING: CPU: 0 PID: 28 at io_uring/io_uring.c:734 io_cqring_event_overflow+0x1c0/0x230 io_uring/io_uring.c:734 CPU: 0 PID: 28 Comm: kworker/u4:1 Not tainted 6.2.0-rc3-syzkaller-16369-g358a161a6a9e #0 Workqueue: events_unbound io_ring_exit_work Call trace: io_cqring_event_overflow+0x1c0/0x230 io_uring/io_uring.c:734 io_req_cqe_overflow+0x5c/0x70 io_uring/io_uring.c:773 io_fill_cqe_req io_uring/io_uring.h:168 [inline] io_do_iopoll+0x474/0x62c io_uring/rw.c:1065 io_iopoll_try_reap_events+0x6c/0x108 io_uring/io_uring.c:1513 io_uring_try_cancel_requests+0x13c/0x258 io_uring/io_uring.c:3056 io_ring_exit_work+0xec/0x390 io_uring/io_uring.c:2869 process_one_work+0x2d8/0x504 kernel/workqueue.c:2289 worker_thread+0x340/0x610 kernel/workqueue.c:2436 kthread+0x12c/0x158 kernel/kthread.c:376 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:863
There is no real problem for normal IOPOLL as flush is also called with uring_lock taken, but it's getting more complicated for IOPOLL|SQPOLL, for which __io_cqring_overflow_flush() happens from the CQ waiting path.(CVE-2023-52903)
A race condition was found in the Linux kernel's drm/exynos device driver in exynos_drm_crtc_atomic_disable() function. This can result in a null pointer dereference issue, possibly leading to a kernel panic or denial of service issue.
(CVE-2024-22386)
In the Linux kernel, the following vulnerability has been resolved:
phonet: fix rtm_phonet_notify() skb allocation
fill_route() stores three components in the skb:
- struct rtmsg
- RTA_DST (u8)
- RTA_OIF (u32)
Therefore, rtm_phonet_notify() should use
NLMSG_ALIGN(sizeof(struct rtmsg)) + nla_total_size(1) + nla_total_size(4)(CVE-2024-36946)
In the Linux kernel, the following vulnerability has been resolved:
m68k: Fix spinlock race in kernel thread creation
Context switching does take care to retain the correct lock owner across the switch from 'prev' to 'next' tasks. This does rely on interrupts remaining disabled for the entire duration of the switch.
This condition is guaranteed for normal process creation and context switching between already running processes, because both 'prev' and 'next' already have interrupts disabled in their saved copies of the status register.
The situation is different for newly created kernel threads. The status register is set to PS_S in copy_thread(), which does leave the IPL at 0. Upon restoring the 'next' thread's status register in switch_to() aka resume(), interrupts then become enabled prematurely. resume() then returns via ret_from_kernel_thread() and schedule_tail() where run queue lock is released (see finish_task_switch() and finish_lock_switch()).
A timer interrupt calling scheduler_tick() before the lock is released in finish_task_switch() will find the lock already taken, with the current task as lock owner. This causes a spinlock recursion warning as reported by Guenter Roeck.
As far as I can ascertain, this race has been opened in commit 533e6903bea0 ("m68k: split ret_from_fork(), simplify kernel_thread()") but I haven't done a detailed study of kernel history so it may well predate that commit.
Interrupts cannot be disabled in the saved status register copy for kernel threads (init will complain about interrupts disabled when finally starting user space). Disable interrupts temporarily when switching the tasks' register sets in resume().
Note that a simple oriw 0x700,%sr after restoring sr is not enough here - this leaves enough of a race for the 'spinlock recursion' warning to still be observed.
Tested on ARAnyM and qemu (Quadra 800 emulation).(CVE-2024-38613)
In the Linux kernel, the following vulnerability has been resolved:
ipv6: sr: fix missing sk_buff release in seg6_input_core
The seg6_input() function is responsible for adding the SRH into a packet, delegating the operation to the seg6_input_core(). This function uses the skb_cow_head() to ensure that there is sufficient headroom in the sk_buff for accommodating the link-layer header. In the event that the skb_cow_header() function fails, the seg6_input_core() catches the error but it does not release the sk_buff, which will result in a memory leak.
This issue was introduced in commit af3b5158b89d ("ipv6: sr: fix BUG due to headroom too small after SRH push") and persists even after commit 7a3f5b0de364 ("netfilter: add netfilter hooks to SRv6 data plane"), where the entire seg6_input() code was refactored to deal with netfilter hooks.
The proposed patch addresses the identified memory leak by requiring the seg6_input_core() function to release the sk_buff in the event that skb_cow_head() fails.(CVE-2024-39490)
In the Linux kernel, the following vulnerability has been resolved:
crypto: hisilicon/sec - Fix memory leak for sec resource release
The AIV is one of the SEC resources. When releasing resources, it need to release the AIV resources at the same time. Otherwise, memory leakage occurs.
The aiv resource release is added to the sec resource release function.(CVE-2024-41002)
In the Linux kernel, the following vulnerability has been resolved:
s390/sclp: Fix sclp_init() cleanup on failure
If sclp_init() fails it only partially cleans up: if there are multiple failing calls to sclp_init() sclp_state_change_event will be added several times to sclp_reg_list, which results in the following warning:
------------[ cut here ]------------ list_add double add: new=000003ffe1598c10, prev=000003ffe1598bf0, next=000003ffe1598c10. WARNING: CPU: 0 PID: 1 at lib/list_debug.c:35 __list_add_valid_or_report+0xde/0xf8 CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.10.0-rc3 Krnl PSW : 0404c00180000000 000003ffe0d6076a (__list_add_valid_or_report+0xe2/0xf8) R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 ... Call Trace: [<000003ffe0d6076a>] __list_add_valid_or_report+0xe2/0xf8 ([<000003ffe0d60766>] __list_add_valid_or_report+0xde/0xf8) [<000003ffe0a8d37e>] sclp_init+0x40e/0x450 [<000003ffe00009f2>] do_one_initcall+0x42/0x1e0 [<000003ffe15b77a6>] do_initcalls+0x126/0x150 [<000003ffe15b7a0a>] kernel_init_freeable+0x1ba/0x1f8 [<000003ffe0d6650e>] kernel_init+0x2e/0x180 [<000003ffe000301c>] __ret_from_fork+0x3c/0x60 [<000003ffe0d759ca>] ret_from_fork+0xa/0x30
Fix this by removing sclp_state_change_event from sclp_reg_list when sclp_init() fails.(CVE-2024-41068)
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Check pipe offset before setting vblank
pipe_ctx has a size of MAX_PIPES so checking its index before accessing the array.
This fixes an OVERRUN issue reported by Coverity.(CVE-2024-42120)
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Add NULL pointer check for kzalloc
[Why & How] Check return pointer of kzalloc before using it.(CVE-2024-42122)
In the Linux kernel, the following vulnerability has been resolved:
protect the fetch of ->fd[fd] in do_dup2() from mispredictions
both callers have verified that fd is not greater than ->max_fds; however, misprediction might end up with tofree = fdt->fd[fd]; being speculatively executed. That's wrong for the same reasons why it's wrong in close_fd()/file_close_fd_locked(); the same solution applies - array_index_nospec(fd, fdt->max_fds) could differ from fd only in case of speculative execution on mispredicted path.(CVE-2024-42265)
In the Linux kernel, the following vulnerability has been resolved:
net/iucv: fix use after free in iucv_sock_close()
iucv_sever_path() is called from process context and from bh context. iucv->path is used as indicator whether somebody else is taking care of severing the path (or it is already removed / never existed). This needs to be done with atomic compare and swap, otherwise there is a small window where iucv_sock_close() will try to work with a path that has already been severed and freed by iucv_callback_connrej() called by iucv_tasklet_fn().
Example: [452744.123844] Call Trace: [452744.123845] ([<0000001e87f03880>] 0x1e87f03880) [452744.123966] [<00000000d593001e>] iucv_path_sever+0x96/0x138 [452744.124330] [<000003ff801ddbca>] iucv_sever_path+0xc2/0xd0 [af_iucv] [452744.124336] [<000003ff801e01b6>] iucv_sock_close+0xa6/0x310 [af_iucv] [452744.124341] [<000003ff801e08cc>] iucv_sock_release+0x3c/0xd0 [af_iucv] [452744.124345] [<00000000d574794e>] __sock_release+0x5e/0xe8 [452744.124815] [<00000000d5747a0c>] sock_close+0x34/0x48 [452744.124820] [<00000000d5421642>] __fput+0xba/0x268 [452744.124826] [<00000000d51b382c>] task_work_run+0xbc/0xf0 [452744.124832] [<00000000d5145710>] do_notify_resume+0x88/0x90 [452744.124841] [<00000000d5978096>] system_call+0xe2/0x2c8 [452744.125319] Last Breaking-Event-Address: [452744.125321] [<00000000d5930018>] iucv_path_sever+0x90/0x138 [452744.125324] [452744.125325] Kernel panic - not syncing: Fatal exception in interrupt
Note that bh_lock_sock() is not serializing the tasklet context against process context, because the check for sock_owned_by_user() and corresponding handling is missing.
Ideas for a future clean-up patch: A) Correct usage of bh_lock_sock() in tasklet context, as described in Re-enqueue, if needed. This may require adding return values to the tasklet functions and thus changes to all users of iucv.
B) Change iucv tasklet into worker and use only lock_sock() in af_iucv.(CVE-2024-42271)
In the Linux kernel, the following vulnerability has been resolved:
mISDN: Fix a use after free in hfcmulti_tx()
Don't dereference sp after calling dev_kfree_skb(sp).(CVE-2024-42280)
In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix a segment issue when downgrading gso_size
Linearize the skb when downgrading gso_size because it may trigger a BUG_ON() later when the skb is segmented as described in [1,2].(CVE-2024-42281)
In the Linux kernel, the following vulnerability has been resolved:
tipc: Return non-zero value from tipc_udp_addr2str() on error
tipc_udp_addr2str() should return non-zero value if the UDP media address is invalid. Otherwise, a buffer overflow access can occur in tipc_media_addr_printf(). Fix this by returning 1 on an invalid UDP media address.(CVE-2024-42284)
In the Linux kernel, the following vulnerability has been resolved:
RDMA/iwcm: Fix a use-after-free related to destroying CM IDs
iw_conn_req_handler() associates a new struct rdma_id_private (conn_id) with an existing struct iw_cm_id (cm_id) as follows:
conn_id->cm_id.iw = cm_id;
cm_id->context = conn_id;
cm_id->cm_handler = cma_iw_handler;
rdma_destroy_id() frees both the cm_id and the struct rdma_id_private. Make sure that cm_work_handler() does not trigger a use-after-free by only freeing of the struct rdma_id_private after all pending work has finished.(CVE-2024-42285)
In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix to don't dirty inode for readonly filesystem
syzbot reports f2fs bug as below:
kernel BUG at fs/f2fs/inode.c:933! RIP: 0010:f2fs_evict_inode+0x1576/0x1590 fs/f2fs/inode.c:933 Call Trace: evict+0x2a4/0x620 fs/inode.c:664 dispose_list fs/inode.c:697 [inline] evict_inodes+0x5f8/0x690 fs/inode.c:747 generic_shutdown_super+0x9d/0x2c0 fs/super.c:675 kill_block_super+0x44/0x90 fs/super.c:1667 kill_f2fs_super+0x303/0x3b0 fs/f2fs/super.c:4894 deactivate_locked_super+0xc1/0x130 fs/super.c:484 cleanup_mnt+0x426/0x4c0 fs/namespace.c:1256 task_work_run+0x24a/0x300 kernel/task_work.c:180 ptrace_notify+0x2cd/0x380 kernel/signal.c:2399 ptrace_report_syscall include/linux/ptrace.h:411 [inline] ptrace_report_syscall_exit include/linux/ptrace.h:473 [inline] syscall_exit_work kernel/entry/common.c:251 [inline] syscall_exit_to_user_mode_prepare kernel/entry/common.c:278 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline] syscall_exit_to_user_mode+0x15c/0x280 kernel/entry/common.c:296 do_syscall_64+0x50/0x110 arch/x86/entry/common.c:88 entry_SYSCALL_64_after_hwframe+0x63/0x6b
The root cause is: - do_sys_open - f2fs_lookup - __f2fs_find_entry - f2fs_i_depth_write - f2fs_mark_inode_dirty_sync - f2fs_dirty_inode - set_inode_flag(inode, FI_DIRTY_INODE)
- umount
- kill_f2fs_super
- kill_block_super
- generic_shutdown_super
- sync_filesystem : sb is readonly, skip sync_filesystem()
- evict_inodes
- iput
- f2fs_evict_inode
- f2fs_bug_on(sbi, is_inode_flag_set(inode, FI_DIRTY_INODE)) : trigger kernel panic
When we try to repair i_current_depth in readonly filesystem, let's skip dirty inode to avoid panic in later f2fs_evict_inode().(CVE-2024-42297)
In the Linux kernel, the following vulnerability has been resolved:
ext4: check dot and dotdot of dx_root before making dir indexed
Syzbot reports a issue as follows:
BUG: unable to handle page fault for address: ffffed11022e24fe PGD 23ffee067 P4D 23ffee067 PUD 0 Oops: Oops: 0000 [#1] PREEMPT SMP KASAN PTI CPU: 0 PID: 5079 Comm: syz-executor306 Not tainted 6.10.0-rc5-g55027e689933 #0 Call Trace: <TASK> make_indexed_dir+0xdaf/0x13c0 fs/ext4/namei.c:2341 ext4_add_entry+0x222a/0x25d0 fs/ext4/namei.c:2451 ext4_rename fs/ext4/namei.c:3936 [inline] ext4_rename2+0x26e5/0x4370 fs/ext4/namei.c:4214 [...] ============================================
The immediate cause of this problem is that there is only one valid dentry for the block to be split during do_split, so split==0 results in out of bounds accesses to the map triggering the issue.
do_split
unsigned split
dx_make_map
count = 1
split = count/2 = 0;
continued = hash2 == map[split - 1].hash;
---> map[4294967295]
The maximum length of a filename is 255 and the minimum block size is 1024, so it is always guaranteed that the number of entries is greater than or equal to 2 when do_split() is called.
But syzbot's crafted image has no dot and dotdot in dir, and the dentry distribution in dirblock is as follows:
bus dentry1 hole dentry2 free |xx--|xx-------------|...............|xx-------------|...............| 0 12 (8+248)=256 268 256 524 (8+256)=264 788 236 1024
So when renaming dentry1 increases its name_len length by 1, neither hole nor free is sufficient to hold the new dentry, and make_indexed_dir() is called.
In make_indexed_dir() it is assumed that the first two entries of the dirblock must be dot and dotdot, so bus and dentry1 are left in dx_root because they are treated as dot and dotdot, and only dentry2 is moved to the new leaf block. That's why count is equal to 1.
Therefore add the ext4_check_dx_root() helper function to add more sanity checks to dot and dotdot before starting the conversion to avoid the above issue.(CVE-2024-42305)
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Check for NULL pointer
[why & how] Need to make sure plane_state is initialized before accessing its members.
(cherry picked from commit 295d91cbc700651782a60572f83c24861607b648)(CVE-2024-42308)
In the Linux kernel, the following vulnerability has been resolved:
kvm: s390: Reject memory region operations for ucontrol VMs
This change rejects the KVM_SET_USER_MEMORY_REGION and KVM_SET_USER_MEMORY_REGION2 ioctls when called on a ucontrol VM. This is necessary since ucontrol VMs have kvm->arch.gmap set to 0 and would thus result in a null pointer dereference further in. Memory management needs to be performed in userspace and using the ioctls KVM_S390_UCAS_MAP and KVM_S390_UCAS_UNMAP.
Also improve s390 specific documentation for KVM_SET_USER_MEMORY_REGION and KVM_SET_USER_MEMORY_REGION2.
frankja@linux.ibm.com: commit message spelling fix, subject prefix fix
In the Linux kernel, the following vulnerability has been resolved:
ext4: fix infinite loop when replaying fast_commit
When doing fast_commit replay an infinite loop may occur due to an uninitialized extent_status struct. ext4_ext_determine_insert_hole() does not detect the replay and calls ext4_es_find_extent_range(), which will return immediately without initializing the 'es' variable.
Because 'es' contains garbage, an integer overflow may happen causing an infinite loop in this function, easily reproducible using fstest generic/039.
This commit fixes this issue by unconditionally initializing the structure in function ext4_es_find_extent_range().
Thanks to Zhang Yi, for figuring out the real problem!(CVE-2024-43828)
In the Linux kernel, the following vulnerability has been resolved:
media: mediatek: vcodec: Handle invalid decoder vsi
Handle an invalid decoder vsi in vpu_dec_init to ensure the decoder vsi is valid for future use.(CVE-2024-43831)
In the Linux kernel, the following vulnerability has been resolved:
cgroup/cpuset: Prevent UAF in proc_cpuset_show()
An UAF can happen when /proc/cpuset is read as reported in [1].
This can be reproduced by the following methods: 1.add an mdelay(1000) before acquiring the cgroup_lock In the cgroup_path_ns function. 2.$cat /proc/<pid>/cpuset repeatly. 3.$mount -t cgroup -o cpuset cpuset /sys/fs/cgroup/cpuset/ $umount /sys/fs/cgroup/cpuset/ repeatly.
The race that cause this bug can be shown as below:
(umount) | (cat /proc/<pid>/cpuset) css_release | proc_cpuset_show css_release_work_fn | css = task_get_css(tsk, cpuset_cgrp_id); css_free_rwork_fn | cgroup_path_ns(css->cgroup, ...); cgroup_destroy_root | mutex_lock(&cgroup_mutex); rebind_subsystems | cgroup_free_root | | // cgrp was freed, UAF | cgroup_path_ns_locked(cgrp,..);
When the cpuset is initialized, the root node top_cpuset.css.cgrp will point to &cgrp_dfl_root.cgrp. In cgroup v1, the mount operation will allocate cgroup_root, and top_cpuset.css.cgrp will point to the allocated &cgroup_root.cgrp. When the umount operation is executed, top_cpuset.css.cgrp will be rebound to &cgrp_dfl_root.cgrp.
The problem is that when rebinding to cgrp_dfl_root, there are cases where the cgroup_root allocated by setting up the root for cgroup v1 is cached. This could lead to a Use-After-Free (UAF) if it is subsequently freed. The descendant cgroups of cgroup v1 can only be freed after the css is released. However, the css of the root will never be released, yet the cgroup_root should be freed when it is unmounted. This means that obtaining a reference to the css of the root does not guarantee that css.cgrp->root will not be freed.
Fix this problem by using rcu_read_lock in proc_cpuset_show(). As cgroup_root is kfree_rcu after commit d23b5c577715 ("cgroup: Make operations on the cgroup root_list RCU safe"), css->cgroup won't be freed during the critical section. To call cgroup_path_ns_locked, css_set_lock is needed, so it is safe to replace task_get_css with task_css.
[1] https://syzkaller.appspot.com/bug?extid=9b1ff7be974a403aa4cd(CVE-2024-43853)
In the Linux kernel, the following vulnerability has been resolved:
remoteproc: imx_rproc: Skip over memory region when node value is NULL
In imx_rproc_addr_init() "nph = of_count_phandle_with_args()" just counts number of phandles. But phandles may be empty. So of_parse_phandle() in the parsing loop (0 < a < nph) may return NULL which is later dereferenced. Adjust this issue by adding NULL-return check.
Found by Linux Verification Center (linuxtesting.org) with SVACE.
Fixed title to fit within the prescribed 70-75 charcters
In the Linux kernel, the following vulnerability has been resolved:
net: usb: qmi_wwan: fix memory leak for not ip packets
Free the unused skb when not ip packets arrive.(CVE-2024-43861)
In the Linux kernel, the following vulnerability has been resolved:
net/mlx5: Always drain health in shutdown callback
There is no point in recovery during device shutdown. if health work started need to wait for it to avoid races and NULL pointer access.
Hence, drain health WQ on shutdown callback.(CVE-2024-43866)
In the Linux kernel, the following vulnerability has been resolved:
wifi: cfg80211: handle 2x996 RU allocation in cfg80211_calculate_bitrate_he()
Currently NL80211_RATE_INFO_HE_RU_ALLOC_2x996 is not handled in cfg80211_calculate_bitrate_he(), leading to below warning:
kernel: invalid HE MCS: bw:6, ru:6 kernel: WARNING: CPU: 0 PID: 2312 at net/wireless/util.c:1501 cfg80211_calculate_bitrate_he+0x22b/0x270 [cfg80211]
Fix it by handling 2x996 RU allocation in the same way as 160 MHz bandwidth.(CVE-2024-43879)
In the Linux kernel, the following vulnerability has been resolved:
exec: Fix ToCToU between perm check and set-uid/gid usage
When opening a file for exec via do_filp_open(), permission checking is done against the file's metadata at that moment, and on success, a file pointer is passed back. Much later in the execve() code path, the file metadata (specifically mode, uid, and gid) is used to determine if/how to set the uid and gid. However, those values may have changed since the permissions check, meaning the execution may gain unintended privileges.
For example, if a file could change permissions from executable and not set-id:
---------x 1 root root 16048 Aug 7 13:16 target
to set-id and non-executable:
---S------ 1 root root 16048 Aug 7 13:16 target
it is possible to gain root privileges when execution should have been disallowed.
While this race condition is rare in real-world scenarios, it has been observed (and proven exploitable) when package managers are updating the setuid bits of installed programs. Such files start with being world-executable but then are adjusted to be group-exec with a set-uid bit. For example, "chmod o-x,u+s target" makes "target" executable only by uid "root" and gid "cdrom", while also becoming setuid-root:
-rwxr-xr-x 1 root cdrom 16048 Aug 7 13:16 target
becomes:
-rwsr-xr-- 1 root cdrom 16048 Aug 7 13:16 target
But racing the chmod means users without group "cdrom" membership can get the permission to execute "target" just before the chmod, and when the chmod finishes, the exec reaches brpm_fill_uid(), and performs the setuid to root, violating the expressed authorization of "only cdrom group members can setuid to root".
Re-check that we still have execute permissions in case the metadata has changed. It would be better to keep a copy from the perm-check time, but until we can do that refactoring, the least-bad option is to do a full inode_permission() call (under inode lock). It is understood that this is safe against dead-locks, but hardly optimal.(CVE-2024-43882)
| URL | Type | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"kernel-5.10.0-136.91.0.172.oe2203sp1.aarch64.rpm",
"kernel-debuginfo-5.10.0-136.91.0.172.oe2203sp1.aarch64.rpm",
"kernel-debugsource-5.10.0-136.91.0.172.oe2203sp1.aarch64.rpm",
"kernel-devel-5.10.0-136.91.0.172.oe2203sp1.aarch64.rpm",
"kernel-headers-5.10.0-136.91.0.172.oe2203sp1.aarch64.rpm",
"kernel-source-5.10.0-136.91.0.172.oe2203sp1.aarch64.rpm",
"kernel-tools-5.10.0-136.91.0.172.oe2203sp1.aarch64.rpm",
"kernel-tools-debuginfo-5.10.0-136.91.0.172.oe2203sp1.aarch64.rpm",
"kernel-tools-devel-5.10.0-136.91.0.172.oe2203sp1.aarch64.rpm",
"perf-5.10.0-136.91.0.172.oe2203sp1.aarch64.rpm",
"perf-debuginfo-5.10.0-136.91.0.172.oe2203sp1.aarch64.rpm",
"python3-perf-5.10.0-136.91.0.172.oe2203sp1.aarch64.rpm",
"python3-perf-debuginfo-5.10.0-136.91.0.172.oe2203sp1.aarch64.rpm"
],
"src": [
"kernel-5.10.0-136.91.0.172.oe2203sp1.src.rpm"
],
"x86_64": [
"kernel-5.10.0-136.91.0.172.oe2203sp1.x86_64.rpm",
"kernel-debuginfo-5.10.0-136.91.0.172.oe2203sp1.x86_64.rpm",
"kernel-debugsource-5.10.0-136.91.0.172.oe2203sp1.x86_64.rpm",
"kernel-devel-5.10.0-136.91.0.172.oe2203sp1.x86_64.rpm",
"kernel-headers-5.10.0-136.91.0.172.oe2203sp1.x86_64.rpm",
"kernel-source-5.10.0-136.91.0.172.oe2203sp1.x86_64.rpm",
"kernel-tools-5.10.0-136.91.0.172.oe2203sp1.x86_64.rpm",
"kernel-tools-debuginfo-5.10.0-136.91.0.172.oe2203sp1.x86_64.rpm",
"kernel-tools-devel-5.10.0-136.91.0.172.oe2203sp1.x86_64.rpm",
"perf-5.10.0-136.91.0.172.oe2203sp1.x86_64.rpm",
"perf-debuginfo-5.10.0-136.91.0.172.oe2203sp1.x86_64.rpm",
"python3-perf-5.10.0-136.91.0.172.oe2203sp1.x86_64.rpm",
"python3-perf-debuginfo-5.10.0-136.91.0.172.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.91.0.172.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\nio_uring: fix memleak in io_init_wq_offload()\r\n\r\nI got memory leak report when doing fuzz test:\r\n\r\nBUG: memory leak\nunreferenced object 0xffff888107310a80 (size 96):\ncomm \u0026quot;syz-executor.6\u0026quot;, pid 4610, jiffies 4295140240 (age 20.135s)\nhex dump (first 32 bytes):\n01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00 .....N..........\nbacktrace:\n[\u0026lt;000000001974933b\u0026gt;] kmalloc include/linux/slab.h:591 [inline]\n[\u0026lt;000000001974933b\u0026gt;] kzalloc include/linux/slab.h:721 [inline]\n[\u0026lt;000000001974933b\u0026gt;] io_init_wq_offload fs/io_uring.c:7920 [inline]\n[\u0026lt;000000001974933b\u0026gt;] io_uring_alloc_task_context+0x466/0x640 fs/io_uring.c:7955\n[\u0026lt;0000000039d0800d\u0026gt;] __io_uring_add_tctx_node+0x256/0x360 fs/io_uring.c:9016\n[\u0026lt;000000008482e78c\u0026gt;] io_uring_add_tctx_node fs/io_uring.c:9052 [inline]\n[\u0026lt;000000008482e78c\u0026gt;] __do_sys_io_uring_enter fs/io_uring.c:9354 [inline]\n[\u0026lt;000000008482e78c\u0026gt;] __se_sys_io_uring_enter fs/io_uring.c:9301 [inline]\n[\u0026lt;000000008482e78c\u0026gt;] __x64_sys_io_uring_enter+0xabc/0xc20 fs/io_uring.c:9301\n[\u0026lt;00000000b875f18f\u0026gt;] do_syscall_x64 arch/x86/entry/common.c:50 [inline]\n[\u0026lt;00000000b875f18f\u0026gt;] do_syscall_64+0x3b/0x90 arch/x86/entry/common.c:80\n[\u0026lt;000000006b0a8484\u0026gt;] entry_SYSCALL_64_after_hwframe+0x44/0xae\r\n\r\nCPU0 CPU1\nio_uring_enter io_uring_enter\nio_uring_add_tctx_node io_uring_add_tctx_node\n__io_uring_add_tctx_node __io_uring_add_tctx_node\nio_uring_alloc_task_context io_uring_alloc_task_context\nio_init_wq_offload io_init_wq_offload\nhash = kzalloc hash = kzalloc\nctx-\u0026gt;hash_map = hash ctx-\u0026gt;hash_map = hash \u0026lt;- one of the hash is leaked\r\n\r\nWhen calling io_uring_enter() in parallel, the \u0026apos;hash_map\u0026apos; will be leaked,\nadd uring_lock to protect \u0026apos;hash_map\u0026apos;.(CVE-2021-47292)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nio_uring: ensure task_work gets run as part of cancelations\r\n\r\nIf we successfully cancel a work item but that work item needs to be\nprocessed through task_work, then we can be sleeping uninterruptibly\nin io_uring_cancel_generic() and never process it. Hence we don\u0026apos;t\nmake forward progress and we end up with an uninterruptible sleep\nwarning.\r\n\r\nWhile in there, correct a comment that should be IFF, not IIF.(CVE-2021-47504)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nethtool: ioctl: fix potential NULL deref in ethtool_set_coalesce()\r\n\r\nethtool_set_coalesce() now uses both the .get_coalesce() and\n.set_coalesce() callbacks. But the check for their availability is\nbuggy, so changing the coalesce settings on a device where the driver\nprovides only _one_ of the callbacks results in a NULL pointer\ndereference instead of an -EOPNOTSUPP.\r\n\r\nFix the condition so that the availability of both callbacks is\nensured. This also matches the netlink code.\r\n\r\nNote that reproducing this requires some effort - it only affects the\nlegacy ioctl path, and needs a specific combination of driver options:\n- have .get_coalesce() and .coalesce_supported but no\n .set_coalesce(), or\n- have .set_coalesce() but no .get_coalesce(). Here eg. ethtool doesn\u0026apos;t\n cause the crash as it first attempts to call ethtool_get_coalesce()\n and bails out on error.(CVE-2021-47556)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/gma500: Fix BUG: sleeping function called from invalid context errors\r\n\r\ngma_crtc_page_flip() was holding the event_lock spinlock while calling\ncrtc_funcs-\u0026gt;mode_set_base() which takes ww_mutex.\r\n\r\nThe only reason to hold event_lock is to clear gma_crtc-\u0026gt;page_flip_event\non mode_set_base() errors.\r\n\r\nInstead unlock it after setting gma_crtc-\u0026gt;page_flip_event and on\nerrors re-take the lock and clear gma_crtc-\u0026gt;page_flip_event it\nit is still set.\r\n\r\nThis fixes the following WARN/stacktrace:\r\n\r\n[ 512.122953] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:870\n[ 512.123004] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 1253, name: gnome-shell\n[ 512.123031] preempt_count: 1, expected: 0\n[ 512.123048] RCU nest depth: 0, expected: 0\n[ 512.123066] INFO: lockdep is turned off.\n[ 512.123080] irq event stamp: 0\n[ 512.123094] hardirqs last enabled at (0): [\u0026lt;0000000000000000\u0026gt;] 0x0\n[ 512.123134] hardirqs last disabled at (0): [\u0026lt;ffffffff8d0ec28c\u0026gt;] copy_process+0x9fc/0x1de0\n[ 512.123176] softirqs last enabled at (0): [\u0026lt;ffffffff8d0ec28c\u0026gt;] copy_process+0x9fc/0x1de0\n[ 512.123207] softirqs last disabled at (0): [\u0026lt;0000000000000000\u0026gt;] 0x0\n[ 512.123233] Preemption disabled at:\n[ 512.123241] [\u0026lt;0000000000000000\u0026gt;] 0x0\n[ 512.123275] CPU: 3 PID: 1253 Comm: gnome-shell Tainted: G W 5.19.0+ #1\n[ 512.123304] Hardware name: Packard Bell dot s/SJE01_CT, BIOS V1.10 07/23/2013\n[ 512.123323] Call Trace:\n[ 512.123346] \u0026lt;TASK\u0026gt;\n[ 512.123370] dump_stack_lvl+0x5b/0x77\n[ 512.123412] __might_resched.cold+0xff/0x13a\n[ 512.123458] ww_mutex_lock+0x1e/0xa0\n[ 512.123495] psb_gem_pin+0x2c/0x150 [gma500_gfx]\n[ 512.123601] gma_pipe_set_base+0x76/0x240 [gma500_gfx]\n[ 512.123708] gma_crtc_page_flip+0x95/0x130 [gma500_gfx]\n[ 512.123808] drm_mode_page_flip_ioctl+0x57d/0x5d0\n[ 512.123897] ? drm_mode_cursor2_ioctl+0x10/0x10\n[ 512.123936] drm_ioctl_kernel+0xa1/0x150\n[ 512.123984] drm_ioctl+0x21f/0x420\n[ 512.124025] ? drm_mode_cursor2_ioctl+0x10/0x10\n[ 512.124070] ? rcu_read_lock_bh_held+0xb/0x60\n[ 512.124104] ? lock_release+0x1ef/0x2d0\n[ 512.124161] __x64_sys_ioctl+0x8d/0xd0\n[ 512.124203] do_syscall_64+0x58/0x80\n[ 512.124239] ? do_syscall_64+0x67/0x80\n[ 512.124267] ? trace_hardirqs_on_prepare+0x55/0xe0\n[ 512.124300] ? do_syscall_64+0x67/0x80\n[ 512.124340] ? rcu_read_lock_sched_held+0x10/0x80\n[ 512.124377] entry_SYSCALL_64_after_hwframe+0x63/0xcd\n[ 512.124411] RIP: 0033:0x7fcc4a70740f\n[ 512.124442] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 \u0026lt;89\u0026gt; c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00\n[ 512.124470] RSP: 002b:00007ffda73f5390 EFLAGS: 00000246 ORIG_RAX: 0000000000000010\n[ 512.124503] RAX: ffffffffffffffda RBX: 000055cc9e474500 RCX: 00007fcc4a70740f\n[ 512.124524] RDX: 00007ffda73f5420 RSI: 00000000c01864b0 RDI: 0000000000000009\n[ 512.124544] RBP: 00007ffda73f5420 R08: 000055cc9c0b0cb0 R09: 0000000000000034\n[ 512.124564] R10: 0000000000000000 R11: 0000000000000246 R12: 00000000c01864b0\n[ 512.124584] R13: 0000000000000009 R14: 000055cc9df484d0 R15: 000055cc9af5d0c0\n[ 512.124647] \u0026lt;/TASK\u0026gt;(CVE-2022-48634)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: sched: fix possible refcount leak in tc_new_tfilter()\r\n\r\ntfilter_put need to be called to put the refount got by tp-\u0026gt;ops-\u0026gt;get to\navoid possible refcount leak when chain-\u0026gt;tmplt_ops != NULL and\nchain-\u0026gt;tmplt_ops != tp-\u0026gt;ops.(CVE-2022-48639)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: nf_tables: fix percpu memory leak at nf_tables_addchain()\r\n\r\nIt seems to me that percpu memory for chain stats started leaking since\ncommit 3bc158f8d0330f0a (\u0026quot;netfilter: nf_tables: map basechain priority to\nhardware priority\u0026quot;) when nft_chain_offload_priority() returned an error.(CVE-2022-48642)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: nf_tables: fix nft_counters_enabled underflow at nf_tables_addchain()\r\n\r\nsyzbot is reporting underflow of nft_counters_enabled counter at\nnf_tables_addchain() [1], for commit 43eb8949cfdffa76 (\u0026quot;netfilter:\nnf_tables: do not leave chain stats enabled on error\u0026quot;) missed that\nnf_tables_chain_destroy() after nft_basechain_init() in the error path of\nnf_tables_addchain() decrements the counter because nft_basechain_init()\nmakes nft_is_base_chain() return true by setting NFT_CHAIN_BASE flag.\r\n\r\nIncrement the counter immediately after returning from\nnft_basechain_init().(CVE-2022-48643)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/sched: taprio: avoid disabling offload when it was never enabled\r\n\r\nIn an incredibly strange API design decision, qdisc-\u0026gt;destroy() gets\ncalled even if qdisc-\u0026gt;init() never succeeded, not exclusively since\ncommit 87b60cfacf9f (\u0026quot;net_sched: fix error recovery at qdisc creation\u0026quot;),\nbut apparently also earlier (in the case of qdisc_create_dflt()).\r\n\r\nThe taprio qdisc does not fully acknowledge this when it attempts full\noffload, because it starts off with q-\u0026gt;flags = TAPRIO_FLAGS_INVALID in\ntaprio_init(), then it replaces q-\u0026gt;flags with TCA_TAPRIO_ATTR_FLAGS\nparsed from netlink (in taprio_change(), tail called from taprio_init()).\r\n\r\nBut in taprio_destroy(), we call taprio_disable_offload(), and this\ndetermines what to do based on FULL_OFFLOAD_IS_ENABLED(q-\u0026gt;flags).\r\n\r\nBut looking at the implementation of FULL_OFFLOAD_IS_ENABLED()\n(a bitwise check of bit 1 in q-\u0026gt;flags), it is invalid to call this macro\non q-\u0026gt;flags when it contains TAPRIO_FLAGS_INVALID, because that is set\nto U32_MAX, and therefore FULL_OFFLOAD_IS_ENABLED() will return true on\nan invalid set of flags.\r\n\r\nAs a result, it is possible to crash the kernel if user space forces an\nerror between setting q-\u0026gt;flags = TAPRIO_FLAGS_INVALID, and the calling\nof taprio_enable_offload(). This is because drivers do not expect the\noffload to be disabled when it was never enabled.\r\n\r\nThe error that we force here is to attach taprio as a non-root qdisc,\nbut instead as child of an mqprio root qdisc:\r\n\r\n$ tc qdisc add dev swp0 root handle 1: \\\n\tmqprio num_tc 8 map 0 1 2 3 4 5 6 7 \\\n\tqueues 1@0 1@1 1@2 1@3 1@4 1@5 1@6 1@7 hw 0\n$ tc qdisc replace dev swp0 parent 1:1 \\\n\ttaprio num_tc 8 map 0 1 2 3 4 5 6 7 \\\n\tqueues 1@0 1@1 1@2 1@3 1@4 1@5 1@6 1@7 base-time 0 \\\n\tsched-entry S 0x7f 990000 sched-entry S 0x80 100000 \\\n\tflags 0x0 clockid CLOCK_TAI\nUnable to handle kernel paging request at virtual address fffffffffffffff8\n[fffffffffffffff8] pgd=0000000000000000, p4d=0000000000000000\nInternal error: Oops: 96000004 [#1] PREEMPT SMP\nCall trace:\n taprio_dump+0x27c/0x310\n vsc9959_port_setup_tc+0x1f4/0x460\n felix_port_setup_tc+0x24/0x3c\n dsa_slave_setup_tc+0x54/0x27c\n taprio_disable_offload.isra.0+0x58/0xe0\n taprio_destroy+0x80/0x104\n qdisc_create+0x240/0x470\n tc_modify_qdisc+0x1fc/0x6b0\n rtnetlink_rcv_msg+0x12c/0x390\n netlink_rcv_skb+0x5c/0x130\n rtnetlink_rcv+0x1c/0x2c\r\n\r\nFix this by keeping track of the operations we made, and undo the\noffload only if we actually did it.\r\n\r\nI\u0026apos;ve added \u0026quot;bool offloaded\u0026quot; inside a 4 byte hole between \u0026quot;int clockid\u0026quot;\nand \u0026quot;atomic64_t picos_per_byte\u0026quot;. Now the first cache line looks like\nbelow:\r\n\r\n$ pahole -C taprio_sched net/sched/sch_taprio.o\nstruct taprio_sched {\n struct Qdisc * * qdiscs; /* 0 8 */\n struct Qdisc * root; /* 8 8 */\n u32 flags; /* 16 4 */\n enum tk_offsets tk_offset; /* 20 4 */\n int clockid; /* 24 4 */\n bool offloaded; /* 28 1 */\r\n\r\n /* XXX 3 bytes hole, try to pack */\r\n\r\n atomic64_t picos_per_byte; /* 32 0 */\r\n\r\n /* XXX 8 bytes hole, try to pack */\r\n\r\n spinlock_t current_entry_lock; /* 40 0 */\r\n\r\n /* XXX 8 bytes hole, try to pack */\r\n\r\n struct sched_entry * current_entry; /* 48 8 */\n struct sched_gate_list * oper_sched; /* 56 8 */\n /* --- cacheline 1 boundary (64 bytes) --- */(CVE-2022-48644)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsfc: fix TX channel offset when using legacy interrupts\r\n\r\nIn legacy interrupt mode the tx_channel_offset was hardcoded to 1, but\nthat\u0026apos;s not correct if efx_sepparate_tx_channels is false. In that case,\nthe offset is 0 because the tx queues are in the single existing channel\nat index 0, together with the rx queue.\r\n\r\nWithout this fix, as soon as you try to send any traffic, it tries to\nget the tx queues from an uninitialized channel getting these errors:\n WARNING: CPU: 1 PID: 0 at drivers/net/ethernet/sfc/tx.c:540 efx_hard_start_xmit+0x12e/0x170 [sfc]\n [...]\n RIP: 0010:efx_hard_start_xmit+0x12e/0x170 [sfc]\n [...]\n Call Trace:\n \u0026lt;IRQ\u0026gt;\n dev_hard_start_xmit+0xd7/0x230\n sch_direct_xmit+0x9f/0x360\n __dev_queue_xmit+0x890/0xa40\n [...]\n BUG: unable to handle kernel NULL pointer dereference at 0000000000000020\n [...]\n RIP: 0010:efx_hard_start_xmit+0x153/0x170 [sfc]\n [...]\n Call Trace:\n \u0026lt;IRQ\u0026gt;\n dev_hard_start_xmit+0xd7/0x230\n sch_direct_xmit+0x9f/0x360\n __dev_queue_xmit+0x890/0xa40\n [...](CVE-2022-48647)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nsfc: fix null pointer dereference in efx_hard_start_xmit\r\n\r\nTrying to get the channel from the tx_queue variable here is wrong\nbecause we can only be here if tx_queue is NULL, so we shouldn\u0026apos;t\ndereference it. As the above comment in the code says, this is very\nunlikely to happen, but it\u0026apos;s wrong anyway so let\u0026apos;s fix it.\r\n\r\nI hit this issue because of a different bug that caused tx_queue to be\nNULL. If that happens, this is the error message that we get here:\n BUG: unable to handle kernel NULL pointer dereference at 0000000000000020\n [...]\n RIP: 0010:efx_hard_start_xmit+0x153/0x170 [sfc](CVE-2022-48648)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndmaengine: ti: k3-udma-private: Fix refcount leak bug in of_xudma_dev_get()\r\n\r\nWe should call of_node_put() for the reference returned by\nof_parse_phandle() in fail path or when it is not used anymore.\nHere we only need to move the of_node_put() before the check.(CVE-2022-48656)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ngpio: mockup: fix NULL pointer dereference when removing debugfs\r\n\r\nWe now remove the device\u0026apos;s debugfs entries when unbinding the driver.\nThis now causes a NULL-pointer dereference on module exit because the\nplatform devices are unregistered *after* the global debugfs directory\nhas been recursively removed. Fix it by unregistering the devices first.(CVE-2022-48663)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncgroup: Add missing cpus_read_lock() to cgroup_attach_task_all()\r\n\r\nsyzbot is hitting percpu_rwsem_assert_held(\u0026amp;cpu_hotplug_lock) warning at\ncpuset_attach() [1], for commit 4f7e7236435ca0ab (\u0026quot;cgroup: Fix\nthreadgroup_rwsem \u0026lt;-\u0026gt; cpus_read_lock() deadlock\u0026quot;) missed that\ncpuset_attach() is also called from cgroup_attach_task_all().\nAdd cpus_read_lock() like what cgroup_procs_write_start() does.(CVE-2022-48671)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nof: fdt: fix off-by-one error in unflatten_dt_nodes()\r\n\r\nCommit 78c44d910d3e (\u0026quot;drivers/of: Fix depth when unflattening devicetree\u0026quot;)\nforgot to fix up the depth check in the loop body in unflatten_dt_nodes()\nwhich makes it possible to overflow the nps[] buffer...\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with the SVACE static\nanalysis tool.(CVE-2022-48672)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nIB/core: Fix a nested dead lock as part of ODP flow\r\n\r\nFix a nested dead lock as part of ODP flow by using mmput_async().\r\n\r\nFrom the below call trace [1] can see that calling mmput() once we have\nthe umem_odp-\u0026gt;umem_mutex locked as required by\nib_umem_odp_map_dma_and_lock() might trigger in the same task the\nexit_mmap()-\u0026gt;__mmu_notifier_release()-\u0026gt;mlx5_ib_invalidate_range() which\nmay dead lock when trying to lock the same mutex.\r\n\r\nMoving to use mmput_async() will solve the problem as the above\nexit_mmap() flow will be called in other task and will be executed once\nthe lock will be available.\r\n\r\n[1]\n[64843.077665] task:kworker/u133:2 state:D stack: 0 pid:80906 ppid:\n2 flags:0x00004000\n[64843.077672] Workqueue: mlx5_ib_page_fault mlx5_ib_eqe_pf_action [mlx5_ib]\n[64843.077719] Call Trace:\n[64843.077722] \u0026lt;TASK\u0026gt;\n[64843.077724] __schedule+0x23d/0x590\n[64843.077729] schedule+0x4e/0xb0\n[64843.077735] schedule_preempt_disabled+0xe/0x10\n[64843.077740] __mutex_lock.constprop.0+0x263/0x490\n[64843.077747] __mutex_lock_slowpath+0x13/0x20\n[64843.077752] mutex_lock+0x34/0x40\n[64843.077758] mlx5_ib_invalidate_range+0x48/0x270 [mlx5_ib]\n[64843.077808] __mmu_notifier_release+0x1a4/0x200\n[64843.077816] exit_mmap+0x1bc/0x200\n[64843.077822] ? walk_page_range+0x9c/0x120\n[64843.077828] ? __cond_resched+0x1a/0x50\n[64843.077833] ? mutex_lock+0x13/0x40\n[64843.077839] ? uprobe_clear_state+0xac/0x120\n[64843.077860] mmput+0x5f/0x140\n[64843.077867] ib_umem_odp_map_dma_and_lock+0x21b/0x580 [ib_core]\n[64843.077931] pagefault_real_mr+0x9a/0x140 [mlx5_ib]\n[64843.077962] pagefault_mr+0xb4/0x550 [mlx5_ib]\n[64843.077992] pagefault_single_data_segment.constprop.0+0x2ac/0x560\n[mlx5_ib]\n[64843.078022] mlx5_ib_eqe_pf_action+0x528/0x780 [mlx5_ib]\n[64843.078051] process_one_work+0x22b/0x3d0\n[64843.078059] worker_thread+0x53/0x410\n[64843.078065] ? process_one_work+0x3d0/0x3d0\n[64843.078073] kthread+0x12a/0x150\n[64843.078079] ? set_kthread_struct+0x50/0x50\n[64843.078085] ret_from_fork+0x22/0x30\n[64843.078093] \u0026lt;/TASK\u0026gt;(CVE-2022-48675)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnvme-tcp: fix UAF when detecting digest errors\r\n\r\nWe should also bail from the io_work loop when we set rd_enabled to true,\nso we don\u0026apos;t attempt to read data from the socket when the TCP stream is\nalready out-of-sync or corrupted.(CVE-2022-48686)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nipv6: sr: fix out-of-bounds read when setting HMAC data.\r\n\r\nThe SRv6 layer allows defining HMAC data that can later be used to sign IPv6\nSegment Routing Headers. This configuration is realised via netlink through\nfour attributes: SEG6_ATTR_HMACKEYID, SEG6_ATTR_SECRET, SEG6_ATTR_SECRETLEN and\nSEG6_ATTR_ALGID. Because the SECRETLEN attribute is decoupled from the actual\nlength of the SECRET attribute, it is possible to provide invalid combinations\n(e.g., secret = \u0026quot;\u0026quot;, secretlen = 64). This case is not checked in the code and\nwith an appropriately crafted netlink message, an out-of-bounds read of up\nto 64 bytes (max secret length) can occur past the skb end pointer and into\nskb_shared_info:\r\n\r\nBreakpoint 1, seg6_genl_sethmac (skb=\u0026lt;optimized out\u0026gt;, info=\u0026lt;optimized out\u0026gt;) at net/ipv6/seg6.c:208\n208\t\tmemcpy(hinfo-\u0026gt;secret, secret, slen);\n(gdb) bt\n #0 seg6_genl_sethmac (skb=\u0026lt;optimized out\u0026gt;, info=\u0026lt;optimized out\u0026gt;) at net/ipv6/seg6.c:208\n #1 0xffffffff81e012e9 in genl_family_rcv_msg_doit (skb=skb@entry=0xffff88800b1f9f00, nlh=nlh@entry=0xffff88800b1b7600,\n extack=extack@entry=0xffffc90000ba7af0, ops=ops@entry=0xffffc90000ba7a80, hdrlen=4, net=0xffffffff84237580 \u0026lt;init_net\u0026gt;, family=\u0026lt;optimized out\u0026gt;,\n family=\u0026lt;optimized out\u0026gt;) at net/netlink/genetlink.c:731\n #2 0xffffffff81e01435 in genl_family_rcv_msg (extack=0xffffc90000ba7af0, nlh=0xffff88800b1b7600, skb=0xffff88800b1f9f00,\n family=0xffffffff82fef6c0 \u0026lt;seg6_genl_family\u0026gt;) at net/netlink/genetlink.c:775\n #3 genl_rcv_msg (skb=0xffff88800b1f9f00, nlh=0xffff88800b1b7600, extack=0xffffc90000ba7af0) at net/netlink/genetlink.c:792\n #4 0xffffffff81dfffc3 in netlink_rcv_skb (skb=skb@entry=0xffff88800b1f9f00, cb=cb@entry=0xffffffff81e01350 \u0026lt;genl_rcv_msg\u0026gt;)\n at net/netlink/af_netlink.c:2501\n #5 0xffffffff81e00919 in genl_rcv (skb=0xffff88800b1f9f00) at net/netlink/genetlink.c:803\n #6 0xffffffff81dff6ae in netlink_unicast_kernel (ssk=0xffff888010eec800, skb=0xffff88800b1f9f00, sk=0xffff888004aed000)\n at net/netlink/af_netlink.c:1319\n #7 netlink_unicast (ssk=ssk@entry=0xffff888010eec800, skb=skb@entry=0xffff88800b1f9f00, portid=portid@entry=0, nonblock=\u0026lt;optimized out\u0026gt;)\n at net/netlink/af_netlink.c:1345\n #8 0xffffffff81dff9a4 in netlink_sendmsg (sock=\u0026lt;optimized out\u0026gt;, msg=0xffffc90000ba7e48, len=\u0026lt;optimized out\u0026gt;) at net/netlink/af_netlink.c:1921\n...\n(gdb) p/x ((struct sk_buff *)0xffff88800b1f9f00)-\u0026gt;head + ((struct sk_buff *)0xffff88800b1f9f00)-\u0026gt;end\n$1 = 0xffff88800b1b76c0\n(gdb) p/x secret\n$2 = 0xffff88800b1b76c0\n(gdb) p slen\n$3 = 64 \u0026apos;@\u0026apos;\r\n\r\nThe OOB data can then be read back from userspace by dumping HMAC state. This\ncommit fixes this by ensuring SECRETLEN cannot exceed the actual length of\nSECRET.(CVE-2022-48687)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: nf_tables: clean up hook list when offload flags check fails\r\n\r\nsplice back the hook list so nft_chain_release_hook() has a chance to\nrelease the hooks.\r\n\r\nBUG: memory leak\nunreferenced object 0xffff88810180b100 (size 96):\n comm \u0026quot;syz-executor133\u0026quot;, pid 3619, jiffies 4294945714 (age 12.690s)\n hex dump (first 32 bytes):\n 28 64 23 02 81 88 ff ff 28 64 23 02 81 88 ff ff (d#.....(d#.....\n 90 a8 aa 83 ff ff ff ff 00 00 b5 0f 81 88 ff ff ................\n backtrace:\n [\u0026lt;ffffffff83a8c59b\u0026gt;] kmalloc include/linux/slab.h:600 [inline]\n [\u0026lt;ffffffff83a8c59b\u0026gt;] nft_netdev_hook_alloc+0x3b/0xc0 net/netfilter/nf_tables_api.c:1901\n [\u0026lt;ffffffff83a9239a\u0026gt;] nft_chain_parse_netdev net/netfilter/nf_tables_api.c:1998 [inline]\n [\u0026lt;ffffffff83a9239a\u0026gt;] nft_chain_parse_hook+0x33a/0x530 net/netfilter/nf_tables_api.c:2073\n [\u0026lt;ffffffff83a9b14b\u0026gt;] nf_tables_addchain.constprop.0+0x10b/0x950 net/netfilter/nf_tables_api.c:2218\n [\u0026lt;ffffffff83a9c41b\u0026gt;] nf_tables_newchain+0xa8b/0xc60 net/netfilter/nf_tables_api.c:2593\n [\u0026lt;ffffffff83a3d6a6\u0026gt;] nfnetlink_rcv_batch+0xa46/0xd20 net/netfilter/nfnetlink.c:517\n [\u0026lt;ffffffff83a3db79\u0026gt;] nfnetlink_rcv_skb_batch net/netfilter/nfnetlink.c:638 [inline]\n [\u0026lt;ffffffff83a3db79\u0026gt;] nfnetlink_rcv+0x1f9/0x220 net/netfilter/nfnetlink.c:656\n [\u0026lt;ffffffff83a13b17\u0026gt;] netlink_unicast_kernel net/netlink/af_netlink.c:1319 [inline]\n [\u0026lt;ffffffff83a13b17\u0026gt;] netlink_unicast+0x397/0x4c0 net/netlink/af_netlink.c:1345\n [\u0026lt;ffffffff83a13fd6\u0026gt;] netlink_sendmsg+0x396/0x710 net/netlink/af_netlink.c:1921\n [\u0026lt;ffffffff83865ab6\u0026gt;] sock_sendmsg_nosec net/socket.c:714 [inline]\n [\u0026lt;ffffffff83865ab6\u0026gt;] sock_sendmsg+0x56/0x80 net/socket.c:734\n [\u0026lt;ffffffff8386601c\u0026gt;] ____sys_sendmsg+0x36c/0x390 net/socket.c:2482\n [\u0026lt;ffffffff8386a918\u0026gt;] ___sys_sendmsg+0xa8/0x110 net/socket.c:2536\n [\u0026lt;ffffffff8386aaa8\u0026gt;] __sys_sendmsg+0x88/0x100 net/socket.c:2565\n [\u0026lt;ffffffff845e5955\u0026gt;] do_syscall_x64 arch/x86/entry/common.c:50 [inline]\n [\u0026lt;ffffffff845e5955\u0026gt;] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80\n [\u0026lt;ffffffff84800087\u0026gt;] entry_SYSCALL_64_after_hwframe+0x63/0xcd(CVE-2022-48691)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmisc: fastrpc: Don\u0026apos;t remove map on creater_process and device_release\r\n\r\nDo not remove the map from the list on error path in\nfastrpc_init_create_process, instead call fastrpc_map_put, to avoid\nuse-after-free. Do not remove it on fastrpc_device_release either,\ncall fastrpc_map_put instead.\r\n\r\nThe fastrpc_free_map is the only proper place to remove the map.\nThis is called only after the reference count is 0.(CVE-2022-48873)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nixgbe: fix pci device refcount leak\r\n\r\nAs the comment of pci_get_domain_bus_and_slot() says, it\nreturns a PCI device with refcount incremented, when finish\nusing it, the caller must decrement the reference count by\ncalling pci_dev_put().\r\n\r\nIn ixgbe_get_first_secondary_devfn() and ixgbe_x550em_a_has_mii(),\npci_dev_put() is called to avoid leak.(CVE-2022-48896)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/msm/dp: do not complete dp_aux_cmd_fifo_tx() if irq is not for aux transfer\r\n\r\nThere are 3 possible interrupt sources are handled by DP controller,\nHPDstatus, Controller state changes and Aux read/write transaction.\nAt every irq, DP controller have to check isr status of every interrupt\nsources and service the interrupt if its isr status bits shows interrupts\nare pending. There is potential race condition may happen at current aux\nisr handler implementation since it is always complete dp_aux_cmd_fifo_tx()\neven irq is not for aux read or write transaction. This may cause aux read\ntransaction return premature if host aux data read is in the middle of\nwaiting for sink to complete transferring data to host while irq happen.\nThis will cause host\u0026apos;s receiving buffer contains unexpected data. This\npatch fixes this problem by checking aux isr and return immediately at\naux isr handler if there are no any isr status bits set.\r\n\r\nCurrent there is a bug report regrading eDP edid corruption happen during\nsystem booting up. After lengthy debugging to found that VIDEO_READY\ninterrupt was continuously firing during system booting up which cause\ndp_aux_isr() to complete dp_aux_cmd_fifo_tx() prematurely to retrieve data\nfrom aux hardware buffer which is not yet contains complete data transfer\nfrom sink. This cause edid corruption.\r\n\r\nFollows are the signature at kernel logs when problem happen,\nEDID has corrupt header\npanel-simple-dp-aux aux-aea0000.edp: Couldn\u0026apos;t identify panel via EDID\r\n\r\nChanges in v2:\n-- do complete if (ret == IRQ_HANDLED) ay dp-aux_isr()\n-- add more commit text\r\n\r\nChanges in v3:\n-- add Stephen suggested\n-- dp_aux_isr() return IRQ_XXX back to caller\n-- dp_ctrl_isr() return IRQ_XXX back to caller\r\n\r\nChanges in v4:\n-- split into two patches\r\n\r\nChanges in v5:\n-- delete empty line between tags\r\n\r\nChanges in v6:\n-- remove extra \u0026quot;that\u0026quot; and fixed line more than 75 char at commit text\r\n\r\nPatchwork: https://patchwork.freedesktop.org/patch/516121/(CVE-2022-48898)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/virtio: Fix GEM handle creation UAF\r\n\r\nUserspace can guess the handle value and try to race GEM object creation\nwith handle close, resulting in a use-after-free if we dereference the\nobject after dropping the handle\u0026apos;s reference. For that reason, dropping\nthe handle\u0026apos;s reference must be done *after* we are done dereferencing\nthe object.(CVE-2022-48899)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbtrfs: get rid of warning on transaction commit when using flushoncommit\r\n\r\nWhen using the flushoncommit mount option, during almost every transaction\ncommit we trigger a warning from __writeback_inodes_sb_nr():\r\n\r\n $ cat fs/fs-writeback.c:\n (...)\n static void __writeback_inodes_sb_nr(struct super_block *sb, ...\n {\n (...)\n WARN_ON(!rwsem_is_locked(\u0026amp;sb-\u0026gt;s_umount));\n (...)\n }\n (...)\r\n\r\nThe trace produced in dmesg looks like the following:\r\n\r\n [947.473890] WARNING: CPU: 5 PID: 930 at fs/fs-writeback.c:2610 __writeback_inodes_sb_nr+0x7e/0xb3\n [947.481623] Modules linked in: nfsd nls_cp437 cifs asn1_decoder cifs_arc4 fscache cifs_md4 ipmi_ssif\n [947.489571] CPU: 5 PID: 930 Comm: btrfs-transacti Not tainted 95.16.3-srb-asrock-00001-g36437ad63879 #186\n [947.497969] RIP: 0010:__writeback_inodes_sb_nr+0x7e/0xb3\n [947.502097] Code: 24 10 4c 89 44 24 18 c6 (...)\n [947.519760] RSP: 0018:ffffc90000777e10 EFLAGS: 00010246\n [947.523818] RAX: 0000000000000000 RBX: 0000000000963300 RCX: 0000000000000000\n [947.529765] RDX: 0000000000000000 RSI: 000000000000fa51 RDI: ffffc90000777e50\n [947.535740] RBP: ffff888101628a90 R08: ffff888100955800 R09: ffff888100956000\n [947.541701] R10: 0000000000000002 R11: 0000000000000001 R12: ffff888100963488\n [947.547645] R13: ffff888100963000 R14: ffff888112fb7200 R15: ffff888100963460\n [947.553621] FS: 0000000000000000(0000) GS:ffff88841fd40000(0000) knlGS:0000000000000000\n [947.560537] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n [947.565122] CR2: 0000000008be50c4 CR3: 000000000220c000 CR4: 00000000001006e0\n [947.571072] Call Trace:\n [947.572354] \u0026lt;TASK\u0026gt;\n [947.573266] btrfs_commit_transaction+0x1f1/0x998\n [947.576785] ? start_transaction+0x3ab/0x44e\n [947.579867] ? schedule_timeout+0x8a/0xdd\n [947.582716] transaction_kthread+0xe9/0x156\n [947.585721] ? btrfs_cleanup_transaction.isra.0+0x407/0x407\n [947.590104] kthread+0x131/0x139\n [947.592168] ? set_kthread_struct+0x32/0x32\n [947.595174] ret_from_fork+0x22/0x30\n [947.597561] \u0026lt;/TASK\u0026gt;\n [947.598553] ---[ end trace 644721052755541c ]---\r\n\r\nThis is because we started using writeback_inodes_sb() to flush delalloc\nwhen committing a transaction (when using -o flushoncommit), in order to\navoid deadlocks with filesystem freeze operations. This change was made\nby commit ce8ea7cc6eb313 (\u0026quot;btrfs: don\u0026apos;t call btrfs_start_delalloc_roots\nin flushoncommit\u0026quot;). After that change we started producing that warning,\nand every now and then a user reports this since the warning happens too\noften, it spams dmesg/syslog, and a user is unsure if this reflects any\nproblem that might compromise the filesystem\u0026apos;s reliability.\r\n\r\nWe can not just lock the sb-\u0026gt;s_umount semaphore before calling\nwriteback_inodes_sb(), because that would at least deadlock with\nfilesystem freezing, since at fs/super.c:freeze_super() sync_filesystem()\nis called while we are holding that semaphore in write mode, and that can\ntrigger a transaction commit, resulting in a deadlock. It would also\ntrigger the same type of deadlock in the unmount path. Possibly, it could\nalso introduce some other locking dependencies that lockdep would report.\r\n\r\nTo fix this call try_to_writeback_inodes_sb() instead of\nwriteback_inodes_sb(), because that will try to read lock sb-\u0026gt;s_umount\nand then will only call writeback_inodes_sb() if it was able to lock it.\nThis is fine because the cases where it can\u0026apos;t read lock sb-\u0026gt;s_umount\nare during a filesystem unmount or during a filesystem freeze - in those\ncases sb-\u0026gt;s_umount is write locked and sync_filesystem() is called, which\ncalls writeback_inodes_sb(). In other words, in all cases where we can\u0026apos;t\ntake a read lock on sb-\u0026gt;s_umount, writeback is already being triggered\nelsewhere.\r\n\r\nAn alternative would be to call btrfs_start_delalloc_roots() with a\nnumber of pages different from LONG_MAX, for example matching the number\nof delalloc bytes we currently have, in \n---truncated---(CVE-2022-48920)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnetfilter: nf_tables: unregister flowtable hooks on netns exit\r\n\r\nUnregister flowtable hooks before they are releases via\nnf_tables_flowtable_destroy() otherwise hook core reports UAF.\r\n\r\nBUG: KASAN: use-after-free in nf_hook_entries_grow+0x5a7/0x700 net/netfilter/core.c:142 net/netfilter/core.c:142\nRead of size 4 at addr ffff8880736f7438 by task syz-executor579/3666\r\n\r\nCPU: 0 PID: 3666 Comm: syz-executor579 Not tainted 5.16.0-rc5-syzkaller #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __dump_stack lib/dump_stack.c:88 [inline]\n __dump_stack lib/dump_stack.c:88 [inline] lib/dump_stack.c:106\n dump_stack_lvl+0x1dc/0x2d8 lib/dump_stack.c:106 lib/dump_stack.c:106\n print_address_description+0x65/0x380 mm/kasan/report.c:247 mm/kasan/report.c:247\n __kasan_report mm/kasan/report.c:433 [inline]\n __kasan_report mm/kasan/report.c:433 [inline] mm/kasan/report.c:450\n kasan_report+0x19a/0x1f0 mm/kasan/report.c:450 mm/kasan/report.c:450\n nf_hook_entries_grow+0x5a7/0x700 net/netfilter/core.c:142 net/netfilter/core.c:142\n __nf_register_net_hook+0x27e/0x8d0 net/netfilter/core.c:429 net/netfilter/core.c:429\n nf_register_net_hook+0xaa/0x180 net/netfilter/core.c:571 net/netfilter/core.c:571\n nft_register_flowtable_net_hooks+0x3c5/0x730 net/netfilter/nf_tables_api.c:7232 net/netfilter/nf_tables_api.c:7232\n nf_tables_newflowtable+0x2022/0x2cf0 net/netfilter/nf_tables_api.c:7430 net/netfilter/nf_tables_api.c:7430\n nfnetlink_rcv_batch net/netfilter/nfnetlink.c:513 [inline]\n nfnetlink_rcv_skb_batch net/netfilter/nfnetlink.c:634 [inline]\n nfnetlink_rcv_batch net/netfilter/nfnetlink.c:513 [inline] net/netfilter/nfnetlink.c:652\n nfnetlink_rcv_skb_batch net/netfilter/nfnetlink.c:634 [inline] net/netfilter/nfnetlink.c:652\n nfnetlink_rcv+0x10e6/0x2550 net/netfilter/nfnetlink.c:652 net/netfilter/nfnetlink.c:652\r\n\r\n__nft_release_hook() calls nft_unregister_flowtable_net_hooks() which\nonly unregisters the hooks, then after RCU grace period, it is\nguaranteed that no packets add new entries to the flowtable (no flow\noffload rules and flowtable hooks are reachable from packet path), so it\nis safe to call nf_flow_table_free() which cleans up the remaining\nentries from the flowtable (both software and hardware) and it unbinds\nthe flow_block.(CVE-2022-48935)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ngsmi: fix null-deref in gsmi_get_variable\r\n\r\nWe can get EFI variables without fetching the attribute, so we must\nallow for that in gsmi.\r\n\r\ncommit 859748255b43 (\u0026quot;efi: pstore: Omit efivars caching EFI varstore\naccess layer\u0026quot;) added a new get_variable call with attr=NULL, which\ntriggers panic in gsmi.(CVE-2023-52893)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nxhci: Fix null pointer dereference when host dies\r\n\r\nMake sure xhci_free_dev() and xhci_kill_endpoint_urbs() do not race\nand cause null pointer dereference when host suddenly dies.\r\n\r\nUsb core may call xhci_free_dev() which frees the xhci-\u0026gt;devs[slot_id]\nvirt device at the same time that xhci_kill_endpoint_urbs() tries to\nloop through all the device\u0026apos;s endpoints, checking if there are any\ncancelled urbs left to give back.\r\n\r\nhold the xhci spinlock while freeing the virt device(CVE-2023-52898)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nusb: xhci: Check endpoint is valid before dereferencing it\r\n\r\nWhen the host controller is not responding, all URBs queued to all\nendpoints need to be killed. This can cause a kernel panic if we\ndereference an invalid endpoint.\r\n\r\nFix this by using xhci_get_virt_ep() helper to find the endpoint and\nchecking if the endpoint is valid before dereferencing it.\r\n\r\n[233311.853271] xhci-hcd xhci-hcd.1.auto: xHCI host controller not responding, assume dead\n[233311.853393] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000e8\r\n\r\n[233311.853964] pc : xhci_hc_died+0x10c/0x270\n[233311.853971] lr : xhci_hc_died+0x1ac/0x270\r\n\r\n[233311.854077] Call trace:\n[233311.854085] xhci_hc_died+0x10c/0x270\n[233311.854093] xhci_stop_endpoint_command_watchdog+0x100/0x1a4\n[233311.854105] call_timer_fn+0x50/0x2d4\n[233311.854112] expire_timers+0xac/0x2e4\n[233311.854118] run_timer_softirq+0x300/0xabc\n[233311.854127] __do_softirq+0x148/0x528\n[233311.854135] irq_exit+0x194/0x1a8\n[233311.854143] __handle_domain_irq+0x164/0x1d0\n[233311.854149] gic_handle_irq.22273+0x10c/0x188\n[233311.854156] el1_irq+0xfc/0x1a8\n[233311.854175] lpm_cpuidle_enter+0x25c/0x418 [msm_pm]\n[233311.854185] cpuidle_enter_state+0x1f0/0x764\n[233311.854194] do_idle+0x594/0x6ac\n[233311.854201] cpu_startup_entry+0x7c/0x80\n[233311.854209] secondary_start_kernel+0x170/0x198(CVE-2023-52901)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nio_uring: lock overflowing for IOPOLL\r\n\r\nsyzbot reports an issue with overflow filling for IOPOLL:\r\n\r\nWARNING: CPU: 0 PID: 28 at io_uring/io_uring.c:734 io_cqring_event_overflow+0x1c0/0x230 io_uring/io_uring.c:734\nCPU: 0 PID: 28 Comm: kworker/u4:1 Not tainted 6.2.0-rc3-syzkaller-16369-g358a161a6a9e #0\nWorkqueue: events_unbound io_ring_exit_work\nCall trace:\n\u00a0io_cqring_event_overflow+0x1c0/0x230 io_uring/io_uring.c:734\n\u00a0io_req_cqe_overflow+0x5c/0x70 io_uring/io_uring.c:773\n\u00a0io_fill_cqe_req io_uring/io_uring.h:168 [inline]\n\u00a0io_do_iopoll+0x474/0x62c io_uring/rw.c:1065\n\u00a0io_iopoll_try_reap_events+0x6c/0x108 io_uring/io_uring.c:1513\n\u00a0io_uring_try_cancel_requests+0x13c/0x258 io_uring/io_uring.c:3056\n\u00a0io_ring_exit_work+0xec/0x390 io_uring/io_uring.c:2869\n\u00a0process_one_work+0x2d8/0x504 kernel/workqueue.c:2289\n\u00a0worker_thread+0x340/0x610 kernel/workqueue.c:2436\n\u00a0kthread+0x12c/0x158 kernel/kthread.c:376\n\u00a0ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:863\r\n\r\nThere is no real problem for normal IOPOLL as flush is also called with\nuring_lock taken, but it\u0026apos;s getting more complicated for IOPOLL|SQPOLL,\nfor which __io_cqring_overflow_flush() happens from the CQ waiting path.(CVE-2023-52903)\r\n\r\nA race condition was found in the Linux kernel\u0026apos;s drm/exynos device driver in\u00a0exynos_drm_crtc_atomic_disable() function. This can result in a null pointer dereference issue, possibly leading to a kernel panic or denial of service issue.\r\n\r\n\n(CVE-2024-22386)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nphonet: fix rtm_phonet_notify() skb allocation\r\n\r\nfill_route() stores three components in the skb:\r\n\r\n- struct rtmsg\n- RTA_DST (u8)\n- RTA_OIF (u32)\r\n\r\nTherefore, rtm_phonet_notify() should use\r\n\r\nNLMSG_ALIGN(sizeof(struct rtmsg)) +\nnla_total_size(1) +\nnla_total_size(4)(CVE-2024-36946)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nm68k: Fix spinlock race in kernel thread creation\r\n\r\nContext switching does take care to retain the correct lock owner across\nthe switch from \u0026apos;prev\u0026apos; to \u0026apos;next\u0026apos; tasks. This does rely on interrupts\nremaining disabled for the entire duration of the switch.\r\n\r\nThis condition is guaranteed for normal process creation and context\nswitching between already running processes, because both \u0026apos;prev\u0026apos; and\n\u0026apos;next\u0026apos; already have interrupts disabled in their saved copies of the\nstatus register.\r\n\r\nThe situation is different for newly created kernel threads. The status\nregister is set to PS_S in copy_thread(), which does leave the IPL at 0.\nUpon restoring the \u0026apos;next\u0026apos; thread\u0026apos;s status register in switch_to() aka\nresume(), interrupts then become enabled prematurely. resume() then\nreturns via ret_from_kernel_thread() and schedule_tail() where run queue\nlock is released (see finish_task_switch() and finish_lock_switch()).\r\n\r\nA timer interrupt calling scheduler_tick() before the lock is released\nin finish_task_switch() will find the lock already taken, with the\ncurrent task as lock owner. This causes a spinlock recursion warning as\nreported by Guenter Roeck.\r\n\r\nAs far as I can ascertain, this race has been opened in commit\n533e6903bea0 (\u0026quot;m68k: split ret_from_fork(), simplify kernel_thread()\u0026quot;)\nbut I haven\u0026apos;t done a detailed study of kernel history so it may well\npredate that commit.\r\n\r\nInterrupts cannot be disabled in the saved status register copy for\nkernel threads (init will complain about interrupts disabled when\nfinally starting user space). Disable interrupts temporarily when\nswitching the tasks\u0026apos; register sets in resume().\r\n\r\nNote that a simple oriw 0x700,%sr after restoring sr is not enough here\n- this leaves enough of a race for the \u0026apos;spinlock recursion\u0026apos; warning to\nstill be observed.\r\n\r\nTested on ARAnyM and qemu (Quadra 800 emulation).(CVE-2024-38613)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nipv6: sr: fix missing sk_buff release in seg6_input_core\r\n\r\nThe seg6_input() function is responsible for adding the SRH into a\npacket, delegating the operation to the seg6_input_core(). This function\nuses the skb_cow_head() to ensure that there is sufficient headroom in\nthe sk_buff for accommodating the link-layer header.\nIn the event that the skb_cow_header() function fails, the\nseg6_input_core() catches the error but it does not release the sk_buff,\nwhich will result in a memory leak.\r\n\r\nThis issue was introduced in commit af3b5158b89d (\u0026quot;ipv6: sr: fix BUG due\nto headroom too small after SRH push\u0026quot;) and persists even after commit\n7a3f5b0de364 (\u0026quot;netfilter: add netfilter hooks to SRv6 data plane\u0026quot;),\nwhere the entire seg6_input() code was refactored to deal with netfilter\nhooks.\r\n\r\nThe proposed patch addresses the identified memory leak by requiring the\nseg6_input_core() function to release the sk_buff in the event that\nskb_cow_head() fails.(CVE-2024-39490)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncrypto: hisilicon/sec - Fix memory leak for sec resource release\r\n\r\nThe AIV is one of the SEC resources. When releasing resources,\nit need to release the AIV resources at the same time.\nOtherwise, memory leakage occurs.\r\n\r\nThe aiv resource release is added to the sec resource release\nfunction.(CVE-2024-41002)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ns390/sclp: Fix sclp_init() cleanup on failure\r\n\r\nIf sclp_init() fails it only partially cleans up: if there are multiple\nfailing calls to sclp_init() sclp_state_change_event will be added several\ntimes to sclp_reg_list, which results in the following warning:\r\n\r\n------------[ cut here ]------------\nlist_add double add: new=000003ffe1598c10, prev=000003ffe1598bf0, next=000003ffe1598c10.\nWARNING: CPU: 0 PID: 1 at lib/list_debug.c:35 __list_add_valid_or_report+0xde/0xf8\nCPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.10.0-rc3\nKrnl PSW : 0404c00180000000 000003ffe0d6076a (__list_add_valid_or_report+0xe2/0xf8)\n R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3\n...\nCall Trace:\n [\u0026lt;000003ffe0d6076a\u0026gt;] __list_add_valid_or_report+0xe2/0xf8\n([\u0026lt;000003ffe0d60766\u0026gt;] __list_add_valid_or_report+0xde/0xf8)\n [\u0026lt;000003ffe0a8d37e\u0026gt;] sclp_init+0x40e/0x450\n [\u0026lt;000003ffe00009f2\u0026gt;] do_one_initcall+0x42/0x1e0\n [\u0026lt;000003ffe15b77a6\u0026gt;] do_initcalls+0x126/0x150\n [\u0026lt;000003ffe15b7a0a\u0026gt;] kernel_init_freeable+0x1ba/0x1f8\n [\u0026lt;000003ffe0d6650e\u0026gt;] kernel_init+0x2e/0x180\n [\u0026lt;000003ffe000301c\u0026gt;] __ret_from_fork+0x3c/0x60\n [\u0026lt;000003ffe0d759ca\u0026gt;] ret_from_fork+0xa/0x30\r\n\r\nFix this by removing sclp_state_change_event from sclp_reg_list when\nsclp_init() fails.(CVE-2024-41068)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Check pipe offset before setting vblank\r\n\r\npipe_ctx has a size of MAX_PIPES so checking its index before accessing\nthe array.\r\n\r\nThis fixes an OVERRUN issue reported by Coverity.(CVE-2024-42120)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Add NULL pointer check for kzalloc\r\n\r\n[Why \u0026amp; How]\nCheck return pointer of kzalloc before using it.(CVE-2024-42122)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nprotect the fetch of -\u0026gt;fd[fd] in do_dup2() from mispredictions\r\n\r\nboth callers have verified that fd is not greater than -\u0026gt;max_fds;\nhowever, misprediction might end up with\n tofree = fdt-\u0026gt;fd[fd];\nbeing speculatively executed. That\u0026apos;s wrong for the same reasons\nwhy it\u0026apos;s wrong in close_fd()/file_close_fd_locked(); the same\nsolution applies - array_index_nospec(fd, fdt-\u0026gt;max_fds) could differ\nfrom fd only in case of speculative execution on mispredicted path.(CVE-2024-42265)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/iucv: fix use after free in iucv_sock_close()\r\n\r\niucv_sever_path() is called from process context and from bh context.\niucv-\u0026gt;path is used as indicator whether somebody else is taking care of\nsevering the path (or it is already removed / never existed).\nThis needs to be done with atomic compare and swap, otherwise there is a\nsmall window where iucv_sock_close() will try to work with a path that has\nalready been severed and freed by iucv_callback_connrej() called by\niucv_tasklet_fn().\r\n\r\nExample:\n[452744.123844] Call Trace:\n[452744.123845] ([\u0026lt;0000001e87f03880\u0026gt;] 0x1e87f03880)\n[452744.123966] [\u0026lt;00000000d593001e\u0026gt;] iucv_path_sever+0x96/0x138\n[452744.124330] [\u0026lt;000003ff801ddbca\u0026gt;] iucv_sever_path+0xc2/0xd0 [af_iucv]\n[452744.124336] [\u0026lt;000003ff801e01b6\u0026gt;] iucv_sock_close+0xa6/0x310 [af_iucv]\n[452744.124341] [\u0026lt;000003ff801e08cc\u0026gt;] iucv_sock_release+0x3c/0xd0 [af_iucv]\n[452744.124345] [\u0026lt;00000000d574794e\u0026gt;] __sock_release+0x5e/0xe8\n[452744.124815] [\u0026lt;00000000d5747a0c\u0026gt;] sock_close+0x34/0x48\n[452744.124820] [\u0026lt;00000000d5421642\u0026gt;] __fput+0xba/0x268\n[452744.124826] [\u0026lt;00000000d51b382c\u0026gt;] task_work_run+0xbc/0xf0\n[452744.124832] [\u0026lt;00000000d5145710\u0026gt;] do_notify_resume+0x88/0x90\n[452744.124841] [\u0026lt;00000000d5978096\u0026gt;] system_call+0xe2/0x2c8\n[452744.125319] Last Breaking-Event-Address:\n[452744.125321] [\u0026lt;00000000d5930018\u0026gt;] iucv_path_sever+0x90/0x138\n[452744.125324]\n[452744.125325] Kernel panic - not syncing: Fatal exception in interrupt\r\n\r\nNote that bh_lock_sock() is not serializing the tasklet context against\nprocess context, because the check for sock_owned_by_user() and\ncorresponding handling is missing.\r\n\r\nIdeas for a future clean-up patch:\nA) Correct usage of bh_lock_sock() in tasklet context, as described in\nRe-enqueue, if needed. This may require adding return values to the\ntasklet functions and thus changes to all users of iucv.\r\n\r\nB) Change iucv tasklet into worker and use only lock_sock() in af_iucv.(CVE-2024-42271)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmISDN: Fix a use after free in hfcmulti_tx()\r\n\r\nDon\u0026apos;t dereference *sp after calling dev_kfree_skb(*sp).(CVE-2024-42280)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nbpf: Fix a segment issue when downgrading gso_size\r\n\r\nLinearize the skb when downgrading gso_size because it may trigger a\nBUG_ON() later when the skb is segmented as described in [1,2].(CVE-2024-42281)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ntipc: Return non-zero value from tipc_udp_addr2str() on error\r\n\r\ntipc_udp_addr2str() should return non-zero value if the UDP media\naddress is invalid. Otherwise, a buffer overflow access can occur in\ntipc_media_addr_printf(). Fix this by returning 1 on an invalid UDP\nmedia address.(CVE-2024-42284)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nRDMA/iwcm: Fix a use-after-free related to destroying CM IDs\r\n\r\niw_conn_req_handler() associates a new struct rdma_id_private (conn_id) with\nan existing struct iw_cm_id (cm_id) as follows:\r\n\r\n conn_id-\u0026gt;cm_id.iw = cm_id;\n cm_id-\u0026gt;context = conn_id;\n cm_id-\u0026gt;cm_handler = cma_iw_handler;\r\n\r\nrdma_destroy_id() frees both the cm_id and the struct rdma_id_private. Make\nsure that cm_work_handler() does not trigger a use-after-free by only\nfreeing of the struct rdma_id_private after all pending work has finished.(CVE-2024-42285)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nf2fs: fix to don\u0026apos;t dirty inode for readonly filesystem\r\n\r\nsyzbot reports f2fs bug as below:\r\n\r\nkernel BUG at fs/f2fs/inode.c:933!\nRIP: 0010:f2fs_evict_inode+0x1576/0x1590 fs/f2fs/inode.c:933\nCall Trace:\n evict+0x2a4/0x620 fs/inode.c:664\n dispose_list fs/inode.c:697 [inline]\n evict_inodes+0x5f8/0x690 fs/inode.c:747\n generic_shutdown_super+0x9d/0x2c0 fs/super.c:675\n kill_block_super+0x44/0x90 fs/super.c:1667\n kill_f2fs_super+0x303/0x3b0 fs/f2fs/super.c:4894\n deactivate_locked_super+0xc1/0x130 fs/super.c:484\n cleanup_mnt+0x426/0x4c0 fs/namespace.c:1256\n task_work_run+0x24a/0x300 kernel/task_work.c:180\n ptrace_notify+0x2cd/0x380 kernel/signal.c:2399\n ptrace_report_syscall include/linux/ptrace.h:411 [inline]\n ptrace_report_syscall_exit include/linux/ptrace.h:473 [inline]\n syscall_exit_work kernel/entry/common.c:251 [inline]\n syscall_exit_to_user_mode_prepare kernel/entry/common.c:278 [inline]\n __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline]\n syscall_exit_to_user_mode+0x15c/0x280 kernel/entry/common.c:296\n do_syscall_64+0x50/0x110 arch/x86/entry/common.c:88\n entry_SYSCALL_64_after_hwframe+0x63/0x6b\r\n\r\nThe root cause is:\n- do_sys_open\n - f2fs_lookup\n - __f2fs_find_entry\n - f2fs_i_depth_write\n - f2fs_mark_inode_dirty_sync\n - f2fs_dirty_inode\n - set_inode_flag(inode, FI_DIRTY_INODE)\r\n\r\n- umount\n - kill_f2fs_super\n - kill_block_super\n - generic_shutdown_super\n - sync_filesystem\n : sb is readonly, skip sync_filesystem()\n - evict_inodes\n - iput\n - f2fs_evict_inode\n - f2fs_bug_on(sbi, is_inode_flag_set(inode, FI_DIRTY_INODE))\n : trigger kernel panic\r\n\r\nWhen we try to repair i_current_depth in readonly filesystem, let\u0026apos;s\nskip dirty inode to avoid panic in later f2fs_evict_inode().(CVE-2024-42297)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\next4: check dot and dotdot of dx_root before making dir indexed\r\n\r\nSyzbot reports a issue as follows:\n============================================\nBUG: unable to handle page fault for address: ffffed11022e24fe\nPGD 23ffee067 P4D 23ffee067 PUD 0\nOops: Oops: 0000 [#1] PREEMPT SMP KASAN PTI\nCPU: 0 PID: 5079 Comm: syz-executor306 Not tainted 6.10.0-rc5-g55027e689933 #0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n make_indexed_dir+0xdaf/0x13c0 fs/ext4/namei.c:2341\n ext4_add_entry+0x222a/0x25d0 fs/ext4/namei.c:2451\n ext4_rename fs/ext4/namei.c:3936 [inline]\n ext4_rename2+0x26e5/0x4370 fs/ext4/namei.c:4214\n[...]\n============================================\r\n\r\nThe immediate cause of this problem is that there is only one valid dentry\nfor the block to be split during do_split, so split==0 results in out of\nbounds accesses to the map triggering the issue.\r\n\r\n do_split\n unsigned split\n dx_make_map\n count = 1\n split = count/2 = 0;\n continued = hash2 == map[split - 1].hash;\n ---\u0026gt; map[4294967295]\r\n\r\nThe maximum length of a filename is 255 and the minimum block size is 1024,\nso it is always guaranteed that the number of entries is greater than or\nequal to 2 when do_split() is called.\r\n\r\nBut syzbot\u0026apos;s crafted image has no dot and dotdot in dir, and the dentry\ndistribution in dirblock is as follows:\r\n\r\n bus dentry1 hole dentry2 free\n|xx--|xx-------------|...............|xx-------------|...............|\n0 12 (8+248)=256 268 256 524 (8+256)=264 788 236 1024\r\n\r\nSo when renaming dentry1 increases its name_len length by 1, neither hole\nnor free is sufficient to hold the new dentry, and make_indexed_dir() is\ncalled.\r\n\r\nIn make_indexed_dir() it is assumed that the first two entries of the\ndirblock must be dot and dotdot, so bus and dentry1 are left in dx_root\nbecause they are treated as dot and dotdot, and only dentry2 is moved\nto the new leaf block. That\u0026apos;s why count is equal to 1.\r\n\r\nTherefore add the ext4_check_dx_root() helper function to add more sanity\nchecks to dot and dotdot before starting the conversion to avoid the above\nissue.(CVE-2024-42305)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ndrm/amd/display: Check for NULL pointer\r\n\r\n[why \u0026amp; how]\nNeed to make sure plane_state is initialized\nbefore accessing its members.\r\n\r\n(cherry picked from commit 295d91cbc700651782a60572f83c24861607b648)(CVE-2024-42308)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nkvm: s390: Reject memory region operations for ucontrol VMs\r\n\r\nThis change rejects the KVM_SET_USER_MEMORY_REGION and\nKVM_SET_USER_MEMORY_REGION2 ioctls when called on a ucontrol VM.\nThis is necessary since ucontrol VMs have kvm-\u0026gt;arch.gmap set to 0 and\nwould thus result in a null pointer dereference further in.\nMemory management needs to be performed in userspace and using the\nioctls KVM_S390_UCAS_MAP and KVM_S390_UCAS_UNMAP.\r\n\r\nAlso improve s390 specific documentation for KVM_SET_USER_MEMORY_REGION\nand KVM_SET_USER_MEMORY_REGION2.\r\n\r\n[frankja@linux.ibm.com: commit message spelling fix, subject prefix fix](CVE-2024-43819)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\next4: fix infinite loop when replaying fast_commit\r\n\r\nWhen doing fast_commit replay an infinite loop may occur due to an\nuninitialized extent_status struct. ext4_ext_determine_insert_hole() does\nnot detect the replay and calls ext4_es_find_extent_range(), which will\nreturn immediately without initializing the \u0026apos;es\u0026apos; variable.\r\n\r\nBecause \u0026apos;es\u0026apos; contains garbage, an integer overflow may happen causing an\ninfinite loop in this function, easily reproducible using fstest generic/039.\r\n\r\nThis commit fixes this issue by unconditionally initializing the structure\nin function ext4_es_find_extent_range().\r\n\r\nThanks to Zhang Yi, for figuring out the real problem!(CVE-2024-43828)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmedia: mediatek: vcodec: Handle invalid decoder vsi\r\n\r\nHandle an invalid decoder vsi in vpu_dec_init to ensure the decoder vsi\nis valid for future use.(CVE-2024-43831)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\ncgroup/cpuset: Prevent UAF in proc_cpuset_show()\r\n\r\nAn UAF can happen when /proc/cpuset is read as reported in [1].\r\n\r\nThis can be reproduced by the following methods:\n1.add an mdelay(1000) before acquiring the cgroup_lock In the\n cgroup_path_ns function.\n2.$cat /proc/\u0026lt;pid\u0026gt;/cpuset repeatly.\n3.$mount -t cgroup -o cpuset cpuset /sys/fs/cgroup/cpuset/\n$umount /sys/fs/cgroup/cpuset/ repeatly.\r\n\r\nThe race that cause this bug can be shown as below:\r\n\r\n(umount)\t\t|\t(cat /proc/\u0026lt;pid\u0026gt;/cpuset)\ncss_release\t\t|\tproc_cpuset_show\ncss_release_work_fn\t|\tcss = task_get_css(tsk, cpuset_cgrp_id);\ncss_free_rwork_fn\t|\tcgroup_path_ns(css-\u0026gt;cgroup, ...);\ncgroup_destroy_root\t|\tmutex_lock(\u0026amp;cgroup_mutex);\nrebind_subsystems\t|\ncgroup_free_root \t|\n\t\t\t|\t// cgrp was freed, UAF\n\t\t\t|\tcgroup_path_ns_locked(cgrp,..);\r\n\r\nWhen the cpuset is initialized, the root node top_cpuset.css.cgrp\nwill point to \u0026amp;cgrp_dfl_root.cgrp. In cgroup v1, the mount operation will\nallocate cgroup_root, and top_cpuset.css.cgrp will point to the allocated\n\u0026amp;cgroup_root.cgrp. When the umount operation is executed,\ntop_cpuset.css.cgrp will be rebound to \u0026amp;cgrp_dfl_root.cgrp.\r\n\r\nThe problem is that when rebinding to cgrp_dfl_root, there are cases\nwhere the cgroup_root allocated by setting up the root for cgroup v1\nis cached. This could lead to a Use-After-Free (UAF) if it is\nsubsequently freed. The descendant cgroups of cgroup v1 can only be\nfreed after the css is released. However, the css of the root will never\nbe released, yet the cgroup_root should be freed when it is unmounted.\nThis means that obtaining a reference to the css of the root does\nnot guarantee that css.cgrp-\u0026gt;root will not be freed.\r\n\r\nFix this problem by using rcu_read_lock in proc_cpuset_show().\nAs cgroup_root is kfree_rcu after commit d23b5c577715\n(\u0026quot;cgroup: Make operations on the cgroup root_list RCU safe\u0026quot;),\ncss-\u0026gt;cgroup won\u0026apos;t be freed during the critical section.\nTo call cgroup_path_ns_locked, css_set_lock is needed, so it is safe to\nreplace task_get_css with task_css.\r\n\r\n[1] https://syzkaller.appspot.com/bug?extid=9b1ff7be974a403aa4cd(CVE-2024-43853)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nremoteproc: imx_rproc: Skip over memory region when node value is NULL\r\n\r\nIn imx_rproc_addr_init() \u0026quot;nph = of_count_phandle_with_args()\u0026quot; just counts\nnumber of phandles. But phandles may be empty. So of_parse_phandle() in\nthe parsing loop (0 \u0026lt; a \u0026lt; nph) may return NULL which is later dereferenced.\nAdjust this issue by adding NULL-return check.\r\n\r\nFound by Linux Verification Center (linuxtesting.org) with SVACE.\r\n\r\n[Fixed title to fit within the prescribed 70-75 charcters](CVE-2024-43860)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet: usb: qmi_wwan: fix memory leak for not ip packets\r\n\r\nFree the unused skb when not ip packets arrive.(CVE-2024-43861)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nnet/mlx5: Always drain health in shutdown callback\r\n\r\nThere is no point in recovery during device shutdown. if health\nwork started need to wait for it to avoid races and NULL pointer\naccess.\r\n\r\nHence, drain health WQ on shutdown callback.(CVE-2024-43866)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nwifi: cfg80211: handle 2x996 RU allocation in cfg80211_calculate_bitrate_he()\r\n\r\nCurrently NL80211_RATE_INFO_HE_RU_ALLOC_2x996 is not handled in\ncfg80211_calculate_bitrate_he(), leading to below warning:\r\n\r\nkernel: invalid HE MCS: bw:6, ru:6\nkernel: WARNING: CPU: 0 PID: 2312 at net/wireless/util.c:1501 cfg80211_calculate_bitrate_he+0x22b/0x270 [cfg80211]\r\n\r\nFix it by handling 2x996 RU allocation in the same way as 160 MHz bandwidth.(CVE-2024-43879)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nexec: Fix ToCToU between perm check and set-uid/gid usage\r\n\r\nWhen opening a file for exec via do_filp_open(), permission checking is\ndone against the file\u0026apos;s metadata at that moment, and on success, a file\npointer is passed back. Much later in the execve() code path, the file\nmetadata (specifically mode, uid, and gid) is used to determine if/how\nto set the uid and gid. However, those values may have changed since the\npermissions check, meaning the execution may gain unintended privileges.\r\n\r\nFor example, if a file could change permissions from executable and not\nset-id:\r\n\r\n---------x 1 root root 16048 Aug 7 13:16 target\r\n\r\nto set-id and non-executable:\r\n\r\n---S------ 1 root root 16048 Aug 7 13:16 target\r\n\r\nit is possible to gain root privileges when execution should have been\ndisallowed.\r\n\r\nWhile this race condition is rare in real-world scenarios, it has been\nobserved (and proven exploitable) when package managers are updating\nthe setuid bits of installed programs. Such files start with being\nworld-executable but then are adjusted to be group-exec with a set-uid\nbit. For example, \u0026quot;chmod o-x,u+s target\u0026quot; makes \u0026quot;target\u0026quot; executable only\nby uid \u0026quot;root\u0026quot; and gid \u0026quot;cdrom\u0026quot;, while also becoming setuid-root:\r\n\r\n-rwxr-xr-x 1 root cdrom 16048 Aug 7 13:16 target\r\n\r\nbecomes:\r\n\r\n-rwsr-xr-- 1 root cdrom 16048 Aug 7 13:16 target\r\n\r\nBut racing the chmod means users without group \u0026quot;cdrom\u0026quot; membership can\nget the permission to execute \u0026quot;target\u0026quot; just before the chmod, and when\nthe chmod finishes, the exec reaches brpm_fill_uid(), and performs the\nsetuid to root, violating the expressed authorization of \u0026quot;only cdrom\ngroup members can setuid to root\u0026quot;.\r\n\r\nRe-check that we still have execute permissions in case the metadata\nhas changed. It would be better to keep a copy from the perm-check time,\nbut until we can do that refactoring, the least-bad option is to do a\nfull inode_permission() call (under inode lock). It is understood that\nthis is safe against dead-locks, but hardly optimal.(CVE-2024-43882)",
"id": "OESA-2024-2080",
"modified": "2026-08-06T11:07:33Z",
"published": "2024-08-30T11:07:33Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2024-2080"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-47292"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-47504"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-47556"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48634"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48639"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48642"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48643"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48644"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48647"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48648"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48656"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48663"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48671"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48672"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48675"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48686"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48687"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48691"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48873"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48896"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48898"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48899"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48920"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-48935"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-52893"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-52898"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-52901"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-52903"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-22386"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-36946"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38613"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-39490"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-41002"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-41068"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42120"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42122"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42265"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42271"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42280"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42281"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42284"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42285"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42297"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42305"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42308"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43819"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43828"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43831"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43853"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43860"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43861"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43866"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43879"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-43882"
}
],
"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-47292",
"CVE-2021-47504",
"CVE-2021-47556",
"CVE-2022-48634",
"CVE-2022-48639",
"CVE-2022-48642",
"CVE-2022-48643",
"CVE-2022-48644",
"CVE-2022-48647",
"CVE-2022-48648",
"CVE-2022-48656",
"CVE-2022-48663",
"CVE-2022-48671",
"CVE-2022-48672",
"CVE-2022-48675",
"CVE-2022-48686",
"CVE-2022-48687",
"CVE-2022-48691",
"CVE-2022-48873",
"CVE-2022-48896",
"CVE-2022-48898",
"CVE-2022-48899",
"CVE-2022-48920",
"CVE-2022-48935",
"CVE-2023-52893",
"CVE-2023-52898",
"CVE-2023-52901",
"CVE-2023-52903",
"CVE-2024-22386",
"CVE-2024-36946",
"CVE-2024-38613",
"CVE-2024-39490",
"CVE-2024-41002",
"CVE-2024-41068",
"CVE-2024-42120",
"CVE-2024-42122",
"CVE-2024-42265",
"CVE-2024-42271",
"CVE-2024-42280",
"CVE-2024-42281",
"CVE-2024-42284",
"CVE-2024-42285",
"CVE-2024-42297",
"CVE-2024-42305",
"CVE-2024-42308",
"CVE-2024-43819",
"CVE-2024-43828",
"CVE-2024-43831",
"CVE-2024-43853",
"CVE-2024-43860",
"CVE-2024-43861",
"CVE-2024-43866",
"CVE-2024-43879",
"CVE-2024-43882"
]
}
OESA-2025-2802 (CVE-2024-38381)
Vulnerability from osv_openeuler – Published: 2025-12-12 11:09 – Updated: 2026-08-06 11:09 – Source websiteThe Linux Kernel, the operating system core itself.
Security Fix(es):
In the Linux kernel, the following vulnerability has been resolved:
nfc: nci: Fix uninit-value in nci_rx_work
syzbot reported the following uninit-value access issue [1]
nci_rx_work() parses received packet from ndev->rx_q. It should be validated header size, payload size and total packet size before processing the packet. If an invalid packet is detected, it should be silently discarded.(CVE-2024-38381)
In the Linux kernel, the following vulnerability has been resolved:net: ti: icssg_prueth: Fix NULL pointer dereference in prueth_probe()In the prueth_probe() function, if one of the calls to emac_phy_connect()fails due to of_phy_connect() returning NULL, then the subsequent call tophy_attached_info() will dereference a NULL pointer.Check the return code of emac_phy_connect and fail cleanly if there is anerror.(CVE-2024-38584)
In the Linux kernel, the following vulnerability has been resolved:cpufreq: exit() callback is optionalThe exit() callback is optional and shouldn t be called without checkinga valid pointer first.Also, we must clear freq_table pointer even if the exit() callback isn tpresent.(CVE-2024-38615)
In the Linux kernel, the following vulnerability has been resolved:serial: max3100: Update uart_driver_registered on driver removalThe removal of the last MAX3100 device triggers the removal ofthe driver. However, code doesn t update the respective globalvariable and after insmod — rmmod — insmod cycle the kerneloopses: max3100 spi-PRP0001:01: max3100_probe: adding port 0 BUG: kernel NULL pointer dereference, address: 0000000000000408 ... RIP: 0010:serial_core_register_port+0xa0/0x840 ... max3100_probe+0x1b6/0x280 [max3100] spi_probe+0x8d/0xb0Update the actual state so next time UART driver will be registeredagain.Hugo also noticed, that the error path in the probe also affectedby having the variable set, and not cleared. Instead of clearing itmove the assignment after the successfull uart_register_driver() call.(CVE-2024-38633)
In the Linux kernel, the following vulnerability has been resolved:
enic: Validate length of nl attributes in enic_set_vf_port
enic_set_vf_port assumes that the nl attribute IFLA_PORT_PROFILE is of length PORT_PROFILE_MAX and that the nl attributes IFLA_PORT_INSTANCE_UUID, IFLA_PORT_HOST_UUID are of length PORT_UUID_MAX. These attributes are validated (in the function do_setlink in rtnetlink.c) using the nla_policy ifla_port_policy. The policy defines IFLA_PORT_PROFILE as NLA_STRING, IFLA_PORT_INSTANCE_UUID as NLA_BINARY and IFLA_PORT_HOST_UUID as NLA_STRING. That means that the length validation using the policy is for the max size of the attributes and not on exact size so the length of these attributes might be less than the sizes that enic_set_vf_port expects. This might cause an out of bands read access in the memcpys of the data of these attributes in enic_set_vf_port.(CVE-2024-38659)
In the Linux kernel, the following vulnerability has been resolved:riscv: prevent pt_regs corruption for secondary idle threadsTop of the kernel thread stack should be reserved for pt_regs. Howeverthis 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 problemhas been noticed in some CPU hotplug tests with V enabled. The functionsmp_callin stored several registers on stack, corrupting top of pt_regsstructure including status field. As a result, kernel attempted to saveor restore inexistent V context.(CVE-2024-38667)
In the Linux kernel, the following vulnerability has been resolved:jfs: xattr: fix buffer overflow for invalid xattrWhen an xattr size is not what is expected, it is printed out to thekernel log in hex format as a form of debugging. But when that xattrsize is bigger than the expected size, printing it out can cause anaccess off the end of the buffer.Fix this all up by properly restricting the size of the debug hex dumpin the kernel log.(CVE-2024-40902)
In the Linux kernel, the following vulnerability has been resolved:
USB: class: cdc-wdm: Fix CPU lockup caused by excessive log messages
The syzbot fuzzer found that the interrupt-URB completion callback in the cdc-wdm driver was taking too long, and the driver's immediate resubmission of interrupt URBs with -EPROTO status combined with the dummy-hcd emulation to cause a CPU lockup:
cdc_wdm 1-1:1.0: nonzero urb status received: -71 cdc_wdm 1-1:1.0: wdm_int_callback - 0 bytes watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [syz-executor782:6625] CPU#0 Utilization every 4s during lockup: #1: 98% system, 0% softirq, 3% hardirq, 0% idle #2: 98% system, 0% softirq, 3% hardirq, 0% idle #3: 98% system, 0% softirq, 3% hardirq, 0% idle #4: 98% system, 0% softirq, 3% hardirq, 0% idle #5: 98% system, 1% softirq, 3% hardirq, 0% idle Modules linked in: irq event stamp: 73096 hardirqs last enabled at (73095): [<ffff80008037bc00>] console_emit_next_record kernel/printk/printk.c:2935 [inline] hardirqs last enabled at (73095): [<ffff80008037bc00>] console_flush_all+0x650/0xb74 kernel/printk/printk.c:2994 hardirqs last disabled at (73096): [<ffff80008af10b00>] __el1_irq arch/arm64/kernel/entry-common.c:533 [inline] hardirqs last disabled at (73096): [<ffff80008af10b00>] el1_interrupt+0x24/0x68 arch/arm64/kernel/entry-common.c:551 softirqs last enabled at (73048): [<ffff8000801ea530>] softirq_handle_end kernel/softirq.c:400 [inline] softirqs last enabled at (73048): [<ffff8000801ea530>] handle_softirqs+0xa60/0xc34 kernel/softirq.c:582 softirqs last disabled at (73043): [<ffff800080020de8>] __do_softirq+0x14/0x20 kernel/softirq.c:588 CPU: 0 PID: 6625 Comm: syz-executor782 Tainted: G W 6.10.0-rc2-syzkaller-g8867bbd4a056 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
Testing showed that the problem did not occur if the two error messages -- the first two lines above -- were removed; apparently adding material to the kernel log takes a surprisingly large amount of time.
In any case, the best approach for preventing these lockups and to avoid spamming the log with thousands of error messages per second is to ratelimit the two dev_err() calls. Therefore we replace them with dev_err_ratelimited().(CVE-2024-40904)
In the Linux kernel, the following vulnerability has been resolved:nvmet: always initialize cqe.resultThe spec doesn t mandate that the first two double words (aka results)for the command queue entry need to be set to 0 when they are notused (not specified). Though, the target implemention returns 0 for TCPand FC but not for RDMA.Let s make RDMA behave the same and thus explicitly initializing theresult field. This prevents leaking any data from the stack.(CVE-2024-41079)
In the Linux kernel, the following vulnerability has been resolved:drm/nouveau: fix null pointer dereference in nouveau_connector_get_modesIn nouveau_connector_get_modes(), the return value of drm_mode_duplicate()is assigned to mode, which will lead to a possible NULL pointerdereference on failure of drm_mode_duplicate(). Add a check to avoid npd.(CVE-2024-42101)
In the Linux kernel, the following vulnerability has been resolved:Revert mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again Patch series mm: Avoid possible overflows in dirty throttling .Dirty throttling logic assumes dirty limits in page units fit into32-bits. This patch series makes sure this is true (see patch 2/2 formore details).This patch (of 2):This reverts commit 9319b647902cbd5cc884ac08a8a6d54ce111fc78.The commit is broken in several ways. Firstly, the removed (u64) castfrom the multiplication will introduce a multiplication overflow on 32-bitarchs if wb_thresh * bg_thresh >= 1<<32 (which is actually common - thedefault settings with 4GB of RAM will trigger this). Secondly, thediv64_u64() is unnecessarily expensive on 32-bit archs. We havediv64_ul() in case we want to be safe & cheap. Thirdly, if dirtythresholds are larger than 1<<32 pages, then dirty balancing is going toblow up in many other spectacular ways anyway so trying to fix onepossible overflow is just moot.(CVE-2024-42102)
In the Linux kernel, the following vulnerability has been resolved:Revert sched/fair: Make sure to try to detach at least one movable task This reverts commit b0defa7ae03ecf91b8bfd10ede430cff12fcbd06.b0defa7ae03ec changed the load balancing logic to ignore env.max_loop ifall tasks examined to that point were pinned. The goal of the patch wasto make it more likely to be able to detach a task buried in a long listof pinned tasks. However, this has the unfortunate side effect ofcreating an O(n) iteration in detach_tasks(), as we now must fullyiterate every task on a cpu if all or most are pinned. Since this loadbalance code is done with rq lock held, and often in softirq context, itis very easy to trigger hard lockups. We observed such hard lockups witha user who affined O(10k) threads to a single cpu.When I discussed this with Vincent he initially suggested that we keepthe limit on the number of tasks to detach, but increase the number oftasks we can search. However, after some back and forth on the mailinglist, he recommended we instead revert the original patch, as it seemslikely no one was actually getting hit by the original issue.(CVE-2024-42245)
In the Linux kernel, the following vulnerability has been resolved:wireguard: allowedips: avoid unaligned 64-bit memory accessesOn the parisc platform, the kernel issues kernel warnings becauseswap_endian() tries to load a 128-bit IPv6 address from an unalignedmemory location: Kernel: unaligned access to 0x55f4688c in wg_allowedips_insert_v6+0x2c/0x80 [wireguard] (iir 0xf3010df) Kernel: unaligned access to 0x55f46884 in wg_allowedips_insert_v6+0x38/0x80 [wireguard] (iir 0xf2010dc)Avoid such unaligned memory accesses by instead using theget_unaligned_be64() helper macro.Jason: replace src[8] in original patch with src+8
In the Linux kernel, the following vulnerability has been resolved:f2fs: fix to don t dirty inode for readonly filesystemsyzbot reports f2fs bug as below:kernel BUG at fs/f2fs/inode.c:933!RIP: 0010:f2fs_evict_inode+0x1576/0x1590 fs/f2fs/inode.c:933Call Trace: evict+0x2a4/0x620 fs/inode.c:664 dispose_list fs/inode.c:697 [inline] evict_inodes+0x5f8/0x690 fs/inode.c:747 generic_shutdown_super+0x9d/0x2c0 fs/super.c:675 kill_block_super+0x44/0x90 fs/super.c:1667 kill_f2fs_super+0x303/0x3b0 fs/f2fs/super.c:4894 deactivate_locked_super+0xc1/0x130 fs/super.c:484 cleanup_mnt+0x426/0x4c0 fs/namespace.c:1256 task_work_run+0x24a/0x300 kernel/task_work.c:180 ptrace_notify+0x2cd/0x380 kernel/signal.c:2399 ptrace_report_syscall include/linux/ptrace.h:411 [inline] ptrace_report_syscall_exit include/linux/ptrace.h:473 [inline] syscall_exit_work kernel/entry/common.c:251 [inline] syscall_exit_to_user_mode_prepare kernel/entry/common.c:278 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline] syscall_exit_to_user_mode+0x15c/0x280 kernel/entry/common.c:296 do_syscall_64+0x50/0x110 arch/x86/entry/common.c:88 entry_SYSCALL_64_after_hwframe+0x63/0x6bThe root cause is:- do_sys_open - f2fs_lookup - __f2fs_find_entry - f2fs_i_depth_write - f2fs_mark_inode_dirty_sync - f2fs_dirty_inode - set_inode_flag(inode, FI_DIRTY_INODE)- umount - kill_f2fs_super - kill_block_super - generic_shutdown_super - sync_filesystem : sb is readonly, skip sync_filesystem() - evict_inodes - iput - f2fs_evict_inode - f2fs_bug_on(sbi, is_inode_flag_set(inode, FI_DIRTY_INODE)) : trigger kernel panicWhen we try to repair i_current_depth in readonly filesystem, let sskip dirty inode to avoid panic in later f2fs_evict_inode().(CVE-2024-42297)
In the Linux kernel, the following vulnerability has been resolved:vhost/scsi: null-ptr-dereference in vhost_scsi_get_req()Since commit 3f8ca2e115e5 ( vhost/scsi: Extract common handling codefrom control queue handler ) a null pointer dereference bug can betriggered when guest sends an SCSI AN request.In vhost_scsi_ctl_handle_vq(), vc.target is assigned with&v_req.tmf.lun[1] within a switch-case block and is then passed tovhost_scsi_get_req() which extracts vc->req and tpg. However, fora VIRTIO_SCSI_T_AN_* request, tpg is not required, so vc.target isset to NULL in this branch. Later, in vhost_scsi_get_req(),vc->target is dereferenced without being checked, leading to a nullpointer dereference bug. This bug can be triggered from guest.When this bug occurs, the vhost_worker process is killed while holdingvq->mutex and the corresponding tpg will remain occupiedindefinitely.Below is the KASAN report:Oops: general protection fault, probably for non-canonical address0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN NOPTIKASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]CPU: 1 PID: 840 Comm: poc Not tainted 6.10.0+ #1Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS1.16.3-debian-1.16.3-2 04/01/2014RIP: 0010:vhost_scsi_get_req+0x165/0x3a0Code: 00 fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 2b 02 00 0048 b8 00 00 00 00 00 fc ff df 4d 8b 65 30 4c 89 e2 48 c1 ea 03 <0f> b604 02 4c 89 e2 83 e2 07 38 d0 7f 08 84 c0 0f 85 be 01 00 00RSP: 0018:ffff888017affb50 EFLAGS: 00010246RAX: dffffc0000000000 RBX: ffff88801b000000 RCX: 0000000000000000RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff888017affcb8RBP: ffff888017affb80 R08: 0000000000000000 R09: 0000000000000000R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000R13: ffff888017affc88 R14: ffff888017affd1c R15: ffff888017993000FS: 000055556e076500(0000) GS:ffff88806b100000(0000) knlGS:0000000000000000CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033CR2: 00000000200027c0 CR3: 0000000010ed0004 CR4: 0000000000370ef0Call Trace: <TASK> ? show_regs+0x86/0xa0 ? die_addr+0x4b/0xd0 ? exc_general_protection+0x163/0x260 ? asm_exc_general_protection+0x27/0x30 ? vhost_scsi_get_req+0x165/0x3a0 vhost_scsi_ctl_handle_vq+0x2a4/0xca0 ? __pfx_vhost_scsi_ctl_handle_vq+0x10/0x10 ? __switch_to+0x721/0xeb0 ? __schedule+0xda5/0x5710 ? __kasan_check_write+0x14/0x30 ? _raw_spin_lock+0x82/0xf0 vhost_scsi_ctl_handle_kick+0x52/0x90 vhost_run_work_list+0x134/0x1b0 vhost_task_fn+0x121/0x350... </TASK>---[ end trace 0000000000000000 ]---Let s add a check in vhost_scsi_get_req.whitespace fixes
In the Linux kernel, the following vulnerability has been resolved:nfsd: map the EBADMSG to nfserr_io to avoid warningExt4 will throw -EBADMSG through ext4_readdir when a checksum erroroccurs, 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.qemu.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: Fix index out of bounds in degamma hardware format translationFixes index out of bounds issue incm_helper_translate_curve_to_degamma_hw_format function. The issuecould occur when the index i exceeds the number of transfer functionpoints (TRANSFER_FUNC_POINTS).The fix adds a check to ensure i is within bounds before accessing thetransfer function points. If i is out of bounds the function returnsfalse 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 <= s32maxdrivers/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 <= s32maxdrivers/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: Add null check for afb in amdgpu_dm_plane_handle_cursor_update (v2)This commit adds a null check for the afb variable in theamdgpu_dm_plane_handle_cursor_update function. Previously, afb wasassumed to be null, but was used later in the code without a null check.This could potentially lead to a null pointer dereference.Changes since v1:- Moved the null check for afb to the line where afb is used. (Alex)Fixes the below:drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_plane.c:1298 amdgpu_dm_plane_handle_cursor_update() error: we previously assumed afb could be null (see line 1252)(CVE-2024-49905)
In the Linux kernel, the following vulnerability has been resolved:fbdev: efifb: Register sysfs groups through driver coreThe driver core can register and cleanup sysfs groups already.Make use of that functionality to simplify the error handling andcleanup.Also avoid a UAF race during unregistering where the sysctl attributeswere usable after the info struct was freed.(CVE-2024-49925)
In the Linux kernel, the following vulnerability has been resolved:wifi: ath11k: fix array out-of-bound access in SoC statsCurrently, the ath11k_soc_dp_stats::hal_reo_error array is defined with amaximum size of DP_REO_DST_RING_MAX. However, the ath11k_dp_process_rx()function access ath11k_soc_dp_stats::hal_reo_error using the REOdestination SRNG ring ID, which is incorrect. SRNG ring ID differ fromnormal ring ID, and this usage leads to out-of-bounds array access. To fixthis issue, modify ath11k_dp_process_rx() to use the normal ring IDdirectly instead of the SRNG ring ID to avoid out-of-bounds array access.Tested-on: QCN9074 hw1.0 PCI WLAN.HK.2.7.0.1-01744-QCAHKSWPL_SILICONZ-1(CVE-2024-49930)
In the Linux kernel, the following vulnerability has been resolved:ACPI: PAD: fix crash in exit_round_robin()The kernel occasionally crashes in cpumask_clear_cpu(), which is calledwithin exit_round_robin(), because when executing clear_bit(nr, addr) withnr set to 0xffffffff, the address calculation may cause misalignment withinthe memory, leading to access to an invalid memory address.----------BUG: unable to handle kernel paging request at ffffffffe0740618 ...CPU: 3 PID: 2919323 Comm: acpi_pad/14 Kdump: loaded Tainted: G OE X --------- - - 4.18.0-425.19.2.el8_7.x86_64 #1 ...RIP: 0010:power_saving_thread+0x313/0x411 [acpi_pad]Code: 89 cd 48 89 d3 eb d1 48 c7 c7 55 70 72 c0 e8 64 86 b0 e4 c6 05 0d a1 02 00 01 e9 bc fd ff ff 45 89 e4 42 8b 04 a5 20 82 72 c0 <f0> 48 0f b3 05 f4 9c 01 00 42 c7 04 a5 20 82 72 c0 ff ff ff ff 31RSP: 0018:ff72a5d51fa77ec8 EFLAGS: 00010202RAX: 00000000ffffffff RBX: ff462981e5d8cb80 RCX: 0000000000000000RDX: 0000000000000000 RSI: 0000000000000246 RDI: 0000000000000246RBP: ff46297556959d80 R08: 0000000000000382 R09: ff46297c8d0f38d8R10: 0000000000000000 R11: 0000000000000001 R12: 000000000000000eR13: 0000000000000000 R14: ffffffffffffffff R15: 000000000000000eFS: 0000000000000000(0000) GS:ff46297a800c0000(0000) knlGS:0000000000000000CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033CR2: ffffffffe0740618 CR3: 0000007e20410004 CR4: 0000000000771ee0DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400PKRU: 55555554Call Trace: ? acpi_pad_add+0x120/0x120 [acpi_pad] kthread+0x10b/0x130 ? set_kthread_struct+0x50/0x50 ret_from_fork+0x1f/0x40 ...CR2: ffffffffe0740618crash> dis -lr ffffffffc0726923 .../usr/src/debug/kernel-4.18.0-425.19.2.el8_7/linux-4.18.0-425.19.2.el8_7.x86_64/./include/linux/cpumask.h: 1140xffffffffc0726918 <power_saving_thread+776>: mov %r12d,%r12d/usr/src/debug/kernel-4.18.0-425.19.2.el8_7/linux-4.18.0-425.19.2.el8_7.x86_64/./include/linux/cpumask.h: 3250xffffffffc072691b <power_saving_thread+779>: mov -0x3f8d7de0(,%r12,4),%eax/usr/src/debug/kernel-4.18.0-425.19.2.el8_7/linux-4.18.0-425.19.2.el8_7.x86_64/./arch/x86/include/asm/bitops.h: 800xffffffffc0726923 <power_saving_thread+787>: lock btr %rax,0x19cf4(%rip) # 0xffffffffc0740620 <pad_busy_cpus_bits>crash> px tsk_in_cpu[14]$66 = 0xffffffffcrash> px 0xffffffffc072692c+0x19cf4$99 = 0xffffffffc0740620crash> sym 0xffffffffc0740620ffffffffc0740620 (b) pad_busy_cpus_bits [acpi_pad]crash> px pad_busy_cpus_bits[0]$42 = 0xfffc0----------To fix this, ensure that tsk_in_cpu[tsk_index] != -1 before callingcpumask_clear_cpu() in exit_round_robin(), just as it is done inround_robin_cpu(). rjw: Subject edit, avoid updates to the same value
In the Linux kernel, the following vulnerability has been resolved:net: add more sanity checks to qdisc_pkt_len_init()One path takes care of SKB_GSO_DODGY, assumingskb->len is bigger than hdr_len.virtio_net_hdr_to_skb() does not fully dissect TCP headers,it only make sure it is at least 20 bytes.It is possible for an user to provide a malicious GSO packet,total length of 80 bytes.- 20 bytes of IPv4 header- 60 bytes TCP header- a small gso_size like 8virtio_net_hdr_to_skb() would declare this packet as a normalGSO packet, because it would see 40 bytes of payload,bigger than gso_size.We need to make detect this case to not underflowqdisc_skb_cb(skb)->pkt_len.(CVE-2024-49948)
In the Linux kernel, the following vulnerability has been resolved:net: avoid potential underflow in qdisc_pkt_len_init() with UFOAfter commit 7c6d2ecbda83 ( net: be more gentle about silly gsorequests coming from user ) virtio_net_hdr_to_skb() had sanity checkto detect malicious attempts from user space to cook a bad GSO packet.Then commit cf9acc90c80ec ( net: virtio_net_hdr_to_skb: counttransport header in UFO ) while fixing one issue, allowed user spaceto cook a GSO packet with the following characteristic :IPv4 SKB_GSO_UDP, gso_size=3, skb->len = 28.When this packet arrives in qdisc_pkt_len_init(), we end upwith hdr_len = 28 (IPv4 header + UDP header), matching skb->lenThen the following sets gso_segs to 0 :gso_segs = DIV_ROUND_UP(skb->len - hdr_len, shinfo->gso_size);Then later we set qdisc_skb_cb(skb)->pkt_len to back to zero :/qdisc_skb_cb(skb)->pkt_len += (gso_segs - 1) * hdr_len;This leads to the following crash in fq_codel [1]qdisc_pkt_len_init() is best effort, we only want an estimationof the bytes sent on the wire, not crashing the kernel.This patch is fixing this particular issue, a following oneadds more sanity checks for another potential bug.[1][ 70.724101] BUG: kernel NULL pointer dereference, address: 0000000000000000[ 70.724561] #PF: supervisor read access in kernel mode[ 70.724561] #PF: error_code(0x0000) - not-present page[ 70.724561] PGD 10ac61067 P4D 10ac61067 PUD 107ee2067 PMD 0[ 70.724561] Oops: Oops: 0000 [#1] SMP NOPTI[ 70.724561] CPU: 11 UID: 0 PID: 2163 Comm: b358537762 Not tainted 6.11.0-virtme #991[ 70.724561] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014[ 70.724561] RIP: 0010:fq_codel_enqueue (net/sched/sch_fq_codel.c:120 net/sched/sch_fq_codel.c:168 net/sched/sch_fq_codel.c:230) sch_fq_codel[ 70.724561] Code: 24 08 49 c1 e1 06 44 89 7c 24 18 45 31 ed 45 31 c0 31 ff 89 44 24 14 4c 03 8b 90 01 00 00 eb 04 39 ca 73 37 4d 8b 39 83 c7 01 <49> 8b 17 49 89 11 41 8b 57 28 45 8b 5f 34 49 c7 07 00 00 00 00 49All code======== 0: 24 08 and $0x8,%al 2: 49 c1 e1 06 shl $0x6,%r9 6: 44 89 7c 24 18 mov %r15d,0x18(%rsp) b: 45 31 ed xor %r13d,%r13d e: 45 31 c0 xor %r8d,%r8d 11: 31 ff xor %edi,%edi 13: 89 44 24 14 mov %eax,0x14(%rsp) 17: 4c 03 8b 90 01 00 00 add 0x190(%rbx),%r9 1e: eb 04 jmp 0x24 20: 39 ca cmp %ecx,%edx 22: 73 37 jae 0x5b 24: 4d 8b 39 mov (%r9),%r15 27: 83 c7 01 add $0x1,%edi 2a:* 49 8b 17 mov (%r15),%rdx <-- trapping instruction 2d: 49 89 11 mov %rdx,(%r9) 30: 41 8b 57 28 mov 0x28(%r15),%edx 34: 45 8b 5f 34 mov 0x34(%r15),%r11d 38: 49 c7 07 00 00 00 00 movq $0x0,(%r15) 3f: 49 rex.WBCode starting with the faulting instruction=========================================== 0: 49 8b 17 mov (%r15),%rdx 3: 49 89 11 mov %rdx,(%r9) 6: 41 8b 57 28 mov 0x28(%r15),%edx a: 45 8b 5f 34 mov 0x34(%r15),%r11d e: 49 c7 07 00 00 00 00 movq $0x0,(%r15) 15: 49 rex.WB[ 70.724561] RSP: 0018:ffff95ae85e6fb90 EFLAGS: 00000202[ 70.724561] RAX: 0000000002000000 RBX: ffff95ae841de000 RCX: 0000000000000000[ 70.724561] RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000001[ 70.724561] RBP: ffff95ae85e6fbf8 R08: 0000000000000000 R09: ffff95b710a30000[ 70.724561] R10: 0000000000000000 R11: bdf289445ce31881 R12: ffff95ae85e6fc58[ 70.724561] R13: 0000000000000000 R14: 0000000000000040 R15: 0000000000000000[ 70.724561] FS: 000000002c5c1380(0000) GS:ffff95bd7fcc0000(0000) knlGS:0000000000000000[ 70.724561] CS: 0010 DS: 0000 ES: 0000 C---truncated---(CVE-2024-49949)
In the Linux kernel, the following vulnerability has been resolved:Bluetooth: L2CAP: Fix uaf in l2cap_connect[Syzbot reported]BUG: KASAN: slab-use-after-free in l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949Read of size 8 at addr ffff8880241e9800 by task kworker/u9:0/54CPU: 0 UID: 0 PID: 54 Comm: kworker/u9:0 Not tainted 6.11.0-rc6-syzkaller-00268-g788220eee30d #0Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024Workqueue: hci2 hci_rx_workCall Trace: <TASK> __dump_stack lib/dump_stack.c:93 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:119 print_address_description mm/kasan/report.c:377 [inline] print_report+0xc3/0x620 mm/kasan/report.c:488 kasan_report+0xd9/0x110 mm/kasan/report.c:601 l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949 l2cap_connect_req net/bluetooth/l2cap_core.c:4080 [inline] l2cap_bredr_sig_cmd net/bluetooth/l2cap_core.c:4772 [inline] l2cap_sig_channel net/bluetooth/l2cap_core.c:5543 [inline] l2cap_recv_frame+0xf0b/0x8eb0 net/bluetooth/l2cap_core.c:6825 l2cap_recv_acldata+0x9b4/0xb70 net/bluetooth/l2cap_core.c:7514 hci_acldata_packet net/bluetooth/hci_core.c:3791 [inline] hci_rx_work+0xaab/0x1610 net/bluetooth/hci_core.c:4028 process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231 process_scheduled_works kernel/workqueue.c:3312 [inline] worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389 kthread+0x2c1/0x3a0 kernel/kthread.c:389 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244...Freed by task 5245: kasan_save_stack+0x33/0x60 mm/kasan/common.c:47 kasan_save_track+0x14/0x30 mm/kasan/common.c:68 kasan_save_free_info+0x3b/0x60 mm/kasan/generic.c:579 poison_slab_object+0xf7/0x160 mm/kasan/common.c:240 __kasan_slab_free+0x32/0x50 mm/kasan/common.c:256 kasan_slab_free include/linux/kasan.h:184 [inline] slab_free_hook mm/slub.c:2256 [inline] slab_free mm/slub.c:4477 [inline] kfree+0x12a/0x3b0 mm/slub.c:4598 l2cap_conn_free net/bluetooth/l2cap_core.c:1810 [inline] kref_put include/linux/kref.h:65 [inline] l2cap_conn_put net/bluetooth/l2cap_core.c:1822 [inline] l2cap_conn_del+0x59d/0x730 net/bluetooth/l2cap_core.c:1802 l2cap_connect_cfm+0x9e6/0xf80 net/bluetooth/l2cap_core.c:7241 hci_connect_cfm include/net/bluetooth/hci_core.h:1960 [inline] hci_conn_failed+0x1c3/0x370 net/bluetooth/hci_conn.c:1265 hci_abort_conn_sync+0x75a/0xb50 net/bluetooth/hci_sync.c:5583 abort_conn_sync+0x197/0x360 net/bluetooth/hci_conn.c:2917 hci_cmd_sync_work+0x1a4/0x410 net/bluetooth/hci_sync.c:328 process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231 process_scheduled_works kernel/workqueue.c:3312 [inline] worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389 kthread+0x2c1/0x3a0 kernel/kthread.c:389 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244(CVE-2024-49950)
In the Linux kernel, the following vulnerability has been resolved:ocfs2: fix null-ptr-deref when journal load failed.During the mounting process, if journal_reset() fails because of too shortjournal, then lead to jbd2_journal_load() fails with NULL j_sb_buffer. Subsequently, ocfs2_journal_shutdown() callsjbd2_journal_flush()->jbd2_cleanup_journal_tail()->__jbd2_update_log_tail()->jbd2_journal_update_sb_log_tail()->lock_buffer(journal->j_sb_buffer), resulting in a null-pointerdereference error.To resolve this issue, we should check the JBD2_LOADED flag to ensure thejournal was properly loaded. Additionally, use journal instead ofosb->journal directly to simplify the code.(CVE-2024-49957)
In the Linux kernel, the following vulnerability has been resolved:ACPICA: check null return of ACPI_ALLOCATE_ZEROED() in acpi_db_convert_to_package()ACPICA commit 4d4547cf13cca820ff7e0f859ba83e1a610b9fd0ACPI_ALLOCATE_ZEROED() may fail, elements might be NULL and will causeNULL pointer dereference later. rjw: Subject and changelog edits
In the Linux kernel, the following vulnerability has been resolved:static_call: Handle module init failure correctly in static_call_del_module()Module insertion invokes static_call_add_module() to initialize the staticcalls in a module. static_call_add_module() invokes __static_call_init(),which allocates a struct static_call_mod to either encapsulate the built-instatic call sites of the associated key into it so further modules can beadded or to append the module to the module chain.If that allocation fails the function returns with an error code and themodule core invokes static_call_del_module() to clean up eventually addedstatic_call_mod entries.This works correctly, when all keys used by the module were converted overto a module chain before the failure. If not then static_call_del_module()causes a #GP as it blindly assumes that key::mods points to a valid structstatic_call_mod.The problem is that key::mods is not a individual struct member of structstatic_call_key, it s part of a union to save space: union { / bit 0: 0 = mods, 1 = sites / unsigned long type; struct static_call_mod mods; struct static_call_site sites; };key::sites is a pointer to the list of built-in usage sites of the staticcall. The type of the pointer is differentiated by bit 0. A mods pointerhas the bit clear, the sites pointer has the bit set.As static_call_del_module() blidly assumes that the pointer is a validstatic_call_mod type, it fails to check for this failure case anddereferences the pointer to the list of built-in call sites, which isobviously bogus.Cure it by checking whether the key has a sites or a mods pointer.If it s a sites pointer then the key is not to be touched. As the sites arewalked in the same order as in __static_call_init() the site walk can beterminated because all subsequent sites have not been touched by the initcode due to the error exit.If it was converted before the allocation fail, then the inner loop whichsearches for a module match will find nothing.A fail in the second allocation in __static_call_init() is harmless anddoes not require special treatment. The first allocation succeeded andconverted the key to a module chain. That first entry has mod::mod == NULLand mod::next == NULL, so the inner loop of static_call_del_module() willneither find a module match nor a module chain. The next site in the walkwas either already converted, but can t match the module, or it will exitthe outer loop because it has a static_call_site pointer and not astatic_call_mod pointer.(CVE-2024-50002)
In the Linux kernel, the following vulnerability has been resolved:mac802154: Fix potential RCU dereference issue in mac802154_scan_workerIn the mac802154_scan_worker function, the scan_req->type field wasaccessed after the RCU read-side critical section was unlocked. Accordingto RCU usage rules, this is illegal and can lead to unpredictablebehavior, such as accessing memory that has been updated or causinguse-after-free issues.This possible bug was identified using a static analysis tool developedby myself, specifically designed to detect RCU-related issues.To address this, the scan_req->type value is now stored in a localvariable scan_req_type while still within the RCU read-side criticalsection. The scan_req_type is then used after the RCU lock is released,ensuring that the type value is safely accessed without violating RCUrules.(CVE-2024-50005)
In the Linux kernel, the following vulnerability has been resolved:
nilfs2: fix null-ptr-deref in block_touch_buffer tracepoint
Patch series "nilfs2: fix null-ptr-deref bugs on block tracepoints".
This series fixes null pointer dereference bugs that occur when using nilfs2 and two block-related tracepoints.
This patch (of 2):
It has been reported that when using "block:block_touch_buffer" tracepoint, touch_buffer() called from __nilfs_get_folio_block() causes a NULL pointer dereference, or a general protection fault when KASAN is enabled.
This happens because since the tracepoint was added in touch_buffer(), it references the dev_t member bh->b_bdev->bd_dev regardless of whether the buffer head has a pointer to a block_device structure. In the current implementation, the block_device structure is set after the function returns to the caller.
Here, touch_buffer() is used to mark the folio/page that owns the buffer head as accessed, but the common search helper for folio/page used by the caller function was optimized to mark the folio/page as accessed when it was reimplemented a long time ago, eliminating the need to call touch_buffer() here in the first place.
So this solves the issue by eliminating the touch_buffer() call itself.(CVE-2024-53131)
In the Linux kernel, the following vulnerability has been resolved:drm: adv7511: Fix use-after-free in adv7533_attach_dsi()The host_node pointer was assigned and freed in adv7533_parse_dt(), andlater, adv7533_attach_dsi() uses the same. Fix this use-after-free issueby dropping of_node_put() in adv7533_parse_dt() and calling of_node_put()in error path of probe() and also in the remove().(CVE-2024-57887)
In the Linux kernel, the following vulnerability has been resolved:ila: serialize calls to nf_register_net_hooks()syzbot found a race in ila_add_mapping() [1]commit 031ae72825ce ( ila: call nf_unregister_net_hooks() sooner )attempted to fix a similar issue.Looking at the syzbot repro, we have concurrent ILA_CMD_ADD commands.Add a mutex to make sure at most one thread is calling nf_register_net_hooks().[1] BUG: KASAN: slab-use-after-free in rht_key_hashfn include/linux/rhashtable.h:159 [inline] BUG: KASAN: slab-use-after-free in __rhashtable_lookup.constprop.0+0x426/0x550 include/linux/rhashtable.h:604Read of size 4 at addr ffff888028f40008 by task dhcpcd/5501CPU: 1 UID: 0 PID: 5501 Comm: dhcpcd Not tainted 6.13.0-rc4-syzkaller-00054-gd6ef8b40d075 #0Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024Call Trace: <IRQ> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xc3/0x620 mm/kasan/report.c:489 kasan_report+0xd9/0x110 mm/kasan/report.c:602 rht_key_hashfn include/linux/rhashtable.h:159 [inline] __rhashtable_lookup.constprop.0+0x426/0x550 include/linux/rhashtable.h:604 rhashtable_lookup include/linux/rhashtable.h:646 [inline] rhashtable_lookup_fast include/linux/rhashtable.h:672 [inline] ila_lookup_wildcards net/ipv6/ila/ila_xlat.c:127 [inline] ila_xlat_addr net/ipv6/ila/ila_xlat.c:652 [inline] ila_nf_input+0x1ee/0x620 net/ipv6/ila/ila_xlat.c:185 nf_hook_entry_hookfn include/linux/netfilter.h:154 [inline] nf_hook_slow+0xbb/0x200 net/netfilter/core.c:626 nf_hook.constprop.0+0x42e/0x750 include/linux/netfilter.h:269 NF_HOOK include/linux/netfilter.h:312 [inline] ipv6_rcv+0xa4/0x680 net/ipv6/ip6_input.c:309 __netif_receive_skb_one_core+0x12e/0x1e0 net/core/dev.c:5672 __netif_receive_skb+0x1d/0x160 net/core/dev.c:5785 process_backlog+0x443/0x15f0 net/core/dev.c:6117 __napi_poll.constprop.0+0xb7/0x550 net/core/dev.c:6883 napi_poll net/core/dev.c:6952 [inline] net_rx_action+0xa94/0x1010 net/core/dev.c:7074 handle_softirqs+0x213/0x8f0 kernel/softirq.c:561 __do_softirq kernel/softirq.c:595 [inline] invoke_softirq kernel/softirq.c:435 [inline] __irq_exit_rcu+0x109/0x170 kernel/softirq.c:662 irq_exit_rcu+0x9/0x30 kernel/softirq.c:678 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1049 [inline] sysvec_apic_timer_interrupt+0xa4/0xc0 arch/x86/kernel/apic/apic.c:1049(CVE-2024-57900)
In the Linux kernel, the following vulnerability has been resolved:
jfs: add check read-only before txBeginAnon() call
Added a read-only check before calling txBeginAnon in extAlloc
and extRecord. This prevents modification attempts on a read-only
mounted filesystem, avoiding potential errors or crashes.
Call trace: txBeginAnon+0xac/0x154 extAlloc+0xe8/0xdec fs/jfs/jfs_extent.c:78 jfs_get_block+0x340/0xb98 fs/jfs/inode.c:248 __block_write_begin_int+0x580/0x166c fs/buffer.c:2128 __block_write_begin fs/buffer.c:2177 [inline] block_write_begin+0x98/0x11c fs/buffer.c:2236 jfs_write_begin+0x44/0x88 fs/jfs/inode.c:299(CVE-2024-58095)
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix use-after-free in smb2_lock
If smb_lock->zero_len has value, ->llist of smb_lock is not delete and flock is old one. It will cause use-after-free on error handling routine.(CVE-2025-21945)
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Fix slab-use-after-free on hdcp_work
[Why] A slab-use-after-free is reported when HDCP is destroyed but the property_validate_dwork queue is still running.
[How] Cancel the delayed work when destroying workqueue.
(cherry picked from commit 725a04ba5a95e89c89633d4322430cfbca7ce128)(CVE-2025-21968)
In the Linux kernel, the following vulnerability has been resolved:
usb: xhci: Apply the link chain quirk on NEC isoc endpoints
Two clearly different specimens of NEC uPD720200 (one with start/stop bug, one without) were seen to cause IOMMU faults after some Missed Service Errors. Faulting address is immediately after a transfer ring segment and patched dynamic debug messages revealed that the MSE was received when waiting for a TD near the end of that segment:
[ 1.041954] xhci_hcd: Miss service interval error for slot 1 ep 2 expected TD DMA ffa08fe0 [ 1.042120] xhci_hcd: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffa09000 flags=0x0000] [ 1.042146] xhci_hcd: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffa09040 flags=0x0000]
It gets even funnier if the next page is a ring segment accessible to the HC. Below, it reports MSE in segment at ff1e8000, plows through a zero-filled page at ff1e9000 and starts reporting events for TRBs in page at ff1ea000 every microframe, instead of jumping to seg ff1e6000.
[ 7.041671] xhci_hcd: Miss service interval error for slot 1 ep 2 expected TD DMA ff1e8fe0 [ 7.041999] xhci_hcd: Miss service interval error for slot 1 ep 2 expected TD DMA ff1e8fe0 [ 7.042011] xhci_hcd: WARN: buffer overrun event for slot 1 ep 2 on endpoint [ 7.042028] xhci_hcd: All TDs skipped for slot 1 ep 2. Clear skip flag. [ 7.042134] xhci_hcd: WARN: buffer overrun event for slot 1 ep 2 on endpoint [ 7.042138] xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 31 [ 7.042144] xhci_hcd: Looking for event-dma 00000000ff1ea040 trb-start 00000000ff1e6820 trb-end 00000000ff1e6820 [ 7.042259] xhci_hcd: WARN: buffer overrun event for slot 1 ep 2 on endpoint [ 7.042262] xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 31 [ 7.042266] xhci_hcd: Looking for event-dma 00000000ff1ea050 trb-start 00000000ff1e6820 trb-end 00000000ff1e6820
At some point completion events change from Isoch Buffer Overrun to Short Packet and the HC finally finds cycle bit mismatch in ff1ec000.
[ 7.098130] xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [ 7.098132] xhci_hcd: Looking for event-dma 00000000ff1ecc50 trb-start 00000000ff1e6820 trb-end 00000000ff1e6820 [ 7.098254] xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [ 7.098256] xhci_hcd: Looking for event-dma 00000000ff1ecc60 trb-start 00000000ff1e6820 trb-end 00000000ff1e6820 [ 7.098379] xhci_hcd: Overrun event on slot 1 ep 2
It's possible that data from the isochronous device were written to random buffers of pending TDs on other endpoints (either IN or OUT), other devices or even other HCs in the same IOMMU domain.
Lastly, an error from a different USB device on another HC. Was it caused by the above? I don't know, but it may have been. The disk was working without any other issues and generated PCIe traffic to starve the NEC of upstream BW and trigger those MSEs. The two HCs shared one x1 slot by means of a commercial "PCIe splitter" board.
[ 7.162604] usb 10-2: reset SuperSpeed USB device number 3 using xhci_hcd [ 7.178990] sd 9:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=0s [ 7.179001] sd 9:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 04 02 ae 00 00 02 00 00 [ 7.179004] I/O error, dev sdb, sector 67284480 op 0x0:(READ) flags 0x80700 phys_seg 5 prio class 0
Fortunately, it appears that this ridiculous bug is avoided by setting the chain bit of Link TRBs on isochronous rings. Other ancient HCs are known which also expect the bit to be set and they ignore Link TRBs if it's not. Reportedly, 0.95 spec guaranteed that the bit is set.
The bandwidth-starved NEC HC running a 32KB/uframe UVC endpoint reports tens of MSEs per second and runs into the bug within seconds. Chaining Link TRBs allows the same workload to run for many minutes, many times.
No ne ---truncated---(CVE-2025-22022)
In the Linux kernel, the following vulnerability has been resolved:
nfsd: put dl_stid if fail to queue dl_recall
Before calling nfsd4_run_cb to queue dl_recall to the callback_wq, we increment the reference count of dl_stid. We expect that after the corresponding work_struct is processed, the reference count of dl_stid will be decremented through the callback function nfsd4_cb_recall_release. However, if the call to nfsd4_run_cb fails, the incremented reference count of dl_stid will not be decremented correspondingly, leading to the following nfs4_stid leak: unreferenced object 0xffff88812067b578 (size 344): comm "nfsd", pid 2761, jiffies 4295044002 (age 5541.241s) hex dump (first 32 bytes): 01 00 00 00 6b 6b 6b 6b b8 02 c0 e2 81 88 ff ff ....kkkk........ 00 6b 6b 6b 6b 6b 6b 6b 00 00 00 00 ad 4e ad de .kkkkkkk.....N.. backtrace: kmem_cache_alloc+0x4b9/0x700 nfsd4_process_open1+0x34/0x300 nfsd4_open+0x2d1/0x9d0 nfsd4_proc_compound+0x7a2/0xe30 nfsd_dispatch+0x241/0x3e0 svc_process_common+0x5d3/0xcc0 svc_process+0x2a3/0x320 nfsd+0x180/0x2e0 kthread+0x199/0x1d0 ret_from_fork+0x30/0x50 ret_from_fork_asm+0x1b/0x30 unreferenced object 0xffff8881499f4d28 (size 368): comm "nfsd", pid 2761, jiffies 4295044005 (age 5541.239s) hex dump (first 32 bytes): 01 00 00 00 00 00 00 00 30 4d 9f 49 81 88 ff ff ........0M.I.... 30 4d 9f 49 81 88 ff ff 20 00 00 00 01 00 00 00 0M.I.... ....... backtrace: kmem_cache_alloc+0x4b9/0x700 nfs4_alloc_stid+0x29/0x210 alloc_init_deleg+0x92/0x2e0 nfs4_set_delegation+0x284/0xc00 nfs4_open_delegation+0x216/0x3f0 nfsd4_process_open2+0x2b3/0xee0 nfsd4_open+0x770/0x9d0 nfsd4_proc_compound+0x7a2/0xe30 nfsd_dispatch+0x241/0x3e0 svc_process_common+0x5d3/0xcc0 svc_process+0x2a3/0x320 nfsd+0x180/0x2e0 kthread+0x199/0x1d0 ret_from_fork+0x30/0x50 ret_from_fork_asm+0x1b/0x30 Fix it by checking the result of nfsd4_run_cb and call nfs4_put_stid if fail to queue dl_recall.(CVE-2025-22025)
In the Linux kernel, the following vulnerability has been resolved:
nfsd: don't ignore the return code of svc_proc_register()
Currently, nfsd_proc_stat_init() ignores the return value of svc_proc_register(). If the procfile creation fails, then the kernel will WARN when it tries to remove the entry later.
Fix nfsd_proc_stat_init() to return the same type of pointer as svc_proc_register(), and fix up nfsd_net_init() to check that and fail the nfsd_net construction if it occurs.
svc_proc_register() can fail if the dentry can't be allocated, or if an identical dentry already exists. The second case is pretty unlikely in the nfsd_net construction codepath, so if this happens, return -ENOMEM.(CVE-2025-22026)
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix overflow in dacloffset bounds check
The dacloffset field was originally typed as int and used in an unchecked addition, which could overflow and bypass the existing bounds check in both smb_check_perm_dacl() and smb_inherit_dacl().
This could result in out-of-bounds memory access and a kernel crash when dereferencing the DACL pointer.
This patch converts dacloffset to unsigned int and uses check_add_overflow() to validate access to the DACL.(CVE-2025-22039)
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: add bounds check for create lease context
Add missing bounds check for create lease context.(CVE-2025-22042)
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: add bounds check for durable handle context
Add missing bounds check for durable handle context.(CVE-2025-22043)
In the Linux kernel, the following vulnerability has been resolved:
wifi: ath11k: update channel list in reg notifier instead reg worker
Currently when ath11k gets a new channel list, it will be processed according to the following steps: 1. update new channel list to cfg80211 and queue reg_work. 2. cfg80211 handles new channel list during reg_work. 3. update cfg80211's handled channel list to firmware by ath11k_reg_update_chan_list().
But ath11k will immediately execute step 3 after reg_work is just queued. Since step 2 is asynchronous, cfg80211 may not have completed handling the new channel list, which may leading to an out-of-bounds write error: BUG: KASAN: slab-out-of-bounds in ath11k_reg_update_chan_list Call Trace: ath11k_reg_update_chan_list+0xbfe/0xfe0 [ath11k] kfree+0x109/0x3a0 ath11k_regd_update+0x1cf/0x350 [ath11k] ath11k_regd_update_work+0x14/0x20 [ath11k] process_one_work+0xe35/0x14c0
Should ensure step 2 is completely done before executing step 3. Thus Wen raised patch[1]. When flag NL80211_REGDOM_SET_BY_DRIVER is set, cfg80211 will notify ath11k after step 2 is done.
So enable the flag NL80211_REGDOM_SET_BY_DRIVER then cfg80211 will notify ath11k after step 2 is done. At this time, there will be no KASAN bug during the execution of the step 3.
[1] https://patchwork.kernel.org/project/linux-wireless/patch/(CVE-2025-23133)
In the Linux kernel, the following vulnerability has been resolved:
riscv: uprobes: Add missing fence.i after building the XOL buffer
The XOL (execute out-of-line) buffer is used to single-step the replaced instruction(s) for uprobes. The RISC-V port was missing a proper fence.i (i$ flushing) after constructing the XOL buffer, which can result in incorrect execution of stale/broken instructions.
This was found running the BPF selftests "test_progs: uprobe_autoattach, attach_probe" on the Spacemit K1/X60, where the uprobes tests randomly blew up.(CVE-2025-37822)
In the Linux kernel, the following vulnerability has been resolved:
scsi: mpi3mr: Synchronous access b/w reset and tm thread for reply queue
When the task management thread processes reply queues while the reset thread resets them, the task management thread accesses an invalid queue ID (0xFFFF), set by the reset thread, which points to unallocated memory, causing a crash.
Add flag 'io_admin_reset_sync' to synchronize access between the reset, I/O, and admin threads. Before a reset, the reset handler sets this flag to block I/O and admin processing threads. If any thread bypasses the initial check, the reset thread waits up to 10 seconds for processing to finish. If the wait exceeds 10 seconds, the controller is marked as unrecoverable.(CVE-2025-37861)
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix use-after-free in session logoff
The sess->user object can currently be in use by another thread, for example if another connection has sent a session setup request to bind to the session being free'd. The handler for that connection could be in the smb2_sess_setup function which makes use of sess->user.(CVE-2025-37899)
In the Linux kernel, the following vulnerability has been resolved:
wifi: cfg80211: fix out-of-bounds access during multi-link element defragmentation
Currently during the multi-link element defragmentation process, the multi-link element length added to the total IEs length when calculating the length of remaining IEs after the multi-link element in cfg80211_defrag_mle(). This could lead to out-of-bounds access if the multi-link element or its corresponding fragment elements are the last elements in the IEs buffer.
To address this issue, correctly calculate the remaining IEs length by deducting the multi-link element end offset from total IEs end offset.(CVE-2025-37973)
In the Linux kernel, the following vulnerability has been resolved:
usb: typec: ucsi: displayport: Fix NULL pointer access
This patch ensures that the UCSI driver waits for all pending tasks in the ucsi_displayport_work workqueue to finish executing before proceeding with the partner removal.(CVE-2025-37994)
In the Linux kernel, the following vulnerability has been resolved:
netfilter: ipset: fix region locking in hash types
Region locking introduced in v5.6-rc4 contained three macros to handle the region locks: ahash_bucket_start(), ahash_bucket_end() which gave back the start and end hash bucket values belonging to a given region lock and ahash_region() which should give back the region lock belonging to a given hash bucket. The latter was incorrect which can lead to a race condition between the garbage collector and adding new elements when a hash type of set is defined with timeouts.(CVE-2025-37997)
In the Linux kernel, the following vulnerability has been resolved:
dmaengine: ti: k3-udma: Add missing locking
Recent kernels complain about a missing lock in k3-udma.c when the lock validator is enabled:
[ 4.128073] WARNING: CPU: 0 PID: 746 at drivers/dma/ti/../virt-dma.h:169 udma_start.isra.0+0x34/0x238 [ 4.137352] CPU: 0 UID: 0 PID: 746 Comm: kworker/0:3 Not tainted 6.12.9-arm64 #28 [ 4.144867] Hardware name: pp-v12 (DT) [ 4.148648] Workqueue: events udma_check_tx_completion [ 4.153841] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 4.160834] pc : udma_start.isra.0+0x34/0x238 [ 4.165227] lr : udma_start.isra.0+0x30/0x238 [ 4.169618] sp : ffffffc083cabcf0 [ 4.172963] x29: ffffffc083cabcf0 x28: 0000000000000000 x27: ffffff800001b005 [ 4.180167] x26: ffffffc0812f0000 x25: 0000000000000000 x24: 0000000000000000 [ 4.187370] x23: 0000000000000001 x22: 00000000e21eabe9 x21: ffffff8000fa0670 [ 4.194571] x20: ffffff8001b6bf00 x19: ffffff8000fa0430 x18: ffffffc083b95030 [ 4.201773] x17: 0000000000000000 x16: 00000000f0000000 x15: 0000000000000048 [ 4.208976] x14: 0000000000000048 x13: 0000000000000000 x12: 0000000000000001 [ 4.216179] x11: ffffffc08151a240 x10: 0000000000003ea1 x9 : ffffffc08046ab68 [ 4.223381] x8 : ffffffc083cabac0 x7 : ffffffc081df3718 x6 : 0000000000029fc8 [ 4.230583] x5 : ffffffc0817ee6d8 x4 : 0000000000000bc0 x3 : 0000000000000000 [ 4.237784] x2 : 0000000000000000 x1 : 00000000001fffff x0 : 0000000000000000 [ 4.244986] Call trace: [ 4.247463] udma_start.isra.0+0x34/0x238 [ 4.251509] udma_check_tx_completion+0xd0/0xdc [ 4.256076] process_one_work+0x244/0x3fc [ 4.260129] process_scheduled_works+0x6c/0x74 [ 4.264610] worker_thread+0x150/0x1dc [ 4.268398] kthread+0xd8/0xe8 [ 4.271492] ret_from_fork+0x10/0x20 [ 4.275107] irq event stamp: 220 [ 4.278363] hardirqs last enabled at (219): [<ffffffc080a27c7c>] _raw_spin_unlock_irq+0x38/0x50 [ 4.287183] hardirqs last disabled at (220): [<ffffffc080a1c154>] el1_dbg+0x24/0x50 [ 4.294879] softirqs last enabled at (182): [<ffffffc080037e68>] handle_softirqs+0x1c0/0x3cc [ 4.303437] softirqs last disabled at (177): [<ffffffc080010170>] __do_softirq+0x1c/0x28 [ 4.311559] ---[ end trace 0000000000000000 ]---
This commit adds the missing locking.(CVE-2025-38005)
In the Linux kernel, the following vulnerability has been resolved:
__legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock
... or we risk stealing final mntput from sync umount - raising mnt_count after umount(2) has verified that victim is not busy, but before it has set MNT_SYNC_UMOUNT; in that case __legitimize_mnt() doesn't see that it's safe to quietly undo mnt_count increment and leaves dropping the reference to caller, where it'll be a full-blown mntput().
Check under mount_lock is needed; leaving the current one done before taking that makes no sense - it's nowhere near common enough to bother with.(CVE-2025-38058)
In the Linux kernel, the following vulnerability has been resolved:
x86/mm: Check return value from memblock_phys_alloc_range()
At least with CONFIG_PHYSICAL_START=0x100000, if there is < 4 MiB of contiguous free memory available at this point, the kernel will crash and burn because memblock_phys_alloc_range() returns 0 on failure, which leads memblock_phys_free() to throw the first 4 MiB of physical memory to the wolves.
At a minimum it should fail gracefully with a meaningful diagnostic, but in fact everything seems to work fine without the weird reserve allocation.(CVE-2025-38071)
In the Linux kernel, the following vulnerability has been resolved:
net/mlx5: Fix ECVF vports unload on shutdown flow
Fix shutdown flow UAF when a virtual function is created on the embedded chip (ECVF) of a BlueField device. In such case the vport acl ingress table is not properly destroyed.
ECVF functionality is independent of ecpf_vport_exists capability and thus functions mlx5_eswitch_(enable|disable)_pf_vf_vports() should not test it when enabling/disabling ECVF vports.
kernel log: [] refcount_t: underflow; use-after-free. [] WARNING: CPU: 3 PID: 1 at lib/refcount.c:28 refcount_warn_saturate+0x124/0x220
[] Call trace: [] refcount_warn_saturate+0x124/0x220 [] tree_put_node+0x164/0x1e0 [mlx5_core] [] mlx5_destroy_flow_table+0x98/0x2c0 [mlx5_core] [] esw_acl_ingress_table_destroy+0x28/0x40 [mlx5_core] [] esw_acl_ingress_lgcy_cleanup+0x80/0xf4 [mlx5_core] [] esw_legacy_vport_acl_cleanup+0x44/0x60 [mlx5_core] [] esw_vport_cleanup+0x64/0x90 [mlx5_core] [] mlx5_esw_vport_disable+0xc0/0x1d0 [mlx5_core] [] mlx5_eswitch_unload_ec_vf_vports+0xcc/0x150 [mlx5_core] [] mlx5_eswitch_disable_sriov+0x198/0x2a0 [mlx5_core] [] mlx5_device_disable_sriov+0xb8/0x1e0 [mlx5_core] [] mlx5_sriov_detach+0x40/0x50 [mlx5_core] [] mlx5_unload+0x40/0xc4 [mlx5_core] [] mlx5_unload_one_devl_locked+0x6c/0xe4 [mlx5_core] [] mlx5_unload_one+0x3c/0x60 [mlx5_core] [] shutdown+0x7c/0xa4 [mlx5_core] [] pci_device_shutdown+0x3c/0xa0 [] device_shutdown+0x170/0x340 [] __do_sys_reboot+0x1f4/0x2a0 [] __arm64_sys_reboot+0x2c/0x40 [] invoke_syscall+0x78/0x100 [] el0_svc_common.constprop.0+0x54/0x184 [] do_el0_svc+0x30/0xac [] el0_svc+0x48/0x160 [] el0t_64_sync_handler+0xa4/0x12c [] el0t_64_sync+0x1a4/0x1a8 [] --[ end trace 9c4601d68c70030e ]---(CVE-2025-38109)
In the Linux kernel, the following vulnerability has been resolved:
nfsd: Initialize ssc before laundromat_work to prevent NULL dereference
In nfs4_state_start_net(), laundromat_work may access nfsd_ssc through nfs4_laundromat -> nfsd4_ssc_expire_umount. If nfsd_ssc isn't initialized, this can cause NULL pointer dereference.
Normally the delayed start of laundromat_work allows sufficient time for nfsd_ssc initialization to complete. However, when the kernel waits too long for userspace responses (e.g. in nfs4_state_start_net -> nfsd4_end_grace -> nfsd4_record_grace_done -> nfsd4_cld_grace_done -> cld_pipe_upcall -> __cld_pipe_upcall -> wait_for_completion path), the delayed work may start before nfsd_ssc initialization finishes.
Fix this by moving nfsd_ssc initialization before starting laundromat_work.(CVE-2025-38231)
In the Linux kernel, the following vulnerability has been resolved:
kernfs: Relax constraint in draining guard
The active reference lifecycle provides the break/unbreak mechanism but the active reference is not truly active after unbreak -- callers don't use it afterwards but it's important for proper pairing of kn->active counting. Assuming this mechanism is in place, the WARN check in kernfs_should_drain_open_files() is too sensitive -- it may transiently catch those (rightful) callers between kernfs_unbreak_active_protection() and kernfs_put_active() as found out by Chen Ridong:
kernfs_remove_by_name_ns kernfs_get_active // active=1
__kernfs_remove // active=0x80000002
kernfs_drain ...
wait_event
//waiting (active == 0x80000001)
kernfs_break_active_protection
// active = 0x80000001
// continue
kernfs_unbreak_active_protection
// active = 0x80000002
...
kernfs_should_drain_open_files
// warning occurs
kernfs_put_active
To avoid the false positives (mind panic_on_warn) remove the check altogether. (This is meant as quick fix, I think active reference break/unbreak may be simplified with larger rework.)(CVE-2025-38282)
In the Linux kernel, the following vulnerability has been resolved:
net/sched: Always pass notifications when child class becomes empty
Certain classful qdiscs may invoke their classes' dequeue handler on an enqueue operation. This may unexpectedly empty the child qdisc and thus make an in-flight class passive via qlen_notify(). Most qdiscs do not expect such behaviour at this point in time and may re-activate the class eventually anyways which will lead to a use-after-free.
The referenced fix commit attempted to fix this behavior for the HFSC case by moving the backlog accounting around, though this turned out to be incomplete since the parent's parent may run into the issue too. The following reproducer demonstrates this use-after-free:
tc qdisc add dev lo root handle 1: drr
tc filter add dev lo parent 1: basic classid 1:1
tc class add dev lo parent 1: classid 1:1 drr
tc qdisc add dev lo parent 1:1 handle 2: hfsc def 1
tc class add dev lo parent 2: classid 2:1 hfsc rt m1 8 d 1 m2 0
tc qdisc add dev lo parent 2:1 handle 3: netem
tc qdisc add dev lo parent 3:1 handle 4: blackhole
echo 1 | socat -u STDIN UDP4-DATAGRAM:127.0.0.1:8888
tc class delete dev lo classid 1:1
echo 1 | socat -u STDIN UDP4-DATAGRAM:127.0.0.1:8888
Since backlog accounting issues leading to a use-after-frees on stale class pointers is a recurring pattern at this point, this patch takes a different approach. Instead of trying to fix the accounting, the patch ensures that qdisc_tree_reduce_backlog always calls qlen_notify when the child qdisc is empty. This solves the problem because deletion of qdiscs always involves a call to qdisc_reset() and / or qdisc_purge_queue() which ultimately resets its qlen to 0 thus causing the following qdisc_tree_reduce_backlog() to report to the parent. Note that this may call qlen_notify on passive classes multiple times. This is not a problem after the recent patch series that made all the classful qdiscs qlen_notify() handlers idempotent.(CVE-2025-38350)
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Check dce_hwseq before dereferencing it
[WHAT]
hws was checked for null earlier in dce110_blank_stream, indicating hws can be null, and should be checked whenever it is used.
(cherry picked from commit 79db43611ff61280b6de58ce1305e0b2ecf675ad)(CVE-2025-38361)
In the Linux kernel, the following vulnerability has been resolved:
nbd: fix uaf in nbd_genl_connect() error path
There is a use-after-free issue in nbd:
block nbd6: Receive control failed (result -104) block nbd6: shutting down sockets ================================================================== BUG: KASAN: slab-use-after-free in recv_work+0x694/0xa80 drivers/block/nbd.c:1022 Write of size 4 at addr ffff8880295de478 by task kworker/u33:0/67
CPU: 2 UID: 0 PID: 67 Comm: kworker/u33:0 Not tainted 6.15.0-rc5-syzkaller-00123-g2c89c1b655c0 #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 Workqueue: nbd6-recv recv_work Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:408 [inline] print_report+0xc3/0x670 mm/kasan/report.c:521 kasan_report+0xe0/0x110 mm/kasan/report.c:634 check_region_inline mm/kasan/generic.c:183 [inline] kasan_check_range+0xef/0x1a0 mm/kasan/generic.c:189 instrument_atomic_read_write include/linux/instrumented.h:96 [inline] atomic_dec include/linux/atomic/atomic-instrumented.h:592 [inline] recv_work+0x694/0xa80 drivers/block/nbd.c:1022 process_one_work+0x9cc/0x1b70 kernel/workqueue.c:3238 process_scheduled_works kernel/workqueue.c:3319 [inline] worker_thread+0x6c8/0xf10 kernel/workqueue.c:3400 kthread+0x3c2/0x780 kernel/kthread.c:464 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:153 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 </TASK>
nbd_genl_connect() does not properly stop the device on certain error paths after nbd_start_device() has been called. This causes the error path to put nbd->config while recv_work continue to use the config after putting it, leading to use-after-free in recv_work.
This patch moves nbd_start_device() after the backend file creation.(CVE-2025-38443)
In the Linux kernel, the following vulnerability has been resolved:
net/sched: Abort __tc_modify_qdisc if parent class does not exist
Lion's patch [1] revealed an ancient bug in the qdisc API. Whenever a user creates/modifies a qdisc specifying as a parent another qdisc, the qdisc API will, during grafting, detect that the user is not trying to attach to a class and reject. However grafting is performed after qdisc_create (and thus the qdiscs' init callback) is executed. In qdiscs that eventually call qdisc_tree_reduce_backlog during init or change (such as fq, hhf, choke, etc), an issue arises. For example, executing the following commands:
sudo tc qdisc add dev lo root handle a: htb default 2 sudo tc qdisc add dev lo parent a: handle beef fq
Qdiscs such as fq, hhf, choke, etc unconditionally invoke qdisc_tree_reduce_backlog() in their control path init() or change() which then causes a failure to find the child class; however, that does not stop the unconditional invocation of the assumed child qdisc's qlen_notify with a null class. All these qdiscs make the assumption that class is non-null.
The solution is ensure that qdisc_leaf() which looks up the parent class, and is invoked prior to qdisc_create(), should return failure on not finding the class. In this patch, we leverage qdisc_leaf to return ERR_PTRs whenever the parentid doesn't correspond to a class, so that we can detect it earlier on and abort before qdisc_create is called.
[1] https://lore.kernel.org/netdev/(CVE-2025-38457)
In the Linux kernel, the following vulnerability has been resolved:
net: vlan: fix VLAN 0 refcount imbalance of toggling filtering during runtime
Assuming the "rx-vlan-filter" feature is enabled on a net device, the 8021q module will automatically add or remove VLAN 0 when the net device is put administratively up or down, respectively. There are a couple of problems with the above scheme.
The first problem is a memory leak that can happen if the "rx-vlan-filter" feature is disabled while the device is running:
# ip link add bond1 up type bond mode 0 # ethtool -K bond1 rx-vlan-filter off # ip link del dev bond1
When the device is put administratively down the "rx-vlan-filter" feature is disabled, so the 8021q module will not remove VLAN 0 and the memory will be leaked [1].
Another problem that can happen is that the kernel can automatically delete VLAN 0 when the device is put administratively down despite not adding it when the device was put administratively up since during that time the "rx-vlan-filter" feature was disabled. null-ptr-unref or bug_on[2] will be triggered by unregister_vlan_dev() for refcount imbalance if toggling filtering during runtime:
$ ip link add bond0 type bond mode 0 $ ip link add link bond0 name vlan0 type vlan id 0 protocol 802.1q $ ethtool -K bond0 rx-vlan-filter off $ ifconfig bond0 up $ ethtool -K bond0 rx-vlan-filter on $ ifconfig bond0 down $ ip link del vlan0
Root cause is as below: step1: add vlan0 for real_dev, such as bond, team. register_vlan_dev vlan_vid_add(real_dev,htons(ETH_P_8021Q),0) //refcnt=1 step2: disable vlan filter feature and enable real_dev step3: change filter from 0 to 1 vlan_device_event vlan_filter_push_vids ndo_vlan_rx_add_vid //No refcnt added to real_dev vlan0 step4: real_dev down vlan_device_event vlan_vid_del(dev, htons(ETH_P_8021Q), 0); //refcnt=0 vlan_info_rcu_free //free vlan0 step5: delete vlan0 unregister_vlan_dev BUG_ON(!vlan_info); //vlan_info is null
Fix both problems by noting in the VLAN info whether VLAN 0 was automatically added upon NETDEV_UP and based on that decide whether it should be deleted upon NETDEV_DOWN, regardless of the state of the "rx-vlan-filter" feature.
[1] unreferenced object 0xffff8880068e3100 (size 256): comm "ip", pid 384, jiffies 4296130254 hex dump (first 32 bytes): 00 20 30 0d 80 88 ff ff 00 00 00 00 00 00 00 00 . 0............. 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace (crc 81ce31fa): __kmalloc_cache_noprof+0x2b5/0x340 vlan_vid_add+0x434/0x940 vlan_device_event.cold+0x75/0xa8 notifier_call_chain+0xca/0x150 __dev_notify_flags+0xe3/0x250 rtnl_configure_link+0x193/0x260 rtnl_newlink_create+0x383/0x8e0 __rtnl_newlink+0x22c/0xa40 rtnl_newlink+0x627/0xb00 rtnetlink_rcv_msg+0x6fb/0xb70 netlink_rcv_skb+0x11f/0x350 netlink_unicast+0x426/0x710 netlink_sendmsg+0x75a/0xc20 __sock_sendmsg+0xc1/0x150 _syssendmsg+0x5aa/0x7b0 _sys_sendmsg+0xfc/0x180
[2] kernel BUG at net/8021q/vlan.c:99! Oops: invalid opcode: 0000 [#1] SMP KASAN PTI CPU: 0 UID: 0 PID: 382 Comm: ip Not tainted 6.16.0-rc3 #61 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:unregister_vlan_dev (net/8021q/vlan.c:99 (discriminator 1)) RSP: 0018:ffff88810badf310 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff88810da84000 RCX: ffffffffb47ceb9a RDX: dffffc0000000000 RSI: 0000000000000008 RDI: ffff88810e8b43c8 RBP: 0000000000000000 R08: 0000000000000000 R09: fffffbfff6cefe80 R10: ffffffffb677f407 R11: ffff88810badf3c0 R12: ffff88810e8b4000 R13: 0000000000000000 R14: ffff88810642a5c0 R15: 000000000000017e FS: 00007f1ff68c20c0(0000) GS:ffff888163a24000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f1ff5dad240 CR3: 0000000107e56000 CR4: 00000000000006f0 Call Trace: <TASK ---truncated---(CVE-2025-38470)
In the Linux kernel, the following vulnerability has been resolved:
net/sched: sch_qfq: Fix race condition on qfq_aggregate
A race condition can occur when 'agg' is modified in qfq_change_agg (called during qfq_enqueue) while other threads access it concurrently. For example, qfq_dump_class may trigger a NULL dereference, and qfq_delete_class may cause a use-after-free.
This patch addresses the issue by:
-
Moved qfq_destroy_class into the critical section.
-
Added sch_tree_lock protection to qfq_dump_class and qfq_dump_class_stats.(CVE-2025-38477)
In the Linux kernel, the following vulnerability has been resolved:
smb: client: fix use-after-free in cifs_oplock_break
A race condition can occur in cifs_oplock_break() leading to a use-after-free of the cinode structure when unmounting:
cifs_oplock_break() _cifsFileInfo_put(cfile) cifsFileInfo_put_final() cifs_sb_deactive() [last ref, start releasing sb] kill_sb() kill_anon_super() generic_shutdown_super() evict_inodes() dispose_list() evict() destroy_inode() call_rcu(&inode->i_rcu, i_callback) spin_lock(&cinode->open_file_lock) <- OK [later] i_callback() cifs_free_inode() kmem_cache_free(cinode) spin_unlock(&cinode->open_file_lock) <- UAF cifs_done_oplock_break(cinode) <- UAF
The issue occurs when umount has already released its reference to the superblock. When _cifsFileInfo_put() calls cifs_sb_deactive(), this releases the last reference, triggering the immediate cleanup of all inodes under RCU. However, cifs_oplock_break() continues to access the cinode after this point, resulting in use-after-free.
Fix this by holding an extra reference to the superblock during the entire oplock break operation. This ensures that the superblock and its inodes remain valid until the oplock break completes.(CVE-2025-38527)
In the Linux kernel, the following vulnerability has been resolved:
sunrpc: fix handling of server side tls alerts
Scott Mayhew discovered a security exploit in NFS over TLS in tls_alert_recv() due to its assumption it can read data from the msg iterator's kvec..
kTLS implementation splits TLS non-data record payload between the control message buffer (which includes the type such as TLS aler or TLS cipher change) and the rest of the payload (say TLS alert's level/description) which goes into the msg payload buffer.
This patch proposes to rework how control messages are setup and used by sock_recvmsg().
If no control message structure is setup, kTLS layer will read and process TLS data record types. As soon as it encounters a TLS control message, it would return an error. At that point, NFS can setup a kvec backed msg buffer and read in the control message such as a TLS alert. Msg iterator can advance the kvec pointer as a part of the copy process thus we need to revert the iterator before calling into the tls_alert_recv.(CVE-2025-38566)
In the Linux kernel, the following vulnerability has been resolved:
ipv6: prevent infinite loop in rt6_nlmsg_size()
While testing prior patch, I was able to trigger an infinite loop in rt6_nlmsg_size() in the following place:
list_for_each_entry_rcu(sibling, &f6i->fib6_siblings, fib6_siblings) { rt6_nh_nlmsg_size(sibling->fib6_nh, &nexthop_len); }
This is because fib6_del_route() and fib6_add_rt2node() uses list_del_rcu(), which can confuse rcu readers, because they might no longer see the head of the list.
Restart the loop if f6i->fib6_nsiblings is zero.(CVE-2025-38588)
In the Linux kernel, the following vulnerability has been resolved:
eventpoll: Fix semi-unbounded recursion
Ensure that epoll instances can never form a graph deeper than EP_MAX_NESTS+1 links.
Currently, ep_loop_check_proc() ensures that the graph is loop-free and does some recursion depth checks, but those recursion depth checks don't limit the depth of the resulting tree for two reasons:
- They don't look upwards in the tree.
- If there are multiple downwards paths of different lengths, only one of the paths is actually considered for the depth check since commit 28d82dc1c4ed ("epoll: limit paths").
Essentially, the current recursion depth check in ep_loop_check_proc() just serves to prevent it from recursing too deeply while checking for loops.
A more thorough check is done in reverse_path_check() after the new graph edge has already been created; this checks, among other things, that no paths going upwards from any non-epoll file with a length of more than 5 edges exist. However, this check does not apply to non-epoll files.
As a result, it is possible to recurse to a depth of at least roughly 500, tested on v6.15. (I am unsure if deeper recursion is possible; and this may have changed with commit 8c44dac8add7 ("eventpoll: Fix priority inversion problem").)
To fix it:
- In ep_loop_check_proc(), note the subtree depth of each visited node, and use subtree depths for the total depth calculation even when a subtree has already been visited.
- Add ep_get_upwards_depth_proc() for similarly determining the maximum depth of an upwards walk.
- In ep_loop_check(), use these values to limit the total path length between epoll nodes to EP_MAX_NESTS edges.(CVE-2025-38614)
In the Linux kernel, the following vulnerability has been resolved:
net/packet: fix a race in packet_set_ring() and packet_notifier()
When packet_set_ring() releases po->bind_lock, another thread can run packet_notifier() and process an NETDEV_UP event.
This race and the fix are both similar to that of commit 15fe076edea7 ("net/packet: fix a race in packet_bind() and packet_notifier()").
There too the packet_notifier NETDEV_UP event managed to run while a po->bind_lock critical section had to be temporarily released. And the fix was similarly to temporarily set po->num to zero to keep the socket unhooked until the lock is retaken.
The po->bind_lock in packet_set_ring and packet_notifier precede the introduction of git history.(CVE-2025-38617)
In the Linux kernel, the following vulnerability has been resolved:
rv: Use strings in da monitors tracepoints
Using DA monitors tracepoints with KASAN enabled triggers the following warning:
BUG: KASAN: global-out-of-bounds in do_trace_event_raw_event_event_da_monitor+0xd6/0x1a0 Read of size 32 at addr ffffffffaada8980 by task ... Call Trace: <TASK> [...] do_trace_event_raw_event_event_da_monitor+0xd6/0x1a0 ? __pfx_do_trace_event_raw_event_event_da_monitor+0x10/0x10 ? trace_event_sncid+0x83/0x200 trace_event_sncid+0x163/0x200 [...] The buggy address belongs to the variable: automaton_snep+0x4e0/0x5e0
This is caused by the tracepoints reading 32 bytes __array instead of __string from the automata definition. Such strings are literals and reading 32 bytes ends up in out of bound memory accesses (e.g. the next automaton's data in this case). The error is harmless as, while printing the string, we stop at the null terminator, but it should still be fixed.
Use the __string facilities while defining the tracepoints to avoid reading out of bound memory.(CVE-2025-38636)
In the Linux kernel, the following vulnerability has been resolved:
ice: Fix a null pointer dereference in ice_copy_and_init_pkg()
Add check for the return value of devm_kmemdup() to prevent potential null pointer dereference.(CVE-2025-38664)
In the Linux kernel, the following vulnerability has been resolved:
ASoC: core: Check for rtd == NULL in snd_soc_remove_pcm_runtime()
snd_soc_remove_pcm_runtime() might be called with rtd == NULL which will leads to null pointer dereference. This was reproduced with topology loading and marking a link as ignore due to missing hardware component on the system. On module removal the soc_tplg_remove_link() would call snd_soc_remove_pcm_runtime() with rtd == NULL since the link was ignored, no runtime was created.(CVE-2025-38706)
In the Linux kernel, the following vulnerability has been resolved:
netlink: avoid infinite retry looping in netlink_unicast()
netlink_attachskb() checks for the socket's read memory allocation constraints. Firstly, it has:
rmem < READ_ONCE(sk->sk_rcvbuf)
to check if the just increased rmem value fits into the socket's receive buffer. If not, it proceeds and tries to wait for the memory under:
rmem + skb->truesize > READ_ONCE(sk->sk_rcvbuf)
The checks don't cover the case when skb->truesize + sk->sk_rmem_alloc is equal to sk->sk_rcvbuf. Thus the function neither successfully accepts these conditions, nor manages to reschedule the task - and is called in retry loop for indefinite time which is caught as:
rcu: INFO: rcu_sched self-detected stall on CPU rcu: 0-....: (25999 ticks this GP) idle=ef2/1/0x4000000000000000 softirq=262269/262269 fqs=6212 (t=26000 jiffies g=230833 q=259957) NMI backtrace for cpu 0 CPU: 0 PID: 22 Comm: kauditd Not tainted 5.10.240 #68 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc42 04/01/2014 Call Trace: <IRQ> dump_stack lib/dump_stack.c:120 nmi_cpu_backtrace.cold lib/nmi_backtrace.c:105 nmi_trigger_cpumask_backtrace lib/nmi_backtrace.c:62 rcu_dump_cpu_stacks kernel/rcu/tree_stall.h:335 rcu_sched_clock_irq.cold kernel/rcu/tree.c:2590 update_process_times kernel/time/timer.c:1953 tick_sched_handle kernel/time/tick-sched.c:227 tick_sched_timer kernel/time/tick-sched.c:1399 __hrtimer_run_queues kernel/time/hrtimer.c:1652 hrtimer_interrupt kernel/time/hrtimer.c:1717 __sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1113 asm_call_irq_on_stack arch/x86/entry/entry_64.S:808 </IRQ>
netlink_attachskb net/netlink/af_netlink.c:1234 netlink_unicast net/netlink/af_netlink.c:1349 kauditd_send_queue kernel/audit.c:776 kauditd_thread kernel/audit.c:897 kthread kernel/kthread.c:328 ret_from_fork arch/x86/entry/entry_64.S:304
Restore the original behavior of the check which commit in Fixes accidentally missed when restructuring the code.
Found by Linux Verification Center (linuxtesting.org).(CVE-2025-38727)
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Add null pointer check in mod_hdcp_hdcp1_create_session()
The function mod_hdcp_hdcp1_create_session() calls the function get_first_active_display(), but does not check its return value. The return value is a null pointer if the display list is empty. This will lead to a null pointer dereference.
Add a null pointer check for get_first_active_display() and return MOD_HDCP_STATUS_DISPLAY_NOT_FOUND if the function return null.
This is similar to the commit c3e9826a2202 ("drm/amd/display: Add null pointer check for get_first_active_display()").
(cherry picked from commit 5e43eb3cd731649c4f8b9134f857be62a416c893)(CVE-2025-39675)
In the Linux kernel, the following vulnerability has been resolved:
net/sched: Fix backlog accounting in qdisc_dequeue_internal
This issue applies for the following qdiscs: hhf, fq, fq_codel, and fq_pie, and occurs in their change handlers when adjusting to the new limit. The problem is the following in the values passed to the subsequent qdisc_tree_reduce_backlog call given a tbf parent:
When the tbf parent runs out of tokens, skbs of these qdiscs will be placed in gso_skb. Their peek handlers are qdisc_peek_dequeued, which accounts for both qlen and backlog. However, in the case of qdisc_dequeue_internal, ONLY qlen is accounted for when pulling from gso_skb. This means that these qdiscs are missing a qdisc_qstats_backlog_dec when dropping packets to satisfy the new limit in their change handlers.
One can observe this issue with the following (with tc patched to support a limit of 0):
export TARGET=fq tc qdisc del dev lo root tc qdisc add dev lo root handle 1: tbf rate 8bit burst 100b latency 1ms tc qdisc replace dev lo handle 3: parent 1:1 $TARGET limit 1000 echo ''; echo 'add child'; tc -s -d qdisc show dev lo ping -I lo -f -c2 -s32 -W0.001 127.0.0.1 2>&1 >/dev/null echo ''; echo 'after ping'; tc -s -d qdisc show dev lo tc qdisc change dev lo handle 3: parent 1:1 $TARGET limit 0 echo ''; echo 'after limit drop'; tc -s -d qdisc show dev lo tc qdisc replace dev lo handle 2: parent 1:1 sfq echo ''; echo 'post graft'; tc -s -d qdisc show dev lo
The second to last show command shows 0 packets but a positive number (74) of backlog bytes. The problem becomes clearer in the last show command, where qdisc_purge_queue triggers qdisc_tree_reduce_backlog with the positive backlog and causes an underflow in the tbf parent's backlog (4096 Mb instead of 0).
To fix this issue, the codepath for all clients of qdisc_dequeue_internal has been simplified: codel, pie, hhf, fq, fq_pie, and fq_codel. qdisc_dequeue_internal handles the backlog adjustments for all cases that do not directly use the dequeue handler.
The old fq_codel_change limit adjustment loop accumulated the arguments to the subsequent qdisc_tree_reduce_backlog call through the cstats field. However, this is confusing and error prone as fq_codel_dequeue could also potentially mutate this field (which qdisc_dequeue_internal calls in the non gso_skb case), so we have unified the code here with other qdiscs.(CVE-2025-39677)
In the Linux kernel, the following vulnerability has been resolved:
comedi: Fix use of uninitialized memory in do_insn_ioctl() and do_insnlist_ioctl()
syzbot reports a KMSAN kernel-infoleak in do_insn_ioctl(). A kernel
buffer is allocated to hold insn->n samples (each of which is an
unsigned int). For some instruction types, insn->n samples are
copied back to user-space, unless an error code is being returned. The
problem is that not all the instruction handlers that need to return
data to userspace fill in the whole insn->n samples, so that there is
an information leak. There is a similar syzbot report for
do_insnlist_ioctl(), although it does not have a reproducer for it at
the time of writing.
One culprit is insn_rw_emulate_bits() which is used as the handler for
INSN_READ or INSN_WRITE instructions for subdevices that do not have
a specific handler for that instruction, but do have an INSN_BITS
handler. For INSN_READ it only fills in at most 1 sample, so if
insn->n is greater than 1, the remaining insn->n - 1 samples copied
to userspace will be uninitialized kernel data.
Another culprit is vm80xx_ai_insn_read() in the "vm80xx" driver. It
never returns an error, even if it fails to fill the buffer.
Fix it in do_insn_ioctl() and do_insnlist_ioctl() by making sure
that uninitialized parts of the allocated buffer are zeroed before
handling each instruction.
Thanks to Arnaud Lecomte for their fix to do_insn_ioctl(). That fix
replaced the call to kmalloc_array() with kcalloc(), but it is not
always necessary to clear the whole buffer.(CVE-2025-39684)
In the Linux kernel, the following vulnerability has been resolved:
NFS: Fix a race when updating an existing write
After nfs_lock_and_join_requests() tests for whether the request is still attached to the mapping, nothing prevents a call to nfs_inode_remove_request() from succeeding until we actually lock the page group. The reason is that whoever called nfs_inode_remove_request() doesn't necessarily have a lock on the page group head.
So in order to avoid races, let's take the page group lock earlier in nfs_lock_and_join_requests(), and hold it across the removal of the request in nfs_inode_remove_request().(CVE-2025-39697)
In the Linux kernel, the following vulnerability has been resolved:
bnxt_en: Fix memory corruption when FW resources change during ifdown
bnxt_set_dflt_rings() assumes that it is always called before any TC has been created. So it doesn't take bp->num_tc into account and assumes that it is always 0 or 1.
In the FW resource or capability change scenario, the FW will return flags in bnxt_hwrm_if_change() that will cause the driver to reinitialize and call bnxt_cancel_reservations(). This will lead to bnxt_init_dflt_ring_mode() calling bnxt_set_dflt_rings() and bp->num_tc may be greater than 1. This will cause bp->tx_ring[] to be sized too small and cause memory corruption in bnxt_alloc_cp_rings().
Fix it by properly scaling the TX rings by bp->num_tc in the code paths mentioned above. Add 2 helper functions to determine bp->tx_nr_rings and bp->tx_nr_rings_per_tc.(CVE-2025-39810)
In the Linux kernel, the following vulnerability has been resolved:
efivarfs: Fix slab-out-of-bounds in efivarfs_d_compare
Observed on kernel 6.6 (present on master as well):
BUG: KASAN: slab-out-of-bounds in memcmp+0x98/0xd0 Call trace: kasan_check_range+0xe8/0x190 __asan_loadN+0x1c/0x28 memcmp+0x98/0xd0 efivarfs_d_compare+0x68/0xd8 __d_lookup_rcu_op_compare+0x178/0x218 __d_lookup_rcu+0x1f8/0x228 d_alloc_parallel+0x150/0x648 lookup_open.isra.0+0x5f0/0x8d0 open_last_lookups+0x264/0x828 path_openat+0x130/0x3f8 do_filp_open+0x114/0x248 do_sys_openat2+0x340/0x3c0 __arm64_sys_openat+0x120/0x1a0
If dentry->d_name.len < EFI_VARIABLE_GUID_LEN , 'guid' can become negative, leadings to oob. The issue can be triggered by parallel lookups using invalid filename:
T1 T2 lookup_open ->lookup simple_lookup d_add // invalid dentry is added to hash list
lookup_open
d_alloc_parallel
__d_lookup_rcu
__d_lookup_rcu_op_compare
hlist_bl_for_each_entry_rcu
// invalid dentry can be retrieved
->d_compare
efivarfs_d_compare
// oob
Fix it by checking 'guid' before cmp.(CVE-2025-39817)
In the Linux kernel, the following vulnerability has been resolved:
smb: client: fix race with concurrent opens in rename(2)
Besides sending the rename request to the server, the rename process also involves closing any deferred close, waiting for outstanding I/O to complete as well as marking all existing open handles as deleted to prevent them from deferring closes, which increases the race window for potential concurrent opens on the target file.
Fix this by unhashing the dentry in advance to prevent any concurrent opens on the target.(CVE-2025-39825)
In the Linux kernel, the following vulnerability has been resolved:
fs: writeback: fix use-after-free in __mark_inode_dirty()
An use-after-free issue occurred when __mark_inode_dirty() get the bdi_writeback that was in the progress of switching.
CPU: 1 PID: 562 Comm: systemd-random- Not tainted 6.6.56-gb4403bd46a8e #1 ...... pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __mark_inode_dirty+0x124/0x418 lr : __mark_inode_dirty+0x118/0x418 sp : ffffffc08c9dbbc0 ........ Call trace: __mark_inode_dirty+0x124/0x418 generic_update_time+0x4c/0x60 file_modified+0xcc/0xd0 ext4_buffered_write_iter+0x58/0x124 ext4_file_write_iter+0x54/0x704 vfs_write+0x1c0/0x308 ksys_write+0x74/0x10c __arm64_sys_write+0x1c/0x28 invoke_syscall+0x48/0x114 el0_svc_common.constprop.0+0xc0/0xe0 do_el0_svc+0x1c/0x28 el0_svc+0x40/0xe4 el0t_64_sync_handler+0x120/0x12c el0t_64_sync+0x194/0x198
Root cause is:
systemd-random-seed kworker
___mark_inode_dirty inode_switch_wbs_work_fn
spin_lock(&inode->i_lock); inode_attach_wb locked_inode_to_wb_and_lock_list get inode->i_wb spin_unlock(&inode->i_lock); spin_lock(&wb->list_lock) spin_lock(&inode->i_lock) inode_io_list_move_locked spin_unlock(&wb->list_lock) spin_unlock(&inode->i_lock) spin_lock(&old_wb->list_lock) inode_do_switch_wbs spin_lock(&inode->i_lock) inode->i_wb = new_wb spin_unlock(&inode->i_lock) spin_unlock(&old_wb->list_lock) wb_put_many(old_wb, nr_switched) cgwb_release old wb released wb_wakeup_delayed() accesses wb, then trigger the use-after-free issue
Fix this race condition by holding inode spinlock until wb_wakeup_delayed() finished.(CVE-2025-39866)
In the Linux kernel, the following vulnerability has been resolved:
kernfs: Fix UAF in polling when open file is released
A use-after-free (UAF) vulnerability was identified in the PSI (Pressure Stall Information) monitoring mechanism:
BUG: KASAN: slab-use-after-free in psi_trigger_poll+0x3c/0x140 Read of size 8 at addr ffff3de3d50bd308 by task systemd/1
psi_trigger_poll+0x3c/0x140 cgroup_pressure_poll+0x70/0xa0 cgroup_file_poll+0x8c/0x100 kernfs_fop_poll+0x11c/0x1c0 ep_item_poll.isra.0+0x188/0x2c0
Allocated by task 1: cgroup_file_open+0x88/0x388 kernfs_fop_open+0x73c/0xaf0 do_dentry_open+0x5fc/0x1200 vfs_open+0xa0/0x3f0 do_open+0x7e8/0xd08 path_openat+0x2fc/0x6b0 do_filp_open+0x174/0x368
Freed by task 8462: cgroup_file_release+0x130/0x1f8 kernfs_drain_open_files+0x17c/0x440 kernfs_drain+0x2dc/0x360 kernfs_show+0x1b8/0x288 cgroup_file_show+0x150/0x268 cgroup_pressure_write+0x1dc/0x340 cgroup_file_write+0x274/0x548
Reproduction Steps: 1. Open test/cpu.pressure and establish epoll monitoring 2. Disable monitoring: echo 0 > test/cgroup.pressure 3. Re-enable monitoring: echo 1 > test/cgroup.pressure
The race condition occurs because: 1. When cgroup.pressure is disabled (echo 0 > cgroup.pressure), it: - Releases PSI triggers via cgroup_file_release() - Frees of->priv through kernfs_drain_open_files() 2. While epoll still holds reference to the file and continues polling 3. Re-enabling (echo 1 > cgroup.pressure) accesses freed of->priv
epolling disable/enable cgroup.pressure fd=open(cpu.pressure) while(1) ... epoll_wait kernfs_fop_poll kernfs_get_active = true echo 0 > cgroup.pressure ... cgroup_file_show kernfs_show // inactive kn kernfs_drain_open_files cft->release(of); kfree(ctx); ... kernfs_get_active = false echo 1 > cgroup.pressure kernfs_show kernfs_activate_one(kn); kernfs_fop_poll kernfs_get_active = true cgroup_file_poll psi_trigger_poll // UAF ... end: close(fd)
To address this issue, introduce kernfs_get_active_of() for kernfs open files to obtain active references. This function will fail if the open file has been released. Replace kernfs_get_active() with kernfs_get_active_of() to prevent further operations on released file descriptors.(CVE-2025-39881)
In the Linux kernel, the following vulnerability has been resolved:
i40e: fix IRQ freeing in i40e_vsi_request_irq_msix error path
If request_irq() in i40e_vsi_request_irq_msix() fails in an iteration later than the first, the error path wants to free the IRQs requested so far. However, it uses the wrong dev_id argument for free_irq(), so it does not free the IRQs correctly and instead triggers the warning:
Trying to free already-free IRQ 173 WARNING: CPU: 25 PID: 1091 at kernel/irq/manage.c:1829 __free_irq+0x192/0x2c0 Modules linked in: i40e(+) [...] CPU: 25 UID: 0 PID: 1091 Comm: NetworkManager Not tainted 6.17.0-rc1+ #1 PREEMPT(lazy) Hardware name: [...] RIP: 0010:__free_irq+0x192/0x2c0 [...] Call Trace: <TASK> free_irq+0x32/0x70 i40e_vsi_request_irq_msix.cold+0x63/0x8b [i40e] i40e_vsi_request_irq+0x79/0x80 [i40e] i40e_vsi_open+0x21f/0x2f0 [i40e] i40e_open+0x63/0x130 [i40e] __dev_open+0xfc/0x210 __dev_change_flags+0x1fc/0x240 netif_change_flags+0x27/0x70 do_setlink.isra.0+0x341/0xc70 rtnl_newlink+0x468/0x860 rtnetlink_rcv_msg+0x375/0x450 netlink_rcv_skb+0x5c/0x110 netlink_unicast+0x288/0x3c0 netlink_sendmsg+0x20d/0x430 _syssendmsg+0x3a2/0x3d0 _sys_sendmsg+0x99/0xe0 __sys_sendmsg+0x8a/0xf0 do_syscall_64+0x82/0x2c0 entry_SYSCALL_64_after_hwframe+0x76/0x7e [...] </TASK> ---[ end trace 0000000000000000 ]---
Use the same dev_id for free_irq() as for request_irq().
I tested this with inserting code to fail intentionally.(CVE-2025-39911)
In the Linux kernel, the following vulnerability has been resolved:
net/mlx5e: Harden uplink netdev access against device unbind
The function mlx5_uplink_netdev_get() gets the uplink netdevice pointer from mdev->mlx5e_res.uplink_netdev. However, the netdevice can be removed and its pointer cleared when unbound from the mlx5_core.eth driver. This results in a NULL pointer, causing a kernel panic.
BUG: unable to handle page fault for address: 0000000000001300 at RIP: 0010:mlx5e_vport_rep_load+0x22a/0x270 [mlx5_core] Call Trace: <TASK> mlx5_esw_offloads_rep_load+0x68/0xe0 [mlx5_core] esw_offloads_enable+0x593/0x910 [mlx5_core] mlx5_eswitch_enable_locked+0x341/0x420 [mlx5_core] mlx5_devlink_eswitch_mode_set+0x17e/0x3a0 [mlx5_core] devlink_nl_eswitch_set_doit+0x60/0xd0 genl_family_rcv_msg_doit+0xe0/0x130 genl_rcv_msg+0x183/0x290 netlink_rcv_skb+0x4b/0xf0 genl_rcv+0x24/0x40 netlink_unicast+0x255/0x380 netlink_sendmsg+0x1f3/0x420 __sock_sendmsg+0x38/0x60 __sys_sendto+0x119/0x180 do_syscall_64+0x53/0x1d0 entry_SYSCALL_64_after_hwframe+0x4b/0x53
Ensure the pointer is valid before use by checking it for NULL. If it is valid, immediately call netdev_hold() to take a reference, and preventing the netdevice from being freed while it is in use.(CVE-2025-39947)
In the Linux kernel, the following vulnerability has been resolved:
media: tuner: xc5000: Fix use-after-free in xc5000_release
The original code uses cancel_delayed_work() in xc5000_release(), which does not guarantee that the delayed work item timer_sleep has fully completed if it was already running. This leads to use-after-free scenarios where xc5000_release() may free the xc5000_priv while timer_sleep is still active and attempts to dereference the xc5000_priv.
A typical race condition is illustrated below:
CPU 0 (release thread) | CPU 1 (delayed work callback) xc5000_release() | xc5000_do_timer_sleep() cancel_delayed_work() | hybrid_tuner_release_state(priv) | kfree(priv) | | priv = container_of() // UAF
Replace cancel_delayed_work() with cancel_delayed_work_sync() to ensure that the timer_sleep is properly canceled before the xc5000_priv memory is deallocated.
A deadlock concern was considered: xc5000_release() is called in a process context and is not holding any locks that the timer_sleep work item might also need. Therefore, the use of the _sync() variant is safe here.
This bug was initially identified through static analysis.
hverkuil: fix typo in Subject: tunner -> tuner
In the Linux kernel, the following vulnerability has been resolved:
media: b2c2: Fix use-after-free causing by irq_check_work in flexcop_pci_remove
The original code uses cancel_delayed_work() in flexcop_pci_remove(), which does not guarantee that the delayed work item irq_check_work has fully completed if it was already running. This leads to use-after-free scenarios where flexcop_pci_remove() may free the flexcop_device while irq_check_work is still active and attempts to dereference the device.
A typical race condition is illustrated below:
CPU 0 (remove) | CPU 1 (delayed work callback) flexcop_pci_remove() | flexcop_pci_irq_check_work() cancel_delayed_work() | flexcop_device_kfree(fc_pci->fc_dev) | | fc = fc_pci->fc_dev; // UAF
This is confirmed by a KASAN report:
================================================================== BUG: KASAN: slab-use-after-free in __run_timer_base.part.0+0x7d7/0x8c0 Write of size 8 at addr ffff8880093aa8c8 by task bash/135 ... Call Trace: <IRQ> dump_stack_lvl+0x55/0x70 print_report+0xcf/0x610 ? __run_timer_base.part.0+0x7d7/0x8c0 kasan_report+0xb8/0xf0 ? __run_timer_base.part.0+0x7d7/0x8c0 __run_timer_base.part.0+0x7d7/0x8c0 ? __pfxruntimer_base.part.0+0x10/0x10 ? pfx_read_tsc+0x10/0x10 ? ktime_get+0x60/0x140 ? lapic_next_event+0x11/0x20 ? clockevents_program_event+0x1d4/0x2a0 run_timer_softirq+0xd1/0x190 handle_softirqs+0x16a/0x550 irq_exit_rcu+0xaf/0xe0 sysvec_apic_timer_interrupt+0x70/0x80 </IRQ> ...
Allocated by task 1: kasan_save_stack+0x24/0x50 kasan_save_track+0x14/0x30 __kasan_kmalloc+0x7f/0x90 __kmalloc_noprof+0x1be/0x460 flexcop_device_kmalloc+0x54/0xe0 flexcop_pci_probe+0x1f/0x9d0 local_pci_probe+0xdc/0x190 pci_device_probe+0x2fe/0x470 really_probe+0x1ca/0x5c0 __driver_probe_device+0x248/0x310 driver_probe_device+0x44/0x120 __driver_attach+0xd2/0x310 bus_for_each_dev+0xed/0x170 bus_add_driver+0x208/0x500 driver_register+0x132/0x460 do_one_initcall+0x89/0x300 kernel_init_freeable+0x40d/0x720 kernel_init+0x1a/0x150 ret_from_fork+0x10c/0x1a0 ret_from_fork_asm+0x1a/0x30
Freed by task 135: kasan_save_stack+0x24/0x50 kasan_save_track+0x14/0x30 kasan_save_free_info+0x3a/0x60 __kasan_slab_free+0x3f/0x50 kfree+0x137/0x370 flexcop_device_kfree+0x32/0x50 pci_device_remove+0xa6/0x1d0 device_release_driver_internal+0xf8/0x210 pci_stop_bus_device+0x105/0x150 pci_stop_and_remove_bus_device_locked+0x15/0x30 remove_store+0xcc/0xe0 kernfs_fop_write_iter+0x2c3/0x440 vfs_write+0x871/0xd70 ksys_write+0xee/0x1c0 do_syscall_64+0xac/0x280 entry_SYSCALL_64_after_hwframe+0x77/0x7f ...
Replace cancel_delayed_work() with cancel_delayed_work_sync() to ensure that the delayed work item is properly canceled and any executing delayed work has finished before the device memory is deallocated.
This bug was initially identified through static analysis. To reproduce and test it, I simulated the B2C2 FlexCop PCI device in QEMU and introduced artificial delays within the flexcop_pci_irq_check_work() function to increase the likelihood of triggering the bug.(CVE-2025-39996)
In the Linux kernel, the following vulnerability has been resolved:
media: uvcvideo: Mark invalid entities with id UVC_INVALID_ENTITY_ID
Per UVC 1.1+ specification 3.7.2, units and terminals must have a non-zero unique ID.
Each Unit and Terminal within the video function is assigned a unique
identification number, the Unit ID (UID) or Terminal ID (TID), contained in
the bUnitID or bTerminalID field of the descriptor. The value 0x00 is
reserved for undefined ID,
If we add a new entity with id 0 or a duplicated ID, it will be marked as UVC_INVALID_ENTITY_ID.
In a previous attempt commit 3dd075fe8ebb ("media: uvcvideo: Require entities to have a non-zero unique ID"), we ignored all the invalid units, this broke a lot of non-compatible cameras. Hopefully we are more lucky this time.
This also prevents some syzkaller reproducers from triggering warnings due to a chain of entities referring to themselves. In one particular case, an Output Unit is connected to an Input Unit, both with the same ID of 1. But when looking up for the source ID of the Output Unit, that same entity is found instead of the input entity, which leads to such warnings.
In another case, a backward chain was considered finished as the source ID was 0. Later on, that entity was found, but its pads were not valid.
Here is a sample stack trace for one of those cases.
[ 20.650953] usb 1-1: new high-speed USB device number 2 using dummy_hcd [ 20.830206] usb 1-1: Using ep0 maxpacket: 8 [ 20.833501] usb 1-1: config 0 descriptor?? [ 21.038518] usb 1-1: string descriptor 0 read error: -71 [ 21.038893] usb 1-1: Found UVC 0.00 device <unnamed> (2833:0201) [ 21.039299] uvcvideo 1-1:0.0: Entity type for entity Output 1 was not initialized! [ 21.041583] uvcvideo 1-1:0.0: Entity type for entity Input 1 was not initialized! [ 21.042218] ------------[ cut here ]------------ [ 21.042536] WARNING: CPU: 0 PID: 9 at drivers/media/mc/mc-entity.c:1147 media_create_pad_link+0x2c4/0x2e0 [ 21.043195] Modules linked in: [ 21.043535] CPU: 0 UID: 0 PID: 9 Comm: kworker/0:1 Not tainted 6.11.0-rc7-00030-g3480e43aeccf #444 [ 21.044101] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014 [ 21.044639] Workqueue: usb_hub_wq hub_event [ 21.045100] RIP: 0010:media_create_pad_link+0x2c4/0x2e0 [ 21.045508] Code: fe e8 20 01 00 00 b8 f4 ff ff ff 48 83 c4 30 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc 0f 0b eb e9 0f 0b eb 0a 0f 0b eb 06 <0f> 0b eb 02 0f 0b b8 ea ff ff ff eb d4 66 2e 0f 1f 84 00 00 00 00 [ 21.046801] RSP: 0018:ffffc9000004b318 EFLAGS: 00010246 [ 21.047227] RAX: ffff888004e5d458 RBX: 0000000000000000 RCX: ffffffff818fccf1 [ 21.047719] RDX: 000000000000007b RSI: 0000000000000000 RDI: ffff888004313290 [ 21.048241] RBP: ffff888004313290 R08: 0001ffffffffffff R09: 0000000000000000 [ 21.048701] R10: 0000000000000013 R11: 0001888004313290 R12: 0000000000000003 [ 21.049138] R13: ffff888004313080 R14: ffff888004313080 R15: 0000000000000000 [ 21.049648] FS: 0000000000000000(0000) GS:ffff88803ec00000(0000) knlGS:0000000000000000 [ 21.050271] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 21.050688] CR2: 0000592cc27635b0 CR3: 000000000431c000 CR4: 0000000000750ef0 [ 21.051136] PKRU: 55555554 [ 21.051331] Call Trace: [ 21.051480] <TASK> [ 21.051611] ? __warn+0xc4/0x210 [ 21.051861] ? media_create_pad_link+0x2c4/0x2e0 [ 21.052252] ? report_bug+0x11b/0x1a0 [ 21.052540] ? trace_hardirqs_on+0x31/0x40 [ 21.052901] ? handle_bug+0x3d/0x70 [ 21.053197] ? exc_invalid_op+0x1a/0x50 [ 21.053511] ? asm_exc_invalid_op+0x1a/0x20 [ 21.053924] ? media_create_pad_link+0x91/0x2e0 [ 21.054364] ? media_create_pad_link+0x2c4/0x2e0 [ 21.054834] ? media_create_pad_link+0x91/0x2e0 [ 21.055131] ? _raw_spin_unlock+0x1e/0x40 [ 21.055441] ? __v4l2_device_register_subdev+0x202/0x210 [ 21.055837] uvc_mc_register_entities+0x358/0x400 [ 21.056144] uvc_register_chains+0x1 ---truncated---(CVE-2025-40016)
In the Linux kernel, the following vulnerability has been resolved:
Squashfs: fix uninit-value in squashfs_get_parent
Syzkaller reports a "KMSAN: uninit-value in squashfs_get_parent" bug.
This is caused by open_by_handle_at() being called with a file handle containing an invalid parent inode number. In particular the inode number is that of a symbolic link, rather than a directory.
Squashfs_get_parent() gets called with that symbolic link inode, and accesses the parent member field.
unsigned int parent_ino = squashfs_i(inode)->parent;
Because non-directory inodes in Squashfs do not have a parent value, this is uninitialised, and this causes an uninitialised value access.
The fix is to initialise parent with the invalid inode 0, which will cause an EINVAL error to be returned.
Regular inodes used to share the parent field with the block_list_start field. This is removed in this commit to enable the parent field to contain the invalid inode number 0.(CVE-2025-40049)
In the Linux kernel, the following vulnerability has been resolved:
smb: client: fix crypto buffers in non-linear memory
The crypto API, through the scatterlist API, expects input buffers to be in linear memory. We handle this with the cifs_sg_set_buf() helper that converts vmalloc'd memory to their corresponding pages.
However, when we allocate our aead_request buffer (@creq in smb2ops.c::crypt_message()), we do so with kvzalloc(), which possibly puts aead_request->__ctx in vmalloc area.
AEAD algorithm then uses ->__ctx for its private/internal data and operations, and uses sg_set_buf() for such data on a few places.
This works fine as long as @creq falls into kmalloc zone (small requests) or vmalloc'd memory is still within linear range.
Tasks' stacks are vmalloc'd by default (CONFIG_VMAP_STACK=y), so too many tasks will increment the base stacks' addresses to a point where virt_addr_valid(buf) will fail (BUG() in sg_set_buf()) when that happens.
In practice: too many parallel reads and writes on an encrypted mount will trigger this bug.
To fix this, always alloc @creq with kmalloc() instead. Also drop the @sensitive_size variable/arguments since kfree_sensitive() doesn't need it.
Backtrace:
[ 945.272081] ------------[ cut here ]------------ [ 945.272774] kernel BUG at include/linux/scatterlist.h:209! [ 945.273520] Oops: invalid opcode: 0000 [#1] SMP DEBUG_PAGEALLOC NOPTI [ 945.274412] CPU: 7 UID: 0 PID: 56 Comm: kworker/u33:0 Kdump: loaded Not tainted 6.15.0-lku-11779-g8e9d6efccdd7-dirty #1 PREEMPT(voluntary) [ 945.275736] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-2-gc13ff2cd-prebuilt.qemu.org 04/01/2014 [ 945.276877] Workqueue: writeback wb_workfn (flush-cifs-2) [ 945.277457] RIP: 0010:crypto_gcm_init_common+0x1f9/0x220 [ 945.278018] Code: b0 00 00 00 48 83 c4 08 5b 5d 41 5c 41 5d 41 5e 41 5f c3 cc cc cc cc 48 c7 c0 00 00 00 80 48 2b 05 5c 58 e5 00 e9 58 ff ff ff <0f> 0b 0f 0b 0f 0b 0f 0b 0f 0b 0f 0b 48 c7 04 24 01 00 00 00 48 8b [ 945.279992] RSP: 0018:ffffc90000a27360 EFLAGS: 00010246 [ 945.280578] RAX: 0000000000000000 RBX: ffffc90001d85060 RCX: 0000000000000030 [ 945.281376] RDX: 0000000000080000 RSI: 0000000000000000 RDI: ffffc90081d85070 [ 945.282145] RBP: ffffc90001d85010 R08: ffffc90001d85000 R09: 0000000000000000 [ 945.282898] R10: ffffc90001d85090 R11: 0000000000001000 R12: ffffc90001d85070 [ 945.283656] R13: ffff888113522948 R14: ffffc90001d85060 R15: ffffc90001d85010 [ 945.284407] FS: 0000000000000000(0000) GS:ffff8882e66cf000(0000) knlGS:0000000000000000 [ 945.285262] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 945.285884] CR2: 00007fa7ffdd31f4 CR3: 000000010540d000 CR4: 0000000000350ef0 [ 945.286683] Call Trace: [ 945.286952] <TASK> [ 945.287184] ? crypt_message+0x33f/0xad0 [cifs] [ 945.287719] crypto_gcm_encrypt+0x36/0xe0 [ 945.288152] crypt_message+0x54a/0xad0 [cifs] [ 945.288724] smb3_init_transform_rq+0x277/0x300 [cifs] [ 945.289300] smb_send_rqst+0xa3/0x160 [cifs] [ 945.289944] cifs_call_async+0x178/0x340 [cifs] [ 945.290514] ? __pfx_smb2_writev_callback+0x10/0x10 [cifs] [ 945.291177] smb2_async_writev+0x3e3/0x670 [cifs] [ 945.291759] ? find_held_lock+0x32/0x90 [ 945.292212] ? netfs_advance_write+0xf2/0x310 [ 945.292723] netfs_advance_write+0xf2/0x310 [ 945.293210] netfs_write_folio+0x346/0xcc0 [ 945.293689] ? __pfx__raw_spin_unlock_irq+0x10/0x10 [ 945.294250] netfs_writepages+0x117/0x460 [ 945.294724] do_writepages+0xbe/0x170 [ 945.295152] ? find_held_lock+0x32/0x90 [ 945.295600] ? kvm_sched_clock_read+0x11/0x20 [ 945.296103] __writeback_single_inode+0x56/0x4b0 [ 945.296643] writeback_sb_inodes+0x229/0x550 [ 945.297140] __writeback_inodes_wb+0x4c/0xe0 [ 945.297642] wb_writeback+0x2f1/0x3f0 [ 945.298069] wb_workfn+0x300/0x490 [ 945.298472] process_one_work+0x1fe/0x590 [ 945.298949] worker_thread+0x1ce/0x3c0 [ 945.299397] ? __pfx_worker_thread+0x10/0x10 [ 945.299900] kthr ---truncated---(CVE-2025-40052)
In the Linux kernel, the following vulnerability has been resolved:
iommu/vt-d: Disallow dirty tracking if incoherent page walk
Dirty page tracking relies on the IOMMU atomically updating the dirty bit in the paging-structure entry. For this operation to succeed, the paging- structure memory must be coherent between the IOMMU and the CPU. In another word, if the iommu page walk is incoherent, dirty page tracking doesn't work.
The Intel VT-d specification, Section 3.10 "Snoop Behavior" states:
"Remapping hardware encountering the need to atomically update A/EA/D bits in a paging-structure entry that is not snooped will result in a non- recoverable fault."
To prevent an IOMMU from being incorrectly configured for dirty page tracking when it is operating in an incoherent mode, mark SSADS as supported only when both ecap_slads and ecap_smpwc are supported.(CVE-2025-40058)
In the Linux kernel, the following vulnerability has been resolved:
RDMA/rxe: Fix race in do_task() when draining
When do_task() exhausts its iteration budget (!ret), it sets the state to TASK_STATE_IDLE to reschedule, without a secondary check on the current task->state. This can overwrite the TASK_STATE_DRAINING state set by a concurrent call to rxe_cleanup_task() or rxe_disable_task().
While state changes are protected by a spinlock, both rxe_cleanup_task() and rxe_disable_task() release the lock while waiting for the task to finish draining in the while(!is_done(task)) loop. The race occurs if do_task() hits its iteration limit and acquires the lock in this window. The cleanup logic may then proceed while the task incorrectly reschedules itself, leading to a potential use-after-free.
This bug was introduced during the migration from tasklets to workqueues, where the special handling for the draining case was lost.
Fix this by restoring the original pre-migration behavior. If the state is TASK_STATE_DRAINING when iterations are exhausted, set cont to 1 to force a new loop iteration. This allows the task to finish its work, so that a subsequent iteration can reach the switch statement and correctly transition the state to TASK_STATE_DRAINED, stopping the task as intended.(CVE-2025-40061)
In the Linux kernel, the following vulnerability has been resolved:
ipv4: start using dst_dev_rcu()
Change icmpv4_xrlim_allow(), ip_defrag() to prevent possible UAF.
Change ipmr_prepare_xmit(), ipmr_queue_fwd_xmit(), ip_mr_output(), ipv4_neigh_lookup() to use lockdep enabled dst_dev_rcu().(CVE-2025-40074)
In the Linux kernel, the following vulnerability has been resolved:
tcp_metrics: use dst_dev_net_rcu()
Replace three dst_dev() with a lockdep enabled helper.(CVE-2025-40075)
In the Linux kernel, the following vulnerability has been resolved:
ixgbevf: fix mailbox API compatibility by negotiating supported features
There was backward compatibility in the terms of mailbox API. Various drivers from various OSes supporting 10G adapters from Intel portfolio could easily negotiate mailbox API.
This convention has been broken since introducing API 1.4. Commit 0062e7cc955e ("ixgbevf: add VF IPsec offload code") added support for IPSec which is specific only for the kernel ixgbe driver. None of the rest of the Intel 10G PF/VF drivers supports it. And actually lack of support was not included in the IPSec implementation - there were no such code paths. No possibility to negotiate support for the feature was introduced along with introduction of the feature itself.
Commit 339f28964147 ("ixgbevf: Add support for new mailbox communication between PF and VF") increasing API version to 1.5 did the same - it introduced code supported specifically by the PF ESX driver. It altered API version for the VF driver in the same time not touching the version defined for the PF ixgbe driver. It led to additional discrepancies, as the code provided within API 1.6 cannot be supported for Linux ixgbe driver as it causes crashes.
The issue was noticed some time ago and mitigated by Jake within the commit d0725312adf5 ("ixgbevf: stop attempting IPSEC offload on Mailbox API 1.5"). As a result we have regression for IPsec support and after increasing API to version 1.6 ixgbevf driver stopped to support ESX MBX.
To fix this mess add new mailbox op asking PF driver about supported features. Basing on a response determine whether to set support for IPSec and ESX-specific enhanced mailbox.
New mailbox op, for compatibility purposes, must be added within new API revision, as API version of OOT PF & VF drivers is already increased to 1.6 and doesn't incorporate features negotiate op.
Features negotiation mechanism gives possibility to be extended with new features when needed in the future.(CVE-2025-40104)
In the Linux kernel, the following vulnerability has been resolved:
ASoC: Intel: bytcr_rt5651: Fix invalid quirk input mapping
When an invalid value is passed via quirk option, currently bytcr_rt5640 driver just ignores and leaves as is, which may lead to unepxected results like OOB access.
This patch adds the sanity check and corrects the input mapping to the certain default value if an invalid value is passed.(CVE-2025-40121)
In the Linux kernel, the following vulnerability has been resolved:
ipv6: use RCU in ip6_xmit()
Use RCU in ip6_xmit() in order to use dst_dev_rcu() to prevent possible UAF.(CVE-2025-40135)
In the Linux kernel, the following vulnerability has been resolved:
smc: Use __sk_dst_get() and dst_dev_rcu() in in smc_clc_prfx_set().
smc_clc_prfx_set() is called during connect() and not under RCU nor RTNL.
Using sk_dst_get(sk)->dev could trigger UAF.
Let's use __sk_dst_get() and dev_dst_rcu() under rcu_read_lock() after kernel_getsockname().
Note that the returned value of smc_clc_prfx_set() is not used in the caller.
While at it, we change the 1st arg of smc_clc_prfx_set[46]_rcu() not to touch dst there.(CVE-2025-40139)
In the Linux kernel, the following vulnerability has been resolved:
tls: Use __sk_dst_get() and dst_dev_rcu() in get_netdev_for_sock().
get_netdev_for_sock() is called during setsockopt(), so not under RCU.
Using sk_dst_get(sk)->dev could trigger UAF.
Let's use __sk_dst_get() and dst_dev_rcu().
Note that the only ->ndo_sk_get_lower_dev() user is bond_sk_get_lower_dev(), which uses RCU.(CVE-2025-40149)
In the Linux kernel, the following vulnerability has been resolved:
iommu/vt-d: debugfs: Fix legacy mode page table dump logic
In legacy mode, SSPTPTR is ignored if TT is not 00b or 01b. SSPTPTR maybe uninitialized or zero in that case and may cause oops like:
Oops: general protection fault, probably for non-canonical address 0xf00087d3f000f000: 0000 [#1] SMP NOPTI CPU: 2 UID: 0 PID: 786 Comm: cat Not tainted 6.16.0 #191 PREEMPT(voluntary) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014 RIP: 0010:pgtable_walk_level+0x98/0x150 RSP: 0018:ffffc90000f279c0 EFLAGS: 00010206 RAX: 0000000040000000 RBX: ffffc90000f27ab0 RCX: 000000000000001e RDX: 0000000000000003 RSI: f00087d3f000f000 RDI: f00087d3f0010000 RBP: ffffc90000f27a00 R08: ffffc90000f27a98 R09: 0000000000000002 R10: 0000000000000000 R11: 0000000000000000 R12: f00087d3f000f000 R13: 0000000000000000 R14: 0000000040000000 R15: ffffc90000f27a98 FS: 0000764566dcb740(0000) GS:ffff8881f812c000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000764566d44000 CR3: 0000000109d81003 CR4: 0000000000772ef0 PKRU: 55555554 Call Trace: <TASK> pgtable_walk_level+0x88/0x150 domain_translation_struct_show.isra.0+0x2d9/0x300 dev_domain_translation_struct_show+0x20/0x40 seq_read_iter+0x12d/0x490 ...
Avoid walking the page table if TT is not 00b or 01b.(CVE-2025-40155)
In the Linux kernel, the following vulnerability has been resolved:
ipv6: use RCU in ip6_output()
Use RCU in ip6_output() in order to use dst_dev_rcu() to prevent possible UAF.
We can remove rcu_read_lock()/rcu_read_unlock() pairs from ip6_finish_output2().(CVE-2025-40158)
| URL | Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"bpftool-6.6.0-127.0.0.113.oe2403.aarch64.rpm",
"bpftool-debuginfo-6.6.0-127.0.0.113.oe2403.aarch64.rpm",
"kernel-6.6.0-127.0.0.113.oe2403.aarch64.rpm",
"kernel-debuginfo-6.6.0-127.0.0.113.oe2403.aarch64.rpm",
"kernel-debugsource-6.6.0-127.0.0.113.oe2403.aarch64.rpm",
"kernel-devel-6.6.0-127.0.0.113.oe2403.aarch64.rpm",
"kernel-headers-6.6.0-127.0.0.113.oe2403.aarch64.rpm",
"kernel-source-6.6.0-127.0.0.113.oe2403.aarch64.rpm",
"kernel-tools-6.6.0-127.0.0.113.oe2403.aarch64.rpm",
"kernel-tools-debuginfo-6.6.0-127.0.0.113.oe2403.aarch64.rpm",
"kernel-tools-devel-6.6.0-127.0.0.113.oe2403.aarch64.rpm",
"perf-6.6.0-127.0.0.113.oe2403.aarch64.rpm",
"perf-debuginfo-6.6.0-127.0.0.113.oe2403.aarch64.rpm",
"python3-perf-6.6.0-127.0.0.113.oe2403.aarch64.rpm",
"python3-perf-debuginfo-6.6.0-127.0.0.113.oe2403.aarch64.rpm"
],
"src": [
"kernel-6.6.0-127.0.0.113.oe2403.src.rpm"
],
"x86_64": [
"bpftool-6.6.0-127.0.0.113.oe2403.x86_64.rpm",
"bpftool-debuginfo-6.6.0-127.0.0.113.oe2403.x86_64.rpm",
"kernel-6.6.0-127.0.0.113.oe2403.x86_64.rpm",
"kernel-debuginfo-6.6.0-127.0.0.113.oe2403.x86_64.rpm",
"kernel-debugsource-6.6.0-127.0.0.113.oe2403.x86_64.rpm",
"kernel-devel-6.6.0-127.0.0.113.oe2403.x86_64.rpm",
"kernel-headers-6.6.0-127.0.0.113.oe2403.x86_64.rpm",
"kernel-source-6.6.0-127.0.0.113.oe2403.x86_64.rpm",
"kernel-tools-6.6.0-127.0.0.113.oe2403.x86_64.rpm",
"kernel-tools-debuginfo-6.6.0-127.0.0.113.oe2403.x86_64.rpm",
"kernel-tools-devel-6.6.0-127.0.0.113.oe2403.x86_64.rpm",
"perf-6.6.0-127.0.0.113.oe2403.x86_64.rpm",
"perf-debuginfo-6.6.0-127.0.0.113.oe2403.x86_64.rpm",
"python3-perf-6.6.0-127.0.0.113.oe2403.x86_64.rpm",
"python3-perf-debuginfo-6.6.0-127.0.0.113.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-127.0.0.113.oe2403"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnfc: nci: Fix uninit-value in nci_rx_work\n\nsyzbot reported the following uninit-value access issue [1]\n\nnci_rx_work() parses received packet from ndev-\u0026gt;rx_q. It should be\nvalidated header size, payload size and total packet size before\nprocessing the packet. If an invalid packet is detected, it should be\nsilently discarded.(CVE-2024-38381)\n\nIn the Linux kernel, the following vulnerability has been resolved:net: ti: icssg_prueth: Fix NULL pointer dereference in prueth_probe()In the prueth_probe() function, if one of the calls to emac_phy_connect()fails due to of_phy_connect() returning NULL, then the subsequent call tophy_attached_info() will dereference a NULL pointer.Check the return code of emac_phy_connect and fail cleanly if there is anerror.(CVE-2024-38584)\n\nIn the Linux kernel, the following vulnerability has been resolved:cpufreq: exit() callback is optionalThe exit() callback is optional and shouldn t be called without checkinga valid pointer first.Also, we must clear freq_table pointer even if the exit() callback isn tpresent.(CVE-2024-38615)\n\nIn the Linux kernel, the following vulnerability has been resolved:serial: max3100: Update uart_driver_registered on driver removalThe removal of the last MAX3100 device triggers the removal ofthe driver. However, code doesn t update the respective globalvariable and after insmod \u2014 rmmod \u2014 insmod cycle the kerneloopses: max3100 spi-PRP0001:01: max3100_probe: adding port 0 BUG: kernel NULL pointer dereference, address: 0000000000000408 ... RIP: 0010:serial_core_register_port+0xa0/0x840 ... max3100_probe+0x1b6/0x280 [max3100] spi_probe+0x8d/0xb0Update the actual state so next time UART driver will be registeredagain.Hugo also noticed, that the error path in the probe also affectedby having the variable set, and not cleared. Instead of clearing itmove the assignment after the successfull uart_register_driver() call.(CVE-2024-38633)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nenic: Validate length of nl attributes in enic_set_vf_port\n\nenic_set_vf_port assumes that the nl attribute IFLA_PORT_PROFILE\nis of length PORT_PROFILE_MAX and that the nl attributes\nIFLA_PORT_INSTANCE_UUID, IFLA_PORT_HOST_UUID are of length PORT_UUID_MAX.\nThese attributes are validated (in the function do_setlink in rtnetlink.c)\nusing the nla_policy ifla_port_policy. The policy defines IFLA_PORT_PROFILE\nas NLA_STRING, IFLA_PORT_INSTANCE_UUID as NLA_BINARY and\nIFLA_PORT_HOST_UUID as NLA_STRING. That means that the length validation\nusing the policy is for the max size of the attributes and not on exact\nsize so the length of these attributes might be less than the sizes that\nenic_set_vf_port expects. This might cause an out of bands\nread access in the memcpys of the data of these\nattributes in enic_set_vf_port.(CVE-2024-38659)\n\nIn the Linux kernel, the following vulnerability has been resolved:riscv: prevent pt_regs corruption for secondary idle threadsTop of the kernel thread stack should be reserved for pt_regs. Howeverthis 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 problemhas been noticed in some CPU hotplug tests with V enabled. The functionsmp_callin stored several registers on stack, corrupting top of pt_regsstructure including status field. As a result, kernel attempted to saveor restore inexistent V context.(CVE-2024-38667)\n\nIn the Linux kernel, the following vulnerability has been resolved:jfs: xattr: fix buffer overflow for invalid xattrWhen an xattr size is not what is expected, it is printed out to thekernel log in hex format as a form of debugging. But when that xattrsize is bigger than the expected size, printing it out can cause anaccess off the end of the buffer.Fix this all up by properly restricting the size of the debug hex dumpin the kernel log.(CVE-2024-40902)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nUSB: class: cdc-wdm: Fix CPU lockup caused by excessive log messages\n\nThe syzbot fuzzer found that the interrupt-URB completion callback in\nthe cdc-wdm driver was taking too long, and the driver\u0026apos;s immediate\nresubmission of interrupt URBs with -EPROTO status combined with the\ndummy-hcd emulation to cause a CPU lockup:\n\ncdc_wdm 1-1:1.0: nonzero urb status received: -71\ncdc_wdm 1-1:1.0: wdm_int_callback - 0 bytes\nwatchdog: BUG: soft lockup - CPU#0 stuck for 26s! [syz-executor782:6625]\nCPU#0 Utilization every 4s during lockup:\n\t#1: 98% system,\t 0% softirq,\t 3% hardirq,\t 0% idle\n\t#2: 98% system,\t 0% softirq,\t 3% hardirq,\t 0% idle\n\t#3: 98% system,\t 0% softirq,\t 3% hardirq,\t 0% idle\n\t#4: 98% system,\t 0% softirq,\t 3% hardirq,\t 0% idle\n\t#5: 98% system,\t 1% softirq,\t 3% hardirq,\t 0% idle\nModules linked in:\nirq event stamp: 73096\nhardirqs last enabled at (73095): [\u0026lt;ffff80008037bc00\u0026gt;] console_emit_next_record kernel/printk/printk.c:2935 [inline]\nhardirqs last enabled at (73095): [\u0026lt;ffff80008037bc00\u0026gt;] console_flush_all+0x650/0xb74 kernel/printk/printk.c:2994\nhardirqs last disabled at (73096): [\u0026lt;ffff80008af10b00\u0026gt;] __el1_irq arch/arm64/kernel/entry-common.c:533 [inline]\nhardirqs last disabled at (73096): [\u0026lt;ffff80008af10b00\u0026gt;] el1_interrupt+0x24/0x68 arch/arm64/kernel/entry-common.c:551\nsoftirqs last enabled at (73048): [\u0026lt;ffff8000801ea530\u0026gt;] softirq_handle_end kernel/softirq.c:400 [inline]\nsoftirqs last enabled at (73048): [\u0026lt;ffff8000801ea530\u0026gt;] handle_softirqs+0xa60/0xc34 kernel/softirq.c:582\nsoftirqs last disabled at (73043): [\u0026lt;ffff800080020de8\u0026gt;] __do_softirq+0x14/0x20 kernel/softirq.c:588\nCPU: 0 PID: 6625 Comm: syz-executor782 Tainted: G W 6.10.0-rc2-syzkaller-g8867bbd4a056 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024\n\nTesting showed that the problem did not occur if the two error\nmessages -- the first two lines above -- were removed; apparently adding\nmaterial to the kernel log takes a surprisingly large amount of time.\n\nIn any case, the best approach for preventing these lockups and to\navoid spamming the log with thousands of error messages per second is\nto ratelimit the two dev_err() calls. Therefore we replace them with\ndev_err_ratelimited().(CVE-2024-40904)\n\nIn the Linux kernel, the following vulnerability has been resolved:nvmet: always initialize cqe.resultThe spec doesn t mandate that the first two double words (aka results)for the command queue entry need to be set to 0 when they are notused (not specified). Though, the target implemention returns 0 for TCPand FC but not for RDMA.Let s make RDMA behave the same and thus explicitly initializing theresult field. This prevents leaking any data from the stack.(CVE-2024-41079)\n\nIn the Linux kernel, the following vulnerability has been resolved:drm/nouveau: fix null pointer dereference in nouveau_connector_get_modesIn nouveau_connector_get_modes(), the return value of drm_mode_duplicate()is assigned to mode, which will lead to a possible NULL pointerdereference on failure of drm_mode_duplicate(). Add a check to avoid npd.(CVE-2024-42101)\n\nIn the Linux kernel, the following vulnerability has been resolved:Revert mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again Patch series mm: Avoid possible overflows in dirty throttling .Dirty throttling logic assumes dirty limits in page units fit into32-bits. This patch series makes sure this is true (see patch 2/2 formore details).This patch (of 2):This reverts commit 9319b647902cbd5cc884ac08a8a6d54ce111fc78.The commit is broken in several ways. Firstly, the removed (u64) castfrom the multiplication will introduce a multiplication overflow on 32-bitarchs if wb_thresh * bg_thresh \u0026gt;= 1\u0026lt;\u0026lt;32 (which is actually common - thedefault settings with 4GB of RAM will trigger this). Secondly, thediv64_u64() is unnecessarily expensive on 32-bit archs. We havediv64_ul() in case we want to be safe \u0026amp; cheap. Thirdly, if dirtythresholds are larger than 1\u0026lt;\u0026lt;32 pages, then dirty balancing is going toblow up in many other spectacular ways anyway so trying to fix onepossible overflow is just moot.(CVE-2024-42102)\n\nIn the Linux kernel, the following vulnerability has been resolved:Revert sched/fair: Make sure to try to detach at least one movable task This reverts commit b0defa7ae03ecf91b8bfd10ede430cff12fcbd06.b0defa7ae03ec changed the load balancing logic to ignore env.max_loop ifall tasks examined to that point were pinned. The goal of the patch wasto make it more likely to be able to detach a task buried in a long listof pinned tasks. However, this has the unfortunate side effect ofcreating an O(n) iteration in detach_tasks(), as we now must fullyiterate every task on a cpu if all or most are pinned. Since this loadbalance code is done with rq lock held, and often in softirq context, itis very easy to trigger hard lockups. We observed such hard lockups witha user who affined O(10k) threads to a single cpu.When I discussed this with Vincent he initially suggested that we keepthe limit on the number of tasks to detach, but increase the number oftasks we can search. However, after some back and forth on the mailinglist, he recommended we instead revert the original patch, as it seemslikely no one was actually getting hit by the original issue.(CVE-2024-42245)\n\nIn the Linux kernel, the following vulnerability has been resolved:wireguard: allowedips: avoid unaligned 64-bit memory accessesOn the parisc platform, the kernel issues kernel warnings becauseswap_endian() tries to load a 128-bit IPv6 address from an unalignedmemory location: Kernel: unaligned access to 0x55f4688c in wg_allowedips_insert_v6+0x2c/0x80 [wireguard] (iir 0xf3010df) Kernel: unaligned access to 0x55f46884 in wg_allowedips_insert_v6+0x38/0x80 [wireguard] (iir 0xf2010dc)Avoid such unaligned memory accesses by instead using theget_unaligned_be64() helper macro.[Jason: replace src[8] in original patch with src+8](CVE-2024-42247)\n\nIn the Linux kernel, the following vulnerability has been resolved:f2fs: fix to don t dirty inode for readonly filesystemsyzbot reports f2fs bug as below:kernel BUG at fs/f2fs/inode.c:933!RIP: 0010:f2fs_evict_inode+0x1576/0x1590 fs/f2fs/inode.c:933Call Trace: evict+0x2a4/0x620 fs/inode.c:664 dispose_list fs/inode.c:697 [inline] evict_inodes+0x5f8/0x690 fs/inode.c:747 generic_shutdown_super+0x9d/0x2c0 fs/super.c:675 kill_block_super+0x44/0x90 fs/super.c:1667 kill_f2fs_super+0x303/0x3b0 fs/f2fs/super.c:4894 deactivate_locked_super+0xc1/0x130 fs/super.c:484 cleanup_mnt+0x426/0x4c0 fs/namespace.c:1256 task_work_run+0x24a/0x300 kernel/task_work.c:180 ptrace_notify+0x2cd/0x380 kernel/signal.c:2399 ptrace_report_syscall include/linux/ptrace.h:411 [inline] ptrace_report_syscall_exit include/linux/ptrace.h:473 [inline] syscall_exit_work kernel/entry/common.c:251 [inline] syscall_exit_to_user_mode_prepare kernel/entry/common.c:278 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline] syscall_exit_to_user_mode+0x15c/0x280 kernel/entry/common.c:296 do_syscall_64+0x50/0x110 arch/x86/entry/common.c:88 entry_SYSCALL_64_after_hwframe+0x63/0x6bThe root cause is:- do_sys_open - f2fs_lookup - __f2fs_find_entry - f2fs_i_depth_write - f2fs_mark_inode_dirty_sync - f2fs_dirty_inode - set_inode_flag(inode, FI_DIRTY_INODE)- umount - kill_f2fs_super - kill_block_super - generic_shutdown_super - sync_filesystem : sb is readonly, skip sync_filesystem() - evict_inodes - iput - f2fs_evict_inode - f2fs_bug_on(sbi, is_inode_flag_set(inode, FI_DIRTY_INODE)) : trigger kernel panicWhen we try to repair i_current_depth in readonly filesystem, let sskip dirty inode to avoid panic in later f2fs_evict_inode().(CVE-2024-42297)\n\nIn the Linux kernel, the following vulnerability has been resolved:vhost/scsi: null-ptr-dereference in vhost_scsi_get_req()Since commit 3f8ca2e115e5 ( vhost/scsi: Extract common handling codefrom control queue handler ) a null pointer dereference bug can betriggered when guest sends an SCSI AN request.In vhost_scsi_ctl_handle_vq(), `vc.target` is assigned with`\u0026amp;v_req.tmf.lun[1]` within a switch-case block and is then passed tovhost_scsi_get_req() which extracts `vc-\u0026gt;req` and `tpg`. However, fora `VIRTIO_SCSI_T_AN_*` request, tpg is not required, so `vc.target` isset to NULL in this branch. Later, in vhost_scsi_get_req(),`vc-\u0026gt;target` is dereferenced without being checked, leading to a nullpointer dereference bug. This bug can be triggered from guest.When this bug occurs, the vhost_worker process is killed while holding`vq-\u0026gt;mutex` and the corresponding tpg will remain occupiedindefinitely.Below is the KASAN report:Oops: general protection fault, probably for non-canonical address0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN NOPTIKASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]CPU: 1 PID: 840 Comm: poc Not tainted 6.10.0+ #1Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS1.16.3-debian-1.16.3-2 04/01/2014RIP: 0010:vhost_scsi_get_req+0x165/0x3a0Code: 00 fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 2b 02 00 0048 b8 00 00 00 00 00 fc ff df 4d 8b 65 30 4c 89 e2 48 c1 ea 03 \u0026lt;0f\u0026gt; b604 02 4c 89 e2 83 e2 07 38 d0 7f 08 84 c0 0f 85 be 01 00 00RSP: 0018:ffff888017affb50 EFLAGS: 00010246RAX: dffffc0000000000 RBX: ffff88801b000000 RCX: 0000000000000000RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff888017affcb8RBP: ffff888017affb80 R08: 0000000000000000 R09: 0000000000000000R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000R13: ffff888017affc88 R14: ffff888017affd1c R15: ffff888017993000FS: 000055556e076500(0000) GS:ffff88806b100000(0000) knlGS:0000000000000000CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033CR2: 00000000200027c0 CR3: 0000000010ed0004 CR4: 0000000000370ef0Call Trace: \u0026lt;TASK\u0026gt; ? show_regs+0x86/0xa0 ? die_addr+0x4b/0xd0 ? exc_general_protection+0x163/0x260 ? asm_exc_general_protection+0x27/0x30 ? vhost_scsi_get_req+0x165/0x3a0 vhost_scsi_ctl_handle_vq+0x2a4/0xca0 ? __pfx_vhost_scsi_ctl_handle_vq+0x10/0x10 ? __switch_to+0x721/0xeb0 ? __schedule+0xda5/0x5710 ? __kasan_check_write+0x14/0x30 ? _raw_spin_lock+0x82/0xf0 vhost_scsi_ctl_handle_kick+0x52/0x90 vhost_run_work_list+0x134/0x1b0 vhost_task_fn+0x121/0x350... \u0026lt;/TASK\u0026gt;---[ end trace 0000000000000000 ]---Let s add a check in vhost_scsi_get_req.[whitespace fixes](CVE-2024-49863)\n\nIn the Linux kernel, the following vulnerability has been resolved:nfsd: map the EBADMSG to nfserr_io to avoid warningExt4 will throw -EBADMSG through ext4_readdir when a checksum erroroccurs, 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.qemu.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)\n\nIn the Linux kernel, the following vulnerability has been resolved:drm/amd/display: Fix index out of bounds in degamma hardware format translationFixes index out of bounds issue in`cm_helper_translate_curve_to_degamma_hw_format` function. The issuecould occur when the index i exceeds the number of transfer functionpoints (TRANSFER_FUNC_POINTS).The fix adds a check to ensure i is within bounds before accessing thetransfer function points. If i is out of bounds the function returnsfalse 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-\u0026gt;tf_pts.red 1025 \u0026lt;= s32maxdrivers/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-\u0026gt;tf_pts.green 1025 \u0026lt;= s32maxdrivers/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-\u0026gt;tf_pts.blue 1025 \u0026lt;= s32max(CVE-2024-49894)\n\nIn the Linux kernel, the following vulnerability has been resolved:drm/amd/display: Add null check for afb in amdgpu_dm_plane_handle_cursor_update (v2)This commit adds a null check for the afb variable in theamdgpu_dm_plane_handle_cursor_update function. Previously, afb wasassumed to be null, but was used later in the code without a null check.This could potentially lead to a null pointer dereference.Changes since v1:- Moved the null check for afb to the line where afb is used. (Alex)Fixes the below:drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_plane.c:1298 amdgpu_dm_plane_handle_cursor_update() error: we previously assumed afb could be null (see line 1252)(CVE-2024-49905)\n\nIn the Linux kernel, the following vulnerability has been resolved:fbdev: efifb: Register sysfs groups through driver coreThe driver core can register and cleanup sysfs groups already.Make use of that functionality to simplify the error handling andcleanup.Also avoid a UAF race during unregistering where the sysctl attributeswere usable after the info struct was freed.(CVE-2024-49925)\n\nIn the Linux kernel, the following vulnerability has been resolved:wifi: ath11k: fix array out-of-bound access in SoC statsCurrently, the ath11k_soc_dp_stats::hal_reo_error array is defined with amaximum size of DP_REO_DST_RING_MAX. However, the ath11k_dp_process_rx()function access ath11k_soc_dp_stats::hal_reo_error using the REOdestination SRNG ring ID, which is incorrect. SRNG ring ID differ fromnormal ring ID, and this usage leads to out-of-bounds array access. To fixthis issue, modify ath11k_dp_process_rx() to use the normal ring IDdirectly instead of the SRNG ring ID to avoid out-of-bounds array access.Tested-on: QCN9074 hw1.0 PCI WLAN.HK.2.7.0.1-01744-QCAHKSWPL_SILICONZ-1(CVE-2024-49930)\n\nIn the Linux kernel, the following vulnerability has been resolved:ACPI: PAD: fix crash in exit_round_robin()The kernel occasionally crashes in cpumask_clear_cpu(), which is calledwithin exit_round_robin(), because when executing clear_bit(nr, addr) withnr set to 0xffffffff, the address calculation may cause misalignment withinthe memory, leading to access to an invalid memory address.----------BUG: unable to handle kernel paging request at ffffffffe0740618 ...CPU: 3 PID: 2919323 Comm: acpi_pad/14 Kdump: loaded Tainted: G OE X --------- - - 4.18.0-425.19.2.el8_7.x86_64 #1 ...RIP: 0010:power_saving_thread+0x313/0x411 [acpi_pad]Code: 89 cd 48 89 d3 eb d1 48 c7 c7 55 70 72 c0 e8 64 86 b0 e4 c6 05 0d a1 02 00 01 e9 bc fd ff ff 45 89 e4 42 8b 04 a5 20 82 72 c0 \u0026lt;f0\u0026gt; 48 0f b3 05 f4 9c 01 00 42 c7 04 a5 20 82 72 c0 ff ff ff ff 31RSP: 0018:ff72a5d51fa77ec8 EFLAGS: 00010202RAX: 00000000ffffffff RBX: ff462981e5d8cb80 RCX: 0000000000000000RDX: 0000000000000000 RSI: 0000000000000246 RDI: 0000000000000246RBP: ff46297556959d80 R08: 0000000000000382 R09: ff46297c8d0f38d8R10: 0000000000000000 R11: 0000000000000001 R12: 000000000000000eR13: 0000000000000000 R14: ffffffffffffffff R15: 000000000000000eFS: 0000000000000000(0000) GS:ff46297a800c0000(0000) knlGS:0000000000000000CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033CR2: ffffffffe0740618 CR3: 0000007e20410004 CR4: 0000000000771ee0DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400PKRU: 55555554Call Trace: ? acpi_pad_add+0x120/0x120 [acpi_pad] kthread+0x10b/0x130 ? set_kthread_struct+0x50/0x50 ret_from_fork+0x1f/0x40 ...CR2: ffffffffe0740618crash\u0026gt; dis -lr ffffffffc0726923 .../usr/src/debug/kernel-4.18.0-425.19.2.el8_7/linux-4.18.0-425.19.2.el8_7.x86_64/./include/linux/cpumask.h: 1140xffffffffc0726918 \u0026lt;power_saving_thread+776\u0026gt;: mov %r12d,%r12d/usr/src/debug/kernel-4.18.0-425.19.2.el8_7/linux-4.18.0-425.19.2.el8_7.x86_64/./include/linux/cpumask.h: 3250xffffffffc072691b \u0026lt;power_saving_thread+779\u0026gt;: mov -0x3f8d7de0(,%r12,4),%eax/usr/src/debug/kernel-4.18.0-425.19.2.el8_7/linux-4.18.0-425.19.2.el8_7.x86_64/./arch/x86/include/asm/bitops.h: 800xffffffffc0726923 \u0026lt;power_saving_thread+787\u0026gt;: lock btr %rax,0x19cf4(%rip) # 0xffffffffc0740620 \u0026lt;pad_busy_cpus_bits\u0026gt;crash\u0026gt; px tsk_in_cpu[14]$66 = 0xffffffffcrash\u0026gt; px 0xffffffffc072692c+0x19cf4$99 = 0xffffffffc0740620crash\u0026gt; sym 0xffffffffc0740620ffffffffc0740620 (b) pad_busy_cpus_bits [acpi_pad]crash\u0026gt; px pad_busy_cpus_bits[0]$42 = 0xfffc0----------To fix this, ensure that tsk_in_cpu[tsk_index] != -1 before callingcpumask_clear_cpu() in exit_round_robin(), just as it is done inround_robin_cpu().[ rjw: Subject edit, avoid updates to the same value ](CVE-2024-49935)\n\nIn the Linux kernel, the following vulnerability has been resolved:net: add more sanity checks to qdisc_pkt_len_init()One path takes care of SKB_GSO_DODGY, assumingskb-\u0026gt;len is bigger than hdr_len.virtio_net_hdr_to_skb() does not fully dissect TCP headers,it only make sure it is at least 20 bytes.It is possible for an user to provide a malicious GSO packet,total length of 80 bytes.- 20 bytes of IPv4 header- 60 bytes TCP header- a small gso_size like 8virtio_net_hdr_to_skb() would declare this packet as a normalGSO packet, because it would see 40 bytes of payload,bigger than gso_size.We need to make detect this case to not underflowqdisc_skb_cb(skb)-\u0026gt;pkt_len.(CVE-2024-49948)\n\nIn the Linux kernel, the following vulnerability has been resolved:net: avoid potential underflow in qdisc_pkt_len_init() with UFOAfter commit 7c6d2ecbda83 ( net: be more gentle about silly gsorequests coming from user ) virtio_net_hdr_to_skb() had sanity checkto detect malicious attempts from user space to cook a bad GSO packet.Then commit cf9acc90c80ec ( net: virtio_net_hdr_to_skb: counttransport header in UFO ) while fixing one issue, allowed user spaceto cook a GSO packet with the following characteristic :IPv4 SKB_GSO_UDP, gso_size=3, skb-\u0026gt;len = 28.When this packet arrives in qdisc_pkt_len_init(), we end upwith hdr_len = 28 (IPv4 header + UDP header), matching skb-\u0026gt;lenThen the following sets gso_segs to 0 :gso_segs = DIV_ROUND_UP(skb-\u0026gt;len - hdr_len, shinfo-\u0026gt;gso_size);Then later we set qdisc_skb_cb(skb)-\u0026gt;pkt_len to back to zero :/qdisc_skb_cb(skb)-\u0026gt;pkt_len += (gso_segs - 1) * hdr_len;This leads to the following crash in fq_codel [1]qdisc_pkt_len_init() is best effort, we only want an estimationof the bytes sent on the wire, not crashing the kernel.This patch is fixing this particular issue, a following oneadds more sanity checks for another potential bug.[1][ 70.724101] BUG: kernel NULL pointer dereference, address: 0000000000000000[ 70.724561] #PF: supervisor read access in kernel mode[ 70.724561] #PF: error_code(0x0000) - not-present page[ 70.724561] PGD 10ac61067 P4D 10ac61067 PUD 107ee2067 PMD 0[ 70.724561] Oops: Oops: 0000 [#1] SMP NOPTI[ 70.724561] CPU: 11 UID: 0 PID: 2163 Comm: b358537762 Not tainted 6.11.0-virtme #991[ 70.724561] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014[ 70.724561] RIP: 0010:fq_codel_enqueue (net/sched/sch_fq_codel.c:120 net/sched/sch_fq_codel.c:168 net/sched/sch_fq_codel.c:230) sch_fq_codel[ 70.724561] Code: 24 08 49 c1 e1 06 44 89 7c 24 18 45 31 ed 45 31 c0 31 ff 89 44 24 14 4c 03 8b 90 01 00 00 eb 04 39 ca 73 37 4d 8b 39 83 c7 01 \u0026lt;49\u0026gt; 8b 17 49 89 11 41 8b 57 28 45 8b 5f 34 49 c7 07 00 00 00 00 49All code======== 0: 24 08 and $0x8,%al 2: 49 c1 e1 06 shl $0x6,%r9 6: 44 89 7c 24 18 mov %r15d,0x18(%rsp) b: 45 31 ed xor %r13d,%r13d e: 45 31 c0 xor %r8d,%r8d 11: 31 ff xor %edi,%edi 13: 89 44 24 14 mov %eax,0x14(%rsp) 17: 4c 03 8b 90 01 00 00 add 0x190(%rbx),%r9 1e: eb 04 jmp 0x24 20: 39 ca cmp %ecx,%edx 22: 73 37 jae 0x5b 24: 4d 8b 39 mov (%r9),%r15 27: 83 c7 01 add $0x1,%edi 2a:* 49 8b 17 mov (%r15),%rdx \u0026lt;-- trapping instruction 2d: 49 89 11 mov %rdx,(%r9) 30: 41 8b 57 28 mov 0x28(%r15),%edx 34: 45 8b 5f 34 mov 0x34(%r15),%r11d 38: 49 c7 07 00 00 00 00 movq $0x0,(%r15) 3f: 49 rex.WBCode starting with the faulting instruction=========================================== 0: 49 8b 17 mov (%r15),%rdx 3: 49 89 11 mov %rdx,(%r9) 6: 41 8b 57 28 mov 0x28(%r15),%edx a: 45 8b 5f 34 mov 0x34(%r15),%r11d e: 49 c7 07 00 00 00 00 movq $0x0,(%r15) 15: 49 rex.WB[ 70.724561] RSP: 0018:ffff95ae85e6fb90 EFLAGS: 00000202[ 70.724561] RAX: 0000000002000000 RBX: ffff95ae841de000 RCX: 0000000000000000[ 70.724561] RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000001[ 70.724561] RBP: ffff95ae85e6fbf8 R08: 0000000000000000 R09: ffff95b710a30000[ 70.724561] R10: 0000000000000000 R11: bdf289445ce31881 R12: ffff95ae85e6fc58[ 70.724561] R13: 0000000000000000 R14: 0000000000000040 R15: 0000000000000000[ 70.724561] FS: 000000002c5c1380(0000) GS:ffff95bd7fcc0000(0000) knlGS:0000000000000000[ 70.724561] CS: 0010 DS: 0000 ES: 0000 C---truncated---(CVE-2024-49949)\n\nIn the Linux kernel, the following vulnerability has been resolved:Bluetooth: L2CAP: Fix uaf in l2cap_connect[Syzbot reported]BUG: KASAN: slab-use-after-free in l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949Read of size 8 at addr ffff8880241e9800 by task kworker/u9:0/54CPU: 0 UID: 0 PID: 54 Comm: kworker/u9:0 Not tainted 6.11.0-rc6-syzkaller-00268-g788220eee30d #0Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024Workqueue: hci2 hci_rx_workCall Trace: \u0026lt;TASK\u0026gt; __dump_stack lib/dump_stack.c:93 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:119 print_address_description mm/kasan/report.c:377 [inline] print_report+0xc3/0x620 mm/kasan/report.c:488 kasan_report+0xd9/0x110 mm/kasan/report.c:601 l2cap_connect.constprop.0+0x10d8/0x1270 net/bluetooth/l2cap_core.c:3949 l2cap_connect_req net/bluetooth/l2cap_core.c:4080 [inline] l2cap_bredr_sig_cmd net/bluetooth/l2cap_core.c:4772 [inline] l2cap_sig_channel net/bluetooth/l2cap_core.c:5543 [inline] l2cap_recv_frame+0xf0b/0x8eb0 net/bluetooth/l2cap_core.c:6825 l2cap_recv_acldata+0x9b4/0xb70 net/bluetooth/l2cap_core.c:7514 hci_acldata_packet net/bluetooth/hci_core.c:3791 [inline] hci_rx_work+0xaab/0x1610 net/bluetooth/hci_core.c:4028 process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231 process_scheduled_works kernel/workqueue.c:3312 [inline] worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389 kthread+0x2c1/0x3a0 kernel/kthread.c:389 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244...Freed by task 5245: kasan_save_stack+0x33/0x60 mm/kasan/common.c:47 kasan_save_track+0x14/0x30 mm/kasan/common.c:68 kasan_save_free_info+0x3b/0x60 mm/kasan/generic.c:579 poison_slab_object+0xf7/0x160 mm/kasan/common.c:240 __kasan_slab_free+0x32/0x50 mm/kasan/common.c:256 kasan_slab_free include/linux/kasan.h:184 [inline] slab_free_hook mm/slub.c:2256 [inline] slab_free mm/slub.c:4477 [inline] kfree+0x12a/0x3b0 mm/slub.c:4598 l2cap_conn_free net/bluetooth/l2cap_core.c:1810 [inline] kref_put include/linux/kref.h:65 [inline] l2cap_conn_put net/bluetooth/l2cap_core.c:1822 [inline] l2cap_conn_del+0x59d/0x730 net/bluetooth/l2cap_core.c:1802 l2cap_connect_cfm+0x9e6/0xf80 net/bluetooth/l2cap_core.c:7241 hci_connect_cfm include/net/bluetooth/hci_core.h:1960 [inline] hci_conn_failed+0x1c3/0x370 net/bluetooth/hci_conn.c:1265 hci_abort_conn_sync+0x75a/0xb50 net/bluetooth/hci_sync.c:5583 abort_conn_sync+0x197/0x360 net/bluetooth/hci_conn.c:2917 hci_cmd_sync_work+0x1a4/0x410 net/bluetooth/hci_sync.c:328 process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231 process_scheduled_works kernel/workqueue.c:3312 [inline] worker_thread+0x6c8/0xed0 kernel/workqueue.c:3389 kthread+0x2c1/0x3a0 kernel/kthread.c:389 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244(CVE-2024-49950)\n\nIn the Linux kernel, the following vulnerability has been resolved:ocfs2: fix null-ptr-deref when journal load failed.During the mounting process, if journal_reset() fails because of too shortjournal, then lead to jbd2_journal_load() fails with NULL j_sb_buffer. Subsequently, ocfs2_journal_shutdown() callsjbd2_journal_flush()-\u0026gt;jbd2_cleanup_journal_tail()-\u0026gt;__jbd2_update_log_tail()-\u0026gt;jbd2_journal_update_sb_log_tail()-\u0026gt;lock_buffer(journal-\u0026gt;j_sb_buffer), resulting in a null-pointerdereference error.To resolve this issue, we should check the JBD2_LOADED flag to ensure thejournal was properly loaded. Additionally, use journal instead ofosb-\u0026gt;journal directly to simplify the code.(CVE-2024-49957)\n\nIn the Linux kernel, the following vulnerability has been resolved:ACPICA: check null return of ACPI_ALLOCATE_ZEROED() in acpi_db_convert_to_package()ACPICA commit 4d4547cf13cca820ff7e0f859ba83e1a610b9fd0ACPI_ALLOCATE_ZEROED() may fail, elements might be NULL and will causeNULL pointer dereference later.[ rjw: Subject and changelog edits ](CVE-2024-49962)\n\nIn the Linux kernel, the following vulnerability has been resolved:static_call: Handle module init failure correctly in static_call_del_module()Module insertion invokes static_call_add_module() to initialize the staticcalls in a module. static_call_add_module() invokes __static_call_init(),which allocates a struct static_call_mod to either encapsulate the built-instatic call sites of the associated key into it so further modules can beadded or to append the module to the module chain.If that allocation fails the function returns with an error code and themodule core invokes static_call_del_module() to clean up eventually addedstatic_call_mod entries.This works correctly, when all keys used by the module were converted overto a module chain before the failure. If not then static_call_del_module()causes a #GP as it blindly assumes that key::mods points to a valid structstatic_call_mod.The problem is that key::mods is not a individual struct member of structstatic_call_key, it s part of a union to save space: union { /* bit 0: 0 = mods, 1 = sites */ unsigned long type; struct static_call_mod *mods; struct static_call_site *sites; };key::sites is a pointer to the list of built-in usage sites of the staticcall. The type of the pointer is differentiated by bit 0. A mods pointerhas the bit clear, the sites pointer has the bit set.As static_call_del_module() blidly assumes that the pointer is a validstatic_call_mod type, it fails to check for this failure case anddereferences the pointer to the list of built-in call sites, which isobviously bogus.Cure it by checking whether the key has a sites or a mods pointer.If it s a sites pointer then the key is not to be touched. As the sites arewalked in the same order as in __static_call_init() the site walk can beterminated because all subsequent sites have not been touched by the initcode due to the error exit.If it was converted before the allocation fail, then the inner loop whichsearches for a module match will find nothing.A fail in the second allocation in __static_call_init() is harmless anddoes not require special treatment. The first allocation succeeded andconverted the key to a module chain. That first entry has mod::mod == NULLand mod::next == NULL, so the inner loop of static_call_del_module() willneither find a module match nor a module chain. The next site in the walkwas either already converted, but can t match the module, or it will exitthe outer loop because it has a static_call_site pointer and not astatic_call_mod pointer.(CVE-2024-50002)\n\nIn the Linux kernel, the following vulnerability has been resolved:mac802154: Fix potential RCU dereference issue in mac802154_scan_workerIn the `mac802154_scan_worker` function, the `scan_req-\u0026gt;type` field wasaccessed after the RCU read-side critical section was unlocked. Accordingto RCU usage rules, this is illegal and can lead to unpredictablebehavior, such as accessing memory that has been updated or causinguse-after-free issues.This possible bug was identified using a static analysis tool developedby myself, specifically designed to detect RCU-related issues.To address this, the `scan_req-\u0026gt;type` value is now stored in a localvariable `scan_req_type` while still within the RCU read-side criticalsection. The `scan_req_type` is then used after the RCU lock is released,ensuring that the type value is safely accessed without violating RCUrules.(CVE-2024-50005)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnilfs2: fix null-ptr-deref in block_touch_buffer tracepoint\n\nPatch series \u0026quot;nilfs2: fix null-ptr-deref bugs on block tracepoints\u0026quot;.\n\nThis series fixes null pointer dereference bugs that occur when using\nnilfs2 and two block-related tracepoints.\n\n\nThis patch (of 2):\n\nIt has been reported that when using \u0026quot;block:block_touch_buffer\u0026quot;\ntracepoint, touch_buffer() called from __nilfs_get_folio_block() causes a\nNULL pointer dereference, or a general protection fault when KASAN is\nenabled.\n\nThis happens because since the tracepoint was added in touch_buffer(), it\nreferences the dev_t member bh-\u0026gt;b_bdev-\u0026gt;bd_dev regardless of whether the\nbuffer head has a pointer to a block_device structure. In the current\nimplementation, the block_device structure is set after the function\nreturns to the caller.\n\nHere, touch_buffer() is used to mark the folio/page that owns the buffer\nhead as accessed, but the common search helper for folio/page used by the\ncaller function was optimized to mark the folio/page as accessed when it\nwas reimplemented a long time ago, eliminating the need to call\ntouch_buffer() here in the first place.\n\nSo this solves the issue by eliminating the touch_buffer() call itself.(CVE-2024-53131)\n\nIn the Linux kernel, the following vulnerability has been resolved:drm: adv7511: Fix use-after-free in adv7533_attach_dsi()The host_node pointer was assigned and freed in adv7533_parse_dt(), andlater, adv7533_attach_dsi() uses the same. Fix this use-after-free issueby\u00a0dropping of_node_put() in adv7533_parse_dt() and calling of_node_put()in error path of probe() and also in the remove().(CVE-2024-57887)\n\nIn the Linux kernel, the following vulnerability has been resolved:ila: serialize calls to nf_register_net_hooks()syzbot found a race in ila_add_mapping() [1]commit 031ae72825ce ( ila: call nf_unregister_net_hooks() sooner )attempted to fix a similar issue.Looking at the syzbot repro, we have concurrent ILA_CMD_ADD commands.Add a mutex to make sure at most one thread is calling nf_register_net_hooks().[1] BUG: KASAN: slab-use-after-free in rht_key_hashfn include/linux/rhashtable.h:159 [inline] BUG: KASAN: slab-use-after-free in __rhashtable_lookup.constprop.0+0x426/0x550 include/linux/rhashtable.h:604Read of size 4 at addr ffff888028f40008 by task dhcpcd/5501CPU: 1 UID: 0 PID: 5501 Comm: dhcpcd Not tainted 6.13.0-rc4-syzkaller-00054-gd6ef8b40d075 #0Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024Call Trace: \u0026lt;IRQ\u0026gt; __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xc3/0x620 mm/kasan/report.c:489 kasan_report+0xd9/0x110 mm/kasan/report.c:602 rht_key_hashfn include/linux/rhashtable.h:159 [inline] __rhashtable_lookup.constprop.0+0x426/0x550 include/linux/rhashtable.h:604 rhashtable_lookup include/linux/rhashtable.h:646 [inline] rhashtable_lookup_fast include/linux/rhashtable.h:672 [inline] ila_lookup_wildcards net/ipv6/ila/ila_xlat.c:127 [inline] ila_xlat_addr net/ipv6/ila/ila_xlat.c:652 [inline] ila_nf_input+0x1ee/0x620 net/ipv6/ila/ila_xlat.c:185 nf_hook_entry_hookfn include/linux/netfilter.h:154 [inline] nf_hook_slow+0xbb/0x200 net/netfilter/core.c:626 nf_hook.constprop.0+0x42e/0x750 include/linux/netfilter.h:269 NF_HOOK include/linux/netfilter.h:312 [inline] ipv6_rcv+0xa4/0x680 net/ipv6/ip6_input.c:309 __netif_receive_skb_one_core+0x12e/0x1e0 net/core/dev.c:5672 __netif_receive_skb+0x1d/0x160 net/core/dev.c:5785 process_backlog+0x443/0x15f0 net/core/dev.c:6117 __napi_poll.constprop.0+0xb7/0x550 net/core/dev.c:6883 napi_poll net/core/dev.c:6952 [inline] net_rx_action+0xa94/0x1010 net/core/dev.c:7074 handle_softirqs+0x213/0x8f0 kernel/softirq.c:561 __do_softirq kernel/softirq.c:595 [inline] invoke_softirq kernel/softirq.c:435 [inline] __irq_exit_rcu+0x109/0x170 kernel/softirq.c:662 irq_exit_rcu+0x9/0x30 kernel/softirq.c:678 instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1049 [inline] sysvec_apic_timer_interrupt+0xa4/0xc0 arch/x86/kernel/apic/apic.c:1049(CVE-2024-57900)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njfs: add check read-only before txBeginAnon() call\n\nAdded a read-only check before calling `txBeginAnon` in `extAlloc`\nand `extRecord`. This prevents modification attempts on a read-only\nmounted filesystem, avoiding potential errors or crashes.\n\nCall trace:\n txBeginAnon+0xac/0x154\n extAlloc+0xe8/0xdec fs/jfs/jfs_extent.c:78\n jfs_get_block+0x340/0xb98 fs/jfs/inode.c:248\n __block_write_begin_int+0x580/0x166c fs/buffer.c:2128\n __block_write_begin fs/buffer.c:2177 [inline]\n block_write_begin+0x98/0x11c fs/buffer.c:2236\n jfs_write_begin+0x44/0x88 fs/jfs/inode.c:299(CVE-2024-58095)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix use-after-free in smb2_lock\n\nIf smb_lock-\u0026gt;zero_len has value, -\u0026gt;llist of smb_lock is not delete and\nflock is old one. It will cause use-after-free on error handling\nroutine.(CVE-2025-21945)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/display: Fix slab-use-after-free on hdcp_work\n\n[Why]\nA slab-use-after-free is reported when HDCP is destroyed but the\nproperty_validate_dwork queue is still running.\n\n[How]\nCancel the delayed work when destroying workqueue.\n\n(cherry picked from commit 725a04ba5a95e89c89633d4322430cfbca7ce128)(CVE-2025-21968)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: xhci: Apply the link chain quirk on NEC isoc endpoints\n\nTwo clearly different specimens of NEC uPD720200 (one with start/stop\nbug, one without) were seen to cause IOMMU faults after some Missed\nService Errors. Faulting address is immediately after a transfer ring\nsegment and patched dynamic debug messages revealed that the MSE was\nreceived when waiting for a TD near the end of that segment:\n\n[ 1.041954] xhci_hcd: Miss service interval error for slot 1 ep 2 expected TD DMA ffa08fe0\n[ 1.042120] xhci_hcd: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffa09000 flags=0x0000]\n[ 1.042146] xhci_hcd: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0005 address=0xffa09040 flags=0x0000]\n\nIt gets even funnier if the next page is a ring segment accessible to\nthe HC. Below, it reports MSE in segment at ff1e8000, plows through a\nzero-filled page at ff1e9000 and starts reporting events for TRBs in\npage at ff1ea000 every microframe, instead of jumping to seg ff1e6000.\n\n[ 7.041671] xhci_hcd: Miss service interval error for slot 1 ep 2 expected TD DMA ff1e8fe0\n[ 7.041999] xhci_hcd: Miss service interval error for slot 1 ep 2 expected TD DMA ff1e8fe0\n[ 7.042011] xhci_hcd: WARN: buffer overrun event for slot 1 ep 2 on endpoint\n[ 7.042028] xhci_hcd: All TDs skipped for slot 1 ep 2. Clear skip flag.\n[ 7.042134] xhci_hcd: WARN: buffer overrun event for slot 1 ep 2 on endpoint\n[ 7.042138] xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 31\n[ 7.042144] xhci_hcd: Looking for event-dma 00000000ff1ea040 trb-start 00000000ff1e6820 trb-end 00000000ff1e6820\n[ 7.042259] xhci_hcd: WARN: buffer overrun event for slot 1 ep 2 on endpoint\n[ 7.042262] xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 31\n[ 7.042266] xhci_hcd: Looking for event-dma 00000000ff1ea050 trb-start 00000000ff1e6820 trb-end 00000000ff1e6820\n\nAt some point completion events change from Isoch Buffer Overrun to\nShort Packet and the HC finally finds cycle bit mismatch in ff1ec000.\n\n[ 7.098130] xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13\n[ 7.098132] xhci_hcd: Looking for event-dma 00000000ff1ecc50 trb-start 00000000ff1e6820 trb-end 00000000ff1e6820\n[ 7.098254] xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13\n[ 7.098256] xhci_hcd: Looking for event-dma 00000000ff1ecc60 trb-start 00000000ff1e6820 trb-end 00000000ff1e6820\n[ 7.098379] xhci_hcd: Overrun event on slot 1 ep 2\n\nIt\u0026apos;s possible that data from the isochronous device were written to\nrandom buffers of pending TDs on other endpoints (either IN or OUT),\nother devices or even other HCs in the same IOMMU domain.\n\nLastly, an error from a different USB device on another HC. Was it\ncaused by the above? I don\u0026apos;t know, but it may have been. The disk\nwas working without any other issues and generated PCIe traffic to\nstarve the NEC of upstream BW and trigger those MSEs. The two HCs\nshared one x1 slot by means of a commercial \u0026quot;PCIe splitter\u0026quot; board.\n\n[ 7.162604] usb 10-2: reset SuperSpeed USB device number 3 using xhci_hcd\n[ 7.178990] sd 9:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=0s\n[ 7.179001] sd 9:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 04 02 ae 00 00 02 00 00\n[ 7.179004] I/O error, dev sdb, sector 67284480 op 0x0:(READ) flags 0x80700 phys_seg 5 prio class 0\n\nFortunately, it appears that this ridiculous bug is avoided by setting\nthe chain bit of Link TRBs on isochronous rings. Other ancient HCs are\nknown which also expect the bit to be set and they ignore Link TRBs if\nit\u0026apos;s not. Reportedly, 0.95 spec guaranteed that the bit is set.\n\nThe bandwidth-starved NEC HC running a 32KB/uframe UVC endpoint reports\ntens of MSEs per second and runs into the bug within seconds. Chaining\nLink TRBs allows the same workload to run for many minutes, many times.\n\nNo ne\n---truncated---(CVE-2025-22022)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnfsd: put dl_stid if fail to queue dl_recall\n\nBefore calling nfsd4_run_cb to queue dl_recall to the callback_wq, we\nincrement the reference count of dl_stid.\nWe expect that after the corresponding work_struct is processed, the\nreference count of dl_stid will be decremented through the callback\nfunction nfsd4_cb_recall_release.\nHowever, if the call to nfsd4_run_cb fails, the incremented reference\ncount of dl_stid will not be decremented correspondingly, leading to the\nfollowing nfs4_stid leak:\nunreferenced object 0xffff88812067b578 (size 344):\n comm \u0026quot;nfsd\u0026quot;, pid 2761, jiffies 4295044002 (age 5541.241s)\n hex dump (first 32 bytes):\n 01 00 00 00 6b 6b 6b 6b b8 02 c0 e2 81 88 ff ff ....kkkk........\n 00 6b 6b 6b 6b 6b 6b 6b 00 00 00 00 ad 4e ad de .kkkkkkk.....N..\n backtrace:\n kmem_cache_alloc+0x4b9/0x700\n nfsd4_process_open1+0x34/0x300\n nfsd4_open+0x2d1/0x9d0\n nfsd4_proc_compound+0x7a2/0xe30\n nfsd_dispatch+0x241/0x3e0\n svc_process_common+0x5d3/0xcc0\n svc_process+0x2a3/0x320\n nfsd+0x180/0x2e0\n kthread+0x199/0x1d0\n ret_from_fork+0x30/0x50\n ret_from_fork_asm+0x1b/0x30\nunreferenced object 0xffff8881499f4d28 (size 368):\n comm \u0026quot;nfsd\u0026quot;, pid 2761, jiffies 4295044005 (age 5541.239s)\n hex dump (first 32 bytes):\n 01 00 00 00 00 00 00 00 30 4d 9f 49 81 88 ff ff ........0M.I....\n 30 4d 9f 49 81 88 ff ff 20 00 00 00 01 00 00 00 0M.I.... .......\n backtrace:\n kmem_cache_alloc+0x4b9/0x700\n nfs4_alloc_stid+0x29/0x210\n alloc_init_deleg+0x92/0x2e0\n nfs4_set_delegation+0x284/0xc00\n nfs4_open_delegation+0x216/0x3f0\n nfsd4_process_open2+0x2b3/0xee0\n nfsd4_open+0x770/0x9d0\n nfsd4_proc_compound+0x7a2/0xe30\n nfsd_dispatch+0x241/0x3e0\n svc_process_common+0x5d3/0xcc0\n svc_process+0x2a3/0x320\n nfsd+0x180/0x2e0\n kthread+0x199/0x1d0\n ret_from_fork+0x30/0x50\n ret_from_fork_asm+0x1b/0x30\nFix it by checking the result of nfsd4_run_cb and call nfs4_put_stid if\nfail to queue dl_recall.(CVE-2025-22025)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnfsd: don\u0026apos;t ignore the return code of svc_proc_register()\n\nCurrently, nfsd_proc_stat_init() ignores the return value of\nsvc_proc_register(). If the procfile creation fails, then the kernel\nwill WARN when it tries to remove the entry later.\n\nFix nfsd_proc_stat_init() to return the same type of pointer as\nsvc_proc_register(), and fix up nfsd_net_init() to check that and fail\nthe nfsd_net construction if it occurs.\n\nsvc_proc_register() can fail if the dentry can\u0026apos;t be allocated, or if an\nidentical dentry already exists. The second case is pretty unlikely in\nthe nfsd_net construction codepath, so if this happens, return -ENOMEM.(CVE-2025-22026)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix overflow in dacloffset bounds check\n\nThe dacloffset field was originally typed as int and used in an\nunchecked addition, which could overflow and bypass the existing\nbounds check in both smb_check_perm_dacl() and smb_inherit_dacl().\n\nThis could result in out-of-bounds memory access and a kernel crash\nwhen dereferencing the DACL pointer.\n\nThis patch converts dacloffset to unsigned int and uses\ncheck_add_overflow() to validate access to the DACL.(CVE-2025-22039)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: add bounds check for create lease context\n\nAdd missing bounds check for create lease context.(CVE-2025-22042)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: add bounds check for durable handle context\n\nAdd missing bounds check for durable handle context.(CVE-2025-22043)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: ath11k: update channel list in reg notifier instead reg worker\n\nCurrently when ath11k gets a new channel list, it will be processed\naccording to the following steps:\n1. update new channel list to cfg80211 and queue reg_work.\n2. cfg80211 handles new channel list during reg_work.\n3. update cfg80211\u0026apos;s handled channel list to firmware by\nath11k_reg_update_chan_list().\n\nBut ath11k will immediately execute step 3 after reg_work is just\nqueued. Since step 2 is asynchronous, cfg80211 may not have completed\nhandling the new channel list, which may leading to an out-of-bounds\nwrite error:\nBUG: KASAN: slab-out-of-bounds in ath11k_reg_update_chan_list\nCall Trace:\n ath11k_reg_update_chan_list+0xbfe/0xfe0 [ath11k]\n kfree+0x109/0x3a0\n ath11k_regd_update+0x1cf/0x350 [ath11k]\n ath11k_regd_update_work+0x14/0x20 [ath11k]\n process_one_work+0xe35/0x14c0\n\nShould ensure step 2 is completely done before executing step 3. Thus\nWen raised patch[1]. When flag NL80211_REGDOM_SET_BY_DRIVER is set,\ncfg80211 will notify ath11k after step 2 is done.\n\nSo enable the flag NL80211_REGDOM_SET_BY_DRIVER then cfg80211 will\nnotify ath11k after step 2 is done. At this time, there will be no\nKASAN bug during the execution of the step 3.\n\n[1] https://patchwork.kernel.org/project/linux-wireless/patch/(CVE-2025-23133)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nriscv: uprobes: Add missing fence.i after building the XOL buffer\n\nThe XOL (execute out-of-line) buffer is used to single-step the\nreplaced instruction(s) for uprobes. The RISC-V port was missing a\nproper fence.i (i$ flushing) after constructing the XOL buffer, which\ncan result in incorrect execution of stale/broken instructions.\n\nThis was found running the BPF selftests \u0026quot;test_progs:\nuprobe_autoattach, attach_probe\u0026quot; on the Spacemit K1/X60, where the\nuprobes tests randomly blew up.(CVE-2025-37822)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: mpi3mr: Synchronous access b/w reset and tm thread for reply queue\n\nWhen the task management thread processes reply queues while the reset\nthread resets them, the task management thread accesses an invalid queue ID\n(0xFFFF), set by the reset thread, which points to unallocated memory,\ncausing a crash.\n\nAdd flag \u0026apos;io_admin_reset_sync\u0026apos; to synchronize access between the reset,\nI/O, and admin threads. Before a reset, the reset handler sets this flag to\nblock I/O and admin processing threads. If any thread bypasses the initial\ncheck, the reset thread waits up to 10 seconds for processing to finish. If\nthe wait exceeds 10 seconds, the controller is marked as unrecoverable.(CVE-2025-37861)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix use-after-free in session logoff\n\nThe sess-\u0026gt;user object can currently be in use by another thread, for\nexample if another connection has sent a session setup request to\nbind to the session being free\u0026apos;d. The handler for that connection could\nbe in the smb2_sess_setup function which makes use of sess-\u0026gt;user.(CVE-2025-37899)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: cfg80211: fix out-of-bounds access during multi-link element defragmentation\n\nCurrently during the multi-link element defragmentation process, the\nmulti-link element length added to the total IEs length when calculating\nthe length of remaining IEs after the multi-link element in\ncfg80211_defrag_mle(). This could lead to out-of-bounds access if the\nmulti-link element or its corresponding fragment elements are the last\nelements in the IEs buffer.\n\nTo address this issue, correctly calculate the remaining IEs length by\ndeducting the multi-link element end offset from total IEs end offset.(CVE-2025-37973)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: typec: ucsi: displayport: Fix NULL pointer access\n\nThis patch ensures that the UCSI driver waits for all pending tasks in the\nucsi_displayport_work workqueue to finish executing before proceeding with\nthe partner removal.(CVE-2025-37994)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: ipset: fix region locking in hash types\n\nRegion locking introduced in v5.6-rc4 contained three macros to handle\nthe region locks: ahash_bucket_start(), ahash_bucket_end() which gave\nback the start and end hash bucket values belonging to a given region\nlock and ahash_region() which should give back the region lock belonging\nto a given hash bucket. The latter was incorrect which can lead to a\nrace condition between the garbage collector and adding new elements\nwhen a hash type of set is defined with timeouts.(CVE-2025-37997)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: ti: k3-udma: Add missing locking\n\nRecent kernels complain about a missing lock in k3-udma.c when the lock\nvalidator is enabled:\n\n[ 4.128073] WARNING: CPU: 0 PID: 746 at drivers/dma/ti/../virt-dma.h:169 udma_start.isra.0+0x34/0x238\n[ 4.137352] CPU: 0 UID: 0 PID: 746 Comm: kworker/0:3 Not tainted 6.12.9-arm64 #28\n[ 4.144867] Hardware name: pp-v12 (DT)\n[ 4.148648] Workqueue: events udma_check_tx_completion\n[ 4.153841] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[ 4.160834] pc : udma_start.isra.0+0x34/0x238\n[ 4.165227] lr : udma_start.isra.0+0x30/0x238\n[ 4.169618] sp : ffffffc083cabcf0\n[ 4.172963] x29: ffffffc083cabcf0 x28: 0000000000000000 x27: ffffff800001b005\n[ 4.180167] x26: ffffffc0812f0000 x25: 0000000000000000 x24: 0000000000000000\n[ 4.187370] x23: 0000000000000001 x22: 00000000e21eabe9 x21: ffffff8000fa0670\n[ 4.194571] x20: ffffff8001b6bf00 x19: ffffff8000fa0430 x18: ffffffc083b95030\n[ 4.201773] x17: 0000000000000000 x16: 00000000f0000000 x15: 0000000000000048\n[ 4.208976] x14: 0000000000000048 x13: 0000000000000000 x12: 0000000000000001\n[ 4.216179] x11: ffffffc08151a240 x10: 0000000000003ea1 x9 : ffffffc08046ab68\n[ 4.223381] x8 : ffffffc083cabac0 x7 : ffffffc081df3718 x6 : 0000000000029fc8\n[ 4.230583] x5 : ffffffc0817ee6d8 x4 : 0000000000000bc0 x3 : 0000000000000000\n[ 4.237784] x2 : 0000000000000000 x1 : 00000000001fffff x0 : 0000000000000000\n[ 4.244986] Call trace:\n[ 4.247463] udma_start.isra.0+0x34/0x238\n[ 4.251509] udma_check_tx_completion+0xd0/0xdc\n[ 4.256076] process_one_work+0x244/0x3fc\n[ 4.260129] process_scheduled_works+0x6c/0x74\n[ 4.264610] worker_thread+0x150/0x1dc\n[ 4.268398] kthread+0xd8/0xe8\n[ 4.271492] ret_from_fork+0x10/0x20\n[ 4.275107] irq event stamp: 220\n[ 4.278363] hardirqs last enabled at (219): [\u0026lt;ffffffc080a27c7c\u0026gt;] _raw_spin_unlock_irq+0x38/0x50\n[ 4.287183] hardirqs last disabled at (220): [\u0026lt;ffffffc080a1c154\u0026gt;] el1_dbg+0x24/0x50\n[ 4.294879] softirqs last enabled at (182): [\u0026lt;ffffffc080037e68\u0026gt;] handle_softirqs+0x1c0/0x3cc\n[ 4.303437] softirqs last disabled at (177): [\u0026lt;ffffffc080010170\u0026gt;] __do_softirq+0x1c/0x28\n[ 4.311559] ---[ end trace 0000000000000000 ]---\n\nThis commit adds the missing locking.(CVE-2025-38005)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\n__legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock\n\n... or we risk stealing final mntput from sync umount - raising mnt_count\nafter umount(2) has verified that victim is not busy, but before it\nhas set MNT_SYNC_UMOUNT; in that case __legitimize_mnt() doesn\u0026apos;t see\nthat it\u0026apos;s safe to quietly undo mnt_count increment and leaves dropping\nthe reference to caller, where it\u0026apos;ll be a full-blown mntput().\n\nCheck under mount_lock is needed; leaving the current one done before\ntaking that makes no sense - it\u0026apos;s nowhere near common enough to bother\nwith.(CVE-2025-38058)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/mm: Check return value from memblock_phys_alloc_range()\n\nAt least with CONFIG_PHYSICAL_START=0x100000, if there is \u0026lt; 4 MiB of\ncontiguous free memory available at this point, the kernel will crash\nand burn because memblock_phys_alloc_range() returns 0 on failure,\nwhich leads memblock_phys_free() to throw the first 4 MiB of physical\nmemory to the wolves.\n\nAt a minimum it should fail gracefully with a meaningful diagnostic,\nbut in fact everything seems to work fine without the weird reserve\nallocation.(CVE-2025-38071)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: Fix ECVF vports unload on shutdown flow\n\nFix shutdown flow UAF when a virtual function is created on the embedded\nchip (ECVF) of a BlueField device. In such case the vport acl ingress\ntable is not properly destroyed.\n\nECVF functionality is independent of ecpf_vport_exists capability and\nthus functions mlx5_eswitch_(enable|disable)_pf_vf_vports() should not\ntest it when enabling/disabling ECVF vports.\n\nkernel log:\n[] refcount_t: underflow; use-after-free.\n[] WARNING: CPU: 3 PID: 1 at lib/refcount.c:28\n refcount_warn_saturate+0x124/0x220\n----------------\n[] Call trace:\n[] refcount_warn_saturate+0x124/0x220\n[] tree_put_node+0x164/0x1e0 [mlx5_core]\n[] mlx5_destroy_flow_table+0x98/0x2c0 [mlx5_core]\n[] esw_acl_ingress_table_destroy+0x28/0x40 [mlx5_core]\n[] esw_acl_ingress_lgcy_cleanup+0x80/0xf4 [mlx5_core]\n[] esw_legacy_vport_acl_cleanup+0x44/0x60 [mlx5_core]\n[] esw_vport_cleanup+0x64/0x90 [mlx5_core]\n[] mlx5_esw_vport_disable+0xc0/0x1d0 [mlx5_core]\n[] mlx5_eswitch_unload_ec_vf_vports+0xcc/0x150 [mlx5_core]\n[] mlx5_eswitch_disable_sriov+0x198/0x2a0 [mlx5_core]\n[] mlx5_device_disable_sriov+0xb8/0x1e0 [mlx5_core]\n[] mlx5_sriov_detach+0x40/0x50 [mlx5_core]\n[] mlx5_unload+0x40/0xc4 [mlx5_core]\n[] mlx5_unload_one_devl_locked+0x6c/0xe4 [mlx5_core]\n[] mlx5_unload_one+0x3c/0x60 [mlx5_core]\n[] shutdown+0x7c/0xa4 [mlx5_core]\n[] pci_device_shutdown+0x3c/0xa0\n[] device_shutdown+0x170/0x340\n[] __do_sys_reboot+0x1f4/0x2a0\n[] __arm64_sys_reboot+0x2c/0x40\n[] invoke_syscall+0x78/0x100\n[] el0_svc_common.constprop.0+0x54/0x184\n[] do_el0_svc+0x30/0xac\n[] el0_svc+0x48/0x160\n[] el0t_64_sync_handler+0xa4/0x12c\n[] el0t_64_sync+0x1a4/0x1a8\n[] --[ end trace 9c4601d68c70030e ]---(CVE-2025-38109)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnfsd: Initialize ssc before laundromat_work to prevent NULL dereference\n\nIn nfs4_state_start_net(), laundromat_work may access nfsd_ssc through\nnfs4_laundromat -\u0026gt; nfsd4_ssc_expire_umount. If nfsd_ssc isn\u0026apos;t initialized,\nthis can cause NULL pointer dereference.\n\nNormally the delayed start of laundromat_work allows sufficient time for\nnfsd_ssc initialization to complete. However, when the kernel waits too\nlong for userspace responses (e.g. in nfs4_state_start_net -\u0026gt;\nnfsd4_end_grace -\u0026gt; nfsd4_record_grace_done -\u0026gt; nfsd4_cld_grace_done -\u0026gt;\ncld_pipe_upcall -\u0026gt; __cld_pipe_upcall -\u0026gt; wait_for_completion path), the\ndelayed work may start before nfsd_ssc initialization finishes.\n\nFix this by moving nfsd_ssc initialization before starting laundromat_work.(CVE-2025-38231)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nkernfs: Relax constraint in draining guard\n\nThe active reference lifecycle provides the break/unbreak mechanism but\nthe active reference is not truly active after unbreak -- callers don\u0026apos;t\nuse it afterwards but it\u0026apos;s important for proper pairing of kn-\u0026gt;active\ncounting. Assuming this mechanism is in place, the WARN check in\nkernfs_should_drain_open_files() is too sensitive -- it may transiently\ncatch those (rightful) callers between\nkernfs_unbreak_active_protection() and kernfs_put_active() as found out by Chen\nRidong:\n\n\tkernfs_remove_by_name_ns\tkernfs_get_active // active=1\n\t__kernfs_remove\t\t\t\t\t // active=0x80000002\n\tkernfs_drain\t\t\t...\n\twait_event\n\t//waiting (active == 0x80000001)\n\t\t\t\t\tkernfs_break_active_protection\n\t\t\t\t\t// active = 0x80000001\n\t// continue\n\t\t\t\t\tkernfs_unbreak_active_protection\n\t\t\t\t\t// active = 0x80000002\n\t...\n\tkernfs_should_drain_open_files\n\t// warning occurs\n\t\t\t\t\tkernfs_put_active\n\nTo avoid the false positives (mind panic_on_warn) remove the check altogether.\n(This is meant as quick fix, I think active reference break/unbreak may be\nsimplified with larger rework.)(CVE-2025-38282)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: Always pass notifications when child class becomes empty\n\nCertain classful qdiscs may invoke their classes\u0026apos; dequeue handler on an\nenqueue operation. This may unexpectedly empty the child qdisc and thus\nmake an in-flight class passive via qlen_notify(). Most qdiscs do not\nexpect such behaviour at this point in time and may re-activate the\nclass eventually anyways which will lead to a use-after-free.\n\nThe referenced fix commit attempted to fix this behavior for the HFSC\ncase by moving the backlog accounting around, though this turned out to\nbe incomplete since the parent\u0026apos;s parent may run into the issue too.\nThe following reproducer demonstrates this use-after-free:\n\n tc qdisc add dev lo root handle 1: drr\n tc filter add dev lo parent 1: basic classid 1:1\n tc class add dev lo parent 1: classid 1:1 drr\n tc qdisc add dev lo parent 1:1 handle 2: hfsc def 1\n tc class add dev lo parent 2: classid 2:1 hfsc rt m1 8 d 1 m2 0\n tc qdisc add dev lo parent 2:1 handle 3: netem\n tc qdisc add dev lo parent 3:1 handle 4: blackhole\n\n echo 1 | socat -u STDIN UDP4-DATAGRAM:127.0.0.1:8888\n tc class delete dev lo classid 1:1\n echo 1 | socat -u STDIN UDP4-DATAGRAM:127.0.0.1:8888\n\nSince backlog accounting issues leading to a use-after-frees on stale\nclass pointers is a recurring pattern at this point, this patch takes\na different approach. Instead of trying to fix the accounting, the patch\nensures that qdisc_tree_reduce_backlog always calls qlen_notify when\nthe child qdisc is empty. This solves the problem because deletion of\nqdiscs always involves a call to qdisc_reset() and / or\nqdisc_purge_queue() which ultimately resets its qlen to 0 thus causing\nthe following qdisc_tree_reduce_backlog() to report to the parent. Note\nthat this may call qlen_notify on passive classes multiple times. This\nis not a problem after the recent patch series that made all the\nclassful qdiscs qlen_notify() handlers idempotent.(CVE-2025-38350)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/display: Check dce_hwseq before dereferencing it\n\n[WHAT]\n\nhws was checked for null earlier in dce110_blank_stream, indicating hws\ncan be null, and should be checked whenever it is used.\n\n(cherry picked from commit 79db43611ff61280b6de58ce1305e0b2ecf675ad)(CVE-2025-38361)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnbd: fix uaf in nbd_genl_connect() error path\n\nThere is a use-after-free issue in nbd:\n\nblock nbd6: Receive control failed (result -104)\nblock nbd6: shutting down sockets\n==================================================================\nBUG: KASAN: slab-use-after-free in recv_work+0x694/0xa80 drivers/block/nbd.c:1022\nWrite of size 4 at addr ffff8880295de478 by task kworker/u33:0/67\n\nCPU: 2 UID: 0 PID: 67 Comm: kworker/u33:0 Not tainted 6.15.0-rc5-syzkaller-00123-g2c89c1b655c0 #0 PREEMPT(full)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014\nWorkqueue: nbd6-recv recv_work\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __dump_stack lib/dump_stack.c:94 [inline]\n dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120\n print_address_description mm/kasan/report.c:408 [inline]\n print_report+0xc3/0x670 mm/kasan/report.c:521\n kasan_report+0xe0/0x110 mm/kasan/report.c:634\n check_region_inline mm/kasan/generic.c:183 [inline]\n kasan_check_range+0xef/0x1a0 mm/kasan/generic.c:189\n instrument_atomic_read_write include/linux/instrumented.h:96 [inline]\n atomic_dec include/linux/atomic/atomic-instrumented.h:592 [inline]\n recv_work+0x694/0xa80 drivers/block/nbd.c:1022\n process_one_work+0x9cc/0x1b70 kernel/workqueue.c:3238\n process_scheduled_works kernel/workqueue.c:3319 [inline]\n worker_thread+0x6c8/0xf10 kernel/workqueue.c:3400\n kthread+0x3c2/0x780 kernel/kthread.c:464\n ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:153\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245\n \u0026lt;/TASK\u0026gt;\n\nnbd_genl_connect() does not properly stop the device on certain\nerror paths after nbd_start_device() has been called. This causes\nthe error path to put nbd-\u0026gt;config while recv_work continue to use\nthe config after putting it, leading to use-after-free in recv_work.\n\nThis patch moves nbd_start_device() after the backend file creation.(CVE-2025-38443)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: Abort __tc_modify_qdisc if parent class does not exist\n\nLion\u0026apos;s patch [1] revealed an ancient bug in the qdisc API.\nWhenever a user creates/modifies a qdisc specifying as a parent another\nqdisc, the qdisc API will, during grafting, detect that the user is\nnot trying to attach to a class and reject. However grafting is\nperformed after qdisc_create (and thus the qdiscs\u0026apos; init callback) is\nexecuted. In qdiscs that eventually call qdisc_tree_reduce_backlog\nduring init or change (such as fq, hhf, choke, etc), an issue\narises. For example, executing the following commands:\n\nsudo tc qdisc add dev lo root handle a: htb default 2\nsudo tc qdisc add dev lo parent a: handle beef fq\n\nQdiscs such as fq, hhf, choke, etc unconditionally invoke\nqdisc_tree_reduce_backlog() in their control path init() or change() which\nthen causes a failure to find the child class; however, that does not stop\nthe unconditional invocation of the assumed child qdisc\u0026apos;s qlen_notify with\na null class. All these qdiscs make the assumption that class is non-null.\n\nThe solution is ensure that qdisc_leaf() which looks up the parent\nclass, and is invoked prior to qdisc_create(), should return failure on\nnot finding the class.\nIn this patch, we leverage qdisc_leaf to return ERR_PTRs whenever the\nparentid doesn\u0026apos;t correspond to a class, so that we can detect it\nearlier on and abort before qdisc_create is called.\n\n[1] https://lore.kernel.org/netdev/(CVE-2025-38457)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: vlan: fix VLAN 0 refcount imbalance of toggling filtering during runtime\n\nAssuming the \u0026quot;rx-vlan-filter\u0026quot; feature is enabled on a net device, the\n8021q module will automatically add or remove VLAN 0 when the net device\nis put administratively up or down, respectively. There are a couple of\nproblems with the above scheme.\n\nThe first problem is a memory leak that can happen if the \u0026quot;rx-vlan-filter\u0026quot;\nfeature is disabled while the device is running:\n\n # ip link add bond1 up type bond mode 0\n # ethtool -K bond1 rx-vlan-filter off\n # ip link del dev bond1\n\nWhen the device is put administratively down the \u0026quot;rx-vlan-filter\u0026quot;\nfeature is disabled, so the 8021q module will not remove VLAN 0 and the\nmemory will be leaked [1].\n\nAnother problem that can happen is that the kernel can automatically\ndelete VLAN 0 when the device is put administratively down despite not\nadding it when the device was put administratively up since during that\ntime the \u0026quot;rx-vlan-filter\u0026quot; feature was disabled. null-ptr-unref or\nbug_on[2] will be triggered by unregister_vlan_dev() for refcount\nimbalance if toggling filtering during runtime:\n\n$ ip link add bond0 type bond mode 0\n$ ip link add link bond0 name vlan0 type vlan id 0 protocol 802.1q\n$ ethtool -K bond0 rx-vlan-filter off\n$ ifconfig bond0 up\n$ ethtool -K bond0 rx-vlan-filter on\n$ ifconfig bond0 down\n$ ip link del vlan0\n\nRoot cause is as below:\nstep1: add vlan0 for real_dev, such as bond, team.\nregister_vlan_dev\n vlan_vid_add(real_dev,htons(ETH_P_8021Q),0) //refcnt=1\nstep2: disable vlan filter feature and enable real_dev\nstep3: change filter from 0 to 1\nvlan_device_event\n vlan_filter_push_vids\n ndo_vlan_rx_add_vid //No refcnt added to real_dev vlan0\nstep4: real_dev down\nvlan_device_event\n vlan_vid_del(dev, htons(ETH_P_8021Q), 0); //refcnt=0\n vlan_info_rcu_free //free vlan0\nstep5: delete vlan0\nunregister_vlan_dev\n BUG_ON(!vlan_info); //vlan_info is null\n\nFix both problems by noting in the VLAN info whether VLAN 0 was\nautomatically added upon NETDEV_UP and based on that decide whether it\nshould be deleted upon NETDEV_DOWN, regardless of the state of the\n\u0026quot;rx-vlan-filter\u0026quot; feature.\n\n[1]\nunreferenced object 0xffff8880068e3100 (size 256):\n comm \u0026quot;ip\u0026quot;, pid 384, jiffies 4296130254\n hex dump (first 32 bytes):\n 00 20 30 0d 80 88 ff ff 00 00 00 00 00 00 00 00 . 0.............\n 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................\n backtrace (crc 81ce31fa):\n __kmalloc_cache_noprof+0x2b5/0x340\n vlan_vid_add+0x434/0x940\n vlan_device_event.cold+0x75/0xa8\n notifier_call_chain+0xca/0x150\n __dev_notify_flags+0xe3/0x250\n rtnl_configure_link+0x193/0x260\n rtnl_newlink_create+0x383/0x8e0\n __rtnl_newlink+0x22c/0xa40\n rtnl_newlink+0x627/0xb00\n rtnetlink_rcv_msg+0x6fb/0xb70\n netlink_rcv_skb+0x11f/0x350\n netlink_unicast+0x426/0x710\n netlink_sendmsg+0x75a/0xc20\n __sock_sendmsg+0xc1/0x150\n ____sys_sendmsg+0x5aa/0x7b0\n ___sys_sendmsg+0xfc/0x180\n\n[2]\nkernel BUG at net/8021q/vlan.c:99!\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 0 UID: 0 PID: 382 Comm: ip Not tainted 6.16.0-rc3 #61 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996),\nBIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014\nRIP: 0010:unregister_vlan_dev (net/8021q/vlan.c:99 (discriminator 1))\nRSP: 0018:ffff88810badf310 EFLAGS: 00010246\nRAX: 0000000000000000 RBX: ffff88810da84000 RCX: ffffffffb47ceb9a\nRDX: dffffc0000000000 RSI: 0000000000000008 RDI: ffff88810e8b43c8\nRBP: 0000000000000000 R08: 0000000000000000 R09: fffffbfff6cefe80\nR10: ffffffffb677f407 R11: ffff88810badf3c0 R12: ffff88810e8b4000\nR13: 0000000000000000 R14: ffff88810642a5c0 R15: 000000000000017e\nFS: 00007f1ff68c20c0(0000) GS:ffff888163a24000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f1ff5dad240 CR3: 0000000107e56000 CR4: 00000000000006f0\nCall Trace:\n \u0026lt;TASK\n---truncated---(CVE-2025-38470)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: sch_qfq: Fix race condition on qfq_aggregate\n\nA race condition can occur when \u0026apos;agg\u0026apos; is modified in qfq_change_agg\n(called during qfq_enqueue) while other threads access it\nconcurrently. For example, qfq_dump_class may trigger a NULL\ndereference, and qfq_delete_class may cause a use-after-free.\n\nThis patch addresses the issue by:\n\n1. Moved qfq_destroy_class into the critical section.\n\n2. Added sch_tree_lock protection to qfq_dump_class and\nqfq_dump_class_stats.(CVE-2025-38477)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix use-after-free in cifs_oplock_break\n\nA race condition can occur in cifs_oplock_break() leading to a\nuse-after-free of the cinode structure when unmounting:\n\n cifs_oplock_break()\n _cifsFileInfo_put(cfile)\n cifsFileInfo_put_final()\n cifs_sb_deactive()\n [last ref, start releasing sb]\n kill_sb()\n kill_anon_super()\n generic_shutdown_super()\n evict_inodes()\n dispose_list()\n evict()\n destroy_inode()\n call_rcu(\u0026amp;inode-\u0026gt;i_rcu, i_callback)\n spin_lock(\u0026amp;cinode-\u0026gt;open_file_lock) \u0026lt;- OK\n [later] i_callback()\n cifs_free_inode()\n kmem_cache_free(cinode)\n spin_unlock(\u0026amp;cinode-\u0026gt;open_file_lock) \u0026lt;- UAF\n cifs_done_oplock_break(cinode) \u0026lt;- UAF\n\nThe issue occurs when umount has already released its reference to the\nsuperblock. When _cifsFileInfo_put() calls cifs_sb_deactive(), this\nreleases the last reference, triggering the immediate cleanup of all\ninodes under RCU. However, cifs_oplock_break() continues to access the\ncinode after this point, resulting in use-after-free.\n\nFix this by holding an extra reference to the superblock during the\nentire oplock break operation. This ensures that the superblock and\nits inodes remain valid until the oplock break completes.(CVE-2025-38527)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsunrpc: fix handling of server side tls alerts\n\nScott Mayhew discovered a security exploit in NFS over TLS in\ntls_alert_recv() due to its assumption it can read data from\nthe msg iterator\u0026apos;s kvec..\n\nkTLS implementation splits TLS non-data record payload between\nthe control message buffer (which includes the type such as TLS\naler or TLS cipher change) and the rest of the payload (say TLS\nalert\u0026apos;s level/description) which goes into the msg payload buffer.\n\nThis patch proposes to rework how control messages are setup and\nused by sock_recvmsg().\n\nIf no control message structure is setup, kTLS layer will read and\nprocess TLS data record types. As soon as it encounters a TLS control\nmessage, it would return an error. At that point, NFS can setup a\nkvec backed msg buffer and read in the control message such as a\nTLS alert. Msg iterator can advance the kvec pointer as a part of\nthe copy process thus we need to revert the iterator before calling\ninto the tls_alert_recv.(CVE-2025-38566)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: prevent infinite loop in rt6_nlmsg_size()\n\nWhile testing prior patch, I was able to trigger\nan infinite loop in rt6_nlmsg_size() in the following place:\n\nlist_for_each_entry_rcu(sibling, \u0026amp;f6i-\u0026gt;fib6_siblings,\n\t\t\tfib6_siblings) {\n\trt6_nh_nlmsg_size(sibling-\u0026gt;fib6_nh, \u0026amp;nexthop_len);\n}\n\nThis is because fib6_del_route() and fib6_add_rt2node()\nuses list_del_rcu(), which can confuse rcu readers,\nbecause they might no longer see the head of the list.\n\nRestart the loop if f6i-\u0026gt;fib6_nsiblings is zero.(CVE-2025-38588)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\neventpoll: Fix semi-unbounded recursion\n\nEnsure that epoll instances can never form a graph deeper than\nEP_MAX_NESTS+1 links.\n\nCurrently, ep_loop_check_proc() ensures that the graph is loop-free and\ndoes some recursion depth checks, but those recursion depth checks don\u0026apos;t\nlimit the depth of the resulting tree for two reasons:\n\n - They don\u0026apos;t look upwards in the tree.\n - If there are multiple downwards paths of different lengths, only one of\n the paths is actually considered for the depth check since commit\n 28d82dc1c4ed (\u0026quot;epoll: limit paths\u0026quot;).\n\nEssentially, the current recursion depth check in ep_loop_check_proc() just\nserves to prevent it from recursing too deeply while checking for loops.\n\nA more thorough check is done in reverse_path_check() after the new graph\nedge has already been created; this checks, among other things, that no\npaths going upwards from any non-epoll file with a length of more than 5\nedges exist. However, this check does not apply to non-epoll files.\n\nAs a result, it is possible to recurse to a depth of at least roughly 500,\ntested on v6.15. (I am unsure if deeper recursion is possible; and this may\nhave changed with commit 8c44dac8add7 (\u0026quot;eventpoll: Fix priority inversion\nproblem\u0026quot;).)\n\nTo fix it:\n\n1. In ep_loop_check_proc(), note the subtree depth of each visited node,\nand use subtree depths for the total depth calculation even when a subtree\nhas already been visited.\n2. Add ep_get_upwards_depth_proc() for similarly determining the maximum\ndepth of an upwards walk.\n3. In ep_loop_check(), use these values to limit the total path length\nbetween epoll nodes to EP_MAX_NESTS edges.(CVE-2025-38614)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/packet: fix a race in packet_set_ring() and packet_notifier()\n\nWhen packet_set_ring() releases po-\u0026gt;bind_lock, another thread can\nrun packet_notifier() and process an NETDEV_UP event.\n\nThis race and the fix are both similar to that of commit 15fe076edea7\n(\u0026quot;net/packet: fix a race in packet_bind() and packet_notifier()\u0026quot;).\n\nThere too the packet_notifier NETDEV_UP event managed to run while a\npo-\u0026gt;bind_lock critical section had to be temporarily released. And\nthe fix was similarly to temporarily set po-\u0026gt;num to zero to keep\nthe socket unhooked until the lock is retaken.\n\nThe po-\u0026gt;bind_lock in packet_set_ring and packet_notifier precede the\nintroduction of git history.(CVE-2025-38617)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nrv: Use strings in da monitors tracepoints\n\nUsing DA monitors tracepoints with KASAN enabled triggers the following\nwarning:\n\n BUG: KASAN: global-out-of-bounds in do_trace_event_raw_event_event_da_monitor+0xd6/0x1a0\n Read of size 32 at addr ffffffffaada8980 by task ...\n Call Trace:\n \u0026lt;TASK\u0026gt;\n [...]\n do_trace_event_raw_event_event_da_monitor+0xd6/0x1a0\n ? __pfx_do_trace_event_raw_event_event_da_monitor+0x10/0x10\n ? trace_event_sncid+0x83/0x200\n trace_event_sncid+0x163/0x200\n [...]\n The buggy address belongs to the variable:\n automaton_snep+0x4e0/0x5e0\n\nThis is caused by the tracepoints reading 32 bytes __array instead of\n__string from the automata definition. Such strings are literals and\nreading 32 bytes ends up in out of bound memory accesses (e.g. the next\nautomaton\u0026apos;s data in this case).\nThe error is harmless as, while printing the string, we stop at the null\nterminator, but it should still be fixed.\n\nUse the __string facilities while defining the tracepoints to avoid\nreading out of bound memory.(CVE-2025-38636)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nice: Fix a null pointer dereference in ice_copy_and_init_pkg()\n\nAdd check for the return value of devm_kmemdup()\nto prevent potential null pointer dereference.(CVE-2025-38664)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: core: Check for rtd == NULL in snd_soc_remove_pcm_runtime()\n\nsnd_soc_remove_pcm_runtime() might be called with rtd == NULL which will\nleads to null pointer dereference.\nThis was reproduced with topology loading and marking a link as ignore\ndue to missing hardware component on the system.\nOn module removal the soc_tplg_remove_link() would call\nsnd_soc_remove_pcm_runtime() with rtd == NULL since the link was ignored,\nno runtime was created.(CVE-2025-38706)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetlink: avoid infinite retry looping in netlink_unicast()\n\nnetlink_attachskb() checks for the socket\u0026apos;s read memory allocation\nconstraints. Firstly, it has:\n\n rmem \u0026lt; READ_ONCE(sk-\u0026gt;sk_rcvbuf)\n\nto check if the just increased rmem value fits into the socket\u0026apos;s receive\nbuffer. If not, it proceeds and tries to wait for the memory under:\n\n rmem + skb-\u0026gt;truesize \u0026gt; READ_ONCE(sk-\u0026gt;sk_rcvbuf)\n\nThe checks don\u0026apos;t cover the case when skb-\u0026gt;truesize + sk-\u0026gt;sk_rmem_alloc is\nequal to sk-\u0026gt;sk_rcvbuf. Thus the function neither successfully accepts\nthese conditions, nor manages to reschedule the task - and is called in\nretry loop for indefinite time which is caught as:\n\n rcu: INFO: rcu_sched self-detected stall on CPU\n rcu: 0-....: (25999 ticks this GP) idle=ef2/1/0x4000000000000000 softirq=262269/262269 fqs=6212\n (t=26000 jiffies g=230833 q=259957)\n NMI backtrace for cpu 0\n CPU: 0 PID: 22 Comm: kauditd Not tainted 5.10.240 #68\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc42 04/01/2014\n Call Trace:\n \u0026lt;IRQ\u0026gt;\n dump_stack lib/dump_stack.c:120\n nmi_cpu_backtrace.cold lib/nmi_backtrace.c:105\n nmi_trigger_cpumask_backtrace lib/nmi_backtrace.c:62\n rcu_dump_cpu_stacks kernel/rcu/tree_stall.h:335\n rcu_sched_clock_irq.cold kernel/rcu/tree.c:2590\n update_process_times kernel/time/timer.c:1953\n tick_sched_handle kernel/time/tick-sched.c:227\n tick_sched_timer kernel/time/tick-sched.c:1399\n __hrtimer_run_queues kernel/time/hrtimer.c:1652\n hrtimer_interrupt kernel/time/hrtimer.c:1717\n __sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1113\n asm_call_irq_on_stack arch/x86/entry/entry_64.S:808\n \u0026lt;/IRQ\u0026gt;\n\n netlink_attachskb net/netlink/af_netlink.c:1234\n netlink_unicast net/netlink/af_netlink.c:1349\n kauditd_send_queue kernel/audit.c:776\n kauditd_thread kernel/audit.c:897\n kthread kernel/kthread.c:328\n ret_from_fork arch/x86/entry/entry_64.S:304\n\nRestore the original behavior of the check which commit in Fixes\naccidentally missed when restructuring the code.\n\nFound by Linux Verification Center (linuxtesting.org).(CVE-2025-38727)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/display: Add null pointer check in mod_hdcp_hdcp1_create_session()\n\nThe function mod_hdcp_hdcp1_create_session() calls the function\nget_first_active_display(), but does not check its return value.\nThe return value is a null pointer if the display list is empty.\nThis will lead to a null pointer dereference.\n\nAdd a null pointer check for get_first_active_display() and return\nMOD_HDCP_STATUS_DISPLAY_NOT_FOUND if the function return null.\n\nThis is similar to the commit c3e9826a2202\n(\u0026quot;drm/amd/display: Add null pointer check for get_first_active_display()\u0026quot;).\n\n(cherry picked from commit 5e43eb3cd731649c4f8b9134f857be62a416c893)(CVE-2025-39675)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: Fix backlog accounting in qdisc_dequeue_internal\n\nThis issue applies for the following qdiscs: hhf, fq, fq_codel, and\nfq_pie, and occurs in their change handlers when adjusting to the new\nlimit. The problem is the following in the values passed to the\nsubsequent qdisc_tree_reduce_backlog call given a tbf parent:\n\n When the tbf parent runs out of tokens, skbs of these qdiscs will\n be placed in gso_skb. Their peek handlers are qdisc_peek_dequeued,\n which accounts for both qlen and backlog. However, in the case of\n qdisc_dequeue_internal, ONLY qlen is accounted for when pulling\n from gso_skb. This means that these qdiscs are missing a\n qdisc_qstats_backlog_dec when dropping packets to satisfy the\n new limit in their change handlers.\n\n One can observe this issue with the following (with tc patched to\n support a limit of 0):\n\n export TARGET=fq\n tc qdisc del dev lo root\n tc qdisc add dev lo root handle 1: tbf rate 8bit burst 100b latency 1ms\n tc qdisc replace dev lo handle 3: parent 1:1 $TARGET limit 1000\n echo \u0026apos;\u0026apos;; echo \u0026apos;add child\u0026apos;; tc -s -d qdisc show dev lo\n ping -I lo -f -c2 -s32 -W0.001 127.0.0.1 2\u0026gt;\u0026amp;1 \u0026gt;/dev/null\n echo \u0026apos;\u0026apos;; echo \u0026apos;after ping\u0026apos;; tc -s -d qdisc show dev lo\n tc qdisc change dev lo handle 3: parent 1:1 $TARGET limit 0\n echo \u0026apos;\u0026apos;; echo \u0026apos;after limit drop\u0026apos;; tc -s -d qdisc show dev lo\n tc qdisc replace dev lo handle 2: parent 1:1 sfq\n echo \u0026apos;\u0026apos;; echo \u0026apos;post graft\u0026apos;; tc -s -d qdisc show dev lo\n\n The second to last show command shows 0 packets but a positive\n number (74) of backlog bytes. The problem becomes clearer in the\n last show command, where qdisc_purge_queue triggers\n qdisc_tree_reduce_backlog with the positive backlog and causes an\n underflow in the tbf parent\u0026apos;s backlog (4096 Mb instead of 0).\n\nTo fix this issue, the codepath for all clients of qdisc_dequeue_internal\nhas been simplified: codel, pie, hhf, fq, fq_pie, and fq_codel.\nqdisc_dequeue_internal handles the backlog adjustments for all cases that\ndo not directly use the dequeue handler.\n\nThe old fq_codel_change limit adjustment loop accumulated the arguments to\nthe subsequent qdisc_tree_reduce_backlog call through the cstats field.\nHowever, this is confusing and error prone as fq_codel_dequeue could also\npotentially mutate this field (which qdisc_dequeue_internal calls in the\nnon gso_skb case), so we have unified the code here with other qdiscs.(CVE-2025-39677)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncomedi: Fix use of uninitialized memory in do_insn_ioctl() and do_insnlist_ioctl()\n\nsyzbot reports a KMSAN kernel-infoleak in `do_insn_ioctl()`. A kernel\nbuffer is allocated to hold `insn-\u0026gt;n` samples (each of which is an\n`unsigned int`). For some instruction types, `insn-\u0026gt;n` samples are\ncopied back to user-space, unless an error code is being returned. The\nproblem is that not all the instruction handlers that need to return\ndata to userspace fill in the whole `insn-\u0026gt;n` samples, so that there is\nan information leak. There is a similar syzbot report for\n`do_insnlist_ioctl()`, although it does not have a reproducer for it at\nthe time of writing.\n\nOne culprit is `insn_rw_emulate_bits()` which is used as the handler for\n`INSN_READ` or `INSN_WRITE` instructions for subdevices that do not have\na specific handler for that instruction, but do have an `INSN_BITS`\nhandler. For `INSN_READ` it only fills in at most 1 sample, so if\n`insn-\u0026gt;n` is greater than 1, the remaining `insn-\u0026gt;n - 1` samples copied\nto userspace will be uninitialized kernel data.\n\nAnother culprit is `vm80xx_ai_insn_read()` in the \u0026quot;vm80xx\u0026quot; driver. It\nnever returns an error, even if it fails to fill the buffer.\n\nFix it in `do_insn_ioctl()` and `do_insnlist_ioctl()` by making sure\nthat uninitialized parts of the allocated buffer are zeroed before\nhandling each instruction.\n\nThanks to Arnaud Lecomte for their fix to `do_insn_ioctl()`. That fix\nreplaced the call to `kmalloc_array()` with `kcalloc()`, but it is not\nalways necessary to clear the whole buffer.(CVE-2025-39684)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Fix a race when updating an existing write\n\nAfter nfs_lock_and_join_requests() tests for whether the request is\nstill attached to the mapping, nothing prevents a call to\nnfs_inode_remove_request() from succeeding until we actually lock the\npage group.\nThe reason is that whoever called nfs_inode_remove_request() doesn\u0026apos;t\nnecessarily have a lock on the page group head.\n\nSo in order to avoid races, let\u0026apos;s take the page group lock earlier in\nnfs_lock_and_join_requests(), and hold it across the removal of the\nrequest in nfs_inode_remove_request().(CVE-2025-39697)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbnxt_en: Fix memory corruption when FW resources change during ifdown\n\nbnxt_set_dflt_rings() assumes that it is always called before any TC has\nbeen created. So it doesn\u0026apos;t take bp-\u0026gt;num_tc into account and assumes\nthat it is always 0 or 1.\n\nIn the FW resource or capability change scenario, the FW will return\nflags in bnxt_hwrm_if_change() that will cause the driver to\nreinitialize and call bnxt_cancel_reservations(). This will lead to\nbnxt_init_dflt_ring_mode() calling bnxt_set_dflt_rings() and bp-\u0026gt;num_tc\nmay be greater than 1. This will cause bp-\u0026gt;tx_ring[] to be sized too\nsmall and cause memory corruption in bnxt_alloc_cp_rings().\n\nFix it by properly scaling the TX rings by bp-\u0026gt;num_tc in the code\npaths mentioned above. Add 2 helper functions to determine\nbp-\u0026gt;tx_nr_rings and bp-\u0026gt;tx_nr_rings_per_tc.(CVE-2025-39810)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nefivarfs: Fix slab-out-of-bounds in efivarfs_d_compare\n\nObserved on kernel 6.6 (present on master as well):\n\n BUG: KASAN: slab-out-of-bounds in memcmp+0x98/0xd0\n Call trace:\n kasan_check_range+0xe8/0x190\n __asan_loadN+0x1c/0x28\n memcmp+0x98/0xd0\n efivarfs_d_compare+0x68/0xd8\n __d_lookup_rcu_op_compare+0x178/0x218\n __d_lookup_rcu+0x1f8/0x228\n d_alloc_parallel+0x150/0x648\n lookup_open.isra.0+0x5f0/0x8d0\n open_last_lookups+0x264/0x828\n path_openat+0x130/0x3f8\n do_filp_open+0x114/0x248\n do_sys_openat2+0x340/0x3c0\n __arm64_sys_openat+0x120/0x1a0\n\nIf dentry-\u0026gt;d_name.len \u0026lt; EFI_VARIABLE_GUID_LEN , \u0026apos;guid\u0026apos; can become\nnegative, leadings to oob. The issue can be triggered by parallel\nlookups using invalid filename:\n\n T1\t\t\tT2\n lookup_open\n -\u0026gt;lookup\n simple_lookup\n d_add\n // invalid dentry is added to hash list\n\n\t\t\tlookup_open\n\t\t\t d_alloc_parallel\n\t\t\t __d_lookup_rcu\n\t\t\t __d_lookup_rcu_op_compare\n\t\t\t hlist_bl_for_each_entry_rcu\n\t\t\t // invalid dentry can be retrieved\n\t\t\t -\u0026gt;d_compare\n\t\t\t efivarfs_d_compare\n\t\t\t // oob\n\nFix it by checking \u0026apos;guid\u0026apos; before cmp.(CVE-2025-39817)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix race with concurrent opens in rename(2)\n\nBesides sending the rename request to the server, the rename process\nalso involves closing any deferred close, waiting for outstanding I/O\nto complete as well as marking all existing open handles as deleted to\nprevent them from deferring closes, which increases the race window\nfor potential concurrent opens on the target file.\n\nFix this by unhashing the dentry in advance to prevent any concurrent\nopens on the target.(CVE-2025-39825)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs: writeback: fix use-after-free in __mark_inode_dirty()\n\nAn use-after-free issue occurred when __mark_inode_dirty() get the\nbdi_writeback that was in the progress of switching.\n\nCPU: 1 PID: 562 Comm: systemd-random- Not tainted 6.6.56-gb4403bd46a8e #1\n......\npstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\npc : __mark_inode_dirty+0x124/0x418\nlr : __mark_inode_dirty+0x118/0x418\nsp : ffffffc08c9dbbc0\n........\nCall trace:\n __mark_inode_dirty+0x124/0x418\n generic_update_time+0x4c/0x60\n file_modified+0xcc/0xd0\n ext4_buffered_write_iter+0x58/0x124\n ext4_file_write_iter+0x54/0x704\n vfs_write+0x1c0/0x308\n ksys_write+0x74/0x10c\n __arm64_sys_write+0x1c/0x28\n invoke_syscall+0x48/0x114\n el0_svc_common.constprop.0+0xc0/0xe0\n do_el0_svc+0x1c/0x28\n el0_svc+0x40/0xe4\n el0t_64_sync_handler+0x120/0x12c\n el0t_64_sync+0x194/0x198\n\nRoot cause is:\n\nsystemd-random-seed kworker\n----------------------------------------------------------------------\n___mark_inode_dirty inode_switch_wbs_work_fn\n\n spin_lock(\u0026amp;inode-\u0026gt;i_lock);\n inode_attach_wb\n locked_inode_to_wb_and_lock_list\n get inode-\u0026gt;i_wb\n spin_unlock(\u0026amp;inode-\u0026gt;i_lock);\n spin_lock(\u0026amp;wb-\u0026gt;list_lock)\n spin_lock(\u0026amp;inode-\u0026gt;i_lock)\n inode_io_list_move_locked\n spin_unlock(\u0026amp;wb-\u0026gt;list_lock)\n spin_unlock(\u0026amp;inode-\u0026gt;i_lock)\n spin_lock(\u0026amp;old_wb-\u0026gt;list_lock)\n inode_do_switch_wbs\n spin_lock(\u0026amp;inode-\u0026gt;i_lock)\n inode-\u0026gt;i_wb = new_wb\n spin_unlock(\u0026amp;inode-\u0026gt;i_lock)\n spin_unlock(\u0026amp;old_wb-\u0026gt;list_lock)\n wb_put_many(old_wb, nr_switched)\n cgwb_release\n old wb released\n wb_wakeup_delayed() accesses wb,\n then trigger the use-after-free\n issue\n\nFix this race condition by holding inode spinlock until\nwb_wakeup_delayed() finished.(CVE-2025-39866)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nkernfs: Fix UAF in polling when open file is released\n\nA use-after-free (UAF) vulnerability was identified in the PSI (Pressure\nStall Information) monitoring mechanism:\n\nBUG: KASAN: slab-use-after-free in psi_trigger_poll+0x3c/0x140\nRead of size 8 at addr ffff3de3d50bd308 by task systemd/1\n\npsi_trigger_poll+0x3c/0x140\ncgroup_pressure_poll+0x70/0xa0\ncgroup_file_poll+0x8c/0x100\nkernfs_fop_poll+0x11c/0x1c0\nep_item_poll.isra.0+0x188/0x2c0\n\nAllocated by task 1:\ncgroup_file_open+0x88/0x388\nkernfs_fop_open+0x73c/0xaf0\ndo_dentry_open+0x5fc/0x1200\nvfs_open+0xa0/0x3f0\ndo_open+0x7e8/0xd08\npath_openat+0x2fc/0x6b0\ndo_filp_open+0x174/0x368\n\nFreed by task 8462:\ncgroup_file_release+0x130/0x1f8\nkernfs_drain_open_files+0x17c/0x440\nkernfs_drain+0x2dc/0x360\nkernfs_show+0x1b8/0x288\ncgroup_file_show+0x150/0x268\ncgroup_pressure_write+0x1dc/0x340\ncgroup_file_write+0x274/0x548\n\nReproduction Steps:\n1. Open test/cpu.pressure and establish epoll monitoring\n2. Disable monitoring: echo 0 \u0026gt; test/cgroup.pressure\n3. Re-enable monitoring: echo 1 \u0026gt; test/cgroup.pressure\n\nThe race condition occurs because:\n1. When cgroup.pressure is disabled (echo 0 \u0026gt; cgroup.pressure), it:\n - Releases PSI triggers via cgroup_file_release()\n - Frees of-\u0026gt;priv through kernfs_drain_open_files()\n2. While epoll still holds reference to the file and continues polling\n3. Re-enabling (echo 1 \u0026gt; cgroup.pressure) accesses freed of-\u0026gt;priv\n\nepolling\t\t\tdisable/enable cgroup.pressure\nfd=open(cpu.pressure)\nwhile(1)\n...\nepoll_wait\nkernfs_fop_poll\nkernfs_get_active = true\techo 0 \u0026gt; cgroup.pressure\n...\t\t\t\tcgroup_file_show\n\t\t\t\tkernfs_show\n\t\t\t\t// inactive kn\n\t\t\t\tkernfs_drain_open_files\n\t\t\t\tcft-\u0026gt;release(of);\n\t\t\t\tkfree(ctx);\n\t\t\t\t...\nkernfs_get_active = false\n\t\t\t\techo 1 \u0026gt; cgroup.pressure\n\t\t\t\tkernfs_show\n\t\t\t\tkernfs_activate_one(kn);\nkernfs_fop_poll\nkernfs_get_active = true\ncgroup_file_poll\npsi_trigger_poll\n// UAF\n...\nend: close(fd)\n\nTo address this issue, introduce kernfs_get_active_of() for kernfs open\nfiles to obtain active references. This function will fail if the open file\nhas been released. Replace kernfs_get_active() with kernfs_get_active_of()\nto prevent further operations on released file descriptors.(CVE-2025-39881)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ni40e: fix IRQ freeing in i40e_vsi_request_irq_msix error path\n\nIf request_irq() in i40e_vsi_request_irq_msix() fails in an iteration\nlater than the first, the error path wants to free the IRQs requested\nso far. However, it uses the wrong dev_id argument for free_irq(), so\nit does not free the IRQs correctly and instead triggers the warning:\n\n Trying to free already-free IRQ 173\n WARNING: CPU: 25 PID: 1091 at kernel/irq/manage.c:1829 __free_irq+0x192/0x2c0\n Modules linked in: i40e(+) [...]\n CPU: 25 UID: 0 PID: 1091 Comm: NetworkManager Not tainted 6.17.0-rc1+ #1 PREEMPT(lazy)\n Hardware name: [...]\n RIP: 0010:__free_irq+0x192/0x2c0\n [...]\n Call Trace:\n \u0026lt;TASK\u0026gt;\n free_irq+0x32/0x70\n i40e_vsi_request_irq_msix.cold+0x63/0x8b [i40e]\n i40e_vsi_request_irq+0x79/0x80 [i40e]\n i40e_vsi_open+0x21f/0x2f0 [i40e]\n i40e_open+0x63/0x130 [i40e]\n __dev_open+0xfc/0x210\n __dev_change_flags+0x1fc/0x240\n netif_change_flags+0x27/0x70\n do_setlink.isra.0+0x341/0xc70\n rtnl_newlink+0x468/0x860\n rtnetlink_rcv_msg+0x375/0x450\n netlink_rcv_skb+0x5c/0x110\n netlink_unicast+0x288/0x3c0\n netlink_sendmsg+0x20d/0x430\n ____sys_sendmsg+0x3a2/0x3d0\n ___sys_sendmsg+0x99/0xe0\n __sys_sendmsg+0x8a/0xf0\n do_syscall_64+0x82/0x2c0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n [...]\n \u0026lt;/TASK\u0026gt;\n ---[ end trace 0000000000000000 ]---\n\nUse the same dev_id for free_irq() as for request_irq().\n\nI tested this with inserting code to fail intentionally.(CVE-2025-39911)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Harden uplink netdev access against device unbind\n\nThe function mlx5_uplink_netdev_get() gets the uplink netdevice\npointer from mdev-\u0026gt;mlx5e_res.uplink_netdev. However, the netdevice can\nbe removed and its pointer cleared when unbound from the mlx5_core.eth\ndriver. This results in a NULL pointer, causing a kernel panic.\n\n BUG: unable to handle page fault for address: 0000000000001300\n at RIP: 0010:mlx5e_vport_rep_load+0x22a/0x270 [mlx5_core]\n Call Trace:\n \u0026lt;TASK\u0026gt;\n mlx5_esw_offloads_rep_load+0x68/0xe0 [mlx5_core]\n esw_offloads_enable+0x593/0x910 [mlx5_core]\n mlx5_eswitch_enable_locked+0x341/0x420 [mlx5_core]\n mlx5_devlink_eswitch_mode_set+0x17e/0x3a0 [mlx5_core]\n devlink_nl_eswitch_set_doit+0x60/0xd0\n genl_family_rcv_msg_doit+0xe0/0x130\n genl_rcv_msg+0x183/0x290\n netlink_rcv_skb+0x4b/0xf0\n genl_rcv+0x24/0x40\n netlink_unicast+0x255/0x380\n netlink_sendmsg+0x1f3/0x420\n __sock_sendmsg+0x38/0x60\n __sys_sendto+0x119/0x180\n do_syscall_64+0x53/0x1d0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nEnsure the pointer is valid before use by checking it for NULL. If it\nis valid, immediately call netdev_hold() to take a reference, and\npreventing the netdevice from being freed while it is in use.(CVE-2025-39947)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: tuner: xc5000: Fix use-after-free in xc5000_release\n\nThe original code uses cancel_delayed_work() in xc5000_release(), which\ndoes not guarantee that the delayed work item timer_sleep has fully\ncompleted if it was already running. This leads to use-after-free scenarios\nwhere xc5000_release() may free the xc5000_priv while timer_sleep is still\nactive and attempts to dereference the xc5000_priv.\n\nA typical race condition is illustrated below:\n\nCPU 0 (release thread) | CPU 1 (delayed work callback)\nxc5000_release() | xc5000_do_timer_sleep()\n cancel_delayed_work() |\n hybrid_tuner_release_state(priv) |\n kfree(priv) |\n | priv = container_of() // UAF\n\nReplace cancel_delayed_work() with cancel_delayed_work_sync() to ensure\nthat the timer_sleep is properly canceled before the xc5000_priv memory\nis deallocated.\n\nA deadlock concern was considered: xc5000_release() is called in a process\ncontext and is not holding any locks that the timer_sleep work item might\nalso need. Therefore, the use of the _sync() variant is safe here.\n\nThis bug was initially identified through static analysis.\n\n[hverkuil: fix typo in Subject: tunner -\u0026gt; tuner](CVE-2025-39994)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: b2c2: Fix use-after-free causing by irq_check_work in flexcop_pci_remove\n\nThe original code uses cancel_delayed_work() in flexcop_pci_remove(), which\ndoes not guarantee that the delayed work item irq_check_work has fully\ncompleted if it was already running. This leads to use-after-free scenarios\nwhere flexcop_pci_remove() may free the flexcop_device while irq_check_work\nis still active and attempts to dereference the device.\n\nA typical race condition is illustrated below:\n\nCPU 0 (remove) | CPU 1 (delayed work callback)\nflexcop_pci_remove() | flexcop_pci_irq_check_work()\n cancel_delayed_work() |\n flexcop_device_kfree(fc_pci-\u0026gt;fc_dev) |\n | fc = fc_pci-\u0026gt;fc_dev; // UAF\n\nThis is confirmed by a KASAN report:\n\n==================================================================\nBUG: KASAN: slab-use-after-free in __run_timer_base.part.0+0x7d7/0x8c0\nWrite of size 8 at addr ffff8880093aa8c8 by task bash/135\n...\nCall Trace:\n \u0026lt;IRQ\u0026gt;\n dump_stack_lvl+0x55/0x70\n print_report+0xcf/0x610\n ? __run_timer_base.part.0+0x7d7/0x8c0\n kasan_report+0xb8/0xf0\n ? __run_timer_base.part.0+0x7d7/0x8c0\n __run_timer_base.part.0+0x7d7/0x8c0\n ? __pfx___run_timer_base.part.0+0x10/0x10\n ? __pfx_read_tsc+0x10/0x10\n ? ktime_get+0x60/0x140\n ? lapic_next_event+0x11/0x20\n ? clockevents_program_event+0x1d4/0x2a0\n run_timer_softirq+0xd1/0x190\n handle_softirqs+0x16a/0x550\n irq_exit_rcu+0xaf/0xe0\n sysvec_apic_timer_interrupt+0x70/0x80\n \u0026lt;/IRQ\u0026gt;\n...\n\nAllocated by task 1:\n kasan_save_stack+0x24/0x50\n kasan_save_track+0x14/0x30\n __kasan_kmalloc+0x7f/0x90\n __kmalloc_noprof+0x1be/0x460\n flexcop_device_kmalloc+0x54/0xe0\n flexcop_pci_probe+0x1f/0x9d0\n local_pci_probe+0xdc/0x190\n pci_device_probe+0x2fe/0x470\n really_probe+0x1ca/0x5c0\n __driver_probe_device+0x248/0x310\n driver_probe_device+0x44/0x120\n __driver_attach+0xd2/0x310\n bus_for_each_dev+0xed/0x170\n bus_add_driver+0x208/0x500\n driver_register+0x132/0x460\n do_one_initcall+0x89/0x300\n kernel_init_freeable+0x40d/0x720\n kernel_init+0x1a/0x150\n ret_from_fork+0x10c/0x1a0\n ret_from_fork_asm+0x1a/0x30\n\nFreed by task 135:\n kasan_save_stack+0x24/0x50\n kasan_save_track+0x14/0x30\n kasan_save_free_info+0x3a/0x60\n __kasan_slab_free+0x3f/0x50\n kfree+0x137/0x370\n flexcop_device_kfree+0x32/0x50\n pci_device_remove+0xa6/0x1d0\n device_release_driver_internal+0xf8/0x210\n pci_stop_bus_device+0x105/0x150\n pci_stop_and_remove_bus_device_locked+0x15/0x30\n remove_store+0xcc/0xe0\n kernfs_fop_write_iter+0x2c3/0x440\n vfs_write+0x871/0xd70\n ksys_write+0xee/0x1c0\n do_syscall_64+0xac/0x280\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n...\n\nReplace cancel_delayed_work() with cancel_delayed_work_sync() to ensure\nthat the delayed work item is properly canceled and any executing delayed\nwork has finished before the device memory is deallocated.\n\nThis bug was initially identified through static analysis. To reproduce\nand test it, I simulated the B2C2 FlexCop PCI device in QEMU and introduced\nartificial delays within the flexcop_pci_irq_check_work() function to\nincrease the likelihood of triggering the bug.(CVE-2025-39996)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: uvcvideo: Mark invalid entities with id UVC_INVALID_ENTITY_ID\n\nPer UVC 1.1+ specification 3.7.2, units and terminals must have a non-zero\nunique ID.\n\n```\nEach Unit and Terminal within the video function is assigned a unique\nidentification number, the Unit ID (UID) or Terminal ID (TID), contained in\nthe bUnitID or bTerminalID field of the descriptor. The value 0x00 is\nreserved for undefined ID,\n```\n\nIf we add a new entity with id 0 or a duplicated ID, it will be marked\nas UVC_INVALID_ENTITY_ID.\n\nIn a previous attempt commit 3dd075fe8ebb (\u0026quot;media: uvcvideo: Require\nentities to have a non-zero unique ID\u0026quot;), we ignored all the invalid units,\nthis broke a lot of non-compatible cameras. Hopefully we are more lucky\nthis time.\n\nThis also prevents some syzkaller reproducers from triggering warnings due\nto a chain of entities referring to themselves. In one particular case, an\nOutput Unit is connected to an Input Unit, both with the same ID of 1. But\nwhen looking up for the source ID of the Output Unit, that same entity is\nfound instead of the input entity, which leads to such warnings.\n\nIn another case, a backward chain was considered finished as the source ID\nwas 0. Later on, that entity was found, but its pads were not valid.\n\nHere is a sample stack trace for one of those cases.\n\n[ 20.650953] usb 1-1: new high-speed USB device number 2 using dummy_hcd\n[ 20.830206] usb 1-1: Using ep0 maxpacket: 8\n[ 20.833501] usb 1-1: config 0 descriptor??\n[ 21.038518] usb 1-1: string descriptor 0 read error: -71\n[ 21.038893] usb 1-1: Found UVC 0.00 device \u0026lt;unnamed\u0026gt; (2833:0201)\n[ 21.039299] uvcvideo 1-1:0.0: Entity type for entity Output 1 was not initialized!\n[ 21.041583] uvcvideo 1-1:0.0: Entity type for entity Input 1 was not initialized!\n[ 21.042218] ------------[ cut here ]------------\n[ 21.042536] WARNING: CPU: 0 PID: 9 at drivers/media/mc/mc-entity.c:1147 media_create_pad_link+0x2c4/0x2e0\n[ 21.043195] Modules linked in:\n[ 21.043535] CPU: 0 UID: 0 PID: 9 Comm: kworker/0:1 Not tainted 6.11.0-rc7-00030-g3480e43aeccf #444\n[ 21.044101] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014\n[ 21.044639] Workqueue: usb_hub_wq hub_event\n[ 21.045100] RIP: 0010:media_create_pad_link+0x2c4/0x2e0\n[ 21.045508] Code: fe e8 20 01 00 00 b8 f4 ff ff ff 48 83 c4 30 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc 0f 0b eb e9 0f 0b eb 0a 0f 0b eb 06 \u0026lt;0f\u0026gt; 0b eb 02 0f 0b b8 ea ff ff ff eb d4 66 2e 0f 1f 84 00 00 00 00\n[ 21.046801] RSP: 0018:ffffc9000004b318 EFLAGS: 00010246\n[ 21.047227] RAX: ffff888004e5d458 RBX: 0000000000000000 RCX: ffffffff818fccf1\n[ 21.047719] RDX: 000000000000007b RSI: 0000000000000000 RDI: ffff888004313290\n[ 21.048241] RBP: ffff888004313290 R08: 0001ffffffffffff R09: 0000000000000000\n[ 21.048701] R10: 0000000000000013 R11: 0001888004313290 R12: 0000000000000003\n[ 21.049138] R13: ffff888004313080 R14: ffff888004313080 R15: 0000000000000000\n[ 21.049648] FS: 0000000000000000(0000) GS:ffff88803ec00000(0000) knlGS:0000000000000000\n[ 21.050271] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 21.050688] CR2: 0000592cc27635b0 CR3: 000000000431c000 CR4: 0000000000750ef0\n[ 21.051136] PKRU: 55555554\n[ 21.051331] Call Trace:\n[ 21.051480] \u0026lt;TASK\u0026gt;\n[ 21.051611] ? __warn+0xc4/0x210\n[ 21.051861] ? media_create_pad_link+0x2c4/0x2e0\n[ 21.052252] ? report_bug+0x11b/0x1a0\n[ 21.052540] ? trace_hardirqs_on+0x31/0x40\n[ 21.052901] ? handle_bug+0x3d/0x70\n[ 21.053197] ? exc_invalid_op+0x1a/0x50\n[ 21.053511] ? asm_exc_invalid_op+0x1a/0x20\n[ 21.053924] ? media_create_pad_link+0x91/0x2e0\n[ 21.054364] ? media_create_pad_link+0x2c4/0x2e0\n[ 21.054834] ? media_create_pad_link+0x91/0x2e0\n[ 21.055131] ? _raw_spin_unlock+0x1e/0x40\n[ 21.055441] ? __v4l2_device_register_subdev+0x202/0x210\n[ 21.055837] uvc_mc_register_entities+0x358/0x400\n[ 21.056144] uvc_register_chains+0x1\n---truncated---(CVE-2025-40016)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nSquashfs: fix uninit-value in squashfs_get_parent\n\nSyzkaller reports a \u0026quot;KMSAN: uninit-value in squashfs_get_parent\u0026quot; bug.\n\nThis is caused by open_by_handle_at() being called with a file handle\ncontaining an invalid parent inode number. In particular the inode number\nis that of a symbolic link, rather than a directory.\n\nSquashfs_get_parent() gets called with that symbolic link inode, and\naccesses the parent member field.\n\n\tunsigned int parent_ino = squashfs_i(inode)-\u0026gt;parent;\n\nBecause non-directory inodes in Squashfs do not have a parent value, this\nis uninitialised, and this causes an uninitialised value access.\n\nThe fix is to initialise parent with the invalid inode 0, which will cause\nan EINVAL error to be returned.\n\nRegular inodes used to share the parent field with the block_list_start\nfield. This is removed in this commit to enable the parent field to\ncontain the invalid inode number 0.(CVE-2025-40049)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix crypto buffers in non-linear memory\n\nThe crypto API, through the scatterlist API, expects input buffers to be\nin linear memory. We handle this with the cifs_sg_set_buf() helper\nthat converts vmalloc\u0026apos;d memory to their corresponding pages.\n\nHowever, when we allocate our aead_request buffer (@creq in\nsmb2ops.c::crypt_message()), we do so with kvzalloc(), which possibly\nputs aead_request-\u0026gt;__ctx in vmalloc area.\n\nAEAD algorithm then uses -\u0026gt;__ctx for its private/internal data and\noperations, and uses sg_set_buf() for such data on a few places.\n\nThis works fine as long as @creq falls into kmalloc zone (small\nrequests) or vmalloc\u0026apos;d memory is still within linear range.\n\nTasks\u0026apos; stacks are vmalloc\u0026apos;d by default (CONFIG_VMAP_STACK=y), so too\nmany tasks will increment the base stacks\u0026apos; addresses to a point where\nvirt_addr_valid(buf) will fail (BUG() in sg_set_buf()) when that\nhappens.\n\nIn practice: too many parallel reads and writes on an encrypted mount\nwill trigger this bug.\n\nTo fix this, always alloc @creq with kmalloc() instead.\nAlso drop the @sensitive_size variable/arguments since\nkfree_sensitive() doesn\u0026apos;t need it.\n\nBacktrace:\n\n[ 945.272081] ------------[ cut here ]------------\n[ 945.272774] kernel BUG at include/linux/scatterlist.h:209!\n[ 945.273520] Oops: invalid opcode: 0000 [#1] SMP DEBUG_PAGEALLOC NOPTI\n[ 945.274412] CPU: 7 UID: 0 PID: 56 Comm: kworker/u33:0 Kdump: loaded Not tainted 6.15.0-lku-11779-g8e9d6efccdd7-dirty #1 PREEMPT(voluntary)\n[ 945.275736] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-2-gc13ff2cd-prebuilt.qemu.org 04/01/2014\n[ 945.276877] Workqueue: writeback wb_workfn (flush-cifs-2)\n[ 945.277457] RIP: 0010:crypto_gcm_init_common+0x1f9/0x220\n[ 945.278018] Code: b0 00 00 00 48 83 c4 08 5b 5d 41 5c 41 5d 41 5e 41 5f c3 cc cc cc cc 48 c7 c0 00 00 00 80 48 2b 05 5c 58 e5 00 e9 58 ff ff ff \u0026lt;0f\u0026gt; 0b 0f 0b 0f 0b 0f 0b 0f 0b 0f 0b 48 c7 04 24 01 00 00 00 48 8b\n[ 945.279992] RSP: 0018:ffffc90000a27360 EFLAGS: 00010246\n[ 945.280578] RAX: 0000000000000000 RBX: ffffc90001d85060 RCX: 0000000000000030\n[ 945.281376] RDX: 0000000000080000 RSI: 0000000000000000 RDI: ffffc90081d85070\n[ 945.282145] RBP: ffffc90001d85010 R08: ffffc90001d85000 R09: 0000000000000000\n[ 945.282898] R10: ffffc90001d85090 R11: 0000000000001000 R12: ffffc90001d85070\n[ 945.283656] R13: ffff888113522948 R14: ffffc90001d85060 R15: ffffc90001d85010\n[ 945.284407] FS: 0000000000000000(0000) GS:ffff8882e66cf000(0000) knlGS:0000000000000000\n[ 945.285262] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 945.285884] CR2: 00007fa7ffdd31f4 CR3: 000000010540d000 CR4: 0000000000350ef0\n[ 945.286683] Call Trace:\n[ 945.286952] \u0026lt;TASK\u0026gt;\n[ 945.287184] ? crypt_message+0x33f/0xad0 [cifs]\n[ 945.287719] crypto_gcm_encrypt+0x36/0xe0\n[ 945.288152] crypt_message+0x54a/0xad0 [cifs]\n[ 945.288724] smb3_init_transform_rq+0x277/0x300 [cifs]\n[ 945.289300] smb_send_rqst+0xa3/0x160 [cifs]\n[ 945.289944] cifs_call_async+0x178/0x340 [cifs]\n[ 945.290514] ? __pfx_smb2_writev_callback+0x10/0x10 [cifs]\n[ 945.291177] smb2_async_writev+0x3e3/0x670 [cifs]\n[ 945.291759] ? find_held_lock+0x32/0x90\n[ 945.292212] ? netfs_advance_write+0xf2/0x310\n[ 945.292723] netfs_advance_write+0xf2/0x310\n[ 945.293210] netfs_write_folio+0x346/0xcc0\n[ 945.293689] ? __pfx__raw_spin_unlock_irq+0x10/0x10\n[ 945.294250] netfs_writepages+0x117/0x460\n[ 945.294724] do_writepages+0xbe/0x170\n[ 945.295152] ? find_held_lock+0x32/0x90\n[ 945.295600] ? kvm_sched_clock_read+0x11/0x20\n[ 945.296103] __writeback_single_inode+0x56/0x4b0\n[ 945.296643] writeback_sb_inodes+0x229/0x550\n[ 945.297140] __writeback_inodes_wb+0x4c/0xe0\n[ 945.297642] wb_writeback+0x2f1/0x3f0\n[ 945.298069] wb_workfn+0x300/0x490\n[ 945.298472] process_one_work+0x1fe/0x590\n[ 945.298949] worker_thread+0x1ce/0x3c0\n[ 945.299397] ? __pfx_worker_thread+0x10/0x10\n[ 945.299900] kthr\n---truncated---(CVE-2025-40052)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/vt-d: Disallow dirty tracking if incoherent page walk\n\nDirty page tracking relies on the IOMMU atomically updating the dirty bit\nin the paging-structure entry. For this operation to succeed, the paging-\nstructure memory must be coherent between the IOMMU and the CPU. In\nanother word, if the iommu page walk is incoherent, dirty page tracking\ndoesn\u0026apos;t work.\n\nThe Intel VT-d specification, Section 3.10 \u0026quot;Snoop Behavior\u0026quot; states:\n\n\u0026quot;Remapping hardware encountering the need to atomically update A/EA/D bits\n in a paging-structure entry that is not snooped will result in a non-\n recoverable fault.\u0026quot;\n\nTo prevent an IOMMU from being incorrectly configured for dirty page\ntracking when it is operating in an incoherent mode, mark SSADS as\nsupported only when both ecap_slads and ecap_smpwc are supported.(CVE-2025-40058)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/rxe: Fix race in do_task() when draining\n\nWhen do_task() exhausts its iteration budget (!ret), it sets the state\nto TASK_STATE_IDLE to reschedule, without a secondary check on the\ncurrent task-\u0026gt;state. This can overwrite the TASK_STATE_DRAINING state\nset by a concurrent call to rxe_cleanup_task() or rxe_disable_task().\n\nWhile state changes are protected by a spinlock, both rxe_cleanup_task()\nand rxe_disable_task() release the lock while waiting for the task to\nfinish draining in the while(!is_done(task)) loop. The race occurs if\ndo_task() hits its iteration limit and acquires the lock in this window.\nThe cleanup logic may then proceed while the task incorrectly\nreschedules itself, leading to a potential use-after-free.\n\nThis bug was introduced during the migration from tasklets to workqueues,\nwhere the special handling for the draining case was lost.\n\nFix this by restoring the original pre-migration behavior. If the state is\nTASK_STATE_DRAINING when iterations are exhausted, set cont to 1 to\nforce a new loop iteration. This allows the task to finish its work, so\nthat a subsequent iteration can reach the switch statement and correctly\ntransition the state to TASK_STATE_DRAINED, stopping the task as intended.(CVE-2025-40061)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: start using dst_dev_rcu()\n\nChange icmpv4_xrlim_allow(), ip_defrag() to prevent possible UAF.\n\nChange ipmr_prepare_xmit(), ipmr_queue_fwd_xmit(), ip_mr_output(),\nipv4_neigh_lookup() to use lockdep enabled dst_dev_rcu().(CVE-2025-40074)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntcp_metrics: use dst_dev_net_rcu()\n\nReplace three dst_dev() with a lockdep enabled helper.(CVE-2025-40075)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nixgbevf: fix mailbox API compatibility by negotiating supported features\n\nThere was backward compatibility in the terms of mailbox API. Various\ndrivers from various OSes supporting 10G adapters from Intel portfolio\ncould easily negotiate mailbox API.\n\nThis convention has been broken since introducing API 1.4.\nCommit 0062e7cc955e (\u0026quot;ixgbevf: add VF IPsec offload code\u0026quot;) added support\nfor IPSec which is specific only for the kernel ixgbe driver. None of the\nrest of the Intel 10G PF/VF drivers supports it. And actually lack of\nsupport was not included in the IPSec implementation - there were no such\ncode paths. No possibility to negotiate support for the feature was\nintroduced along with introduction of the feature itself.\n\nCommit 339f28964147 (\u0026quot;ixgbevf: Add support for new mailbox communication\nbetween PF and VF\u0026quot;) increasing API version to 1.5 did the same - it\nintroduced code supported specifically by the PF ESX driver. It altered API\nversion for the VF driver in the same time not touching the version\ndefined for the PF ixgbe driver. It led to additional discrepancies,\nas the code provided within API 1.6 cannot be supported for Linux ixgbe\ndriver as it causes crashes.\n\nThe issue was noticed some time ago and mitigated by Jake within the commit\nd0725312adf5 (\u0026quot;ixgbevf: stop attempting IPSEC offload on Mailbox API 1.5\u0026quot;).\nAs a result we have regression for IPsec support and after increasing API\nto version 1.6 ixgbevf driver stopped to support ESX MBX.\n\nTo fix this mess add new mailbox op asking PF driver about supported\nfeatures. Basing on a response determine whether to set support for IPSec\nand ESX-specific enhanced mailbox.\n\nNew mailbox op, for compatibility purposes, must be added within new API\nrevision, as API version of OOT PF \u0026amp; VF drivers is already increased to\n1.6 and doesn\u0026apos;t incorporate features negotiate op.\n\nFeatures negotiation mechanism gives possibility to be extended with new\nfeatures when needed in the future.(CVE-2025-40104)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: Intel: bytcr_rt5651: Fix invalid quirk input mapping\n\nWhen an invalid value is passed via quirk option, currently\nbytcr_rt5640 driver just ignores and leaves as is, which may lead to\nunepxected results like OOB access.\n\nThis patch adds the sanity check and corrects the input mapping to the\ncertain default value if an invalid value is passed.(CVE-2025-40121)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: use RCU in ip6_xmit()\n\nUse RCU in ip6_xmit() in order to use dst_dev_rcu() to prevent\npossible UAF.(CVE-2025-40135)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmc: Use __sk_dst_get() and dst_dev_rcu() in in smc_clc_prfx_set().\n\nsmc_clc_prfx_set() is called during connect() and not under RCU\nnor RTNL.\n\nUsing sk_dst_get(sk)-\u0026gt;dev could trigger UAF.\n\nLet\u0026apos;s use __sk_dst_get() and dev_dst_rcu() under rcu_read_lock()\nafter kernel_getsockname().\n\nNote that the returned value of smc_clc_prfx_set() is not used\nin the caller.\n\nWhile at it, we change the 1st arg of smc_clc_prfx_set[46]_rcu()\nnot to touch dst there.(CVE-2025-40139)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntls: Use __sk_dst_get() and dst_dev_rcu() in get_netdev_for_sock().\n\nget_netdev_for_sock() is called during setsockopt(),\nso not under RCU.\n\nUsing sk_dst_get(sk)-\u0026gt;dev could trigger UAF.\n\nLet\u0026apos;s use __sk_dst_get() and dst_dev_rcu().\n\nNote that the only -\u0026gt;ndo_sk_get_lower_dev() user is\nbond_sk_get_lower_dev(), which uses RCU.(CVE-2025-40149)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/vt-d: debugfs: Fix legacy mode page table dump logic\n\nIn legacy mode, SSPTPTR is ignored if TT is not 00b or 01b. SSPTPTR\nmaybe uninitialized or zero in that case and may cause oops like:\n\n Oops: general protection fault, probably for non-canonical address\n 0xf00087d3f000f000: 0000 [#1] SMP NOPTI\n CPU: 2 UID: 0 PID: 786 Comm: cat Not tainted 6.16.0 #191 PREEMPT(voluntary)\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014\n RIP: 0010:pgtable_walk_level+0x98/0x150\n RSP: 0018:ffffc90000f279c0 EFLAGS: 00010206\n RAX: 0000000040000000 RBX: ffffc90000f27ab0 RCX: 000000000000001e\n RDX: 0000000000000003 RSI: f00087d3f000f000 RDI: f00087d3f0010000\n RBP: ffffc90000f27a00 R08: ffffc90000f27a98 R09: 0000000000000002\n R10: 0000000000000000 R11: 0000000000000000 R12: f00087d3f000f000\n R13: 0000000000000000 R14: 0000000040000000 R15: ffffc90000f27a98\n FS: 0000764566dcb740(0000) GS:ffff8881f812c000(0000) knlGS:0000000000000000\n CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 0000764566d44000 CR3: 0000000109d81003 CR4: 0000000000772ef0\n PKRU: 55555554\n Call Trace:\n \u0026lt;TASK\u0026gt;\n pgtable_walk_level+0x88/0x150\n domain_translation_struct_show.isra.0+0x2d9/0x300\n dev_domain_translation_struct_show+0x20/0x40\n seq_read_iter+0x12d/0x490\n...\n\nAvoid walking the page table if TT is not 00b or 01b.(CVE-2025-40155)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: use RCU in ip6_output()\n\nUse RCU in ip6_output() in order to use dst_dev_rcu() to prevent\npossible UAF.\n\nWe can remove rcu_read_lock()/rcu_read_unlock() pairs\nfrom ip6_finish_output2().(CVE-2025-40158)",
"id": "OESA-2025-2802",
"modified": "2026-08-06T11:09:55Z",
"published": "2025-12-12T11:09:55Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-2802"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38381"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38584"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38615"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38633"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38659"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-38667"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-40902"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-40904"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-41079"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42101"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42102"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42245"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42247"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-42297"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49863"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49875"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49894"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49905"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49925"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49930"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49935"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49948"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49949"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49950"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49957"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49962"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50002"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50005"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53131"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-57887"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-57900"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-58095"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-21945"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-21968"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-22022"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-22025"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-22026"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-22039"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-22042"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-22043"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-23133"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-37822"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-37861"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-37899"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-37973"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-37994"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-37997"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-38005"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-38058"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-38071"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-38109"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-38231"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-38282"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-38350"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-38361"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-38443"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-38457"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-38470"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-38477"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-38527"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-38566"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-38588"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-38614"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-38617"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-38636"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-38664"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-38706"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-38727"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-39675"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-39677"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-39684"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-39697"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-39810"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-39817"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-39825"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-39866"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-39881"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-39911"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-39947"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-39994"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-39996"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-40016"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-40049"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-40052"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-40058"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-40061"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-40074"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-40075"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-40104"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-40121"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-40135"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-40139"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-40149"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-40155"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-40158"
}
],
"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-2024-38381",
"CVE-2024-38584",
"CVE-2024-38615",
"CVE-2024-38633",
"CVE-2024-38659",
"CVE-2024-38667",
"CVE-2024-40902",
"CVE-2024-40904",
"CVE-2024-41079",
"CVE-2024-42101",
"CVE-2024-42102",
"CVE-2024-42245",
"CVE-2024-42247",
"CVE-2024-42297",
"CVE-2024-49863",
"CVE-2024-49875",
"CVE-2024-49894",
"CVE-2024-49905",
"CVE-2024-49925",
"CVE-2024-49930",
"CVE-2024-49935",
"CVE-2024-49948",
"CVE-2024-49949",
"CVE-2024-49950",
"CVE-2024-49957",
"CVE-2024-49962",
"CVE-2024-50002",
"CVE-2024-50005",
"CVE-2024-53131",
"CVE-2024-57887",
"CVE-2024-57900",
"CVE-2024-58095",
"CVE-2025-21945",
"CVE-2025-21968",
"CVE-2025-22022",
"CVE-2025-22025",
"CVE-2025-22026",
"CVE-2025-22039",
"CVE-2025-22042",
"CVE-2025-22043",
"CVE-2025-23133",
"CVE-2025-37822",
"CVE-2025-37861",
"CVE-2025-37899",
"CVE-2025-37973",
"CVE-2025-37994",
"CVE-2025-37997",
"CVE-2025-38005",
"CVE-2025-38058",
"CVE-2025-38071",
"CVE-2025-38109",
"CVE-2025-38231",
"CVE-2025-38282",
"CVE-2025-38350",
"CVE-2025-38361",
"CVE-2025-38443",
"CVE-2025-38457",
"CVE-2025-38470",
"CVE-2025-38477",
"CVE-2025-38527",
"CVE-2025-38566",
"CVE-2025-38588",
"CVE-2025-38614",
"CVE-2025-38617",
"CVE-2025-38636",
"CVE-2025-38664",
"CVE-2025-38706",
"CVE-2025-38727",
"CVE-2025-39675",
"CVE-2025-39677",
"CVE-2025-39684",
"CVE-2025-39697",
"CVE-2025-39810",
"CVE-2025-39817",
"CVE-2025-39825",
"CVE-2025-39866",
"CVE-2025-39881",
"CVE-2025-39911",
"CVE-2025-39947",
"CVE-2025-39994",
"CVE-2025-39996",
"CVE-2025-40016",
"CVE-2025-40049",
"CVE-2025-40052",
"CVE-2025-40058",
"CVE-2025-40061",
"CVE-2025-40074",
"CVE-2025-40075",
"CVE-2025-40104",
"CVE-2025-40121",
"CVE-2025-40135",
"CVE-2025-40139",
"CVE-2025-40149",
"CVE-2025-40155",
"CVE-2025-40158"
]
}
UBUNTU-CVE-2024-42297 (CVE-2024-42297)
Vulnerability from osv_ubuntu – Published: 2024-08-17 09:15 – Updated: 2026-10-01 15:52 – Source websiteIn the Linux kernel, the following vulnerability has been resolved: f2fs: fix to don't dirty inode for readonly filesystem syzbot reports f2fs bug as below: kernel BUG at fs/f2fs/inode.c:933! RIP: 0010:f2fs_evict_inode+0x1576/0x1590 fs/f2fs/inode.c:933 Call Trace: evict+0x2a4/0x620 fs/inode.c:664 dispose_list fs/inode.c:697 [inline] evict_inodes+0x5f8/0x690 fs/inode.c:747 generic_shutdown_super+0x9d/0x2c0 fs/super.c:675 kill_block_super+0x44/0x90 fs/super.c:1667 kill_f2fs_super+0x303/0x3b0 fs/f2fs/super.c:4894 deactivate_locked_super+0xc1/0x130 fs/super.c:484 cleanup_mnt+0x426/0x4c0 fs/namespace.c:1256 task_work_run+0x24a/0x300 kernel/task_work.c:180 ptrace_notify+0x2cd/0x380 kernel/signal.c:2399 ptrace_report_syscall include/linux/ptrace.h:411 [inline] ptrace_report_syscall_exit include/linux/ptrace.h:473 [inline] syscall_exit_work kernel/entry/common.c:251 [inline] syscall_exit_to_user_mode_prepare kernel/entry/common.c:278 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline] syscall_exit_to_user_mode+0x15c/0x280 kernel/entry/common.c:296 do_syscall_64+0x50/0x110 arch/x86/entry/common.c:88 entry_SYSCALL_64_after_hwframe+0x63/0x6b The root cause is: - do_sys_open - f2fs_lookup - __f2fs_find_entry - f2fs_i_depth_write - f2fs_mark_inode_dirty_sync - f2fs_dirty_inode - set_inode_flag(inode, FI_DIRTY_INODE) - umount - kill_f2fs_super - kill_block_super - generic_shutdown_super - sync_filesystem : sb is readonly, skip sync_filesystem() - evict_inodes - iput - f2fs_evict_inode - f2fs_bug_on(sbi, is_inode_flag_set(inode, FI_DIRTY_INODE)) : trigger kernel panic When we try to repair i_current_depth in readonly filesystem, let's skip dirty inode to avoid panic in later f2fs_evict_inode().
| URL | Type | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "block-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "crypto-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "fat-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "fb-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "firewire-core-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "floppy-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "fs-core-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "fs-secondary-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "input-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "ipmi-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "irda-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "kernel-image-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-buildinfo-3.13.0-217-generic",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-buildinfo-3.13.0-217-lowlatency",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-cloud-tools-3.13.0-217",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-cloud-tools-3.13.0-217-generic",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-cloud-tools-3.13.0-217-lowlatency",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-cloud-tools-common",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-headers-3.13.0-217",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-headers-3.13.0-217-generic",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-headers-3.13.0-217-lowlatency",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-image-unsigned-3.13.0-217-generic",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-image-unsigned-3.13.0-217-lowlatency",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-modules-3.13.0-217-generic",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-modules-3.13.0-217-lowlatency",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-modules-extra-3.13.0-217-generic",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-source-3.13.0",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-tools-3.13.0-217",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-tools-3.13.0-217-generic",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-tools-3.13.0-217-lowlatency",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-tools-common",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "linux-udebs-generic",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "md-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "message-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "mouse-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "multipath-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "nfs-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "nic-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "nic-pcmcia-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "nic-shared-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "nic-usb-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "parport-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "pata-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "pcmcia-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "pcmcia-storage-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "plip-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "ppp-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "sata-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "scsi-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "serial-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "speakup-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "squashfs-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "storage-core-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "usb-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "virtio-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
},
{
"binary_name": "vlan-modules-3.13.0-217-generic-di",
"binary_version": "3.13.0-217.268"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:14.04:LTS",
"name": "linux",
"purl": "pkg:deb/ubuntu/linux@3.13.0-217.268?arch=source\u0026distro=esm-infra-legacy/trusty"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.11.0-12.19",
"3.12.0-1.3",
"3.12.0-2.5",
"3.12.0-2.7",
"3.12.0-3.8",
"3.12.0-3.9",
"3.12.0-4.10",
"3.12.0-4.12",
"3.12.0-5.13",
"3.12.0-7.15",
"3.13.0-1.16",
"3.13.0-2.17",
"3.13.0-3.18",
"3.13.0-4.19",
"3.13.0-5.20",
"3.13.0-6.23",
"3.13.0-7.25",
"3.13.0-7.26",
"3.13.0-8.27",
"3.13.0-8.28",
"3.13.0-10.30",
"3.13.0-11.31",
"3.13.0-12.32",
"3.13.0-13.33",
"3.13.0-14.34",
"3.13.0-15.35",
"3.13.0-16.36",
"3.13.0-17.37",
"3.13.0-18.38",
"3.13.0-19.39",
"3.13.0-19.40",
"3.13.0-20.42",
"3.13.0-21.43",
"3.13.0-22.44",
"3.13.0-23.45",
"3.13.0-24.46",
"3.13.0-24.47",
"3.13.0-27.50",
"3.13.0-29.53",
"3.13.0-30.54",
"3.13.0-30.55",
"3.13.0-32.57",
"3.13.0-33.58",
"3.13.0-34.60",
"3.13.0-35.62",
"3.13.0-36.63",
"3.13.0-37.64",
"3.13.0-39.66",
"3.13.0-40.69",
"3.13.0-41.70",
"3.13.0-43.72",
"3.13.0-44.73",
"3.13.0-45.74",
"3.13.0-46.75",
"3.13.0-46.76",
"3.13.0-46.77",
"3.13.0-46.79",
"3.13.0-48.80",
"3.13.0-49.81",
"3.13.0-49.83",
"3.13.0-51.84",
"3.13.0-52.85",
"3.13.0-52.86",
"3.13.0-53.88",
"3.13.0-53.89",
"3.13.0-54.91",
"3.13.0-55.92",
"3.13.0-55.94",
"3.13.0-57.95",
"3.13.0-58.97",
"3.13.0-59.98",
"3.13.0-61.100",
"3.13.0-62.102",
"3.13.0-63.103",
"3.13.0-65.105",
"3.13.0-65.106",
"3.13.0-66.108",
"3.13.0-67.110",
"3.13.0-68.111",
"3.13.0-70.113",
"3.13.0-71.114",
"3.13.0-73.116",
"3.13.0-74.118",
"3.13.0-76.120",
"3.13.0-77.121",
"3.13.0-79.123",
"3.13.0-83.127",
"3.13.0-85.129",
"3.13.0-86.130",
"3.13.0-86.131",
"3.13.0-87.133",
"3.13.0-88.135",
"3.13.0-91.138",
"3.13.0-92.139",
"3.13.0-93.140",
"3.13.0-95.142",
"3.13.0-96.143",
"3.13.0-98.145",
"3.13.0-100.147",
"3.13.0-101.148",
"3.13.0-103.150",
"3.13.0-105.152",
"3.13.0-106.153",
"3.13.0-107.154",
"3.13.0-108.155",
"3.13.0-109.156",
"3.13.0-110.157",
"3.13.0-111.158",
"3.13.0-112.159",
"3.13.0-113.160",
"3.13.0-115.162",
"3.13.0-116.163",
"3.13.0-117.164",
"3.13.0-119.166",
"3.13.0-121.170",
"3.13.0-123.172",
"3.13.0-125.174",
"3.13.0-126.175",
"3.13.0-128.177",
"3.13.0-129.178",
"3.13.0-132.181",
"3.13.0-133.182",
"3.13.0-135.184",
"3.13.0-137.186",
"3.13.0-139.188",
"3.13.0-141.190",
"3.13.0-142.191",
"3.13.0-143.192",
"3.13.0-144.193",
"3.13.0-145.194",
"3.13.0-147.196",
"3.13.0-149.199",
"3.13.0-151.201",
"3.13.0-153.203",
"3.13.0-155.205",
"3.13.0-156.206",
"3.13.0-157.207",
"3.13.0-158.208",
"3.13.0-160.210",
"3.13.0-161.211",
"3.13.0-162.212",
"3.13.0-163.213",
"3.13.0-164.214",
"3.13.0-165.215",
"3.13.0-166.216",
"3.13.0-167.217",
"3.13.0-168.218",
"3.13.0-169.219",
"3.13.0-170.220",
"3.13.0-171.222",
"3.13.0-172.223",
"3.13.0-173.224",
"3.13.0-174.225",
"3.13.0-175.226",
"3.13.0-176.227",
"3.13.0-180.231",
"3.13.0-181.232",
"3.13.0-182.233",
"3.13.0-183.234",
"3.13.0-184.235",
"3.13.0-185.236",
"3.13.0-186.237",
"3.13.0-187.238",
"3.13.0-188.239",
"3.13.0-189.240",
"3.13.0-190.241",
"3.13.0-191.242",
"3.13.0-192.243",
"3.13.0-193.244",
"3.13.0-194.245",
"3.13.0-195.246",
"3.13.0-196.247",
"3.13.0-197.248",
"3.13.0-198.249",
"3.13.0-199.250",
"3.13.0-200.251",
"3.13.0-201.252",
"3.13.0-202.253",
"3.13.0-203.254",
"3.13.0-204.255",
"3.13.0-205.256",
"3.13.0-206.257",
"3.13.0-207.258",
"3.13.0-208.259",
"3.13.0-209.260",
"3.13.0-210.261",
"3.13.0-211.262",
"3.13.0-212.263",
"3.13.0-214.265",
"3.13.0-215.266",
"3.13.0-217.268"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-aws-cloud-tools-4.4.0-1159",
"binary_version": "4.4.0-1159.165"
},
{
"binary_name": "linux-aws-headers-4.4.0-1159",
"binary_version": "4.4.0-1159.165"
},
{
"binary_name": "linux-aws-tools-4.4.0-1159",
"binary_version": "4.4.0-1159.165"
},
{
"binary_name": "linux-buildinfo-4.4.0-1159-aws",
"binary_version": "4.4.0-1159.165"
},
{
"binary_name": "linux-cloud-tools-4.4.0-1159-aws",
"binary_version": "4.4.0-1159.165"
},
{
"binary_name": "linux-headers-4.4.0-1159-aws",
"binary_version": "4.4.0-1159.165"
},
{
"binary_name": "linux-image-4.4.0-1159-aws",
"binary_version": "4.4.0-1159.165"
},
{
"binary_name": "linux-modules-4.4.0-1159-aws",
"binary_version": "4.4.0-1159.165"
},
{
"binary_name": "linux-tools-4.4.0-1159-aws",
"binary_version": "4.4.0-1159.165"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:14.04:LTS",
"name": "linux-aws",
"purl": "pkg:deb/ubuntu/linux-aws@4.4.0-1159.165?arch=source\u0026distro=esm-infra-legacy/trusty"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.4.0-1002.2",
"4.4.0-1003.3",
"4.4.0-1005.5",
"4.4.0-1006.6",
"4.4.0-1009.9",
"4.4.0-1010.10",
"4.4.0-1011.11",
"4.4.0-1012.12",
"4.4.0-1014.14",
"4.4.0-1016.16",
"4.4.0-1017.17",
"4.4.0-1019.19",
"4.4.0-1022.22",
"4.4.0-1023.23",
"4.4.0-1024.25",
"4.4.0-1025.26",
"4.4.0-1027.30",
"4.4.0-1028.31",
"4.4.0-1029.32",
"4.4.0-1031.34",
"4.4.0-1032.35",
"4.4.0-1034.37",
"4.4.0-1036.39",
"4.4.0-1037.40",
"4.4.0-1038.41",
"4.4.0-1039.42",
"4.4.0-1040.43",
"4.4.0-1042.45",
"4.4.0-1044.47",
"4.4.0-1045.48",
"4.4.0-1046.50",
"4.4.0-1048.52",
"4.4.0-1050.54",
"4.4.0-1052.56",
"4.4.0-1054.58",
"4.4.0-1055.59",
"4.4.0-1056.60",
"4.4.0-1058.62",
"4.4.0-1059.63",
"4.4.0-1060.64",
"4.4.0-1061.65",
"4.4.0-1062.66",
"4.4.0-1064.68",
"4.4.0-1065.69",
"4.4.0-1066.70",
"4.4.0-1067.71",
"4.4.0-1073.77",
"4.4.0-1074.78",
"4.4.0-1075.79",
"4.4.0-1076.80",
"4.4.0-1077.81",
"4.4.0-1078.82",
"4.4.0-1081.85",
"4.4.0-1082.86",
"4.4.0-1083.87",
"4.4.0-1085.89",
"4.4.0-1086.90",
"4.4.0-1087.91",
"4.4.0-1088.92",
"4.4.0-1090.94",
"4.4.0-1091.95",
"4.4.0-1092.96",
"4.4.0-1093.97",
"4.4.0-1094.99",
"4.4.0-1095.100",
"4.4.0-1096.101",
"4.4.0-1097.102",
"4.4.0-1098.103",
"4.4.0-1099.104",
"4.4.0-1101.106",
"4.4.0-1102.107",
"4.4.0-1103.108",
"4.4.0-1104.109",
"4.4.0-1107.113",
"4.4.0-1109.115",
"4.4.0-1110.116",
"4.4.0-1111.117",
"4.4.0-1112.118",
"4.4.0-1113.119",
"4.4.0-1114.120",
"4.4.0-1115.121",
"4.4.0-1116.122",
"4.4.0-1117.123",
"4.4.0-1118.124",
"4.4.0-1119.125",
"4.4.0-1120.126",
"4.4.0-1121.127",
"4.4.0-1122.128",
"4.4.0-1123.129",
"4.4.0-1124.130",
"4.4.0-1125.131",
"4.4.0-1127.133",
"4.4.0-1128.134",
"4.4.0-1129.135",
"4.4.0-1130.136",
"4.4.0-1131.137",
"4.4.0-1133.139",
"4.4.0-1134.140",
"4.4.0-1135.141",
"4.4.0-1136.142",
"4.4.0-1137.143",
"4.4.0-1138.144",
"4.4.0-1139.145",
"4.4.0-1140.146",
"4.4.0-1141.147",
"4.4.0-1142.148",
"4.4.0-1143.149",
"4.4.0-1144.150",
"4.4.0-1145.151",
"4.4.0-1146.152",
"4.4.0-1147.153",
"4.4.0-1148.154",
"4.4.0-1149.155",
"4.4.0-1150.156",
"4.4.0-1151.157",
"4.4.0-1152.158",
"4.4.0-1153.159",
"4.4.0-1154.160",
"4.4.0-1155.161",
"4.4.0-1156.162",
"4.4.0-1157.163",
"4.4.0-1158.164",
"4.4.0-1159.165"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-azure-cloud-tools-4.15.0-1207",
"binary_version": "4.15.0-1207.222~14.04.1"
},
{
"binary_name": "linux-azure-headers-4.15.0-1207",
"binary_version": "4.15.0-1207.222~14.04.1"
},
{
"binary_name": "linux-azure-tools-4.15.0-1207",
"binary_version": "4.15.0-1207.222~14.04.1"
},
{
"binary_name": "linux-buildinfo-4.15.0-1207-azure",
"binary_version": "4.15.0-1207.222~14.04.1"
},
{
"binary_name": "linux-cloud-tools-4.15.0-1207-azure",
"binary_version": "4.15.0-1207.222~14.04.1"
},
{
"binary_name": "linux-headers-4.15.0-1207-azure",
"binary_version": "4.15.0-1207.222~14.04.1"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1207-azure",
"binary_version": "4.15.0-1207.222~14.04.1"
},
{
"binary_name": "linux-modules-4.15.0-1207-azure",
"binary_version": "4.15.0-1207.222~14.04.1"
},
{
"binary_name": "linux-modules-extra-4.15.0-1207-azure",
"binary_version": "4.15.0-1207.222~14.04.1"
},
{
"binary_name": "linux-tools-4.15.0-1207-azure",
"binary_version": "4.15.0-1207.222~14.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:14.04:LTS",
"name": "linux-azure",
"purl": "pkg:deb/ubuntu/linux-azure@4.15.0-1207.222~14.04.1?arch=source\u0026distro=esm-infra-legacy/trusty"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1023.24~14.04.1",
"4.15.0-1030.31~14.04.1",
"4.15.0-1031.32~14.04.1",
"4.15.0-1032.33~14.04.2",
"4.15.0-1035.36~14.04.2",
"4.15.0-1036.38~14.04.2",
"4.15.0-1037.39~14.04.2",
"4.15.0-1039.41~14.04.2",
"4.15.0-1040.44~14.04.1",
"4.15.0-1041.45~14.04.1",
"4.15.0-1042.46~14.04.1",
"4.15.0-1045.49~14.04.1",
"4.15.0-1046.50~14.04.1",
"4.15.0-1047.51~14.04.1",
"4.15.0-1049.54~14.04.1",
"4.15.0-1050.55~14.04.1",
"4.15.0-1051.56~14.04.1",
"4.15.0-1052.57~14.04.1",
"4.15.0-1055.60~14.04.1",
"4.15.0-1056.61~14.04.1",
"4.15.0-1057.62~14.04.1",
"4.15.0-1059.64~14.04.1",
"4.15.0-1060.65~14.04.1",
"4.15.0-1061.66~14.04.1",
"4.15.0-1063.68~14.04.1",
"4.15.0-1064.69~14.04.1",
"4.15.0-1066.71~14.04.1",
"4.15.0-1067.72~14.04.1",
"4.15.0-1069.74~14.04.1",
"4.15.0-1071.76~14.04.1",
"4.15.0-1074.79~14.04.1",
"4.15.0-1077.82~14.04.1",
"4.15.0-1082.92~14.04.1",
"4.15.0-1083.93~14.04.1",
"4.15.0-1089.99~14.04.1",
"4.15.0-1091.101~14.04.1",
"4.15.0-1092.102~14.04.1",
"4.15.0-1093.103~14.04.1",
"4.15.0-1095.105~14.04.1",
"4.15.0-1096.106~14.04.1",
"4.15.0-1098.109~14.04.1",
"4.15.0-1100.111~14.04.1",
"4.15.0-1102.113~14.04.1",
"4.15.0-1103.114~14.04.1",
"4.15.0-1106.118~14.04.1",
"4.15.0-1108.120~14.04.1",
"4.15.0-1109.121~14.04.1",
"4.15.0-1110.122~14.04.1",
"4.15.0-1111.123~14.04.1",
"4.15.0-1112.124~14.04.1",
"4.15.0-1113.126~14.04.1",
"4.15.0-1114.127~14.04.1",
"4.15.0-1115.128~14.04.1",
"4.15.0-1118.131~14.04.1",
"4.15.0-1121.134~14.04.1",
"4.15.0-1122.135~14.04.1",
"4.15.0-1123.136~14.04.1",
"4.15.0-1124.137~14.04.1",
"4.15.0-1125.138~14.04.1",
"4.15.0-1126.139~14.04.1",
"4.15.0-1127.140~14.04.1",
"4.15.0-1129.142~14.04.1",
"4.15.0-1130.143~14.04.1",
"4.15.0-1131.144~14.04.1",
"4.15.0-1133.146~14.04.1",
"4.15.0-1134.147~14.04.1",
"4.15.0-1136.149~14.04.1",
"4.15.0-1137.150~14.04.1",
"4.15.0-1138.151~14.04.1",
"4.15.0-1139.152~14.04.1",
"4.15.0-1142.156~14.04.1",
"4.15.0-1145.160~14.04.1",
"4.15.0-1146.161~14.04.1",
"4.15.0-1149.164~14.04.1",
"4.15.0-1150.165~14.04.1",
"4.15.0-1151.166~14.04.1",
"4.15.0-1153.168~14.04.1",
"4.15.0-1157.172~14.04.2",
"4.15.0-1158.173~14.04.1",
"4.15.0-1159.174~14.04.1",
"4.15.0-1162.177~14.04.1",
"4.15.0-1163.178~14.04.1",
"4.15.0-1164.179~14.04.1",
"4.15.0-1165.180~14.04.1",
"4.15.0-1166.181~14.04.1",
"4.15.0-1167.182~14.04.1",
"4.15.0-1168.183~14.04.1",
"4.15.0-1169.184~14.04.1",
"4.15.0-1170.185~14.04.1",
"4.15.0-1171.186~14.04.1",
"4.15.0-1172.187~14.04.1",
"4.15.0-1173.188~14.04.1",
"4.15.0-1174.189~14.04.1",
"4.15.0-1175.190~14.04.1",
"4.15.0-1176.191~14.04.1",
"4.15.0-1177.192~14.04.1",
"4.15.0-1178.193~14.04.1",
"4.15.0-1179.194~14.04.1",
"4.15.0-1180.195~14.04.1",
"4.15.0-1181.196~14.04.1",
"4.15.0-1182.197~14.04.1",
"4.15.0-1183.198~14.04.1",
"4.15.0-1184.199~14.04.1",
"4.15.0-1185.200~14.04.1",
"4.15.0-1186.201~14.04.1",
"4.15.0-1187.202~14.04.1",
"4.15.0-1188.203~14.04.1",
"4.15.0-1189.204~14.04.1",
"4.15.0-1190.205~14.04.1",
"4.15.0-1191.206~14.04.1",
"4.15.0-1192.207~14.04.1",
"4.15.0-1193.208~14.04.1",
"4.15.0-1194.209~14.04.1",
"4.15.0-1195.210~14.04.1",
"4.15.0-1196.211~14.04.1",
"4.15.0-1197.212~14.04.1",
"4.15.0-1199.214~14.04.1",
"4.15.0-1200.215~14.04.1",
"4.15.0-1201.216~14.04.1",
"4.15.0-1202.217~14.04.1",
"4.15.0-1205.220~14.04.1",
"4.15.0-1206.221~14.04.1",
"4.15.0-1207.222~14.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "block-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "crypto-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "fat-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "fb-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "firewire-core-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "floppy-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "fs-core-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "fs-secondary-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "input-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "ipmi-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "irda-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "kernel-image-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "linux-buildinfo-4.4.0-288-generic",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "linux-buildinfo-4.4.0-288-lowlatency",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "linux-cloud-tools-4.4.0-288-generic",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "linux-cloud-tools-4.4.0-288-lowlatency",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "linux-headers-4.4.0-288",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "linux-headers-4.4.0-288-generic",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "linux-headers-4.4.0-288-lowlatency",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "linux-image-4.4.0-288-generic",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "linux-image-unsigned-4.4.0-288-generic",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "linux-image-unsigned-4.4.0-288-lowlatency",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "linux-lts-xenial-cloud-tools-4.4.0-288",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "linux-lts-xenial-tools-4.4.0-288",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "linux-lts-xenial-udebs-generic",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "linux-modules-4.4.0-288-generic",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "linux-modules-4.4.0-288-lowlatency",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "linux-modules-extra-4.4.0-288-generic",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "linux-tools-4.4.0-288-generic",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "linux-tools-4.4.0-288-lowlatency",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "md-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "message-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "mouse-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "multipath-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "nfs-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "nic-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "nic-pcmcia-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "nic-shared-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "nic-usb-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "parport-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "pata-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "pcmcia-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "pcmcia-storage-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "plip-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "ppp-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "sata-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "scsi-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "serial-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "speakup-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "storage-core-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "usb-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "virtio-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
},
{
"binary_name": "vlan-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322~14.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:14.04:LTS",
"name": "linux-lts-xenial",
"purl": "pkg:deb/ubuntu/linux-lts-xenial@4.4.0-288.322~14.04.1?arch=source\u0026distro=esm-infra-legacy/trusty"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.4.0-13.29~14.04.1",
"4.4.0-14.30~14.04.2",
"4.4.0-15.31~14.04.1",
"4.4.0-18.34~14.04.1",
"4.4.0-21.37~14.04.1",
"4.4.0-22.39~14.04.1",
"4.4.0-22.40~14.04.1",
"4.4.0-24.43~14.04.1",
"4.4.0-28.47~14.04.1",
"4.4.0-31.50~14.04.1",
"4.4.0-34.53~14.04.1",
"4.4.0-36.55~14.04.1",
"4.4.0-38.57~14.04.1",
"4.4.0-42.62~14.04.1",
"4.4.0-45.66~14.04.1",
"4.4.0-47.68~14.04.1",
"4.4.0-51.72~14.04.1",
"4.4.0-53.74~14.04.1",
"4.4.0-57.78~14.04.1",
"4.4.0-59.80~14.04.1",
"4.4.0-62.83~14.04.1",
"4.4.0-63.84~14.04.2",
"4.4.0-64.85~14.04.1",
"4.4.0-66.87~14.04.1",
"4.4.0-67.88~14.04.1",
"4.4.0-70.91~14.04.1",
"4.4.0-71.92~14.04.1",
"4.4.0-72.93~14.04.1",
"4.4.0-75.96~14.04.1",
"4.4.0-78.99~14.04.2",
"4.4.0-79.100~14.04.1",
"4.4.0-81.104~14.04.1",
"4.4.0-83.106~14.04.1",
"4.4.0-87.110~14.04.1",
"4.4.0-89.112~14.04.1",
"4.4.0-91.114~14.04.1",
"4.4.0-92.115~14.04.1",
"4.4.0-93.116~14.04.1",
"4.4.0-96.119~14.04.1",
"4.4.0-97.120~14.04.1",
"4.4.0-98.121~14.04.1",
"4.4.0-101.124~14.04.1",
"4.4.0-103.126~14.04.1",
"4.4.0-104.127~14.04.1",
"4.4.0-108.131~14.04.1",
"4.4.0-109.132~14.04.1",
"4.4.0-111.134~14.04.1",
"4.4.0-112.135~14.04.1",
"4.4.0-116.140~14.04.1",
"4.4.0-119.143~14.04.1",
"4.4.0-121.145~14.04.1",
"4.4.0-124.148~14.04.1",
"4.4.0-127.153~14.04.1",
"4.4.0-128.154~14.04.1",
"4.4.0-130.156~14.04.1",
"4.4.0-131.157~14.04.1",
"4.4.0-133.159~14.04.1",
"4.4.0-134.160~14.04.1",
"4.4.0-135.161~14.04.1",
"4.4.0-137.163~14.04.1",
"4.4.0-138.164~14.04.1",
"4.4.0-139.165~14.04.1",
"4.4.0-140.166~14.04.1",
"4.4.0-141.167~14.04.1",
"4.4.0-142.168~14.04.1",
"4.4.0-143.169~14.04.2",
"4.4.0-144.170~14.04.1",
"4.4.0-146.172~14.04.1",
"4.4.0-148.174~14.04.1",
"4.4.0-150.176~14.04.1",
"4.4.0-151.178~14.04.1",
"4.4.0-154.181~14.04.1",
"4.4.0-157.185~14.04.1",
"4.4.0-159.187~14.04.1",
"4.4.0-161.189~14.04.1",
"4.4.0-164.192~14.04.1",
"4.4.0-165.193~14.04.1",
"4.4.0-166.195~14.04.1",
"4.4.0-168.197~14.04.1",
"4.4.0-169.198~14.04.1",
"4.4.0-170.199~14.04.1",
"4.4.0-171.200~14.04.1",
"4.4.0-173.203~14.04.1",
"4.4.0-174.204~14.04.1",
"4.4.0-176.206~14.04.1",
"4.4.0-177.207~14.04.1",
"4.4.0-178.208~14.04.1",
"4.4.0-179.209~14.04.1",
"4.4.0-184.214~14.04.1",
"4.4.0-185.215~14.04.1",
"4.4.0-186.216~14.04.1",
"4.4.0-187.217~14.04.1",
"4.4.0-189.219~14.04.1",
"4.4.0-190.220~14.04.1",
"4.4.0-193.224~14.04.1",
"4.4.0-194.226~14.04.1",
"4.4.0-197.229~14.04.1",
"4.4.0-198.230~14.04.1",
"4.4.0-200.232~14.04.1",
"4.4.0-201.233~14.04.1",
"4.4.0-203.235~14.04.1",
"4.4.0-204.236~14.04.1",
"4.4.0-206.238~14.04.1",
"4.4.0-208.240~14.04.1",
"4.4.0-209.241~14.04.1",
"4.4.0-210.242~14.04.1",
"4.4.0-211.243~14.04.1",
"4.4.0-212.244~14.04.1",
"4.4.0-213.245~14.04.1",
"4.4.0-214.246~14.04.1",
"4.4.0-215.247~14.04.1",
"4.4.0-218.251~14.04.1",
"4.4.0-219.252~14.04.1",
"4.4.0-221.254~14.04.1",
"4.4.0-222.255~14.04.1",
"4.4.0-223.256~14.04.1",
"4.4.0-224.257~14.04.1",
"4.4.0-227.261~14.04.1",
"4.4.0-229.263~14.04.1",
"4.4.0-230.264~14.04.1",
"4.4.0-231.265~14.04.1",
"4.4.0-233.267~14.04.1",
"4.4.0-234.268~14.04.1",
"4.4.0-235.269~14.04.1",
"4.4.0-236.270~14.04.1",
"4.4.0-237.271~14.04.1",
"4.4.0-239.273~14.04.1",
"4.4.0-240.274~14.04.1",
"4.4.0-241.275~14.04.1",
"4.4.0-242.276~14.04.1",
"4.4.0-243.277~14.04.1",
"4.4.0-244.278~14.04.1",
"4.4.0-245.279~14.04.1",
"4.4.0-246.280~14.04.1",
"4.4.0-248.282~14.04.1",
"4.4.0-250.284~14.04.1",
"4.4.0-251.285~14.04.1",
"4.4.0-252.286~14.04.1",
"4.4.0-253.287~14.04.1",
"4.4.0-254.288~14.04.1",
"4.4.0-256.290~14.04.1",
"4.4.0-257.291~14.04.1",
"4.4.0-258.292~14.04.2",
"4.4.0-259.293~14.04.1",
"4.4.0-260.294~14.04.1",
"4.4.0-261.295~14.04.1",
"4.4.0-262.296~14.04.1",
"4.4.0-263.297~14.04.1",
"4.4.0-264.298~14.04.1",
"4.4.0-266.300~14.04.1",
"4.4.0-267.301~14.04.1",
"4.4.0-268.302~14.04.1",
"4.4.0-269.303~14.04.1",
"4.4.0-270.304~14.04.1",
"4.4.0-271.305~14.04.1",
"4.4.0-272.306~14.04.1",
"4.4.0-273.307~14.04.1",
"4.4.0-274.308~14.04.1",
"4.4.0-276.310~14.04.1",
"4.4.0-277.311~14.04.1",
"4.4.0-278.312~14.04.1",
"4.4.0-279.313~14.04.1",
"4.4.0-280.314~14.04.1",
"4.4.0-281.315~14.04.1",
"4.4.0-283.317~14.04.1",
"4.4.0-284.318~14.04.1",
"4.4.0-287.321~14.04.1",
"4.4.0-288.322~14.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "block-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "crypto-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "dasd-extra-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "dasd-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "fat-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "fb-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "firewire-core-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "floppy-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "fs-core-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "fs-secondary-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "input-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "ipmi-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "irda-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "kernel-image-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "linux-buildinfo-4.4.0-288-generic",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "linux-buildinfo-4.4.0-288-lowlatency",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "linux-cloud-tools-4.4.0-288",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "linux-cloud-tools-4.4.0-288-generic",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "linux-cloud-tools-4.4.0-288-lowlatency",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "linux-cloud-tools-common",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "linux-headers-4.4.0-288",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "linux-headers-4.4.0-288-generic",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "linux-headers-4.4.0-288-lowlatency",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "linux-image-4.4.0-288-generic",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "linux-image-unsigned-4.4.0-288-generic",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "linux-image-unsigned-4.4.0-288-lowlatency",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "linux-modules-4.4.0-288-generic",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "linux-modules-4.4.0-288-lowlatency",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "linux-modules-extra-4.4.0-288-generic",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "linux-source-4.4.0",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "linux-tools-4.4.0-288",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "linux-tools-4.4.0-288-generic",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "linux-tools-4.4.0-288-lowlatency",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "linux-tools-common",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "linux-tools-host",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "linux-udebs-generic",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "md-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "message-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "mouse-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "multipath-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "nfs-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "nic-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "nic-pcmcia-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "nic-shared-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "nic-usb-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "parport-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "pata-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "pcmcia-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "pcmcia-storage-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "plip-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "ppp-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "sata-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "scsi-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "serial-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "speakup-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "storage-core-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "usb-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "virtio-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
},
{
"binary_name": "vlan-modules-4.4.0-288-generic-di",
"binary_version": "4.4.0-288.322"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "linux",
"purl": "pkg:deb/ubuntu/linux@4.4.0-288.322?arch=source\u0026distro=esm-infra-legacy/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.2.0-16.19",
"4.2.0-17.21",
"4.2.0-19.23",
"4.3.0-1.10",
"4.3.0-2.11",
"4.3.0-5.16",
"4.3.0-6.17",
"4.3.0-7.18",
"4.4.0-2.16",
"4.4.0-4.19",
"4.4.0-6.21",
"4.4.0-7.22",
"4.4.0-8.23",
"4.4.0-9.24",
"4.4.0-10.25",
"4.4.0-11.26",
"4.4.0-12.28",
"4.4.0-13.29",
"4.4.0-14.30",
"4.4.0-15.31",
"4.4.0-16.32",
"4.4.0-17.33",
"4.4.0-18.34",
"4.4.0-21.37",
"4.4.0-22.39",
"4.4.0-22.40",
"4.4.0-24.43",
"4.4.0-28.47",
"4.4.0-31.50",
"4.4.0-34.53",
"4.4.0-36.55",
"4.4.0-38.57",
"4.4.0-42.62",
"4.4.0-43.63",
"4.4.0-45.66",
"4.4.0-47.68",
"4.4.0-51.72",
"4.4.0-53.74",
"4.4.0-57.78",
"4.4.0-59.80",
"4.4.0-62.83",
"4.4.0-63.84",
"4.4.0-64.85",
"4.4.0-65.86",
"4.4.0-66.87",
"4.4.0-67.88",
"4.4.0-70.91",
"4.4.0-71.92",
"4.4.0-72.93",
"4.4.0-75.96",
"4.4.0-77.98",
"4.4.0-78.99",
"4.4.0-79.100",
"4.4.0-81.104",
"4.4.0-83.106",
"4.4.0-87.110",
"4.4.0-89.112",
"4.4.0-91.114",
"4.4.0-92.115",
"4.4.0-93.116",
"4.4.0-96.119",
"4.4.0-97.120",
"4.4.0-98.121",
"4.4.0-101.124",
"4.4.0-103.126",
"4.4.0-104.127",
"4.4.0-108.131",
"4.4.0-109.132",
"4.4.0-112.135",
"4.4.0-116.140",
"4.4.0-119.143",
"4.4.0-121.145",
"4.4.0-122.146",
"4.4.0-124.148",
"4.4.0-127.153",
"4.4.0-128.154",
"4.4.0-130.156",
"4.4.0-131.157",
"4.4.0-133.159",
"4.4.0-134.160",
"4.4.0-135.161",
"4.4.0-137.163",
"4.4.0-138.164",
"4.4.0-139.165",
"4.4.0-140.166",
"4.4.0-141.167",
"4.4.0-142.168",
"4.4.0-143.169",
"4.4.0-145.171",
"4.4.0-146.172",
"4.4.0-148.174",
"4.4.0-150.176",
"4.4.0-151.178",
"4.4.0-154.181",
"4.4.0-157.185",
"4.4.0-159.187",
"4.4.0-161.189",
"4.4.0-164.192",
"4.4.0-165.193",
"4.4.0-166.195",
"4.4.0-168.197",
"4.4.0-169.198",
"4.4.0-170.199",
"4.4.0-171.200",
"4.4.0-173.203",
"4.4.0-174.204",
"4.4.0-176.206",
"4.4.0-177.207",
"4.4.0-178.208",
"4.4.0-179.209",
"4.4.0-184.214",
"4.4.0-185.215",
"4.4.0-186.216",
"4.4.0-187.217",
"4.4.0-189.219",
"4.4.0-190.220",
"4.4.0-193.224",
"4.4.0-194.226",
"4.4.0-197.229",
"4.4.0-198.230",
"4.4.0-200.232",
"4.4.0-201.233",
"4.4.0-203.235",
"4.4.0-204.236",
"4.4.0-206.238",
"4.4.0-208.240",
"4.4.0-209.241",
"4.4.0-210.242",
"4.4.0-211.243",
"4.4.0-212.244",
"4.4.0-213.245",
"4.4.0-214.246",
"4.4.0-216.249",
"4.4.0-217.250",
"4.4.0-218.251",
"4.4.0-219.252",
"4.4.0-221.254",
"4.4.0-222.255",
"4.4.0-223.256",
"4.4.0-224.257",
"4.4.0-227.261",
"4.4.0-229.263",
"4.4.0-230.264",
"4.4.0-231.265",
"4.4.0-233.267",
"4.4.0-234.268",
"4.4.0-235.269",
"4.4.0-236.270",
"4.4.0-237.271",
"4.4.0-239.273",
"4.4.0-240.274",
"4.4.0-241.275",
"4.4.0-242.276",
"4.4.0-243.277",
"4.4.0-244.278",
"4.4.0-245.279",
"4.4.0-246.280",
"4.4.0-248.282",
"4.4.0-250.284",
"4.4.0-251.285",
"4.4.0-252.286",
"4.4.0-253.287",
"4.4.0-254.288",
"4.4.0-256.290",
"4.4.0-257.291",
"4.4.0-258.292",
"4.4.0-259.293",
"4.4.0-260.294",
"4.4.0-261.295",
"4.4.0-262.296",
"4.4.0-263.297",
"4.4.0-264.298",
"4.4.0-266.300",
"4.4.0-267.301",
"4.4.0-268.302",
"4.4.0-269.303",
"4.4.0-270.304",
"4.4.0-271.305",
"4.4.0-272.306",
"4.4.0-273.307",
"4.4.0-274.308",
"4.4.0-276.310",
"4.4.0-277.311",
"4.4.0-278.312",
"4.4.0-279.313",
"4.4.0-280.314",
"4.4.0-281.315",
"4.4.0-283.317",
"4.4.0-284.318",
"4.4.0-287.321",
"4.4.0-288.322"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-aws-cloud-tools-4.4.0-1197",
"binary_version": "4.4.0-1197.212"
},
{
"binary_name": "linux-aws-headers-4.4.0-1197",
"binary_version": "4.4.0-1197.212"
},
{
"binary_name": "linux-aws-tools-4.4.0-1197",
"binary_version": "4.4.0-1197.212"
},
{
"binary_name": "linux-buildinfo-4.4.0-1197-aws",
"binary_version": "4.4.0-1197.212"
},
{
"binary_name": "linux-cloud-tools-4.4.0-1197-aws",
"binary_version": "4.4.0-1197.212"
},
{
"binary_name": "linux-headers-4.4.0-1197-aws",
"binary_version": "4.4.0-1197.212"
},
{
"binary_name": "linux-image-4.4.0-1197-aws",
"binary_version": "4.4.0-1197.212"
},
{
"binary_name": "linux-modules-4.4.0-1197-aws",
"binary_version": "4.4.0-1197.212"
},
{
"binary_name": "linux-modules-extra-4.4.0-1197-aws",
"binary_version": "4.4.0-1197.212"
},
{
"binary_name": "linux-tools-4.4.0-1197-aws",
"binary_version": "4.4.0-1197.212"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "linux-aws",
"purl": "pkg:deb/ubuntu/linux-aws@4.4.0-1197.212?arch=source\u0026distro=esm-infra-legacy/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.4.0-1001.10",
"4.4.0-1003.12",
"4.4.0-1004.13",
"4.4.0-1007.16",
"4.4.0-1009.18",
"4.4.0-1011.20",
"4.4.0-1012.21",
"4.4.0-1013.22",
"4.4.0-1016.25",
"4.4.0-1017.26",
"4.4.0-1018.27",
"4.4.0-1020.29",
"4.4.0-1022.31",
"4.4.0-1026.35",
"4.4.0-1028.37",
"4.4.0-1030.39",
"4.4.0-1031.40",
"4.4.0-1032.41",
"4.4.0-1035.44",
"4.4.0-1037.46",
"4.4.0-1038.47",
"4.4.0-1039.48",
"4.4.0-1041.50",
"4.4.0-1043.52",
"4.4.0-1044.53",
"4.4.0-1047.56",
"4.4.0-1048.57",
"4.4.0-1049.58",
"4.4.0-1050.59",
"4.4.0-1052.61",
"4.4.0-1054.63",
"4.4.0-1055.64",
"4.4.0-1057.66",
"4.4.0-1060.69",
"4.4.0-1061.70",
"4.4.0-1062.71",
"4.4.0-1063.72",
"4.4.0-1065.75",
"4.4.0-1066.76",
"4.4.0-1067.77",
"4.4.0-1069.79",
"4.4.0-1070.80",
"4.4.0-1072.82",
"4.4.0-1073.83",
"4.4.0-1074.84",
"4.4.0-1075.85",
"4.4.0-1077.87",
"4.4.0-1079.89",
"4.4.0-1081.91",
"4.4.0-1083.93",
"4.4.0-1084.94",
"4.4.0-1085.96",
"4.4.0-1087.98",
"4.4.0-1088.99",
"4.4.0-1090.101",
"4.4.0-1092.103",
"4.4.0-1094.105",
"4.4.0-1095.106",
"4.4.0-1096.107",
"4.4.0-1098.109",
"4.4.0-1099.110",
"4.4.0-1100.111",
"4.4.0-1101.112",
"4.4.0-1102.113",
"4.4.0-1104.115",
"4.4.0-1105.116",
"4.4.0-1106.117",
"4.4.0-1107.118",
"4.4.0-1109.120",
"4.4.0-1110.121",
"4.4.0-1111.123",
"4.4.0-1112.124",
"4.4.0-1113.126",
"4.4.0-1114.127",
"4.4.0-1117.131",
"4.4.0-1118.132",
"4.4.0-1119.133",
"4.4.0-1121.135",
"4.4.0-1122.136",
"4.4.0-1123.137",
"4.4.0-1124.138",
"4.4.0-1126.140",
"4.4.0-1127.141",
"4.4.0-1128.142",
"4.4.0-1129.143",
"4.4.0-1130.144",
"4.4.0-1131.145",
"4.4.0-1132.146",
"4.4.0-1133.147",
"4.4.0-1134.148",
"4.4.0-1135.149",
"4.4.0-1137.151",
"4.4.0-1138.152",
"4.4.0-1139.153",
"4.4.0-1140.154",
"4.4.0-1143.158",
"4.4.0-1145.160",
"4.4.0-1146.161",
"4.4.0-1147.162",
"4.4.0-1148.163",
"4.4.0-1150.165",
"4.4.0-1151.166",
"4.4.0-1152.167",
"4.4.0-1153.168",
"4.4.0-1154.169",
"4.4.0-1155.170",
"4.4.0-1156.171",
"4.4.0-1157.172",
"4.4.0-1158.173",
"4.4.0-1159.174",
"4.4.0-1160.175",
"4.4.0-1161.176",
"4.4.0-1162.177",
"4.4.0-1163.178",
"4.4.0-1164.179",
"4.4.0-1165.180",
"4.4.0-1166.181",
"4.4.0-1167.182",
"4.4.0-1168.183",
"4.4.0-1169.184",
"4.4.0-1171.186",
"4.4.0-1172.187",
"4.4.0-1173.188",
"4.4.0-1174.189",
"4.4.0-1175.190",
"4.4.0-1176.191",
"4.4.0-1177.192",
"4.4.0-1178.193",
"4.4.0-1179.194",
"4.4.0-1180.195",
"4.4.0-1181.196",
"4.4.0-1182.197",
"4.4.0-1183.198",
"4.4.0-1184.199",
"4.4.0-1185.200",
"4.4.0-1186.201",
"4.4.0-1187.202",
"4.4.0-1188.203",
"4.4.0-1189.204",
"4.4.0-1190.205",
"4.4.0-1191.206",
"4.4.0-1192.207",
"4.4.0-1193.208",
"4.4.0-1194.209",
"4.4.0-1195.210",
"4.4.0-1196.211",
"4.4.0-1197.212"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-aws-headers-4.15.0-1197",
"binary_version": "4.15.0-1197.210~16.04.1"
},
{
"binary_name": "linux-aws-hwe-cloud-tools-4.15.0-1197",
"binary_version": "4.15.0-1197.210~16.04.1"
},
{
"binary_name": "linux-aws-hwe-tools-4.15.0-1197",
"binary_version": "4.15.0-1197.210~16.04.1"
},
{
"binary_name": "linux-buildinfo-4.15.0-1197-aws",
"binary_version": "4.15.0-1197.210~16.04.1"
},
{
"binary_name": "linux-cloud-tools-4.15.0-1197-aws",
"binary_version": "4.15.0-1197.210~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-1197-aws",
"binary_version": "4.15.0-1197.210~16.04.1"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1197-aws",
"binary_version": "4.15.0-1197.210~16.04.1"
},
{
"binary_name": "linux-modules-4.15.0-1197-aws",
"binary_version": "4.15.0-1197.210~16.04.1"
},
{
"binary_name": "linux-modules-extra-4.15.0-1197-aws",
"binary_version": "4.15.0-1197.210~16.04.1"
},
{
"binary_name": "linux-tools-4.15.0-1197-aws",
"binary_version": "4.15.0-1197.210~16.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "linux-aws-hwe",
"purl": "pkg:deb/ubuntu/linux-aws-hwe@4.15.0-1197.210~16.04.1?arch=source\u0026distro=esm-infra-legacy/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1030.31~16.04.1",
"4.15.0-1031.33~16.04.1",
"4.15.0-1032.34~16.04.1",
"4.15.0-1033.35~16.04.1",
"4.15.0-1035.37~16.04.1",
"4.15.0-1036.38~16.04.1",
"4.15.0-1039.41~16.04.1",
"4.15.0-1040.42~16.04.1",
"4.15.0-1041.43~16.04.1",
"4.15.0-1043.45~16.04.1",
"4.15.0-1044.46~16.04.1",
"4.15.0-1045.47~16.04.1",
"4.15.0-1047.49~16.04.1",
"4.15.0-1048.50~16.04.1",
"4.15.0-1050.52~16.04.1",
"4.15.0-1051.53~16.04.1",
"4.15.0-1052.54~16.04.1",
"4.15.0-1054.56~16.04.1",
"4.15.0-1056.58~16.04.1",
"4.15.0-1057.59~16.04.1",
"4.15.0-1058.60~16.04.1",
"4.15.0-1060.62~16.04.1",
"4.15.0-1063.67~16.04.1",
"4.15.0-1065.69~16.04.1",
"4.15.0-1066.70~16.04.1",
"4.15.0-1067.71~16.04.1",
"4.15.0-1073.77~16.04.1",
"4.15.0-1074.78~16.04.1",
"4.15.0-1079.83~16.04.1",
"4.15.0-1080.84~16.04.1",
"4.15.0-1082.86~16.04.1",
"4.15.0-1083.87~16.04.1",
"4.15.0-1085.90~16.04.1",
"4.15.0-1088.93~16.04.1",
"4.15.0-1090.95~16.04.1",
"4.15.0-1091.96~16.04.1",
"4.15.0-1093.99~16.04.1",
"4.15.0-1094.101~16.04.1",
"4.15.0-1095.102~16.04.1",
"4.15.0-1096.103~16.04.1",
"4.15.0-1097.104~16.04.1",
"4.15.0-1098.105~16.04.1",
"4.15.0-1099.106~16.04.1",
"4.15.0-1102.109~16.04.1",
"4.15.0-1103.110~16.04.1",
"4.15.0-1106.113~16.04.1",
"4.15.0-1109.116~16.04.1",
"4.15.0-1110.117~16.04.1",
"4.15.0-1111.118~16.04.1",
"4.15.0-1112.119~16.04.1",
"4.15.0-1113.120~16.04.1",
"4.15.0-1115.122~16.04.1",
"4.15.0-1116.123~16.04.1",
"4.15.0-1118.125~16.04.1",
"4.15.0-1119.126~16.04.2",
"4.15.0-1120.128~16.04.1",
"4.15.0-1123.132~16.04.1",
"4.15.0-1124.133~16.04.1",
"4.15.0-1126.135~16.04.2",
"4.15.0-1127.136~16.04.1",
"4.15.0-1128.137~16.04.1",
"4.15.0-1130.139~16.04.1",
"4.15.0-1133.143~16.04.1",
"4.15.0-1136.147~16.04.1",
"4.15.0-1137.148~16.04.1",
"4.15.0-1139.150~16.04.1",
"4.15.0-1140.151~16.04.1",
"4.15.0-1141.152~16.04.1",
"4.15.0-1142.154~16.04.1",
"4.15.0-1143.155~16.04.1",
"4.15.0-1146.158~16.04.2",
"4.15.0-1147.159~16.04.1",
"4.15.0-1148.160~16.04.1",
"4.15.0-1151.164~16.04.1",
"4.15.0-1153.166~16.04.1",
"4.15.0-1154.167~16.04.1",
"4.15.0-1155.168~16.04.1",
"4.15.0-1156.169~16.04.1",
"4.15.0-1157.170~16.04.1",
"4.15.0-1158.171~16.04.1",
"4.15.0-1159.172~16.04.1",
"4.15.0-1160.173~16.04.1",
"4.15.0-1161.174~16.04.1",
"4.15.0-1162.175~16.04.1",
"4.15.0-1163.176~16.04.1",
"4.15.0-1164.177~16.04.1",
"4.15.0-1165.178~16.04.1",
"4.15.0-1166.179~16.04.1",
"4.15.0-1167.180~16.04.1",
"4.15.0-1168.181~16.04.1",
"4.15.0-1169.182~16.04.1",
"4.15.0-1170.183~16.04.1",
"4.15.0-1172.185~16.04.1",
"4.15.0-1173.186~16.04.1",
"4.15.0-1174.187~16.04.1",
"4.15.0-1175.188~16.04.1",
"4.15.0-1176.189~16.04.1",
"4.15.0-1177.190~16.04.1",
"4.15.0-1178.191~16.04.1",
"4.15.0-1179.192~16.04.1",
"4.15.0-1180.193~16.04.1",
"4.15.0-1181.194~16.04.1",
"4.15.0-1182.195~16.04.1",
"4.15.0-1183.196~16.04.1",
"4.15.0-1184.197~16.04.1",
"4.15.0-1185.198~16.04.1",
"4.15.0-1186.199~16.04.1",
"4.15.0-1187.200~16.04.1",
"4.15.0-1188.201~16.04.1",
"4.15.0-1189.202~16.04.1",
"4.15.0-1190.203~16.04.1",
"4.15.0-1191.204~16.04.1",
"4.15.0-1192.205~16.04.1",
"4.15.0-1194.207~16.04.1",
"4.15.0-1195.208~16.04.1",
"4.15.0-1196.209~16.04.1",
"4.15.0-1197.210~16.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-azure-cloud-tools-4.15.0-1206",
"binary_version": "4.15.0-1206.221~16.04.1"
},
{
"binary_name": "linux-azure-headers-4.15.0-1206",
"binary_version": "4.15.0-1206.221~16.04.1"
},
{
"binary_name": "linux-azure-tools-4.15.0-1206",
"binary_version": "4.15.0-1206.221~16.04.1"
},
{
"binary_name": "linux-buildinfo-4.15.0-1206-azure",
"binary_version": "4.15.0-1206.221~16.04.1"
},
{
"binary_name": "linux-cloud-tools-4.15.0-1206-azure",
"binary_version": "4.15.0-1206.221~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-1206-azure",
"binary_version": "4.15.0-1206.221~16.04.1"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1206-azure",
"binary_version": "4.15.0-1206.221~16.04.1"
},
{
"binary_name": "linux-modules-4.15.0-1206-azure",
"binary_version": "4.15.0-1206.221~16.04.1"
},
{
"binary_name": "linux-modules-extra-4.15.0-1206-azure",
"binary_version": "4.15.0-1206.221~16.04.1"
},
{
"binary_name": "linux-tools-4.15.0-1206-azure",
"binary_version": "4.15.0-1206.221~16.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "linux-azure",
"purl": "pkg:deb/ubuntu/linux-azure@4.15.0-1206.221~16.04.1?arch=source\u0026distro=esm-infra-legacy/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.11.0-1009.9",
"4.11.0-1011.11",
"4.11.0-1013.13",
"4.11.0-1014.14",
"4.11.0-1015.15",
"4.11.0-1016.16",
"4.13.0-1005.7",
"4.13.0-1006.8",
"4.13.0-1007.9",
"4.13.0-1009.12",
"4.13.0-1011.14",
"4.13.0-1012.15",
"4.13.0-1014.17",
"4.13.0-1016.19",
"4.13.0-1018.21",
"4.15.0-1013.13~16.04.2",
"4.15.0-1014.14~16.04.1",
"4.15.0-1018.18~16.04.1",
"4.15.0-1019.19~16.04.1",
"4.15.0-1021.21~16.04.1",
"4.15.0-1022.22~16.04.1",
"4.15.0-1023.24~16.04.1",
"4.15.0-1025.26~16.04.1",
"4.15.0-1028.29~16.04.1",
"4.15.0-1030.31~16.04.1",
"4.15.0-1031.32~16.04.1",
"4.15.0-1032.33~16.04.1",
"4.15.0-1035.36~16.04.1",
"4.15.0-1036.38~16.04.1",
"4.15.0-1037.39~16.04.1",
"4.15.0-1039.43",
"4.15.0-1040.44",
"4.15.0-1041.45",
"4.15.0-1042.46",
"4.15.0-1045.49",
"4.15.0-1046.50",
"4.15.0-1047.51",
"4.15.0-1049.54",
"4.15.0-1050.55",
"4.15.0-1051.56",
"4.15.0-1052.57",
"4.15.0-1055.60",
"4.15.0-1056.61",
"4.15.0-1057.62",
"4.15.0-1059.64",
"4.15.0-1060.65",
"4.15.0-1061.66",
"4.15.0-1063.68",
"4.15.0-1064.69",
"4.15.0-1066.71",
"4.15.0-1067.72",
"4.15.0-1069.74",
"4.15.0-1071.76",
"4.15.0-1075.80",
"4.15.0-1077.82",
"4.15.0-1082.92~16.04.1",
"4.15.0-1083.93~16.04.1",
"4.15.0-1089.99~16.04.1",
"4.15.0-1091.101~16.04.1",
"4.15.0-1092.102~16.04.1",
"4.15.0-1093.103~16.04.1",
"4.15.0-1095.105~16.04.1",
"4.15.0-1096.106~16.04.1",
"4.15.0-1098.109~16.04.1",
"4.15.0-1100.111~16.04.1",
"4.15.0-1102.113~16.04.1",
"4.15.0-1103.114~16.04.1",
"4.15.0-1106.118~16.04.1",
"4.15.0-1108.120~16.04.1",
"4.15.0-1109.121~16.04.1",
"4.15.0-1110.122~16.04.1",
"4.15.0-1111.123~16.04.1",
"4.15.0-1112.124~16.04.1",
"4.15.0-1113.126~16.04.1",
"4.15.0-1114.127~16.04.1",
"4.15.0-1115.128~16.04.1",
"4.15.0-1118.131~16.04.1",
"4.15.0-1121.134~16.04.1",
"4.15.0-1122.135~16.04.1",
"4.15.0-1123.136~16.04.1",
"4.15.0-1124.137~16.04.1",
"4.15.0-1125.138~16.04.1",
"4.15.0-1126.139~16.04.1",
"4.15.0-1127.140~16.04.1",
"4.15.0-1129.142~16.04.1",
"4.15.0-1130.143~16.04.1",
"4.15.0-1131.144~16.04.1",
"4.15.0-1133.146~16.04.1",
"4.15.0-1134.147~16.04.1",
"4.15.0-1136.149~16.04.1",
"4.15.0-1137.150~16.04.1",
"4.15.0-1138.151~16.04.1",
"4.15.0-1139.152~16.04.1",
"4.15.0-1142.156~16.04.1",
"4.15.0-1145.160~16.04.1",
"4.15.0-1146.161~16.04.1",
"4.15.0-1149.164~16.04.1",
"4.15.0-1150.165~16.04.1",
"4.15.0-1151.166~16.04.1",
"4.15.0-1153.168~16.04.1",
"4.15.0-1159.174~16.04.1",
"4.15.0-1162.177~16.04.1",
"4.15.0-1163.178~16.04.1",
"4.15.0-1164.179~16.04.1",
"4.15.0-1165.180~16.04.1",
"4.15.0-1166.181~16.04.1",
"4.15.0-1167.182~16.04.1",
"4.15.0-1168.183~16.04.1",
"4.15.0-1169.184~16.04.1",
"4.15.0-1170.185~16.04.1",
"4.15.0-1171.186~16.04.1",
"4.15.0-1172.187~16.04.1",
"4.15.0-1173.188~16.04.1",
"4.15.0-1174.189~16.04.1",
"4.15.0-1175.190~16.04.1",
"4.15.0-1176.191~16.04.1",
"4.15.0-1177.192~16.04.1",
"4.15.0-1178.193~16.04.1",
"4.15.0-1179.194~16.04.1",
"4.15.0-1180.195~16.04.1",
"4.15.0-1181.196~16.04.1",
"4.15.0-1182.197~16.04.1",
"4.15.0-1183.198~16.04.1",
"4.15.0-1184.199~16.04.1",
"4.15.0-1185.200~16.04.1",
"4.15.0-1186.201~16.04.1",
"4.15.0-1187.202~16.04.1",
"4.15.0-1188.203~16.04.1",
"4.15.0-1189.204~16.04.1",
"4.15.0-1190.205~16.04.1",
"4.15.0-1191.206~16.04.1",
"4.15.0-1192.207~16.04.1",
"4.15.0-1193.208~16.04.1",
"4.15.0-1194.209~16.04.1",
"4.15.0-1195.210~16.04.1",
"4.15.0-1196.211~16.04.1",
"4.15.0-1197.212~16.04.1",
"4.15.0-1200.215~16.04.1",
"4.15.0-1204.219~16.04.1",
"4.15.0-1205.220~16.04.1",
"4.15.0-1206.221~16.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-1190-gcp",
"binary_version": "4.15.0-1190.207~16.04.1"
},
{
"binary_name": "linux-gcp-headers-4.15.0-1190",
"binary_version": "4.15.0-1190.207~16.04.1"
},
{
"binary_name": "linux-gcp-tools-4.15.0-1190",
"binary_version": "4.15.0-1190.207~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-1190-gcp",
"binary_version": "4.15.0-1190.207~16.04.1"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1190-gcp",
"binary_version": "4.15.0-1190.207~16.04.1"
},
{
"binary_name": "linux-modules-4.15.0-1190-gcp",
"binary_version": "4.15.0-1190.207~16.04.1"
},
{
"binary_name": "linux-modules-extra-4.15.0-1190-gcp",
"binary_version": "4.15.0-1190.207~16.04.1"
},
{
"binary_name": "linux-tools-4.15.0-1190-gcp",
"binary_version": "4.15.0-1190.207~16.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "linux-gcp",
"purl": "pkg:deb/ubuntu/linux-gcp@4.15.0-1190.207~16.04.1?arch=source\u0026distro=esm-infra-legacy/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.10.0-1004.4",
"4.10.0-1006.6",
"4.10.0-1007.7",
"4.10.0-1008.8",
"4.10.0-1009.9",
"4.13.0-1002.5",
"4.13.0-1006.9",
"4.13.0-1007.10",
"4.13.0-1008.11",
"4.13.0-1011.15",
"4.13.0-1012.16",
"4.13.0-1013.17",
"4.13.0-1015.19",
"4.13.0-1017.21",
"4.13.0-1019.23",
"4.15.0-1014.14~16.04.1",
"4.15.0-1015.15~16.04.1",
"4.15.0-1017.18~16.04.1",
"4.15.0-1018.19~16.04.2",
"4.15.0-1019.20~16.04.1",
"4.15.0-1021.22~16.04.1",
"4.15.0-1023.24~16.04.1",
"4.15.0-1024.25~16.04.2",
"4.15.0-1025.26~16.04.1",
"4.15.0-1026.27~16.04.1",
"4.15.0-1027.28~16.04.1",
"4.15.0-1028.29~16.04.1",
"4.15.0-1029.31~16.04.1",
"4.15.0-1030.32~16.04.1",
"4.15.0-1032.34~16.04.1",
"4.15.0-1033.35~16.04.1",
"4.15.0-1034.36~16.04.1",
"4.15.0-1036.38~16.04.1",
"4.15.0-1037.39~16.04.1",
"4.15.0-1040.42~16.04.1",
"4.15.0-1041.43",
"4.15.0-1042.44",
"4.15.0-1044.46",
"4.15.0-1046.49",
"4.15.0-1047.50",
"4.15.0-1049.52",
"4.15.0-1050.53",
"4.15.0-1052.56",
"4.15.0-1055.59",
"4.15.0-1058.62",
"4.15.0-1060.64",
"4.15.0-1061.65",
"4.15.0-1071.81~16.04.1",
"4.15.0-1077.87~16.04.1",
"4.15.0-1078.88~16.04.1",
"4.15.0-1080.90~16.04.1",
"4.15.0-1081.92~16.04.1",
"4.15.0-1083.94~16.04.1",
"4.15.0-1084.95~16.04.1",
"4.15.0-1086.98~16.04.1",
"4.15.0-1087.100~16.04.1",
"4.15.0-1088.101~16.04.1",
"4.15.0-1090.103~16.04.1",
"4.15.0-1091.104~16.04.1",
"4.15.0-1092.105~16.04.1",
"4.15.0-1093.106~16.04.1",
"4.15.0-1094.107~16.04.1",
"4.15.0-1095.108~16.04.1",
"4.15.0-1096.109~16.04.1",
"4.15.0-1097.110~16.04.1",
"4.15.0-1098.111~16.04.1",
"4.15.0-1099.112~16.04.1",
"4.15.0-1100.113~16.04.1",
"4.15.0-1103.116~16.04.1",
"4.15.0-1106.120~16.04.1",
"4.15.0-1107.121~16.04.1",
"4.15.0-1108.122~16.04.1",
"4.15.0-1109.123~16.04.1",
"4.15.0-1110.124~16.04.1",
"4.15.0-1111.125~16.04.1",
"4.15.0-1112.126~16.04.1",
"4.15.0-1114.128~16.04.1",
"4.15.0-1115.129~16.04.1",
"4.15.0-1116.130~16.04.1",
"4.15.0-1118.132~16.04.1",
"4.15.0-1119.133~16.04.1",
"4.15.0-1120.134~16.04.1",
"4.15.0-1121.135~16.04.1",
"4.15.0-1122.136~16.04.1",
"4.15.0-1124.138~16.04.1",
"4.15.0-1127.142~16.04.1",
"4.15.0-1130.146~16.04.1",
"4.15.0-1131.147~16.04.1",
"4.15.0-1134.150~16.04.2",
"4.15.0-1135.151~16.04.2",
"4.15.0-1136.152~16.04.1",
"4.15.0-1137.153~16.04.1",
"4.15.0-1138.154~16.04.1",
"4.15.0-1141.157~16.04.2",
"4.15.0-1142.158~16.04.1",
"4.15.0-1143.159~16.04.1",
"4.15.0-1146.162~16.04.1",
"4.15.0-1147.163~16.04.1",
"4.15.0-1148.164~16.04.1",
"4.15.0-1149.165~16.04.1",
"4.15.0-1150.166~16.04.1",
"4.15.0-1151.167~16.04.1",
"4.15.0-1152.168~16.04.1",
"4.15.0-1153.170~16.04.1",
"4.15.0-1154.171~16.04.1",
"4.15.0-1155.172~16.04.1",
"4.15.0-1156.173~16.04.1",
"4.15.0-1157.174~16.04.1",
"4.15.0-1158.175~16.04.1",
"4.15.0-1159.176~16.04.1",
"4.15.0-1160.177~16.04.1",
"4.15.0-1161.178~16.04.1",
"4.15.0-1162.179~16.04.1",
"4.15.0-1163.180~16.04.1",
"4.15.0-1164.181~16.04.1",
"4.15.0-1165.182~16.04.1",
"4.15.0-1166.183~16.04.1",
"4.15.0-1167.184~16.04.2",
"4.15.0-1168.185~16.04.1",
"4.15.0-1169.186~16.04.1",
"4.15.0-1170.187~16.04.1",
"4.15.0-1171.188~16.04.1",
"4.15.0-1172.189~16.04.1",
"4.15.0-1173.190~16.04.1",
"4.15.0-1174.191~16.04.1",
"4.15.0-1175.192~16.04.1",
"4.15.0-1176.193~16.04.1",
"4.15.0-1177.194~16.04.1",
"4.15.0-1178.195~16.04.1",
"4.15.0-1179.196~16.04.1",
"4.15.0-1180.197~16.04.1",
"4.15.0-1181.198~16.04.1",
"4.15.0-1182.199~16.04.1",
"4.15.0-1183.200~16.04.2",
"4.15.0-1184.201~16.04.1",
"4.15.0-1185.202~16.04.1",
"4.15.0-1187.204~16.04.1",
"4.15.0-1188.205~16.04.1",
"4.15.0-1189.206~16.04.1",
"4.15.0-1190.207~16.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "block-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "crypto-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "dasd-extra-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "dasd-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "fat-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "fb-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "firewire-core-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "floppy-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "fs-core-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "fs-secondary-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "input-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "ipmi-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "irda-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "kernel-image-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "linux-buildinfo-4.15.0-260-generic",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "linux-buildinfo-4.15.0-260-lowlatency",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "linux-cloud-tools-4.15.0-260-generic",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "linux-cloud-tools-4.15.0-260-lowlatency",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "linux-headers-4.15.0-260",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "linux-headers-4.15.0-260-generic",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "linux-headers-4.15.0-260-lowlatency",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "linux-hwe-cloud-tools-4.15.0-260",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "linux-hwe-tools-4.15.0-260",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "linux-hwe-udebs-generic",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "linux-image-4.15.0-260-generic",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "linux-image-unsigned-4.15.0-260-generic",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "linux-image-unsigned-4.15.0-260-lowlatency",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "linux-modules-4.15.0-260-generic",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "linux-modules-4.15.0-260-lowlatency",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "linux-modules-extra-4.15.0-260-generic",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "linux-tools-4.15.0-260-generic",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "linux-tools-4.15.0-260-lowlatency",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "md-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "message-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "mouse-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "multipath-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "nfs-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "nic-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "nic-pcmcia-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "nic-shared-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "nic-usb-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "parport-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "pata-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "pcmcia-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "pcmcia-storage-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "plip-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "ppp-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "sata-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "scsi-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "serial-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "storage-core-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "usb-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "virtio-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
},
{
"binary_name": "vlan-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272~16.04.2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "linux-hwe",
"purl": "pkg:deb/ubuntu/linux-hwe@4.15.0-260.272~16.04.2?arch=source\u0026distro=esm-infra-legacy/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.8.0-36.36~16.04.1",
"4.8.0-39.42~16.04.1",
"4.8.0-41.44~16.04.1",
"4.8.0-42.45~16.04.1",
"4.8.0-44.47~16.04.1",
"4.8.0-45.48~16.04.1",
"4.8.0-46.49~16.04.1",
"4.8.0-49.52~16.04.1",
"4.8.0-51.54~16.04.1",
"4.8.0-52.55~16.04.1",
"4.8.0-53.56~16.04.1",
"4.8.0-54.57~16.04.1",
"4.8.0-56.61~16.04.1",
"4.8.0-58.63~16.04.1",
"4.10.0-27.30~16.04.2",
"4.10.0-28.32~16.04.2",
"4.10.0-30.34~16.04.1",
"4.10.0-32.36~16.04.1",
"4.10.0-33.37~16.04.1",
"4.10.0-35.39~16.04.1",
"4.10.0-37.41~16.04.1",
"4.10.0-38.42~16.04.1",
"4.10.0-40.44~16.04.1",
"4.10.0-42.46~16.04.1",
"4.13.0-26.29~16.04.2",
"4.13.0-31.34~16.04.1",
"4.13.0-32.35~16.04.1",
"4.13.0-36.40~16.04.1",
"4.13.0-37.42~16.04.1",
"4.13.0-38.43~16.04.1",
"4.13.0-39.44~16.04.1",
"4.13.0-41.46~16.04.1",
"4.13.0-43.48~16.04.1",
"4.13.0-45.50~16.04.1",
"4.15.0-24.26~16.04.1",
"4.15.0-29.31~16.04.1",
"4.15.0-30.32~16.04.1",
"4.15.0-32.35~16.04.1",
"4.15.0-33.36~16.04.1",
"4.15.0-34.37~16.04.1",
"4.15.0-36.39~16.04.1",
"4.15.0-38.41~16.04.1",
"4.15.0-39.42~16.04.1",
"4.15.0-42.45~16.04.1",
"4.15.0-43.46~16.04.1",
"4.15.0-45.48~16.04.1",
"4.15.0-46.49~16.04.1",
"4.15.0-47.50~16.04.1",
"4.15.0-48.51~16.04.1",
"4.15.0-50.54~16.04.1",
"4.15.0-51.55~16.04.1",
"4.15.0-52.56~16.04.1",
"4.15.0-54.58~16.04.1",
"4.15.0-55.60~16.04.2",
"4.15.0-58.64~16.04.1",
"4.15.0-60.67~16.04.1",
"4.15.0-62.69~16.04.1",
"4.15.0-64.73~16.04.1",
"4.15.0-65.74~16.04.1",
"4.15.0-66.75~16.04.1",
"4.15.0-69.78~16.04.1",
"4.15.0-70.79~16.04.1",
"4.15.0-72.81~16.04.1",
"4.15.0-74.83~16.04.1",
"4.15.0-76.86~16.04.1",
"4.15.0-88.88~16.04.1",
"4.15.0-91.92~16.04.1",
"4.15.0-96.97~16.04.1",
"4.15.0-99.100~16.04.1",
"4.15.0-101.102~16.04.1",
"4.15.0-106.107~16.04.1",
"4.15.0-107.108~16.04.1",
"4.15.0-112.113~16.04.1",
"4.15.0-115.116~16.04.1",
"4.15.0-117.118~16.04.1",
"4.15.0-118.119~16.04.1",
"4.15.0-120.122~16.04.1",
"4.15.0-122.124~16.04.1",
"4.15.0-123.126~16.04.1",
"4.15.0-126.129~16.04.1",
"4.15.0-128.131~16.04.1",
"4.15.0-129.132~16.04.1",
"4.15.0-132.136~16.04.1",
"4.15.0-133.137~16.04.1",
"4.15.0-136.140~16.04.1",
"4.15.0-137.141~16.04.1",
"4.15.0-139.143~16.04.1",
"4.15.0-140.144~16.04.1",
"4.15.0-142.146~16.04.1",
"4.15.0-143.147~16.04.3",
"4.15.0-144.148~16.04.1",
"4.15.0-147.151~16.04.1",
"4.15.0-151.157~16.04.1",
"4.15.0-153.160~16.04.1",
"4.15.0-154.161~16.04.1",
"4.15.0-156.163~16.04.1",
"4.15.0-158.166~16.04.1",
"4.15.0-159.167~16.04.1",
"4.15.0-161.169~16.04.1",
"4.15.0-162.170~16.04.1",
"4.15.0-163.171~16.04.1",
"4.15.0-166.174~16.04.1",
"4.15.0-167.175~16.04.1",
"4.15.0-169.177~16.04.1",
"4.15.0-171.180~16.04.1",
"4.15.0-173.182~16.04.1",
"4.15.0-175.184~16.04.1",
"4.15.0-176.185~16.04.1",
"4.15.0-177.186~16.04.1",
"4.15.0-180.189~16.04.1",
"4.15.0-184.194~16.04.1",
"4.15.0-187.198~16.04.1",
"4.15.0-188.199~16.04.1",
"4.15.0-189.200~16.04.1",
"4.15.0-191.202~16.04.1",
"4.15.0-192.203~16.04.1",
"4.15.0-193.204~16.04.1",
"4.15.0-194.205~16.04.1",
"4.15.0-196.207~16.04.1",
"4.15.0-197.208~16.04.1",
"4.15.0-200.211~16.04.2",
"4.15.0-201.212~16.04.1",
"4.15.0-202.213~16.04.1",
"4.15.0-206.217~16.04.1",
"4.15.0-208.219~16.04.1",
"4.15.0-209.220~16.04.1",
"4.15.0-210.221~16.04.1",
"4.15.0-211.222~16.04.1",
"4.15.0-212.223~16.04.1",
"4.15.0-213.224~16.04.1",
"4.15.0-214.225~16.04.1",
"4.15.0-216.227~16.04.1",
"4.15.0-218.229~16.04.1",
"4.15.0-219.230~16.04.1",
"4.15.0-220.231~16.04.1",
"4.15.0-221.232~16.04.1",
"4.15.0-222.233~16.04.1",
"4.15.0-223.235~16.04.1",
"4.15.0-224.236~16.04.1",
"4.15.0-225.237~16.04.1",
"4.15.0-226.238~16.04.1",
"4.15.0-227.239~16.04.1",
"4.15.0-228.240~16.04.1",
"4.15.0-229.241~16.04.1",
"4.15.0-230.242~16.04.1",
"4.15.0-231.243~16.04.1",
"4.15.0-232.244~16.04.1",
"4.15.0-233.245~16.04.1",
"4.15.0-234.246~16.04.1",
"4.15.0-235.247~16.04.1",
"4.15.0-236.248~16.04.1",
"4.15.0-237.249~16.04.1",
"4.15.0-238.250~16.04.1",
"4.15.0-239.251~16.04.1",
"4.15.0-240.252~16.04.1",
"4.15.0-241.253~16.04.1",
"4.15.0-242.254~16.04.1",
"4.15.0-243.255~16.04.1",
"4.15.0-245.257~16.04.1",
"4.15.0-246.258~16.04.1",
"4.15.0-247.259~16.04.1",
"4.15.0-248.260~16.04.1",
"4.15.0-249.261~16.04.1",
"4.15.0-250.262~16.04.1",
"4.15.0-253.265~16.04.1",
"4.15.0-254.266~16.04.1",
"4.15.0-257.269~16.04.1",
"4.15.0-260.272~16.04.2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "block-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "block-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "crypto-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "crypto-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "dasd-extra-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "dasd-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "fat-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "fat-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "fb-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "firewire-core-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "floppy-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "fs-core-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "fs-core-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "fs-secondary-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "fs-secondary-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "input-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "input-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "ipmi-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "ipmi-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "irda-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "irda-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "kernel-image-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "kernel-image-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-cloud-tools-4.15.0-23-generic",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-cloud-tools-4.15.0-23-lowlatency",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-23",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-23-generic",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-23-generic-lpae",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-23-lowlatency",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-hwe-edge-cloud-tools-4.15.0-23",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-hwe-edge-tools-4.15.0-23",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-hwe-edge-udebs-generic",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-hwe-edge-udebs-generic-lpae",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-image-4.15.0-23-generic",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-image-4.15.0-23-generic-lpae",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-image-4.15.0-23-lowlatency",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-image-unsigned-4.15.0-23-generic",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-image-unsigned-4.15.0-23-lowlatency",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-modules-4.15.0-23-generic",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-modules-4.15.0-23-generic-lpae",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-modules-4.15.0-23-lowlatency",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-modules-extra-4.15.0-23-generic",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-source-4.15.0",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-tools-4.15.0-23-generic",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-tools-4.15.0-23-generic-lpae",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-tools-4.15.0-23-lowlatency",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "md-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "md-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "message-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "mouse-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "mouse-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "multipath-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "multipath-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "nfs-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "nfs-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "nic-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "nic-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "nic-pcmcia-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "nic-shared-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "nic-shared-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "nic-usb-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "nic-usb-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "parport-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "parport-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "pata-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "pcmcia-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "pcmcia-storage-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "plip-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "plip-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "ppp-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "ppp-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "sata-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "sata-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "scsi-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "scsi-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "serial-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "storage-core-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "storage-core-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "usb-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "usb-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "virtio-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "vlan-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "vlan-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:16.04:LTS",
"name": "linux-hwe-edge",
"purl": "pkg:deb/ubuntu/linux-hwe-edge@4.15.0-23.25~16.04.1?arch=source\u0026distro=xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.8.0-28.30~16.04.1",
"4.8.0-30.32~16.04.1",
"4.8.0-32.34~16.04.1",
"4.8.0-34.36~16.04.1",
"4.10.0-14.16~16.04.1",
"4.10.0-19.21~16.04.1",
"4.10.0-20.22~16.04.1",
"4.10.0-21.23~16.04.1",
"4.10.0-22.24~16.04.1",
"4.10.0-24.28~16.04.1",
"4.10.0-26.30~16.04.1",
"4.11.0-13.19~16.04.1",
"4.11.0-14.20~16.04.1",
"4.13.0-16.19~16.04.3",
"4.13.0-17.20~16.04.1",
"4.13.0-19.22~16.04.1",
"4.13.0-21.24~16.04.1",
"4.13.0-25.29~16.04.2",
"4.15.0-13.14~16.04.1",
"4.15.0-15.16~16.04.1",
"4.15.0-20.21~16.04.1",
"4.15.0-22.24~16.04.1",
"4.15.0-23.25~16.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-4.4.0-1160-kvm",
"binary_version": "4.4.0-1160.171"
},
{
"binary_name": "linux-cloud-tools-4.4.0-1160-kvm",
"binary_version": "4.4.0-1160.171"
},
{
"binary_name": "linux-headers-4.4.0-1160-kvm",
"binary_version": "4.4.0-1160.171"
},
{
"binary_name": "linux-image-4.4.0-1160-kvm",
"binary_version": "4.4.0-1160.171"
},
{
"binary_name": "linux-kvm-cloud-tools-4.4.0-1160",
"binary_version": "4.4.0-1160.171"
},
{
"binary_name": "linux-kvm-headers-4.4.0-1160",
"binary_version": "4.4.0-1160.171"
},
{
"binary_name": "linux-kvm-tools-4.4.0-1160",
"binary_version": "4.4.0-1160.171"
},
{
"binary_name": "linux-modules-4.4.0-1160-kvm",
"binary_version": "4.4.0-1160.171"
},
{
"binary_name": "linux-tools-4.4.0-1160-kvm",
"binary_version": "4.4.0-1160.171"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "linux-kvm",
"purl": "pkg:deb/ubuntu/linux-kvm@4.4.0-1160.171?arch=source\u0026distro=esm-infra-legacy/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.4.0-1004.9",
"4.4.0-1007.12",
"4.4.0-1008.13",
"4.4.0-1009.14",
"4.4.0-1010.15",
"4.4.0-1012.17",
"4.4.0-1013.18",
"4.4.0-1015.20",
"4.4.0-1017.22",
"4.4.0-1019.24",
"4.4.0-1020.25",
"4.4.0-1021.26",
"4.4.0-1023.28",
"4.4.0-1026.31",
"4.4.0-1027.32",
"4.4.0-1029.34",
"4.4.0-1031.37",
"4.4.0-1032.38",
"4.4.0-1033.39",
"4.4.0-1035.41",
"4.4.0-1036.42",
"4.4.0-1037.43",
"4.4.0-1038.44",
"4.4.0-1039.45",
"4.4.0-1040.46",
"4.4.0-1041.47",
"4.4.0-1043.49",
"4.4.0-1044.50",
"4.4.0-1046.52",
"4.4.0-1047.53",
"4.4.0-1048.55",
"4.4.0-1051.58",
"4.4.0-1052.59",
"4.4.0-1054.61",
"4.4.0-1056.63",
"4.4.0-1058.65",
"4.4.0-1059.66",
"4.4.0-1060.67",
"4.4.0-1062.69",
"4.4.0-1063.70",
"4.4.0-1064.71",
"4.4.0-1065.72",
"4.4.0-1066.73",
"4.4.0-1068.75",
"4.4.0-1069.76",
"4.4.0-1070.77",
"4.4.0-1071.78",
"4.4.0-1075.82",
"4.4.0-1076.83",
"4.4.0-1077.84",
"4.4.0-1078.85",
"4.4.0-1079.86",
"4.4.0-1080.87",
"4.4.0-1082.91",
"4.4.0-1084.93",
"4.4.0-1085.94",
"4.4.0-1087.96",
"4.4.0-1088.97",
"4.4.0-1089.98",
"4.4.0-1090.99",
"4.4.0-1091.100",
"4.4.0-1092.101",
"4.4.0-1093.102",
"4.4.0-1094.103",
"4.4.0-1095.104",
"4.4.0-1096.105",
"4.4.0-1097.106",
"4.4.0-1098.107",
"4.4.0-1099.108",
"4.4.0-1100.109",
"4.4.0-1102.111",
"4.4.0-1103.112",
"4.4.0-1104.113",
"4.4.0-1105.114",
"4.4.0-1108.118",
"4.4.0-1110.120",
"4.4.0-1111.121",
"4.4.0-1112.122",
"4.4.0-1113.123",
"4.4.0-1114.124",
"4.4.0-1115.125",
"4.4.0-1116.126",
"4.4.0-1117.127",
"4.4.0-1118.128",
"4.4.0-1119.129",
"4.4.0-1120.130",
"4.4.0-1121.131",
"4.4.0-1122.132",
"4.4.0-1123.133",
"4.4.0-1124.134",
"4.4.0-1125.135",
"4.4.0-1126.136",
"4.4.0-1128.138",
"4.4.0-1129.139",
"4.4.0-1130.140",
"4.4.0-1131.141",
"4.4.0-1132.142",
"4.4.0-1134.144",
"4.4.0-1135.145",
"4.4.0-1136.146",
"4.4.0-1137.147",
"4.4.0-1138.148",
"4.4.0-1139.149",
"4.4.0-1140.151",
"4.4.0-1141.152",
"4.4.0-1142.153",
"4.4.0-1143.154",
"4.4.0-1144.155",
"4.4.0-1145.156",
"4.4.0-1146.157",
"4.4.0-1147.158",
"4.4.0-1148.159",
"4.4.0-1149.160",
"4.4.0-1150.161",
"4.4.0-1151.162",
"4.4.0-1152.163",
"4.4.0-1153.164",
"4.4.0-1154.165",
"4.4.0-1155.166",
"4.4.0-1156.167",
"4.4.0-1157.168",
"4.4.0-1158.169",
"4.4.0-1159.170",
"4.4.0-1160.171"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-1158-oracle",
"binary_version": "4.15.0-1158.169~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-1158-oracle",
"binary_version": "4.15.0-1158.169~16.04.1"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1158-oracle",
"binary_version": "4.15.0-1158.169~16.04.1"
},
{
"binary_name": "linux-modules-4.15.0-1158-oracle",
"binary_version": "4.15.0-1158.169~16.04.1"
},
{
"binary_name": "linux-modules-extra-4.15.0-1158-oracle",
"binary_version": "4.15.0-1158.169~16.04.1"
},
{
"binary_name": "linux-oracle-headers-4.15.0-1158",
"binary_version": "4.15.0-1158.169~16.04.1"
},
{
"binary_name": "linux-oracle-tools-4.15.0-1158",
"binary_version": "4.15.0-1158.169~16.04.1"
},
{
"binary_name": "linux-tools-4.15.0-1158-oracle",
"binary_version": "4.15.0-1158.169~16.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "linux-oracle",
"purl": "pkg:deb/ubuntu/linux-oracle@4.15.0-1158.169~16.04.1?arch=source\u0026distro=esm-infra-legacy/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1007.9~16.04.1",
"4.15.0-1008.10~16.04.1",
"4.15.0-1009.11~16.04.1",
"4.15.0-1010.12~16.04.1",
"4.15.0-1011.13~16.04.1",
"4.15.0-1013.15~16.04.1",
"4.15.0-1014.16~16.04.1",
"4.15.0-1015.17~16.04.1",
"4.15.0-1017.19~16.04.2",
"4.15.0-1018.20~16.04.1",
"4.15.0-1021.23~16.04.1",
"4.15.0-1022.25~16.04.1",
"4.15.0-1023.26~16.04.1",
"4.15.0-1025.28~16.04.1",
"4.15.0-1026.29~16.04.1",
"4.15.0-1027.30~16.04.1",
"4.15.0-1029.32~16.04.1",
"4.15.0-1030.33~16.04.1",
"4.15.0-1031.34~16.04.1",
"4.15.0-1033.36~16.04.1",
"4.15.0-1035.38~16.04.1",
"4.15.0-1037.41~16.04.1",
"4.15.0-1038.42~16.04.1",
"4.15.0-1039.43~16.04.1",
"4.15.0-1045.49~16.04.1",
"4.15.0-1046.50~16.04.1",
"4.15.0-1050.54~16.04.1",
"4.15.0-1051.55~16.04.1",
"4.15.0-1053.57~16.04.1",
"4.15.0-1054.58~16.04.1",
"4.15.0-1056.61~16.04.1",
"4.15.0-1058.64~16.04.1",
"4.15.0-1059.65~16.04.1",
"4.15.0-1061.67~16.04.1",
"4.15.0-1062.68~16.04.1",
"4.15.0-1064.71~16.04.1",
"4.15.0-1065.73~16.04.1",
"4.15.0-1066.74~16.04.1",
"4.15.0-1067.75~16.04.1",
"4.15.0-1068.76~16.04.1",
"4.15.0-1069.77~16.04.1",
"4.15.0-1070.78~16.04.1",
"4.15.0-1071.79~16.04.1",
"4.15.0-1072.80~16.04.1",
"4.15.0-1075.83~16.04.1",
"4.15.0-1078.86~16.04.1",
"4.15.0-1079.87~16.04.1",
"4.15.0-1080.88~16.04.1",
"4.15.0-1081.89~16.04.1",
"4.15.0-1082.90~16.04.1",
"4.15.0-1083.91~16.04.1",
"4.15.0-1084.92~16.04.1",
"4.15.0-1085.93~16.04.1",
"4.15.0-1086.94~16.04.1",
"4.15.0-1087.95~16.04.1",
"4.15.0-1089.98~16.04.1",
"4.15.0-1090.99~16.04.1",
"4.15.0-1091.100~16.04.1",
"4.15.0-1092.101~16.04.1",
"4.15.0-1093.102~16.04.1",
"4.15.0-1095.104~16.04.1",
"4.15.0-1098.108~16.04.1",
"4.15.0-1101.112~16.04.1",
"4.15.0-1102.113~16.04.1",
"4.15.0-1104.115~16.04.1",
"4.15.0-1105.116~16.04.1",
"4.15.0-1106.117~16.04.1",
"4.15.0-1107.118~16.04.1",
"4.15.0-1108.119~16.04.1",
"4.15.0-1111.122~16.04.2",
"4.15.0-1112.123~16.04.1",
"4.15.0-1113.124~16.04.1",
"4.15.0-1115.126~16.04.1",
"4.15.0-1116.127~16.04.1",
"4.15.0-1117.128~16.04.1",
"4.15.0-1118.129~16.04.1",
"4.15.0-1119.130~16.04.1",
"4.15.0-1120.131~16.04.1",
"4.15.0-1121.132~16.04.1",
"4.15.0-1122.133~16.04.1",
"4.15.0-1123.134~16.04.1",
"4.15.0-1124.135~16.04.1",
"4.15.0-1125.136~16.04.1",
"4.15.0-1126.137~16.04.1",
"4.15.0-1127.138~16.04.1",
"4.15.0-1128.139~16.04.1",
"4.15.0-1129.140~16.04.1",
"4.15.0-1130.141~16.04.1",
"4.15.0-1131.142~16.04.1",
"4.15.0-1132.143~16.04.1",
"4.15.0-1133.144~16.04.1",
"4.15.0-1134.145~16.04.1",
"4.15.0-1135.146~16.04.1",
"4.15.0-1136.147~16.04.1",
"4.15.0-1137.148~16.04.1",
"4.15.0-1138.149~16.04.1",
"4.15.0-1139.150~16.04.1",
"4.15.0-1140.151~16.04.1",
"4.15.0-1141.152~16.04.1",
"4.15.0-1142.153~16.04.1",
"4.15.0-1143.154~16.04.1",
"4.15.0-1144.155~16.04.1",
"4.15.0-1145.156~16.04.1",
"4.15.0-1148.159~16.04.1",
"4.15.0-1149.160~16.04.1",
"4.15.0-1150.161~16.04.1",
"4.15.0-1151.162~16.04.1",
"4.15.0-1153.164~16.04.1",
"4.15.0-1154.165~16.04.1",
"4.15.0-1156.167~16.04.1",
"4.15.0-1158.169~16.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "block-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "crypto-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "dasd-extra-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "dasd-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "fat-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "fb-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "firewire-core-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "floppy-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "fs-core-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "fs-secondary-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "input-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "ipmi-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "irda-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "kernel-image-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "linux-buildinfo-4.4.0-1129-fips",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "linux-fips-cloud-tools-common",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "linux-fips-headers-4.4.0-1129",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "linux-fips-source-4.4.0",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "linux-fips-tools-4.4.0-1129",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "linux-headers-4.4.0-1129-fips",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "linux-image-4.4.0-1129-fips",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "linux-image-hmac-4.4.0-1129-fips",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "linux-image-unsigned-4.4.0-1129-fips",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "linux-image-unsigned-hmac-4.4.0-1129-fips",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "linux-modules-4.4.0-1129-fips",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "linux-modules-extra-4.4.0-1129-fips",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "linux-tools-4.4.0-1129-fips",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "linux-udebs-fips",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "md-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "message-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "mouse-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "multipath-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "nfs-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "nic-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "nic-pcmcia-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "nic-shared-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "nic-usb-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "parport-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "pata-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "pcmcia-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "pcmcia-storage-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "plip-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "ppp-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "sata-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "scsi-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "serial-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "speakup-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "storage-core-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "usb-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "virtio-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
},
{
"binary_name": "vlan-modules-4.4.0-1129-fips-di",
"binary_version": "4.4.0-1129.136"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS:16.04:LTS",
"name": "linux-fips",
"purl": "pkg:deb/ubuntu/linux-fips@4.4.0-1129.136?arch=source\u0026distro=fips-updates/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.4.0-1003.3",
"4.4.0-1005.5",
"4.4.0-1006.6",
"4.4.0-1008.10",
"4.4.0-1010.13",
"4.4.0-1011.14",
"4.4.0-1012.16",
"4.4.0-1013.17",
"4.4.0-1015.20",
"4.4.0-1017.22",
"4.4.0-1019.24",
"4.4.0-1021.26",
"4.4.0-1022.27",
"4.4.0-1023.28",
"4.4.0-1025.30",
"4.4.0-1026.31",
"4.4.0-1027.32",
"4.4.0-1028.33",
"4.4.0-1029.34",
"4.4.0-1031.36",
"4.4.0-1032.37",
"4.4.0-1033.38",
"4.4.0-1034.39",
"4.4.0-1041.46",
"4.4.0-1042.47",
"4.4.0-1043.48",
"4.4.0-1044.49",
"4.4.0-1045.50",
"4.4.0-1046.51",
"4.4.0-1048.53",
"4.4.0-1049.55",
"4.4.0-1051.57",
"4.4.0-1052.58",
"4.4.0-1054.60",
"4.4.0-1055.61",
"4.4.0-1056.62",
"4.4.0-1057.63",
"4.4.0-1058.64",
"4.4.0-1060.66",
"4.4.0-1061.67",
"4.4.0-1062.68",
"4.4.0-1063.69",
"4.4.0-1064.70",
"4.4.0-1065.71",
"4.4.0-1066.72",
"4.4.0-1067.73",
"4.4.0-1068.74",
"4.4.0-1069.75",
"4.4.0-1071.77",
"4.4.0-1072.78",
"4.4.0-1073.79",
"4.4.0-1074.80",
"4.4.0-1077.84",
"4.4.0-1079.86",
"4.4.0-1080.87",
"4.4.0-1081.88",
"4.4.0-1082.89",
"4.4.0-1083.90",
"4.4.0-1084.91",
"4.4.0-1085.92",
"4.4.0-1086.93",
"4.4.0-1088.95",
"4.4.0-1089.96",
"4.4.0-1090.97",
"4.4.0-1091.98",
"4.4.0-1092.99",
"4.4.0-1093.100",
"4.4.0-1094.101",
"4.4.0-1095.102",
"4.4.0-1097.104",
"4.4.0-1099.106",
"4.4.0-1100.107",
"4.4.0-1101.108",
"4.4.0-1102.109",
"4.4.0-1103.110",
"4.4.0-1104.111",
"4.4.0-1105.112",
"4.4.0-1106.113",
"4.4.0-1107.114",
"4.4.0-1108.115",
"4.4.0-1109.116",
"4.4.0-1110.117",
"4.4.0-1111.118",
"4.4.0-1112.119",
"4.4.0-1113.120",
"4.4.0-1114.121",
"4.4.0-1115.122",
"4.4.0-1116.123",
"4.4.0-1117.124",
"4.4.0-1119.126",
"4.4.0-1120.127",
"4.4.0-1121.128",
"4.4.0-1122.129",
"4.4.0-1123.130",
"4.4.0-1124.131",
"4.4.0-1125.132",
"4.4.0-1126.133",
"4.4.0-1127.134",
"4.4.0-1128.135",
"4.4.0-1129.136"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "block-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "crypto-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "dasd-extra-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "dasd-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "fat-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "fb-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "firewire-core-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "floppy-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "fs-core-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "fs-secondary-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "input-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "ipmi-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "irda-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "kernel-image-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "linux-fips-headers-4.4.0-1002",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "linux-fips-source-4.4.0",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "linux-fips-tools-4.4.0-1002",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "linux-headers-4.4.0-1002-fips",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "linux-image-4.4.0-1002-fips",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "linux-image-extra-4.4.0-1002-fips",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "linux-image-hmac-4.4.0-1002-fips",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "linux-tools-4.4.0-1002-fips",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "linux-udebs-fips",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "md-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "message-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "mouse-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "multipath-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "nfs-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "nic-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "nic-pcmcia-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "nic-shared-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "nic-usb-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "parport-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "pata-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "pcmcia-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "pcmcia-storage-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "plip-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "ppp-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "sata-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "scsi-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "serial-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "speakup-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "storage-core-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "usb-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "virtio-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
},
{
"binary_name": "vlan-modules-4.4.0-1002-fips-di",
"binary_version": "4.4.0-1002.2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS:16.04:LTS",
"name": "linux-fips",
"purl": "pkg:deb/ubuntu/linux-fips@4.4.0-1002.2?arch=source\u0026distro=fips/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.4.0-1001.1",
"4.4.0-1002.2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "block-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "crypto-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "dasd-extra-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "dasd-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "fat-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "fb-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "firewire-core-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "floppy-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "fs-core-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "fs-secondary-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "input-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "ipmi-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "irda-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "kernel-image-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "linux-buildinfo-4.15.0-260-generic",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "linux-buildinfo-4.15.0-260-lowlatency",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "linux-cloud-tools-4.15.0-260",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "linux-cloud-tools-4.15.0-260-generic",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "linux-cloud-tools-4.15.0-260-lowlatency",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "linux-cloud-tools-common",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "linux-headers-4.15.0-260",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "linux-headers-4.15.0-260-generic",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "linux-headers-4.15.0-260-lowlatency",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "linux-image-4.15.0-260-generic",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "linux-image-unsigned-4.15.0-260-generic",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "linux-image-unsigned-4.15.0-260-lowlatency",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "linux-modules-4.15.0-260-generic",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "linux-modules-4.15.0-260-lowlatency",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "linux-modules-extra-4.15.0-260-generic",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "linux-source-4.15.0",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "linux-tools-4.15.0-260",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "linux-tools-4.15.0-260-generic",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "linux-tools-4.15.0-260-lowlatency",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "linux-tools-common",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "linux-tools-host",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "linux-udebs-generic",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "md-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "message-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "mouse-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "multipath-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "nfs-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "nic-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "nic-pcmcia-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "nic-shared-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "nic-usb-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "parport-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "pata-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "pcmcia-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "pcmcia-storage-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "plip-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "ppp-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "sata-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "scsi-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "serial-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "storage-core-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "usb-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "virtio-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
},
{
"binary_name": "vlan-modules-4.15.0-260-generic-di",
"binary_version": "4.15.0-260.272"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "linux",
"purl": "pkg:deb/ubuntu/linux@4.15.0-260.272?arch=source\u0026distro=esm-infra/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.13.0-16.19",
"4.13.0-17.20",
"4.13.0-25.29",
"4.13.0-32.35",
"4.15.0-10.11",
"4.15.0-12.13",
"4.15.0-13.14",
"4.15.0-15.16",
"4.15.0-19.20",
"4.15.0-20.21",
"4.15.0-22.24",
"4.15.0-23.25",
"4.15.0-24.26",
"4.15.0-29.31",
"4.15.0-30.32",
"4.15.0-32.35",
"4.15.0-33.36",
"4.15.0-34.37",
"4.15.0-36.39",
"4.15.0-38.41",
"4.15.0-39.42",
"4.15.0-42.45",
"4.15.0-43.46",
"4.15.0-44.47",
"4.15.0-45.48",
"4.15.0-46.49",
"4.15.0-47.50",
"4.15.0-48.51",
"4.15.0-50.54",
"4.15.0-51.55",
"4.15.0-52.56",
"4.15.0-54.58",
"4.15.0-55.60",
"4.15.0-58.64",
"4.15.0-60.67",
"4.15.0-62.69",
"4.15.0-64.73",
"4.15.0-65.74",
"4.15.0-66.75",
"4.15.0-69.78",
"4.15.0-70.79",
"4.15.0-72.81",
"4.15.0-74.84",
"4.15.0-76.86",
"4.15.0-88.88",
"4.15.0-91.92",
"4.15.0-96.97",
"4.15.0-99.100",
"4.15.0-101.102",
"4.15.0-106.107",
"4.15.0-108.109",
"4.15.0-109.110",
"4.15.0-111.112",
"4.15.0-112.113",
"4.15.0-115.116",
"4.15.0-117.118",
"4.15.0-118.119",
"4.15.0-121.123",
"4.15.0-122.124",
"4.15.0-123.126",
"4.15.0-124.127",
"4.15.0-126.129",
"4.15.0-128.131",
"4.15.0-129.132",
"4.15.0-130.134",
"4.15.0-132.136",
"4.15.0-134.138",
"4.15.0-135.139",
"4.15.0-136.140",
"4.15.0-137.141",
"4.15.0-139.143",
"4.15.0-140.144",
"4.15.0-141.145",
"4.15.0-142.146",
"4.15.0-143.147",
"4.15.0-144.148",
"4.15.0-147.151",
"4.15.0-151.157",
"4.15.0-153.160",
"4.15.0-154.161",
"4.15.0-156.163",
"4.15.0-158.166",
"4.15.0-159.167",
"4.15.0-161.169",
"4.15.0-162.170",
"4.15.0-163.171",
"4.15.0-166.174",
"4.15.0-167.175",
"4.15.0-169.177",
"4.15.0-171.180",
"4.15.0-173.182",
"4.15.0-175.184",
"4.15.0-176.185",
"4.15.0-177.186",
"4.15.0-180.189",
"4.15.0-184.194",
"4.15.0-187.198",
"4.15.0-188.199",
"4.15.0-189.200",
"4.15.0-191.202",
"4.15.0-192.203",
"4.15.0-193.204",
"4.15.0-194.205",
"4.15.0-196.207",
"4.15.0-197.208",
"4.15.0-200.211",
"4.15.0-201.212",
"4.15.0-202.213",
"4.15.0-204.215",
"4.15.0-206.217",
"4.15.0-208.220",
"4.15.0-209.220",
"4.15.0-210.221",
"4.15.0-211.222",
"4.15.0-212.223",
"4.15.0-213.224",
"4.15.0-214.225",
"4.15.0-216.227",
"4.15.0-218.229",
"4.15.0-219.230",
"4.15.0-220.231",
"4.15.0-221.232",
"4.15.0-222.233",
"4.15.0-223.235",
"4.15.0-224.236",
"4.15.0-225.237",
"4.15.0-226.238",
"4.15.0-227.239",
"4.15.0-228.240",
"4.15.0-229.241",
"4.15.0-230.242",
"4.15.0-231.243",
"4.15.0-232.244",
"4.15.0-233.245",
"4.15.0-234.246",
"4.15.0-235.247",
"4.15.0-236.248",
"4.15.0-237.249",
"4.15.0-238.250",
"4.15.0-239.251",
"4.15.0-240.252",
"4.15.0-241.253",
"4.15.0-242.254",
"4.15.0-243.255",
"4.15.0-245.257",
"4.15.0-246.258",
"4.15.0-247.259",
"4.15.0-248.260",
"4.15.0-249.261",
"4.15.0-250.262",
"4.15.0-251.263",
"4.15.0-253.265",
"4.15.0-254.266",
"4.15.0-257.269",
"4.15.0-260.272"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-aws-cloud-tools-4.15.0-1197",
"binary_version": "4.15.0-1197.210"
},
{
"binary_name": "linux-aws-headers-4.15.0-1197",
"binary_version": "4.15.0-1197.210"
},
{
"binary_name": "linux-aws-tools-4.15.0-1197",
"binary_version": "4.15.0-1197.210"
},
{
"binary_name": "linux-buildinfo-4.15.0-1197-aws",
"binary_version": "4.15.0-1197.210"
},
{
"binary_name": "linux-cloud-tools-4.15.0-1197-aws",
"binary_version": "4.15.0-1197.210"
},
{
"binary_name": "linux-headers-4.15.0-1197-aws",
"binary_version": "4.15.0-1197.210"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1197-aws",
"binary_version": "4.15.0-1197.210"
},
{
"binary_name": "linux-modules-4.15.0-1197-aws",
"binary_version": "4.15.0-1197.210"
},
{
"binary_name": "linux-modules-extra-4.15.0-1197-aws",
"binary_version": "4.15.0-1197.210"
},
{
"binary_name": "linux-tools-4.15.0-1197-aws",
"binary_version": "4.15.0-1197.210"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "linux-aws",
"purl": "pkg:deb/ubuntu/linux-aws@4.15.0-1197.210?arch=source\u0026distro=esm-infra/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-1007.7",
"4.15.0-1009.9",
"4.15.0-1010.10",
"4.15.0-1011.11",
"4.15.0-1016.16",
"4.15.0-1017.17",
"4.15.0-1019.19",
"4.15.0-1020.20",
"4.15.0-1021.21",
"4.15.0-1023.23",
"4.15.0-1025.25",
"4.15.0-1027.27",
"4.15.0-1029.30",
"4.15.0-1031.33",
"4.15.0-1032.34",
"4.15.0-1033.35",
"4.15.0-1034.36",
"4.15.0-1035.37",
"4.15.0-1037.39",
"4.15.0-1039.41",
"4.15.0-1040.42",
"4.15.0-1041.43",
"4.15.0-1043.45",
"4.15.0-1044.46",
"4.15.0-1045.47",
"4.15.0-1047.49",
"4.15.0-1048.50",
"4.15.0-1050.52",
"4.15.0-1051.53",
"4.15.0-1052.54",
"4.15.0-1054.56",
"4.15.0-1056.58",
"4.15.0-1057.59",
"4.15.0-1058.60",
"4.15.0-1060.62",
"4.15.0-1063.67",
"4.15.0-1065.69",
"4.15.0-1066.70",
"4.15.0-1067.71",
"4.15.0-1073.77",
"4.15.0-1076.80",
"4.15.0-1077.81",
"4.15.0-1079.83",
"4.15.0-1080.84",
"4.15.0-1082.86",
"4.15.0-1083.87",
"4.15.0-1086.91",
"4.15.0-1087.92",
"4.15.0-1088.93",
"4.15.0-1090.95",
"4.15.0-1091.96",
"4.15.0-1092.98",
"4.15.0-1093.99",
"4.15.0-1094.101",
"4.15.0-1095.102",
"4.15.0-1096.103",
"4.15.0-1097.104",
"4.15.0-1098.105",
"4.15.0-1099.106",
"4.15.0-1101.108",
"4.15.0-1102.109",
"4.15.0-1103.110",
"4.15.0-1106.113",
"4.15.0-1109.116",
"4.15.0-1110.117",
"4.15.0-1111.118",
"4.15.0-1112.119",
"4.15.0-1114.121",
"4.15.0-1115.122",
"4.15.0-1116.123",
"4.15.0-1118.125",
"4.15.0-1119.127",
"4.15.0-1121.129",
"4.15.0-1123.132",
"4.15.0-1124.133",
"4.15.0-1126.135",
"4.15.0-1127.136",
"4.15.0-1128.137",
"4.15.0-1130.139",
"4.15.0-1133.143",
"4.15.0-1136.147",
"4.15.0-1137.148",
"4.15.0-1139.150",
"4.15.0-1140.151",
"4.15.0-1141.152",
"4.15.0-1142.154",
"4.15.0-1143.155",
"4.15.0-1144.156",
"4.15.0-1146.158",
"4.15.0-1147.159",
"4.15.0-1148.160",
"4.15.0-1150.163",
"4.15.0-1151.164",
"4.15.0-1153.166",
"4.15.0-1154.167",
"4.15.0-1155.168",
"4.15.0-1156.169",
"4.15.0-1157.170",
"4.15.0-1158.171",
"4.15.0-1159.172",
"4.15.0-1160.173",
"4.15.0-1161.174",
"4.15.0-1162.175",
"4.15.0-1163.176",
"4.15.0-1164.177",
"4.15.0-1165.178",
"4.15.0-1166.179",
"4.15.0-1167.180",
"4.15.0-1168.181",
"4.15.0-1169.182",
"4.15.0-1170.183",
"4.15.0-1172.185",
"4.15.0-1173.186",
"4.15.0-1174.187",
"4.15.0-1175.188",
"4.15.0-1176.189",
"4.15.0-1177.190",
"4.15.0-1178.191",
"4.15.0-1179.192",
"4.15.0-1180.193",
"4.15.0-1181.194",
"4.15.0-1182.195",
"4.15.0-1183.196",
"4.15.0-1184.197",
"4.15.0-1185.198",
"4.15.0-1186.199",
"4.15.0-1187.200",
"4.15.0-1188.201",
"4.15.0-1189.202",
"4.15.0-1190.203",
"4.15.0-1191.204",
"4.15.0-1192.205",
"4.15.0-1194.207",
"4.15.0-1195.208",
"4.15.0-1196.209",
"4.15.0-1197.210"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-aws-5.0-tools-5.0.0-1027",
"binary_version": "5.0.0-1027.30"
},
{
"binary_name": "linux-aws-headers-5.0.0-1027",
"binary_version": "5.0.0-1027.30"
},
{
"binary_name": "linux-buildinfo-5.0.0-1027-aws",
"binary_version": "5.0.0-1027.30"
},
{
"binary_name": "linux-cloud-tools-5.0.0-1027-aws",
"binary_version": "5.0.0-1027.30"
},
{
"binary_name": "linux-headers-5.0.0-1027-aws",
"binary_version": "5.0.0-1027.30"
},
{
"binary_name": "linux-image-5.0.0-1027-aws",
"binary_version": "5.0.0-1027.30"
},
{
"binary_name": "linux-modules-5.0.0-1027-aws",
"binary_version": "5.0.0-1027.30"
},
{
"binary_name": "linux-modules-extra-5.0.0-1027-aws",
"binary_version": "5.0.0-1027.30"
},
{
"binary_name": "linux-tools-5.0.0-1027-aws",
"binary_version": "5.0.0-1027.30"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-aws-5.0",
"purl": "pkg:deb/ubuntu/linux-aws-5.0@5.0.0-1027.30?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.0.0-1021.24~18.04.1",
"5.0.0-1022.25~18.04.1",
"5.0.0-1023.26~18.04.1",
"5.0.0-1024.27~18.04.1",
"5.0.0-1025.28",
"5.0.0-1027.30"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-aws-5.3-cloud-tools-5.3.0-1035",
"binary_version": "5.3.0-1035.37"
},
{
"binary_name": "linux-aws-5.3-headers-5.3.0-1035",
"binary_version": "5.3.0-1035.37"
},
{
"binary_name": "linux-aws-5.3-tools-5.3.0-1035",
"binary_version": "5.3.0-1035.37"
},
{
"binary_name": "linux-buildinfo-5.3.0-1035-aws",
"binary_version": "5.3.0-1035.37"
},
{
"binary_name": "linux-cloud-tools-5.3.0-1035-aws",
"binary_version": "5.3.0-1035.37"
},
{
"binary_name": "linux-headers-5.3.0-1035-aws",
"binary_version": "5.3.0-1035.37"
},
{
"binary_name": "linux-image-5.3.0-1035-aws",
"binary_version": "5.3.0-1035.37"
},
{
"binary_name": "linux-modules-5.3.0-1035-aws",
"binary_version": "5.3.0-1035.37"
},
{
"binary_name": "linux-modules-extra-5.3.0-1035-aws",
"binary_version": "5.3.0-1035.37"
},
{
"binary_name": "linux-tools-5.3.0-1035-aws",
"binary_version": "5.3.0-1035.37"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-aws-5.3",
"purl": "pkg:deb/ubuntu/linux-aws-5.3@5.3.0-1035.37?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.3.0-1016.17~18.04.1",
"5.3.0-1017.18~18.04.1",
"5.3.0-1019.21~18.04.1",
"5.3.0-1023.25~18.04.1",
"5.3.0-1028.30~18.04.1",
"5.3.0-1030.32~18.04.1",
"5.3.0-1032.34~18.04.2",
"5.3.0-1033.35",
"5.3.0-1034.36",
"5.3.0-1035.37"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-aws-5.4-cloud-tools-5.4.0-1135",
"binary_version": "5.4.0-1135.145~18.04.1"
},
{
"binary_name": "linux-aws-5.4-headers-5.4.0-1135",
"binary_version": "5.4.0-1135.145~18.04.1"
},
{
"binary_name": "linux-aws-5.4-tools-5.4.0-1135",
"binary_version": "5.4.0-1135.145~18.04.1"
},
{
"binary_name": "linux-buildinfo-5.4.0-1135-aws",
"binary_version": "5.4.0-1135.145~18.04.1"
},
{
"binary_name": "linux-cloud-tools-5.4.0-1135-aws",
"binary_version": "5.4.0-1135.145~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-1135-aws",
"binary_version": "5.4.0-1135.145~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1135-aws",
"binary_version": "5.4.0-1135.145~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-1135-aws",
"binary_version": "5.4.0-1135.145~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1135-aws",
"binary_version": "5.4.0-1135.145~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-1135-aws",
"binary_version": "5.4.0-1135.145~18.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "linux-aws-5.4",
"purl": "pkg:deb/ubuntu/linux-aws-5.4@5.4.0-1135.145~18.04.1?arch=source\u0026distro=esm-infra/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1135.145~18.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1018.18~18.04.1",
"5.4.0-1020.20~18.04.2",
"5.4.0-1022.22~18.04.1",
"5.4.0-1024.24~18.04.1",
"5.4.0-1025.25~18.04.1",
"5.4.0-1028.29~18.04.1",
"5.4.0-1029.30~18.04.1",
"5.4.0-1030.31~18.04.1",
"5.4.0-1032.33~18.04.1",
"5.4.0-1034.35~18.04.1",
"5.4.0-1035.37~18.04.1",
"5.4.0-1037.39~18.04.1",
"5.4.0-1038.40~18.04.1",
"5.4.0-1039.41~18.04.1",
"5.4.0-1041.43~18.04.1",
"5.4.0-1043.45~18.04.1",
"5.4.0-1045.47~18.04.1",
"5.4.0-1047.49~18.04.1",
"5.4.0-1048.50~18.04.1",
"5.4.0-1049.51~18.04.1",
"5.4.0-1051.53~18.04.1",
"5.4.0-1054.57~18.04.1",
"5.4.0-1055.58~18.04.1",
"5.4.0-1056.59~18.04.1",
"5.4.0-1057.60~18.04.1",
"5.4.0-1058.61~18.04.3",
"5.4.0-1059.62~18.04.1",
"5.4.0-1060.63~18.04.1",
"5.4.0-1061.64~18.04.1",
"5.4.0-1063.66~18.04.1",
"5.4.0-1064.67~18.04.1",
"5.4.0-1065.68~18.04.1",
"5.4.0-1066.69~18.04.1",
"5.4.0-1068.72~18.04.1",
"5.4.0-1069.73~18.04.1",
"5.4.0-1071.76~18.04.1",
"5.4.0-1072.77~18.04.1",
"5.4.0-1075.80~18.04.1",
"5.4.0-1078.84~18.04.1",
"5.4.0-1080.87~18.04.1",
"5.4.0-1081.88~18.04.1",
"5.4.0-1083.90~18.04.1",
"5.4.0-1084.91~18.04.1",
"5.4.0-1085.92~18.04.1",
"5.4.0-1086.93~18.04.1",
"5.4.0-1088.96~18.04.1",
"5.4.0-1089.97~18.04.1",
"5.4.0-1090.98~18.04.1",
"5.4.0-1092.100~18.04.2",
"5.4.0-1093.102~18.04.2",
"5.4.0-1094.102~18.04.1",
"5.4.0-1096.104~18.04.1",
"5.4.0-1097.105~18.04.1",
"5.4.0-1099.107~18.04.1",
"5.4.0-1100.108~18.04.1",
"5.4.0-1101.109~18.04.1",
"5.4.0-1103.111~18.04.1",
"5.4.0-1104.112~18.04.1",
"5.4.0-1105.113~18.04.1",
"5.4.0-1106.114~18.04.1",
"5.4.0-1107.115~18.04.1",
"5.4.0-1108.116~18.04.1",
"5.4.0-1109.118~18.04.1",
"5.4.0-1110.119~18.04.1",
"5.4.0-1111.120~18.04.1",
"5.4.0-1112.121~18.04.2",
"5.4.0-1113.123~18.04.1",
"5.4.0-1114.124~18.04.1",
"5.4.0-1116.126~18.04.1",
"5.4.0-1117.127~18.04.1",
"5.4.0-1118.128~18.04.1",
"5.4.0-1119.129~18.04.1",
"5.4.0-1120.130~18.04.1",
"5.4.0-1121.131~18.04.1",
"5.4.0-1122.132~18.04.1",
"5.4.0-1123.133~18.04.1",
"5.4.0-1124.134~18.04.1",
"5.4.0-1125.135~18.04.1",
"5.4.0-1126.136~18.04.1",
"5.4.0-1127.137~18.04.2",
"5.4.0-1128.138~18.04.1",
"5.4.0-1129.139~18.04.1",
"5.4.0-1130.140~18.04.1",
"5.4.0-1131.141~18.04.1",
"5.4.0-1132.142~18.04.1",
"5.4.0-1133.143~18.04.1",
"5.4.0-1134.144~18.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-azure-cloud-tools-5.0.0-1036",
"binary_version": "5.0.0-1036.38"
},
{
"binary_name": "linux-azure-headers-5.0.0-1036",
"binary_version": "5.0.0-1036.38"
},
{
"binary_name": "linux-azure-tools-5.0.0-1036",
"binary_version": "5.0.0-1036.38"
},
{
"binary_name": "linux-buildinfo-5.0.0-1036-azure",
"binary_version": "5.0.0-1036.38"
},
{
"binary_name": "linux-cloud-tools-5.0.0-1036-azure",
"binary_version": "5.0.0-1036.38"
},
{
"binary_name": "linux-headers-5.0.0-1036-azure",
"binary_version": "5.0.0-1036.38"
},
{
"binary_name": "linux-image-unsigned-5.0.0-1036-azure",
"binary_version": "5.0.0-1036.38"
},
{
"binary_name": "linux-modules-5.0.0-1036-azure",
"binary_version": "5.0.0-1036.38"
},
{
"binary_name": "linux-modules-extra-5.0.0-1036-azure",
"binary_version": "5.0.0-1036.38"
},
{
"binary_name": "linux-tools-5.0.0-1036-azure",
"binary_version": "5.0.0-1036.38"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-azure",
"purl": "pkg:deb/ubuntu/linux-azure@5.0.0-1036.38?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1002.2",
"4.15.0-1003.3",
"4.15.0-1004.4",
"4.15.0-1008.8",
"4.15.0-1009.9",
"4.15.0-1012.12",
"4.15.0-1013.13",
"4.15.0-1014.14",
"4.15.0-1018.18",
"4.15.0-1019.19",
"4.15.0-1021.21",
"4.15.0-1022.23",
"4.15.0-1023.24",
"4.15.0-1025.26",
"4.15.0-1028.29",
"4.15.0-1030.31",
"4.15.0-1031.32",
"4.15.0-1032.33",
"4.15.0-1035.36",
"4.15.0-1036.38",
"4.15.0-1037.39",
"4.18.0-1011.11~18.04.1",
"4.18.0-1013.13~18.04.1",
"4.18.0-1014.14~18.04.1",
"4.18.0-1018.18~18.04.1",
"4.18.0-1019.19~18.04.1",
"4.18.0-1020.20~18.04.1",
"4.18.0-1023.24~18.04.1",
"4.18.0-1024.25~18.04.1",
"4.18.0-1025.27~18.04.1",
"5.0.0-1014.14~18.04.1",
"5.0.0-1016.17~18.04.1",
"5.0.0-1018.19~18.04.1",
"5.0.0-1020.21~18.04.1",
"5.0.0-1022.23~18.04.1",
"5.0.0-1023.24~18.04.1",
"5.0.0-1025.27~18.04.1",
"5.0.0-1027.29~18.04.1",
"5.0.0-1028.30~18.04.1",
"5.0.0-1029.31~18.04.1",
"5.0.0-1031.33",
"5.0.0-1032.34",
"5.0.0-1035.37",
"5.0.0-1036.38"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-azure-4.15-cloud-tools-4.15.0-1207",
"binary_version": "4.15.0-1207.222"
},
{
"binary_name": "linux-azure-4.15-headers-4.15.0-1207",
"binary_version": "4.15.0-1207.222"
},
{
"binary_name": "linux-azure-4.15-tools-4.15.0-1207",
"binary_version": "4.15.0-1207.222"
},
{
"binary_name": "linux-buildinfo-4.15.0-1207-azure",
"binary_version": "4.15.0-1207.222"
},
{
"binary_name": "linux-cloud-tools-4.15.0-1207-azure",
"binary_version": "4.15.0-1207.222"
},
{
"binary_name": "linux-headers-4.15.0-1207-azure",
"binary_version": "4.15.0-1207.222"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1207-azure",
"binary_version": "4.15.0-1207.222"
},
{
"binary_name": "linux-modules-4.15.0-1207-azure",
"binary_version": "4.15.0-1207.222"
},
{
"binary_name": "linux-modules-extra-4.15.0-1207-azure",
"binary_version": "4.15.0-1207.222"
},
{
"binary_name": "linux-tools-4.15.0-1207-azure",
"binary_version": "4.15.0-1207.222"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "linux-azure-4.15",
"purl": "pkg:deb/ubuntu/linux-azure-4.15@4.15.0-1207.222?arch=source\u0026distro=esm-infra/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1082.92",
"4.15.0-1083.93",
"4.15.0-1089.99",
"4.15.0-1091.101",
"4.15.0-1092.102",
"4.15.0-1093.103",
"4.15.0-1095.105",
"4.15.0-1096.106",
"4.15.0-1099.110",
"4.15.0-1100.111",
"4.15.0-1102.113",
"4.15.0-1103.114",
"4.15.0-1104.116",
"4.15.0-1106.118",
"4.15.0-1108.120",
"4.15.0-1109.121",
"4.15.0-1110.122",
"4.15.0-1111.123",
"4.15.0-1112.125",
"4.15.0-1113.126",
"4.15.0-1114.127",
"4.15.0-1115.128",
"4.15.0-1118.131",
"4.15.0-1121.134",
"4.15.0-1122.135",
"4.15.0-1123.136",
"4.15.0-1124.137",
"4.15.0-1125.138",
"4.15.0-1126.139",
"4.15.0-1127.140",
"4.15.0-1129.142",
"4.15.0-1130.143",
"4.15.0-1131.144",
"4.15.0-1133.146",
"4.15.0-1134.147",
"4.15.0-1136.149",
"4.15.0-1137.150",
"4.15.0-1138.151",
"4.15.0-1139.152",
"4.15.0-1142.156",
"4.15.0-1145.160",
"4.15.0-1146.161",
"4.15.0-1149.164",
"4.15.0-1150.165",
"4.15.0-1151.166",
"4.15.0-1153.168",
"4.15.0-1157.172",
"4.15.0-1158.173",
"4.15.0-1159.174",
"4.15.0-1161.176",
"4.15.0-1162.177",
"4.15.0-1163.178",
"4.15.0-1164.179",
"4.15.0-1165.180",
"4.15.0-1166.181",
"4.15.0-1167.182",
"4.15.0-1168.183",
"4.15.0-1169.184",
"4.15.0-1170.185",
"4.15.0-1171.186",
"4.15.0-1172.187",
"4.15.0-1173.188",
"4.15.0-1174.189",
"4.15.0-1175.190",
"4.15.0-1176.191",
"4.15.0-1177.192",
"4.15.0-1178.193",
"4.15.0-1179.194",
"4.15.0-1180.195",
"4.15.0-1181.196",
"4.15.0-1182.197",
"4.15.0-1183.198",
"4.15.0-1184.199",
"4.15.0-1185.200",
"4.15.0-1186.201",
"4.15.0-1187.202",
"4.15.0-1188.203",
"4.15.0-1189.204",
"4.15.0-1190.205",
"4.15.0-1191.206",
"4.15.0-1192.207",
"4.15.0-1193.208",
"4.15.0-1194.209",
"4.15.0-1195.210",
"4.15.0-1196.211",
"4.15.0-1197.212",
"4.15.0-1199.214",
"4.15.0-1200.215",
"4.15.0-1201.216",
"4.15.0-1202.217",
"4.15.0-1204.219",
"4.15.0-1205.220",
"4.15.0-1206.221",
"4.15.0-1207.222"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-azure-5.3-cloud-tools-5.3.0-1035",
"binary_version": "5.3.0-1035.36"
},
{
"binary_name": "linux-azure-5.3-headers-5.3.0-1035",
"binary_version": "5.3.0-1035.36"
},
{
"binary_name": "linux-azure-5.3-tools-5.3.0-1035",
"binary_version": "5.3.0-1035.36"
},
{
"binary_name": "linux-buildinfo-5.3.0-1035-azure",
"binary_version": "5.3.0-1035.36"
},
{
"binary_name": "linux-cloud-tools-5.3.0-1035-azure",
"binary_version": "5.3.0-1035.36"
},
{
"binary_name": "linux-headers-5.3.0-1035-azure",
"binary_version": "5.3.0-1035.36"
},
{
"binary_name": "linux-image-unsigned-5.3.0-1035-azure",
"binary_version": "5.3.0-1035.36"
},
{
"binary_name": "linux-modules-5.3.0-1035-azure",
"binary_version": "5.3.0-1035.36"
},
{
"binary_name": "linux-modules-extra-5.3.0-1035-azure",
"binary_version": "5.3.0-1035.36"
},
{
"binary_name": "linux-tools-5.3.0-1035-azure",
"binary_version": "5.3.0-1035.36"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-azure-5.3",
"purl": "pkg:deb/ubuntu/linux-azure-5.3@5.3.0-1035.36?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.3.0-1007.8~18.04.1",
"5.3.0-1008.9~18.04.1",
"5.3.0-1009.10~18.04.1",
"5.3.0-1010.11~18.04.1",
"5.3.0-1012.13~18.04.1",
"5.3.0-1013.14~18.04.1",
"5.3.0-1016.17~18.04.1",
"5.3.0-1018.19~18.04.1",
"5.3.0-1019.20~18.04.1",
"5.3.0-1020.21~18.04.1",
"5.3.0-1022.23~18.04.1",
"5.3.0-1028.29~18.04.1",
"5.3.0-1031.32~18.04.1",
"5.3.0-1032.33~18.04.1",
"5.3.0-1034.35~18.04.1",
"5.3.0-1035.36"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-azure-5.4-cloud-tools-5.4.0-1140",
"binary_version": "5.4.0-1140.147~18.04.1"
},
{
"binary_name": "linux-azure-5.4-headers-5.4.0-1140",
"binary_version": "5.4.0-1140.147~18.04.1"
},
{
"binary_name": "linux-azure-5.4-tools-5.4.0-1140",
"binary_version": "5.4.0-1140.147~18.04.1"
},
{
"binary_name": "linux-buildinfo-5.4.0-1140-azure",
"binary_version": "5.4.0-1140.147~18.04.1"
},
{
"binary_name": "linux-cloud-tools-5.4.0-1140-azure",
"binary_version": "5.4.0-1140.147~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-1140-azure",
"binary_version": "5.4.0-1140.147~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1140-azure",
"binary_version": "5.4.0-1140.147~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-1140-azure",
"binary_version": "5.4.0-1140.147~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1140-azure",
"binary_version": "5.4.0-1140.147~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-1140-azure",
"binary_version": "5.4.0-1140.147~18.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "linux-azure-5.4",
"purl": "pkg:deb/ubuntu/linux-azure-5.4@5.4.0-1140.147~18.04.1?arch=source\u0026distro=esm-infra/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1140.147~18.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1020.20~18.04.1",
"5.4.0-1022.22~18.04.1",
"5.4.0-1023.23~18.04.1",
"5.4.0-1025.25~18.04.1",
"5.4.0-1026.26~18.04.1",
"5.4.0-1031.32~18.04.1",
"5.4.0-1032.33~18.04.1",
"5.4.0-1034.35~18.04.1",
"5.4.0-1035.36~18.04.1",
"5.4.0-1036.38~18.04.1",
"5.4.0-1039.41~18.04.1",
"5.4.0-1040.42~18.04.1",
"5.4.0-1041.43~18.04.1",
"5.4.0-1043.45~18.04.1",
"5.4.0-1044.46~18.04.1",
"5.4.0-1046.48~18.04.1",
"5.4.0-1047.49~18.04.1",
"5.4.0-1048.50~18.04.1",
"5.4.0-1049.51~18.04.1",
"5.4.0-1051.53~18.04.1",
"5.4.0-1055.57~18.04.1",
"5.4.0-1056.58~18.04.1",
"5.4.0-1058.60~18.04.1",
"5.4.0-1059.62~18.04.1",
"5.4.0-1061.64~18.04.1",
"5.4.0-1062.65~18.04.1",
"5.4.0-1063.66~18.04.1",
"5.4.0-1064.67~18.04.1",
"5.4.0-1065.68~18.04.1",
"5.4.0-1067.70~18.04.1",
"5.4.0-1068.71~18.04.1",
"5.4.0-1069.72~18.04.1",
"5.4.0-1070.73~18.04.1",
"5.4.0-1072.75~18.04.1",
"5.4.0-1073.76~18.04.1",
"5.4.0-1074.77~18.04.1",
"5.4.0-1077.80~18.04.1",
"5.4.0-1078.81~18.04.1",
"5.4.0-1080.83~18.04.2",
"5.4.0-1083.87~18.04.1",
"5.4.0-1085.90~18.04.1",
"5.4.0-1086.91~18.04.1",
"5.4.0-1089.94~18.04.1",
"5.4.0-1090.95~18.04.1",
"5.4.0-1091.96~18.04.1",
"5.4.0-1094.100~18.04.1",
"5.4.0-1095.101~18.04.1",
"5.4.0-1098.104~18.04.2",
"5.4.0-1100.106~18.04.1",
"5.4.0-1101.107~18.04.1",
"5.4.0-1103.109~18.04.1",
"5.4.0-1104.110~18.04.1",
"5.4.0-1105.111~18.04.1",
"5.4.0-1106.112~18.04.1",
"5.4.0-1107.113~18.04.1",
"5.4.0-1108.114~18.04.1",
"5.4.0-1109.115~18.04.1",
"5.4.0-1110.116~18.04.1",
"5.4.0-1111.117~18.04.1",
"5.4.0-1112.118~18.04.1",
"5.4.0-1113.119~18.04.1",
"5.4.0-1115.122~18.04.1",
"5.4.0-1116.123~18.04.1",
"5.4.0-1117.124~18.04.1",
"5.4.0-1118.125~18.04.1",
"5.4.0-1119.126~18.04.2",
"5.4.0-1120.127~18.04.1",
"5.4.0-1121.128~18.04.1",
"5.4.0-1122.129~18.04.1",
"5.4.0-1123.130~18.04.1",
"5.4.0-1124.131~18.04.1",
"5.4.0-1126.133~18.04.1",
"5.4.0-1127.134~18.04.1",
"5.4.0-1128.135~18.04.1",
"5.4.0-1129.136~18.04.1",
"5.4.0-1130.137~18.04.1",
"5.4.0-1131.138~18.04.1",
"5.4.0-1132.139~18.04.1",
"5.4.0-1133.140~18.04.1",
"5.4.0-1134.141~18.04.1",
"5.4.0-1135.142~18.04.1",
"5.4.0-1136.143~18.04.1",
"5.4.0-1137.144~18.04.1",
"5.4.0-1138.145~18.04.1",
"5.4.0-1139.146~18.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-azure-edge-cloud-tools-5.0.0-1012",
"binary_version": "5.0.0-1012.12~18.04.2"
},
{
"binary_name": "linux-azure-edge-tools-5.0.0-1012",
"binary_version": "5.0.0-1012.12~18.04.2"
},
{
"binary_name": "linux-azure-headers-5.0.0-1012",
"binary_version": "5.0.0-1012.12~18.04.2"
},
{
"binary_name": "linux-buildinfo-5.0.0-1012-azure",
"binary_version": "5.0.0-1012.12~18.04.2"
},
{
"binary_name": "linux-cloud-tools-5.0.0-1012-azure",
"binary_version": "5.0.0-1012.12~18.04.2"
},
{
"binary_name": "linux-headers-5.0.0-1012-azure",
"binary_version": "5.0.0-1012.12~18.04.2"
},
{
"binary_name": "linux-image-unsigned-5.0.0-1012-azure",
"binary_version": "5.0.0-1012.12~18.04.2"
},
{
"binary_name": "linux-modules-5.0.0-1012-azure",
"binary_version": "5.0.0-1012.12~18.04.2"
},
{
"binary_name": "linux-modules-extra-5.0.0-1012-azure",
"binary_version": "5.0.0-1012.12~18.04.2"
},
{
"binary_name": "linux-tools-5.0.0-1012-azure",
"binary_version": "5.0.0-1012.12~18.04.2"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-azure-edge",
"purl": "pkg:deb/ubuntu/linux-azure-edge@5.0.0-1012.12~18.04.2?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.18.0-1006.6~18.04.1",
"4.18.0-1007.7~18.04.1",
"4.18.0-1008.8~18.04.1",
"5.0.0-1012.12~18.04.2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.0.0-1034-gcp",
"binary_version": "5.0.0-1034.35"
},
{
"binary_name": "linux-gcp-headers-5.0.0-1034",
"binary_version": "5.0.0-1034.35"
},
{
"binary_name": "linux-gcp-tools-5.0.0-1034",
"binary_version": "5.0.0-1034.35"
},
{
"binary_name": "linux-headers-5.0.0-1034-gcp",
"binary_version": "5.0.0-1034.35"
},
{
"binary_name": "linux-image-unsigned-5.0.0-1034-gcp",
"binary_version": "5.0.0-1034.35"
},
{
"binary_name": "linux-modules-5.0.0-1034-gcp",
"binary_version": "5.0.0-1034.35"
},
{
"binary_name": "linux-modules-extra-5.0.0-1034-gcp",
"binary_version": "5.0.0-1034.35"
},
{
"binary_name": "linux-tools-5.0.0-1034-gcp",
"binary_version": "5.0.0-1034.35"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-gcp",
"purl": "pkg:deb/ubuntu/linux-gcp@5.0.0-1034.35?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1001.1",
"4.15.0-1003.3",
"4.15.0-1005.5",
"4.15.0-1006.6",
"4.15.0-1008.8",
"4.15.0-1009.9",
"4.15.0-1010.10",
"4.15.0-1014.14",
"4.15.0-1015.15",
"4.15.0-1017.18",
"4.15.0-1018.19",
"4.15.0-1019.20",
"4.15.0-1021.22",
"4.15.0-1023.24",
"4.15.0-1024.25",
"4.15.0-1025.26",
"4.15.0-1026.27",
"4.15.0-1027.28",
"4.15.0-1028.29",
"4.15.0-1029.31",
"4.15.0-1030.32",
"4.15.0-1032.34",
"4.15.0-1033.35",
"4.15.0-1034.36",
"4.15.0-1036.38",
"4.15.0-1037.39",
"4.15.0-1040.42",
"4.15.0-1042.45",
"4.15.0-1044.70",
"5.0.0-1020.20~18.04.1",
"5.0.0-1021.21~18.04.1",
"5.0.0-1025.26~18.04.1",
"5.0.0-1026.27~18.04.1",
"5.0.0-1028.29~18.04.1",
"5.0.0-1029.30~18.04.1",
"5.0.0-1031.32",
"5.0.0-1033.34",
"5.0.0-1034.35"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-1190-gcp",
"binary_version": "4.15.0-1190.207"
},
{
"binary_name": "linux-gcp-4.15-headers-4.15.0-1190",
"binary_version": "4.15.0-1190.207"
},
{
"binary_name": "linux-gcp-4.15-tools-4.15.0-1190",
"binary_version": "4.15.0-1190.207"
},
{
"binary_name": "linux-headers-4.15.0-1190-gcp",
"binary_version": "4.15.0-1190.207"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1190-gcp",
"binary_version": "4.15.0-1190.207"
},
{
"binary_name": "linux-modules-4.15.0-1190-gcp",
"binary_version": "4.15.0-1190.207"
},
{
"binary_name": "linux-modules-extra-4.15.0-1190-gcp",
"binary_version": "4.15.0-1190.207"
},
{
"binary_name": "linux-tools-4.15.0-1190-gcp",
"binary_version": "4.15.0-1190.207"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "linux-gcp-4.15",
"purl": "pkg:deb/ubuntu/linux-gcp-4.15@4.15.0-1190.207?arch=source\u0026distro=esm-infra/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1071.81",
"4.15.0-1077.87",
"4.15.0-1078.88",
"4.15.0-1080.90",
"4.15.0-1081.92",
"4.15.0-1083.94",
"4.15.0-1084.95",
"4.15.0-1086.98",
"4.15.0-1087.100",
"4.15.0-1088.101",
"4.15.0-1090.103",
"4.15.0-1091.104",
"4.15.0-1092.105",
"4.15.0-1093.106",
"4.15.0-1094.107",
"4.15.0-1095.108",
"4.15.0-1096.109",
"4.15.0-1097.110",
"4.15.0-1098.111",
"4.15.0-1099.112",
"4.15.0-1100.113",
"4.15.0-1103.116",
"4.15.0-1106.120",
"4.15.0-1107.121",
"4.15.0-1108.122",
"4.15.0-1109.123",
"4.15.0-1110.124",
"4.15.0-1111.125",
"4.15.0-1112.126",
"4.15.0-1114.128",
"4.15.0-1115.129",
"4.15.0-1116.130",
"4.15.0-1118.132",
"4.15.0-1119.133",
"4.15.0-1120.134",
"4.15.0-1121.135",
"4.15.0-1122.136",
"4.15.0-1124.138",
"4.15.0-1127.142",
"4.15.0-1130.146",
"4.15.0-1131.147",
"4.15.0-1134.150",
"4.15.0-1135.151",
"4.15.0-1136.152",
"4.15.0-1137.153",
"4.15.0-1138.154",
"4.15.0-1141.157",
"4.15.0-1142.158",
"4.15.0-1143.159",
"4.15.0-1145.161",
"4.15.0-1146.162",
"4.15.0-1147.163",
"4.15.0-1148.164",
"4.15.0-1149.165",
"4.15.0-1150.166",
"4.15.0-1151.167",
"4.15.0-1152.168",
"4.15.0-1153.170",
"4.15.0-1154.171",
"4.15.0-1155.172",
"4.15.0-1156.173",
"4.15.0-1157.174",
"4.15.0-1158.175",
"4.15.0-1159.176",
"4.15.0-1160.177",
"4.15.0-1161.178",
"4.15.0-1162.179",
"4.15.0-1163.180",
"4.15.0-1164.181",
"4.15.0-1165.182",
"4.15.0-1166.183",
"4.15.0-1167.184",
"4.15.0-1168.185",
"4.15.0-1169.186",
"4.15.0-1170.187",
"4.15.0-1171.188",
"4.15.0-1172.189",
"4.15.0-1173.190",
"4.15.0-1174.191",
"4.15.0-1175.192",
"4.15.0-1176.193",
"4.15.0-1177.194",
"4.15.0-1178.195",
"4.15.0-1179.196",
"4.15.0-1180.197",
"4.15.0-1181.198",
"4.15.0-1182.199",
"4.15.0-1183.200",
"4.15.0-1184.201",
"4.15.0-1185.202",
"4.15.0-1186.203",
"4.15.0-1187.204",
"4.15.0-1188.205",
"4.15.0-1189.206",
"4.15.0-1190.207"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.3.0-1032-gcp",
"binary_version": "5.3.0-1032.34~18.04.1"
},
{
"binary_name": "linux-gcp-5.3-headers-5.3.0-1032",
"binary_version": "5.3.0-1032.34~18.04.1"
},
{
"binary_name": "linux-gcp-5.3-tools-5.3.0-1032",
"binary_version": "5.3.0-1032.34~18.04.1"
},
{
"binary_name": "linux-headers-5.3.0-1032-gcp",
"binary_version": "5.3.0-1032.34~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.3.0-1032-gcp",
"binary_version": "5.3.0-1032.34~18.04.1"
},
{
"binary_name": "linux-modules-5.3.0-1032-gcp",
"binary_version": "5.3.0-1032.34~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.3.0-1032-gcp",
"binary_version": "5.3.0-1032.34~18.04.1"
},
{
"binary_name": "linux-tools-5.3.0-1032-gcp",
"binary_version": "5.3.0-1032.34~18.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-gcp-5.3",
"purl": "pkg:deb/ubuntu/linux-gcp-5.3@5.3.0-1032.34~18.04.1?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.3.0-1008.9~18.04.1",
"5.3.0-1009.10~18.04.1",
"5.3.0-1010.11~18.04.1",
"5.3.0-1012.13~18.04.1",
"5.3.0-1014.15~18.04.1",
"5.3.0-1016.17~18.04.1",
"5.3.0-1017.18~18.04.1",
"5.3.0-1018.19~18.04.1",
"5.3.0-1020.22~18.04.1",
"5.3.0-1026.28~18.04.1",
"5.3.0-1029.31~18.04.1",
"5.3.0-1030.32~18.04.1",
"5.3.0-1032.34~18.04.1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1139-gcp",
"binary_version": "5.4.0-1139.148~18.04.1"
},
{
"binary_name": "linux-gcp-5.4-headers-5.4.0-1139",
"binary_version": "5.4.0-1139.148~18.04.1"
},
{
"binary_name": "linux-gcp-5.4-tools-5.4.0-1139",
"binary_version": "5.4.0-1139.148~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-1139-gcp",
"binary_version": "5.4.0-1139.148~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1139-gcp",
"binary_version": "5.4.0-1139.148~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-1139-gcp",
"binary_version": "5.4.0-1139.148~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1139-gcp",
"binary_version": "5.4.0-1139.148~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-1139-gcp",
"binary_version": "5.4.0-1139.148~18.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "linux-gcp-5.4",
"purl": "pkg:deb/ubuntu/linux-gcp-5.4@5.4.0-1139.148~18.04.1?arch=source\u0026distro=esm-infra/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1139.148~18.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1019.19~18.04.2",
"5.4.0-1021.21~18.04.1",
"5.4.0-1022.22~18.04.1",
"5.4.0-1024.24~18.04.1",
"5.4.0-1025.25~18.04.1",
"5.4.0-1028.29~18.04.1",
"5.4.0-1029.31~18.04.1",
"5.4.0-1030.32~18.04.1",
"5.4.0-1032.34~18.04.1",
"5.4.0-1033.35~18.04.1",
"5.4.0-1034.37~18.04.1",
"5.4.0-1036.39~18.04.1",
"5.4.0-1037.40~18.04.1",
"5.4.0-1038.41~18.04.1",
"5.4.0-1040.43~18.04.1",
"5.4.0-1041.44~18.04.1",
"5.4.0-1042.45~18.04.1",
"5.4.0-1043.46~18.04.1",
"5.4.0-1044.47~18.04.2",
"5.4.0-1046.49~18.04.1",
"5.4.0-1049.53~18.04.1",
"5.4.0-1051.55~18.04.1",
"5.4.0-1052.56~18.04.1",
"5.4.0-1053.57~18.04.1",
"5.4.0-1055.59~18.04.1",
"5.4.0-1056.60~18.04.1",
"5.4.0-1057.61~18.04.1",
"5.4.0-1058.62~18.04.1",
"5.4.0-1059.63~18.04.1",
"5.4.0-1060.64~18.04.1",
"5.4.0-1062.66~18.04.1",
"5.4.0-1063.67~18.04.1",
"5.4.0-1064.68~18.04.1",
"5.4.0-1065.69~18.04.1",
"5.4.0-1067.71~18.04.1",
"5.4.0-1068.72~18.04.1",
"5.4.0-1069.73~18.04.1",
"5.4.0-1072.77~18.04.1",
"5.4.0-1073.78~18.04.1",
"5.4.0-1075.80~18.04.1",
"5.4.0-1078.84~18.04.1",
"5.4.0-1080.87~18.04.1",
"5.4.0-1083.91~18.04.1",
"5.4.0-1084.92~18.04.1",
"5.4.0-1086.94~18.04.1",
"5.4.0-1087.95~18.04.1",
"5.4.0-1089.97~18.04.1",
"5.4.0-1092.101~18.04.1",
"5.4.0-1093.102~18.04.1",
"5.4.0-1096.105~18.04.2",
"5.4.0-1097.106~18.04.1",
"5.4.0-1098.107~18.04.1",
"5.4.0-1100.109~18.04.1",
"5.4.0-1101.110~18.04.1",
"5.4.0-1102.111~18.04.2",
"5.4.0-1103.112~18.04.1",
"5.4.0-1104.113~18.04.1",
"5.4.0-1105.114~18.04.1",
"5.4.0-1106.115~18.04.1",
"5.4.0-1107.116~18.04.1",
"5.4.0-1108.117~18.04.1",
"5.4.0-1109.118~18.04.1",
"5.4.0-1110.119~18.04.1",
"5.4.0-1111.120~18.04.1",
"5.4.0-1112.121~18.04.1",
"5.4.0-1113.122~18.04.1",
"5.4.0-1115.124~18.04.1",
"5.4.0-1116.125~18.04.1",
"5.4.0-1117.126~18.04.1",
"5.4.0-1118.127~18.04.1",
"5.4.0-1120.129~18.04.1",
"5.4.0-1121.130~18.04.1",
"5.4.0-1122.131~18.04.1",
"5.4.0-1123.132~18.04.1",
"5.4.0-1124.133~18.04.1",
"5.4.0-1125.134~18.04.1",
"5.4.0-1126.135~18.04.1",
"5.4.0-1127.136~18.04.1",
"5.4.0-1128.137~18.04.1",
"5.4.0-1129.138~18.04.1",
"5.4.0-1130.139~18.04.1",
"5.4.0-1132.141~18.04.1",
"5.4.0-1133.142~18.04.1",
"5.4.0-1134.143~18.04.1",
"5.4.0-1135.144~18.04.1",
"5.4.0-1136.145~18.04.1",
"5.4.0-1137.146~18.04.1",
"5.4.0-1138.147~18.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-1079-gke",
"binary_version": "4.15.0-1079.84"
},
{
"binary_name": "linux-gke-4.15-headers-4.15.0-1079",
"binary_version": "4.15.0-1079.84"
},
{
"binary_name": "linux-gke-4.15-tools-4.15.0-1079",
"binary_version": "4.15.0-1079.84"
},
{
"binary_name": "linux-headers-4.15.0-1079-gke",
"binary_version": "4.15.0-1079.84"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1079-gke",
"binary_version": "4.15.0-1079.84"
},
{
"binary_name": "linux-modules-4.15.0-1079-gke",
"binary_version": "4.15.0-1079.84"
},
{
"binary_name": "linux-modules-extra-4.15.0-1079-gke",
"binary_version": "4.15.0-1079.84"
},
{
"binary_name": "linux-tools-4.15.0-1079-gke",
"binary_version": "4.15.0-1079.84"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-gke-4.15",
"purl": "pkg:deb/ubuntu/linux-gke-4.15@4.15.0-1079.84?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1030.32",
"4.15.0-1032.34",
"4.15.0-1033.35",
"4.15.0-1034.36",
"4.15.0-1036.38",
"4.15.0-1037.39",
"4.15.0-1040.42",
"4.15.0-1041.43",
"4.15.0-1042.44",
"4.15.0-1044.46",
"4.15.0-1045.48",
"4.15.0-1046.49",
"4.15.0-1048.51",
"4.15.0-1049.52",
"4.15.0-1050.53",
"4.15.0-1052.55",
"4.15.0-1055.58",
"4.15.0-1057.60",
"4.15.0-1058.61",
"4.15.0-1059.62",
"4.15.0-1063.66",
"4.15.0-1064.67",
"4.15.0-1066.69",
"4.15.0-1067.70",
"4.15.0-1069.72",
"4.15.0-1070.73",
"4.15.0-1072.76",
"4.15.0-1073.78",
"4.15.0-1074.79",
"4.15.0-1076.81",
"4.15.0-1077.82",
"4.15.0-1078.83",
"4.15.0-1079.84"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1080-gke",
"binary_version": "5.4.0-1080.86~18.04.1"
},
{
"binary_name": "linux-gke-5.4-headers-5.4.0-1080",
"binary_version": "5.4.0-1080.86~18.04.1"
},
{
"binary_name": "linux-gke-5.4-tools-5.4.0-1080",
"binary_version": "5.4.0-1080.86~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-1080-gke",
"binary_version": "5.4.0-1080.86~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1080-gke",
"binary_version": "5.4.0-1080.86~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-1080-gke",
"binary_version": "5.4.0-1080.86~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1080-gke",
"binary_version": "5.4.0-1080.86~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-1080-gke",
"binary_version": "5.4.0-1080.86~18.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-gke-5.4",
"purl": "pkg:deb/ubuntu/linux-gke-5.4@5.4.0-1080.86~18.04.1?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1025.25~18.04.1",
"5.4.0-1027.28~18.04.1",
"5.4.0-1029.31~18.04.1",
"5.4.0-1030.32~18.04.1",
"5.4.0-1032.34~18.04.1",
"5.4.0-1033.35~18.04.1",
"5.4.0-1035.37~18.04.1",
"5.4.0-1036.38~18.04.1",
"5.4.0-1037.39~18.04.1",
"5.4.0-1039.41~18.04.1",
"5.4.0-1040.42~18.04.1",
"5.4.0-1042.44~18.04.1",
"5.4.0-1043.45~18.04.1",
"5.4.0-1044.46~18.04.1",
"5.4.0-1046.48~18.04.1",
"5.4.0-1049.52~18.04.1",
"5.4.0-1051.54~18.04.1",
"5.4.0-1052.55~18.04.1",
"5.4.0-1053.56~18.04.1",
"5.4.0-1054.57~18.04.1",
"5.4.0-1055.58~18.04.1",
"5.4.0-1056.59~18.04.1",
"5.4.0-1057.60~18.04.1",
"5.4.0-1059.62~18.04.1",
"5.4.0-1061.64~18.04.1",
"5.4.0-1062.65~18.04.1",
"5.4.0-1063.66~18.04.1",
"5.4.0-1065.68~18.04.1",
"5.4.0-1066.69~18.04.1",
"5.4.0-1067.70~18.04.1",
"5.4.0-1068.71~18.04.1",
"5.4.0-1071.76~18.04.3",
"5.4.0-1072.77~18.04.1",
"5.4.0-1074.79~18.04.1",
"5.4.0-1076.82~18.04.1",
"5.4.0-1078.84~18.04.1",
"5.4.0-1080.86~18.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1051-gkeop",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-cloud-tools-5.4.0-1051-gkeop",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-gkeop-5.4-cloud-tools-5.4.0-1051",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-gkeop-5.4-headers-5.4.0-1051",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-gkeop-5.4-source-5.4.0",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-gkeop-5.4-tools-5.4.0-1051",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-1051-gkeop",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1051-gkeop",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-1051-gkeop",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1051-gkeop",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-1051-gkeop",
"binary_version": "5.4.0-1051.54~18.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-gkeop-5.4",
"purl": "pkg:deb/ubuntu/linux-gkeop-5.4@5.4.0-1051.54~18.04.1?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1001.1",
"5.4.0-1003.3",
"5.4.0-1004.5",
"5.4.0-1005.6",
"5.4.0-1007.8~18.04.1",
"5.4.0-1008.9~18.04.1",
"5.4.0-1009.10~18.04.1",
"5.4.0-1010.11~18.04.1",
"5.4.0-1011.12~18.04.2",
"5.4.0-1012.13~18.04.1",
"5.4.0-1013.14~18.04.1",
"5.4.0-1014.15~18.04.1",
"5.4.0-1015.16~18.04.1",
"5.4.0-1016.17~18.04.1",
"5.4.0-1018.19~18.04.1",
"5.4.0-1021.22~18.04.1",
"5.4.0-1022.23~18.04.1",
"5.4.0-1023.24~18.04.1",
"5.4.0-1024.25~18.04.1",
"5.4.0-1025.26~18.04.1",
"5.4.0-1026.27~18.04.1",
"5.4.0-1027.28~18.04.1",
"5.4.0-1029.30~18.04.2",
"5.4.0-1031.32~18.04.1",
"5.4.0-1032.33~18.04.1",
"5.4.0-1033.34~18.04.1",
"5.4.0-1034.35~18.04.1",
"5.4.0-1036.37~18.04.1",
"5.4.0-1037.38~18.04.1",
"5.4.0-1038.39~18.04.1",
"5.4.0-1039.40~18.04.1",
"5.4.0-1040.41~18.04.1",
"5.4.0-1043.44~18.04.1",
"5.4.0-1046.48~18.04.1",
"5.4.0-1048.51~18.04.1",
"5.4.0-1049.52~18.04.1",
"5.4.0-1051.54~18.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "block-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "crypto-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "fat-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "fb-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "firewire-core-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "floppy-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "fs-core-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "fs-secondary-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "input-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "ipmi-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "kernel-image-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-buildinfo-5.3.0-76-generic",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-buildinfo-5.3.0-76-lowlatency",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-cloud-tools-5.3.0-76-generic",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-cloud-tools-5.3.0-76-lowlatency",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-headers-5.3.0-76-generic",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-headers-5.3.0-76-lowlatency",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-hwe-cloud-tools-5.3.0-76",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-hwe-headers-5.3.0-76",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-hwe-tools-5.3.0-76",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-hwe-udebs-generic",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-image-5.3.0-76-generic",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-image-5.3.0-76-lowlatency",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-image-unsigned-5.3.0-76-generic",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-image-unsigned-5.3.0-76-lowlatency",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-modules-5.3.0-76-generic",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-modules-5.3.0-76-lowlatency",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-modules-extra-5.3.0-76-generic",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-source-5.3.0",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-tools-5.3.0-76-generic",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-tools-5.3.0-76-lowlatency",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "md-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "message-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "mouse-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "multipath-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "nfs-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "nic-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "nic-pcmcia-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "nic-shared-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "nic-usb-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "parport-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "pata-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "pcmcia-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "pcmcia-storage-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "plip-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "ppp-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "sata-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "scsi-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "serial-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "storage-core-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "usb-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "virtio-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "vlan-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-hwe",
"purl": "pkg:deb/ubuntu/linux-hwe@5.3.0-76.72?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.18.0-13.14~18.04.1",
"4.18.0-14.15~18.04.1",
"4.18.0-15.16~18.04.1",
"4.18.0-16.17~18.04.1",
"4.18.0-17.18~18.04.1",
"4.18.0-18.19~18.04.1",
"4.18.0-20.21~18.04.1",
"4.18.0-21.22~18.04.1",
"4.18.0-22.23~18.04.1",
"4.18.0-24.25~18.04.1",
"4.18.0-25.26~18.04.1",
"5.0.0-23.24~18.04.1",
"5.0.0-25.26~18.04.1",
"5.0.0-27.28~18.04.1",
"5.0.0-29.31~18.04.1",
"5.0.0-31.33~18.04.1",
"5.0.0-32.34~18.04.2",
"5.0.0-35.38~18.04.1",
"5.0.0-36.39~18.04.1",
"5.0.0-37.40~18.04.1",
"5.3.0-26.28~18.04.1",
"5.3.0-28.30~18.04.1",
"5.3.0-40.32~18.04.1",
"5.3.0-42.34~18.04.1",
"5.3.0-45.37~18.04.1",
"5.3.0-46.38~18.04.1",
"5.3.0-51.44~18.04.2",
"5.3.0-53.47~18.04.1",
"5.3.0-59.53~18.04.1",
"5.3.0-61.55~18.04.1",
"5.3.0-62.56~18.04.1",
"5.3.0-64.58~18.04.1",
"5.3.0-65.59",
"5.3.0-66.60",
"5.3.0-67.61",
"5.3.0-68.63",
"5.3.0-69.65",
"5.3.0-70.66",
"5.3.0-72.68",
"5.3.0-73.69",
"5.3.0-74.70",
"5.3.0-75.71",
"5.3.0-76.72"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "block-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "crypto-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "dasd-extra-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "dasd-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "fat-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "fb-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "firewire-core-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "floppy-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "fs-core-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "fs-secondary-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "input-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "ipmi-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "kernel-image-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-buildinfo-5.4.0-200-generic",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-buildinfo-5.4.0-200-lowlatency",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-cloud-tools-5.4.0-200-generic",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-cloud-tools-5.4.0-200-lowlatency",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-200-generic",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-200-lowlatency",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-hwe-5.4-cloud-tools-5.4.0-200",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-hwe-5.4-cloud-tools-common",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-hwe-5.4-headers-5.4.0-200",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-hwe-5.4-source-5.4.0",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-hwe-5.4-tools-5.4.0-200",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-hwe-5.4-tools-common",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-hwe-5.4-udebs-generic",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-200-generic",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-200-lowlatency",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-200-generic",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-200-lowlatency",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.4.0-200-generic",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-200-generic",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-200-lowlatency",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "md-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "message-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "mouse-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "multipath-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "nfs-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "nic-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "nic-pcmcia-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "nic-shared-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "nic-usb-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "parport-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "pata-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "pcmcia-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "pcmcia-storage-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "plip-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "ppp-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "sata-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "scsi-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "serial-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "storage-core-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "usb-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "virtio-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
},
{
"binary_name": "vlan-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220~18.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "linux-hwe-5.4",
"purl": "pkg:deb/ubuntu/linux-hwe-5.4@5.4.0-200.220~18.04.1?arch=source\u0026distro=esm-infra/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-200.220~18.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-37.41~18.04.1",
"5.4.0-39.43~18.04.1",
"5.4.0-40.44~18.04.1",
"5.4.0-42.46~18.04.1",
"5.4.0-45.49~18.04.2",
"5.4.0-47.51~18.04.1",
"5.4.0-48.52~18.04.1",
"5.4.0-51.56~18.04.1",
"5.4.0-52.57~18.04.1",
"5.4.0-53.59~18.04.1",
"5.4.0-54.60~18.04.1",
"5.4.0-56.62~18.04.1",
"5.4.0-58.64~18.04.1",
"5.4.0-59.65~18.04.1",
"5.4.0-60.67~18.04.1",
"5.4.0-62.70~18.04.1",
"5.4.0-64.72~18.04.1",
"5.4.0-65.73~18.04.1",
"5.4.0-66.74~18.04.2",
"5.4.0-67.75~18.04.1",
"5.4.0-70.78~18.04.1",
"5.4.0-71.79~18.04.1",
"5.4.0-72.80~18.04.1",
"5.4.0-73.82~18.04.1",
"5.4.0-74.83~18.04.1",
"5.4.0-77.86~18.04.1",
"5.4.0-80.90~18.04.1",
"5.4.0-81.91~18.04.1",
"5.4.0-84.94~18.04.1",
"5.4.0-86.97~18.04.1",
"5.4.0-87.98~18.04.1",
"5.4.0-89.100~18.04.1",
"5.4.0-90.101~18.04.1",
"5.4.0-91.102~18.04.1",
"5.4.0-92.103~18.04.2",
"5.4.0-94.106~18.04.1",
"5.4.0-96.109~18.04.1",
"5.4.0-97.110~18.04.1",
"5.4.0-99.112~18.04.1",
"5.4.0-100.113~18.04.1",
"5.4.0-104.118~18.04.1",
"5.4.0-105.119~18.04.1",
"5.4.0-107.121~18.04.1",
"5.4.0-109.123~18.04.1",
"5.4.0-110.124~18.04.1",
"5.4.0-113.127~18.04.1",
"5.4.0-117.132~18.04.1",
"5.4.0-120.136~18.04.1",
"5.4.0-121.137~18.04.1",
"5.4.0-122.138~18.04.1",
"5.4.0-124.140~18.04.1",
"5.4.0-125.141~18.04.1",
"5.4.0-126.142~18.04.1",
"5.4.0-128.144~18.04.1",
"5.4.0-131.147~18.04.1",
"5.4.0-132.148~18.04.1",
"5.4.0-133.149~18.04.1",
"5.4.0-135.152~18.04.2",
"5.4.0-136.153~18.04.1",
"5.4.0-137.154~18.04.1",
"5.4.0-139.156~18.04.1",
"5.4.0-144.161~18.04.1",
"5.4.0-146.163~18.04.1",
"5.4.0-147.164~18.04.1",
"5.4.0-148.165~18.04.1",
"5.4.0-149.166~18.04.1",
"5.4.0-150.167~18.04.1",
"5.4.0-152.169~18.04.1",
"5.4.0-153.170~18.04.1",
"5.4.0-155.172~18.04.1",
"5.4.0-156.173~18.04.1",
"5.4.0-159.176~18.04.1",
"5.4.0-162.179~18.04.1",
"5.4.0-163.180~18.04.1",
"5.4.0-164.181~18.04.1",
"5.4.0-165.182~18.04.1",
"5.4.0-166.183~18.04.2",
"5.4.0-167.184~18.04.1",
"5.4.0-169.187~18.04.1",
"5.4.0-170.188~18.04.1",
"5.4.0-171.189~18.04.1",
"5.4.0-172.190~18.04.1",
"5.4.0-173.191~18.04.1",
"5.4.0-174.193~18.04.1",
"5.4.0-175.195~18.04.1",
"5.4.0-177.197~18.04.1",
"5.4.0-181.201~18.04.1",
"5.4.0-182.202~18.04.1",
"5.4.0-186.206~18.04.1",
"5.4.0-187.207~18.04.1",
"5.4.0-189.209~18.04.1",
"5.4.0-190.210~18.04.1",
"5.4.0-192.212~18.04.1",
"5.4.0-193.213~18.04.1",
"5.4.0-195.215~18.04.1",
"5.4.0-196.216~18.04.1",
"5.4.0-198.218~18.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "block-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "block-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "crypto-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "crypto-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "dasd-extra-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "dasd-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "fat-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "fat-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "fb-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "firewire-core-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "floppy-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "fs-core-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "fs-core-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "fs-secondary-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "fs-secondary-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "input-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "input-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "ipmi-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "ipmi-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "kernel-image-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "kernel-image-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-buildinfo-5.3.0-24-generic",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-buildinfo-5.3.0-24-generic-lpae",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-buildinfo-5.3.0-24-lowlatency",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-cloud-tools-5.3.0-24-generic",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-cloud-tools-5.3.0-24-lowlatency",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-headers-5.3.0-24",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-headers-5.3.0-24-generic",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-headers-5.3.0-24-generic-lpae",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-headers-5.3.0-24-lowlatency",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-hwe-edge-cloud-tools-5.3.0-24",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-hwe-edge-tools-5.3.0-24",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-hwe-edge-udebs-generic",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-hwe-edge-udebs-generic-lpae",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-image-5.3.0-24-generic",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-image-5.3.0-24-generic-lpae",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-image-5.3.0-24-lowlatency",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-image-unsigned-5.3.0-24-generic",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-image-unsigned-5.3.0-24-lowlatency",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-modules-5.3.0-24-generic",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-modules-5.3.0-24-generic-lpae",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-modules-5.3.0-24-lowlatency",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-modules-extra-5.3.0-24-generic",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-source-5.3.0",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-tools-5.3.0-24-generic",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-tools-5.3.0-24-generic-lpae",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-tools-5.3.0-24-lowlatency",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "md-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "md-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "message-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "mouse-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "mouse-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "multipath-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "multipath-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "nfs-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "nfs-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "nic-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "nic-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "nic-pcmcia-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "nic-shared-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "nic-shared-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "nic-usb-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "nic-usb-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "parport-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "parport-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "pata-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "pcmcia-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "pcmcia-storage-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "plip-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "plip-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "ppp-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "ppp-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "sata-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "sata-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "scsi-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "scsi-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "serial-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "storage-core-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "storage-core-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "usb-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "usb-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "virtio-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "vlan-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "vlan-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-hwe-edge",
"purl": "pkg:deb/ubuntu/linux-hwe-edge@5.3.0-24.26~18.04.2?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.0.0-15.16~18.04.1",
"5.0.0-16.17~18.04.1",
"5.0.0-17.18~18.04.1",
"5.0.0-19.20~18.04.1",
"5.0.0-20.21~18.04.1",
"5.3.0-19.20~18.04.2",
"5.3.0-22.24~18.04.1",
"5.3.0-23.25~18.04.1",
"5.3.0-23.25~18.04.2",
"5.3.0-24.26~18.04.2"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1082-ibm",
"binary_version": "5.4.0-1082.87~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-1082-ibm",
"binary_version": "5.4.0-1082.87~18.04.1"
},
{
"binary_name": "linux-ibm-5.4-cloud-tools-common",
"binary_version": "5.4.0-1082.87~18.04.1"
},
{
"binary_name": "linux-ibm-5.4-headers-5.4.0-1082",
"binary_version": "5.4.0-1082.87~18.04.1"
},
{
"binary_name": "linux-ibm-5.4-source-5.4.0",
"binary_version": "5.4.0-1082.87~18.04.1"
},
{
"binary_name": "linux-ibm-5.4-tools-5.4.0-1082",
"binary_version": "5.4.0-1082.87~18.04.1"
},
{
"binary_name": "linux-ibm-5.4-tools-common",
"binary_version": "5.4.0-1082.87~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1082-ibm",
"binary_version": "5.4.0-1082.87~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-1082-ibm",
"binary_version": "5.4.0-1082.87~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1082-ibm",
"binary_version": "5.4.0-1082.87~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-1082-ibm",
"binary_version": "5.4.0-1082.87~18.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "linux-ibm-5.4",
"purl": "pkg:deb/ubuntu/linux-ibm-5.4@5.4.0-1082.87~18.04.1?arch=source\u0026distro=esm-infra/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1082.87~18.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1010.11~18.04.2",
"5.4.0-1012.13~18.04.1",
"5.4.0-1014.15~18.04.1",
"5.4.0-1015.16~18.04.1",
"5.4.0-1017.19~18.04.1",
"5.4.0-1018.20~18.04.1",
"5.4.0-1019.21~18.04.1",
"5.4.0-1020.22~18.04.1",
"5.4.0-1021.23~18.04.1",
"5.4.0-1023.25~18.04.1",
"5.4.0-1026.29~18.04.1",
"5.4.0-1028.32~18.04.1",
"5.4.0-1029.33~18.04.1",
"5.4.0-1031.35~18.04.1",
"5.4.0-1032.36~18.04.1",
"5.4.0-1033.37~18.04.1",
"5.4.0-1034.38~18.04.1",
"5.4.0-1036.41~18.04.1",
"5.4.0-1037.42~18.04.1",
"5.4.0-1040.45~18.04.2",
"5.4.0-1041.46~18.04.1",
"5.4.0-1042.47~18.04.1",
"5.4.0-1044.49~18.04.1",
"5.4.0-1045.50~18.04.1",
"5.4.0-1046.51~18.04.1",
"5.4.0-1047.52~18.04.1",
"5.4.0-1048.53~18.04.1",
"5.4.0-1049.54~18.04.1",
"5.4.0-1050.55~18.04.1",
"5.4.0-1051.56~18.04.1",
"5.4.0-1052.57~18.04.1",
"5.4.0-1053.58~18.04.1",
"5.4.0-1054.59~18.04.1",
"5.4.0-1056.61~18.04.1",
"5.4.0-1057.62~18.04.1",
"5.4.0-1058.63~18.04.1",
"5.4.0-1059.64~18.04.1",
"5.4.0-1060.65~18.04.1",
"5.4.0-1061.66~18.04.1",
"5.4.0-1063.68~18.04.1",
"5.4.0-1064.69~18.04.1",
"5.4.0-1065.70~18.04.1",
"5.4.0-1066.71~18.04.1",
"5.4.0-1067.72~18.04.1",
"5.4.0-1068.73~18.04.1",
"5.4.0-1069.74~18.04.1",
"5.4.0-1070.75~18.04.1",
"5.4.0-1071.76~18.04.1",
"5.4.0-1072.77~18.04.1",
"5.4.0-1073.78~18.04.1",
"5.4.0-1074.79~18.04.1",
"5.4.0-1075.80~18.04.1",
"5.4.0-1076.81~18.04.1",
"5.4.0-1077.82~18.04.1",
"5.4.0-1078.83~18.04.1",
"5.4.0-1079.84~18.04.1",
"5.4.0-1080.85~18.04.1",
"5.4.0-1081.86~18.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-1179-kvm",
"binary_version": "4.15.0-1179.184"
},
{
"binary_name": "linux-headers-4.15.0-1179-kvm",
"binary_version": "4.15.0-1179.184"
},
{
"binary_name": "linux-image-4.15.0-1179-kvm",
"binary_version": "4.15.0-1179.184"
},
{
"binary_name": "linux-kvm-headers-4.15.0-1179",
"binary_version": "4.15.0-1179.184"
},
{
"binary_name": "linux-kvm-tools-4.15.0-1179",
"binary_version": "4.15.0-1179.184"
},
{
"binary_name": "linux-modules-4.15.0-1179-kvm",
"binary_version": "4.15.0-1179.184"
},
{
"binary_name": "linux-tools-4.15.0-1179-kvm",
"binary_version": "4.15.0-1179.184"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "linux-kvm",
"purl": "pkg:deb/ubuntu/linux-kvm@4.15.0-1179.184?arch=source\u0026distro=esm-infra/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-1006.6",
"4.15.0-1008.8",
"4.15.0-1010.10",
"4.15.0-1011.11",
"4.15.0-1012.12",
"4.15.0-1016.16",
"4.15.0-1017.17",
"4.15.0-1019.19",
"4.15.0-1020.20",
"4.15.0-1021.21",
"4.15.0-1023.23",
"4.15.0-1025.25",
"4.15.0-1026.26",
"4.15.0-1027.27",
"4.15.0-1028.28",
"4.15.0-1029.29",
"4.15.0-1030.30",
"4.15.0-1031.31",
"4.15.0-1032.32",
"4.15.0-1034.34",
"4.15.0-1035.35",
"4.15.0-1036.36",
"4.15.0-1038.38",
"4.15.0-1039.39",
"4.15.0-1042.42",
"4.15.0-1043.43",
"4.15.0-1044.44",
"4.15.0-1046.46",
"4.15.0-1047.47",
"4.15.0-1048.48",
"4.15.0-1050.50",
"4.15.0-1051.51",
"4.15.0-1052.52",
"4.15.0-1053.53",
"4.15.0-1056.57",
"4.15.0-1058.59",
"4.15.0-1059.60",
"4.15.0-1060.61",
"4.15.0-1067.68",
"4.15.0-1069.70",
"4.15.0-1071.72",
"4.15.0-1072.73",
"4.15.0-1074.75",
"4.15.0-1075.76",
"4.15.0-1077.79",
"4.15.0-1079.81",
"4.15.0-1081.83",
"4.15.0-1082.84",
"4.15.0-1084.86",
"4.15.0-1085.87",
"4.15.0-1086.88",
"4.15.0-1087.89",
"4.15.0-1088.90",
"4.15.0-1089.91",
"4.15.0-1090.92",
"4.15.0-1091.93",
"4.15.0-1092.94",
"4.15.0-1094.96",
"4.15.0-1097.99",
"4.15.0-1098.100",
"4.15.0-1099.101",
"4.15.0-1100.102",
"4.15.0-1101.103",
"4.15.0-1102.104",
"4.15.0-1103.105",
"4.15.0-1105.107",
"4.15.0-1106.108",
"4.15.0-1107.109",
"4.15.0-1109.112",
"4.15.0-1110.113",
"4.15.0-1112.115",
"4.15.0-1113.116",
"4.15.0-1114.117",
"4.15.0-1116.119",
"4.15.0-1119.123",
"4.15.0-1122.127",
"4.15.0-1123.128",
"4.15.0-1125.130",
"4.15.0-1126.131",
"4.15.0-1127.132",
"4.15.0-1128.133",
"4.15.0-1129.134",
"4.15.0-1132.137",
"4.15.0-1133.138",
"4.15.0-1134.139",
"4.15.0-1135.140",
"4.15.0-1136.141",
"4.15.0-1137.142",
"4.15.0-1138.143",
"4.15.0-1139.144",
"4.15.0-1140.145",
"4.15.0-1141.146",
"4.15.0-1142.147",
"4.15.0-1143.148",
"4.15.0-1144.149",
"4.15.0-1145.150",
"4.15.0-1146.151",
"4.15.0-1147.152",
"4.15.0-1148.153",
"4.15.0-1149.154",
"4.15.0-1150.155",
"4.15.0-1151.156",
"4.15.0-1152.157",
"4.15.0-1153.158",
"4.15.0-1154.159",
"4.15.0-1155.160",
"4.15.0-1156.161",
"4.15.0-1157.162",
"4.15.0-1158.163",
"4.15.0-1159.164",
"4.15.0-1160.165",
"4.15.0-1161.166",
"4.15.0-1162.167",
"4.15.0-1163.168",
"4.15.0-1164.169",
"4.15.0-1165.170",
"4.15.0-1166.171",
"4.15.0-1167.172",
"4.15.0-1168.173",
"4.15.0-1169.174",
"4.15.0-1170.175",
"4.15.0-1171.176",
"4.15.0-1172.177",
"4.15.0-1173.178",
"4.15.0-1174.179",
"4.15.0-1175.180",
"4.15.0-1176.181",
"4.15.0-1177.182",
"4.15.0-1178.183",
"4.15.0-1179.184"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "block-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "crypto-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "fat-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "fb-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "firewire-core-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "floppy-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "fs-core-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "fs-secondary-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "input-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "ipmi-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "irda-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "kernel-image-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "linux-buildinfo-4.15.0-1103-oem",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "linux-headers-4.15.0-1103-oem",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1103-oem",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "linux-modules-4.15.0-1103-oem",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "linux-oem-headers-4.15.0-1103",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "linux-oem-tools-4.15.0-1103",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "linux-tools-4.15.0-1103-oem",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "linux-udebs-oem",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "md-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "message-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "mouse-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "multipath-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "nfs-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "nic-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "nic-pcmcia-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "nic-shared-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "nic-usb-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "parport-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "pata-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "pcmcia-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "pcmcia-storage-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "plip-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "ppp-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "sata-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "scsi-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "serial-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "storage-core-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "usb-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "virtio-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "vlan-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-oem",
"purl": "pkg:deb/ubuntu/linux-oem@4.15.0-1103.114?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1002.3",
"4.15.0-1004.5",
"4.15.0-1006.9",
"4.15.0-1008.11",
"4.15.0-1009.12",
"4.15.0-1012.15",
"4.15.0-1013.16",
"4.15.0-1015.18",
"4.15.0-1017.20",
"4.15.0-1018.21",
"4.15.0-1021.24",
"4.15.0-1024.29",
"4.15.0-1026.31",
"4.15.0-1028.33",
"4.15.0-1030.35",
"4.15.0-1033.38",
"4.15.0-1034.39",
"4.15.0-1035.40",
"4.15.0-1036.41",
"4.15.0-1038.43",
"4.15.0-1039.44",
"4.15.0-1043.48",
"4.15.0-1045.50",
"4.15.0-1050.57",
"4.15.0-1056.65",
"4.15.0-1057.66",
"4.15.0-1059.68",
"4.15.0-1063.72",
"4.15.0-1064.73",
"4.15.0-1065.75",
"4.15.0-1066.76",
"4.15.0-1067.77",
"4.15.0-1069.79",
"4.15.0-1073.83",
"4.15.0-1076.86",
"4.15.0-1079.89",
"4.15.0-1080.90",
"4.15.0-1081.91",
"4.15.0-1087.97",
"4.15.0-1090.100",
"4.15.0-1091.101",
"4.15.0-1093.103",
"4.15.0-1094.104",
"4.15.0-1096.106",
"4.15.0-1097.107",
"4.15.0-1099.109",
"4.15.0-1100.110",
"4.15.0-1101.112",
"4.15.0-1102.113",
"4.15.0-1103.114"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-1158-oracle",
"binary_version": "4.15.0-1158.169"
},
{
"binary_name": "linux-headers-4.15.0-1158-oracle",
"binary_version": "4.15.0-1158.169"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1158-oracle",
"binary_version": "4.15.0-1158.169"
},
{
"binary_name": "linux-modules-4.15.0-1158-oracle",
"binary_version": "4.15.0-1158.169"
},
{
"binary_name": "linux-modules-extra-4.15.0-1158-oracle",
"binary_version": "4.15.0-1158.169"
},
{
"binary_name": "linux-oracle-headers-4.15.0-1158",
"binary_version": "4.15.0-1158.169"
},
{
"binary_name": "linux-oracle-tools-4.15.0-1158",
"binary_version": "4.15.0-1158.169"
},
{
"binary_name": "linux-tools-4.15.0-1158-oracle",
"binary_version": "4.15.0-1158.169"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "linux-oracle",
"purl": "pkg:deb/ubuntu/linux-oracle@4.15.0-1158.169?arch=source\u0026distro=esm-infra/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1007.9",
"4.15.0-1008.10",
"4.15.0-1009.11",
"4.15.0-1010.12",
"4.15.0-1011.13",
"4.15.0-1013.15",
"4.15.0-1014.16",
"4.15.0-1015.17",
"4.15.0-1017.19",
"4.15.0-1018.20",
"4.15.0-1021.23",
"4.15.0-1022.25",
"4.15.0-1023.26",
"4.15.0-1025.28",
"4.15.0-1026.29",
"4.15.0-1027.30",
"4.15.0-1029.32",
"4.15.0-1030.33",
"4.15.0-1031.34",
"4.15.0-1033.36",
"4.15.0-1035.39",
"4.15.0-1037.41",
"4.15.0-1038.42",
"4.15.0-1039.43",
"4.15.0-1045.49",
"4.15.0-1047.51",
"4.15.0-1048.52",
"4.15.0-1050.54",
"4.15.0-1051.55",
"4.15.0-1053.57",
"4.15.0-1054.58",
"4.15.0-1057.62",
"4.15.0-1058.64",
"4.15.0-1059.65",
"4.15.0-1061.67",
"4.15.0-1062.68",
"4.15.0-1063.70",
"4.15.0-1064.71",
"4.15.0-1065.73",
"4.15.0-1066.74",
"4.15.0-1067.75",
"4.15.0-1068.76",
"4.15.0-1069.77",
"4.15.0-1070.78",
"4.15.0-1071.79",
"4.15.0-1072.80",
"4.15.0-1075.83",
"4.15.0-1078.86",
"4.15.0-1079.87",
"4.15.0-1080.88",
"4.15.0-1081.89",
"4.15.0-1082.90",
"4.15.0-1083.91",
"4.15.0-1084.92",
"4.15.0-1085.93",
"4.15.0-1086.94",
"4.15.0-1087.95",
"4.15.0-1089.98",
"4.15.0-1090.99",
"4.15.0-1091.100",
"4.15.0-1092.101",
"4.15.0-1093.102",
"4.15.0-1095.104",
"4.15.0-1098.108",
"4.15.0-1101.112",
"4.15.0-1102.113",
"4.15.0-1104.115",
"4.15.0-1105.116",
"4.15.0-1106.117",
"4.15.0-1107.118",
"4.15.0-1108.119",
"4.15.0-1111.122",
"4.15.0-1112.123",
"4.15.0-1113.124",
"4.15.0-1114.125",
"4.15.0-1115.126",
"4.15.0-1116.127",
"4.15.0-1117.128",
"4.15.0-1118.129",
"4.15.0-1119.130",
"4.15.0-1120.131",
"4.15.0-1121.132",
"4.15.0-1122.133",
"4.15.0-1123.134",
"4.15.0-1124.135",
"4.15.0-1125.136",
"4.15.0-1126.137",
"4.15.0-1127.138",
"4.15.0-1128.139",
"4.15.0-1129.140",
"4.15.0-1130.141",
"4.15.0-1131.142",
"4.15.0-1132.143",
"4.15.0-1133.144",
"4.15.0-1134.145",
"4.15.0-1135.146",
"4.15.0-1136.147",
"4.15.0-1137.148",
"4.15.0-1138.149",
"4.15.0-1139.150",
"4.15.0-1140.151",
"4.15.0-1141.152",
"4.15.0-1142.153",
"4.15.0-1143.154",
"4.15.0-1144.155",
"4.15.0-1145.156",
"4.15.0-1146.157",
"4.15.0-1147.158",
"4.15.0-1148.159",
"4.15.0-1149.160",
"4.15.0-1150.161",
"4.15.0-1151.162",
"4.15.0-1152.163",
"4.15.0-1153.164",
"4.15.0-1154.165",
"4.15.0-1155.166",
"4.15.0-1156.167",
"4.15.0-1158.169"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.0.0-1014-oracle",
"binary_version": "5.0.0-1014.19"
},
{
"binary_name": "linux-headers-5.0.0-1014-oracle",
"binary_version": "5.0.0-1014.19"
},
{
"binary_name": "linux-image-unsigned-5.0.0-1014-oracle",
"binary_version": "5.0.0-1014.19"
},
{
"binary_name": "linux-modules-5.0.0-1014-oracle",
"binary_version": "5.0.0-1014.19"
},
{
"binary_name": "linux-modules-extra-5.0.0-1014-oracle",
"binary_version": "5.0.0-1014.19"
},
{
"binary_name": "linux-oracle-5.0-headers-5.0.0-1014",
"binary_version": "5.0.0-1014.19"
},
{
"binary_name": "linux-oracle-5.0-tools-5.0.0-1014",
"binary_version": "5.0.0-1014.19"
},
{
"binary_name": "linux-tools-5.0.0-1014-oracle",
"binary_version": "5.0.0-1014.19"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-oracle-5.0",
"purl": "pkg:deb/ubuntu/linux-oracle-5.0@5.0.0-1014.19?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.0.0-1007.12~18.04.1",
"5.0.0-1008.13~18.04.1",
"5.0.0-1009.14~18.04.1",
"5.0.0-1010.15~18.04.1",
"5.0.0-1011.16",
"5.0.0-1013.18",
"5.0.0-1014.19"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.3.0-1030-oracle",
"binary_version": "5.3.0-1030.32~18.04.1"
},
{
"binary_name": "linux-headers-5.3.0-1030-oracle",
"binary_version": "5.3.0-1030.32~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.3.0-1030-oracle",
"binary_version": "5.3.0-1030.32~18.04.1"
},
{
"binary_name": "linux-modules-5.3.0-1030-oracle",
"binary_version": "5.3.0-1030.32~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.3.0-1030-oracle",
"binary_version": "5.3.0-1030.32~18.04.1"
},
{
"binary_name": "linux-oracle-5.3-headers-5.3.0-1030",
"binary_version": "5.3.0-1030.32~18.04.1"
},
{
"binary_name": "linux-oracle-5.3-tools-5.3.0-1030",
"binary_version": "5.3.0-1030.32~18.04.1"
},
{
"binary_name": "linux-tools-5.3.0-1030-oracle",
"binary_version": "5.3.0-1030.32~18.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "linux-oracle-5.3",
"purl": "pkg:deb/ubuntu/linux-oracle-5.3@5.3.0-1030.32~18.04.1?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.3.0-1011.12~18.04.1",
"5.3.0-1013.14~18.04.1",
"5.3.0-1014.15~18.04.1",
"5.3.0-1016.18~18.04.1",
"5.3.0-1018.20~18.04.1",
"5.3.0-1024.26~18.04.1",
"5.3.0-1027.29~18.04.1",
"5.3.0-1028.30~18.04.1",
"5.3.0-1030.32~18.04.1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1134-oracle",
"binary_version": "5.4.0-1134.143~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-1134-oracle",
"binary_version": "5.4.0-1134.143~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1134-oracle",
"binary_version": "5.4.0-1134.143~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-1134-oracle",
"binary_version": "5.4.0-1134.143~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1134-oracle",
"binary_version": "5.4.0-1134.143~18.04.1"
},
{
"binary_name": "linux-oracle-5.4-headers-5.4.0-1134",
"binary_version": "5.4.0-1134.143~18.04.1"
},
{
"binary_name": "linux-oracle-5.4-tools-5.4.0-1134",
"binary_version": "5.4.0-1134.143~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-1134-oracle",
"binary_version": "5.4.0-1134.143~18.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "linux-oracle-5.4",
"purl": "pkg:deb/ubuntu/linux-oracle-5.4@5.4.0-1134.143~18.04.1?arch=source\u0026distro=esm-infra/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1134.143~18.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1019.19~18.04.1",
"5.4.0-1021.21~18.04.1",
"5.4.0-1022.22~18.04.1",
"5.4.0-1024.24~18.04.1",
"5.4.0-1025.25~18.04.1",
"5.4.0-1028.29~18.04.1",
"5.4.0-1029.31~18.04.1",
"5.4.0-1030.32~18.04.1",
"5.4.0-1033.35",
"5.4.0-1034.36~18.04.1",
"5.4.0-1035.38~18.04.1",
"5.4.0-1037.40~18.04.1",
"5.4.0-1038.41~18.04.1",
"5.4.0-1039.42~18.04.1",
"5.4.0-1041.44~18.04.1",
"5.4.0-1042.45~18.04.1",
"5.4.0-1043.46~18.04.1",
"5.4.0-1044.47~18.04.1",
"5.4.0-1046.50~18.04.2",
"5.4.0-1048.52~18.04.1",
"5.4.0-1049.53~18.04.1",
"5.4.0-1052.56~18.04.1",
"5.4.0-1053.57~18.04.1",
"5.4.0-1054.58~18.04.1",
"5.4.0-1055.59~18.04.1",
"5.4.0-1056.60~18.04.1",
"5.4.0-1057.61~18.04.1",
"5.4.0-1058.62~18.04.1",
"5.4.0-1059.63~18.04.1",
"5.4.0-1061.65~18.04.1",
"5.4.0-1062.66~18.04.1",
"5.4.0-1063.67~18.04.1",
"5.4.0-1064.68~18.04.1",
"5.4.0-1066.71~18.04.1",
"5.4.0-1067.72~18.04.1",
"5.4.0-1069.75~18.04.1",
"5.4.0-1070.76~18.04.1",
"5.4.0-1071.77~18.04.1",
"5.4.0-1073.79~18.04.1",
"5.4.0-1076.83~18.04.1",
"5.4.0-1078.86~18.04.1",
"5.4.0-1079.87~18.04.1",
"5.4.0-1081.89~18.04.1",
"5.4.0-1082.90~18.04.1",
"5.4.0-1083.91~18.04.1",
"5.4.0-1084.92~18.04.1",
"5.4.0-1086.95~18.04.1",
"5.4.0-1087.96~18.04.1",
"5.4.0-1090.99~18.04.2",
"5.4.0-1091.100~18.04.1",
"5.4.0-1092.101~18.04.1",
"5.4.0-1093.102~18.04.1",
"5.4.0-1094.103~18.04.1",
"5.4.0-1098.107~18.04.1",
"5.4.0-1099.108~18.04.1",
"5.4.0-1100.109~18.04.1",
"5.4.0-1101.110~18.04.1",
"5.4.0-1102.111~18.04.1",
"5.4.0-1103.112~18.04.1",
"5.4.0-1104.113~18.04.1",
"5.4.0-1105.114~18.04.1",
"5.4.0-1106.115~18.04.1",
"5.4.0-1107.116~18.04.1",
"5.4.0-1108.117~18.04.1",
"5.4.0-1109.118~18.04.1",
"5.4.0-1110.119~18.04.1",
"5.4.0-1111.120~18.04.1",
"5.4.0-1112.121~18.04.4",
"5.4.0-1113.122~18.04.1",
"5.4.0-1115.124~18.04.1",
"5.4.0-1116.125~18.04.1",
"5.4.0-1117.126~18.04.1",
"5.4.0-1118.127~18.04.1",
"5.4.0-1119.128~18.04.1",
"5.4.0-1120.129~18.04.1",
"5.4.0-1121.130~18.04.1",
"5.4.0-1122.131~18.04.1",
"5.4.0-1123.132~18.04.1",
"5.4.0-1124.133~18.04.1",
"5.4.0-1125.134~18.04.1",
"5.4.0-1126.135~18.04.1",
"5.4.0-1127.136~18.04.1",
"5.4.0-1129.138~18.04.1",
"5.4.0-1130.139~18.04.1",
"5.4.0-1131.140~18.04.1",
"5.4.0-1132.141~18.04.1",
"5.4.0-1133.142~18.04.1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1119-raspi",
"binary_version": "5.4.0-1119.131~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-1119-raspi",
"binary_version": "5.4.0-1119.131~18.04.1"
},
{
"binary_name": "linux-image-5.4.0-1119-raspi",
"binary_version": "5.4.0-1119.131~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-1119-raspi",
"binary_version": "5.4.0-1119.131~18.04.1"
},
{
"binary_name": "linux-raspi-5.4-headers-5.4.0-1119",
"binary_version": "5.4.0-1119.131~18.04.1"
},
{
"binary_name": "linux-raspi-5.4-tools-5.4.0-1119",
"binary_version": "5.4.0-1119.131~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-1119-raspi",
"binary_version": "5.4.0-1119.131~18.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:18.04:LTS",
"name": "linux-raspi-5.4",
"purl": "pkg:deb/ubuntu/linux-raspi-5.4@5.4.0-1119.131~18.04.1?arch=source\u0026distro=esm-infra/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1119.131~18.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1013.13~18.04.1",
"5.4.0-1015.15~18.04.1",
"5.4.0-1016.17~18.04.1",
"5.4.0-1018.20~18.04.1",
"5.4.0-1019.21~18.04.1",
"5.4.0-1021.24~18.04.1",
"5.4.0-1022.25~18.04.1",
"5.4.0-1023.26~18.04.1",
"5.4.0-1025.28~18.04.1",
"5.4.0-1026.29~18.04.1",
"5.4.0-1028.31~18.04.1",
"5.4.0-1029.32~18.04.1",
"5.4.0-1030.33~18.04.1",
"5.4.0-1032.35~18.04.1",
"5.4.0-1033.36~18.04.1",
"5.4.0-1034.37~18.04.1",
"5.4.0-1035.38~18.04.1",
"5.4.0-1036.39~18.04.1",
"5.4.0-1038.41~18.04.1",
"5.4.0-1041.45~18.04.1",
"5.4.0-1042.46~18.04.3",
"5.4.0-1043.47~18.04.1",
"5.4.0-1044.48~18.04.1",
"5.4.0-1045.49~18.04.1",
"5.4.0-1046.50~18.04.1",
"5.4.0-1047.52~18.04.1",
"5.4.0-1048.53~18.04.1",
"5.4.0-1050.56~18.04.1",
"5.4.0-1052.58~18.04.1",
"5.4.0-1053.60~18.04.1",
"5.4.0-1055.62~18.04.1",
"5.4.0-1056.63~18.04.1",
"5.4.0-1058.65~18.04.1",
"5.4.0-1059.66~18.04.1",
"5.4.0-1060.68~18.04.1",
"5.4.0-1062.70~18.04.1",
"5.4.0-1065.75~18.04.1",
"5.4.0-1066.76~18.04.1",
"5.4.0-1068.78~18.04.1",
"5.4.0-1069.79~18.04.1",
"5.4.0-1070.80~18.04.1",
"5.4.0-1071.81~18.04.1",
"5.4.0-1073.84~18.04.1",
"5.4.0-1074.85~18.04.1",
"5.4.0-1077.88~18.04.2",
"5.4.0-1078.89~18.04.1",
"5.4.0-1079.90~18.04.1",
"5.4.0-1080.91~18.04.1",
"5.4.0-1081.92~18.04.1",
"5.4.0-1082.93~18.04.1",
"5.4.0-1083.94~18.04.1",
"5.4.0-1084.95~18.04.1",
"5.4.0-1085.96~18.04.1",
"5.4.0-1086.97~18.04.1",
"5.4.0-1088.99~18.04.1",
"5.4.0-1089.100~18.04.1",
"5.4.0-1090.101~18.04.1",
"5.4.0-1091.102~18.04.1",
"5.4.0-1092.103~18.04.1",
"5.4.0-1093.104~18.04.1",
"5.4.0-1094.105~18.04.1",
"5.4.0-1095.106~18.04.1",
"5.4.0-1096.107~18.04.1",
"5.4.0-1097.109~18.04.2",
"5.4.0-1098.110~18.04.2",
"5.4.0-1100.112~18.04.1",
"5.4.0-1101.113~18.04.1",
"5.4.0-1102.114~18.04.1",
"5.4.0-1103.115~18.04.1",
"5.4.0-1104.116~18.04.1",
"5.4.0-1105.117~18.04.1",
"5.4.0-1106.118~18.04.1",
"5.4.0-1107.119~18.04.1",
"5.4.0-1108.120~18.04.1",
"5.4.0-1109.121~18.04.1",
"5.4.0-1110.122~18.04.1",
"5.4.0-1111.123~18.04.1",
"5.4.0-1112.124~18.04.1",
"5.4.0-1114.126~18.04.1",
"5.4.0-1115.127~18.04.1",
"5.4.0-1116.128~18.04.1",
"5.4.0-1117.129~18.04.1",
"5.4.0-1118.130~18.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-aws-fips-headers-4.15.0-2135",
"binary_version": "4.15.0-2135.141"
},
{
"binary_name": "linux-aws-fips-tools-4.15.0-2135",
"binary_version": "4.15.0-2135.141"
},
{
"binary_name": "linux-buildinfo-4.15.0-2135-aws-fips",
"binary_version": "4.15.0-2135.141"
},
{
"binary_name": "linux-headers-4.15.0-2135-aws-fips",
"binary_version": "4.15.0-2135.141"
},
{
"binary_name": "linux-image-unsigned-4.15.0-2135-aws-fips",
"binary_version": "4.15.0-2135.141"
},
{
"binary_name": "linux-image-unsigned-hmac-4.15.0-2135-aws-fips",
"binary_version": "4.15.0-2135.141"
},
{
"binary_name": "linux-modules-4.15.0-2135-aws-fips",
"binary_version": "4.15.0-2135.141"
},
{
"binary_name": "linux-modules-extra-4.15.0-2135-aws-fips",
"binary_version": "4.15.0-2135.141"
},
{
"binary_name": "linux-tools-4.15.0-2135-aws-fips",
"binary_version": "4.15.0-2135.141"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:18.04:LTS",
"name": "linux-aws-fips",
"purl": "pkg:deb/ubuntu/linux-aws-fips@4.15.0-2135.141?arch=source\u0026distro=fips-updates/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-2000.4",
"4.15.0-2018.18",
"4.15.0-2021.21",
"4.15.0-2022.22",
"4.15.0-2024.24",
"4.15.0-2025.25",
"4.15.0-2026.26",
"4.15.0-2027.27",
"4.15.0-2030.31",
"4.15.0-2031.32",
"4.15.0-2033.34",
"4.15.0-2034.35",
"4.15.0-2035.37",
"4.15.0-2036.38",
"4.15.0-2037.39",
"4.15.0-2038.40",
"4.15.0-2039.41",
"4.15.0-2040.42",
"4.15.0-2041.43",
"4.15.0-2042.44",
"4.15.0-2044.46",
"4.15.0-2045.47",
"4.15.0-2048.50",
"4.15.0-2051.53",
"4.15.0-2052.54",
"4.15.0-2053.55",
"4.15.0-2054.56",
"4.15.0-2055.57",
"4.15.0-2056.58",
"4.15.0-2057.59",
"4.15.0-2059.61",
"4.15.0-2060.62",
"4.15.0-2061.63",
"4.15.0-2063.66",
"4.15.0-2064.67",
"4.15.0-2065.68",
"4.15.0-2066.69",
"4.15.0-2067.70",
"4.15.0-2069.72",
"4.15.0-2072.76",
"4.15.0-2075.80",
"4.15.0-2076.81",
"4.15.0-2078.83",
"4.15.0-2079.84",
"4.15.0-2080.85",
"4.15.0-2081.87",
"4.15.0-2082.88",
"4.15.0-2083.89",
"4.15.0-2085.91",
"4.15.0-2087.93",
"4.15.0-2089.95",
"4.15.0-2090.96",
"4.15.0-2092.98",
"4.15.0-2093.99",
"4.15.0-2094.100",
"4.15.0-2095.101",
"4.15.0-2096.102",
"4.15.0-2097.103",
"4.15.0-2098.104",
"4.15.0-2099.105",
"4.15.0-2100.106",
"4.15.0-2101.107",
"4.15.0-2102.108",
"4.15.0-2103.109",
"4.15.0-2104.110",
"4.15.0-2105.111",
"4.15.0-2106.112",
"4.15.0-2107.113",
"4.15.0-2108.114",
"4.15.0-2109.115",
"4.15.0-2110.116",
"4.15.0-2111.117",
"4.15.0-2112.118",
"4.15.0-2113.119",
"4.15.0-2114.120",
"4.15.0-2115.121",
"4.15.0-2116.122",
"4.15.0-2117.123",
"4.15.0-2118.124",
"4.15.0-2119.125",
"4.15.0-2120.126",
"4.15.0-2121.127",
"4.15.0-2122.128",
"4.15.0-2123.129",
"4.15.0-2124.130",
"4.15.0-2125.131",
"4.15.0-2126.132",
"4.15.0-2127.133",
"4.15.0-2128.134",
"4.15.0-2129.135",
"4.15.0-2130.136",
"4.15.0-2132.138",
"4.15.0-2133.139",
"4.15.0-2134.140",
"4.15.0-2135.141"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-azure-fips-cloud-tools-4.15.0-2115",
"binary_version": "4.15.0-2115.121"
},
{
"binary_name": "linux-azure-fips-headers-4.15.0-2115",
"binary_version": "4.15.0-2115.121"
},
{
"binary_name": "linux-azure-fips-tools-4.15.0-2115",
"binary_version": "4.15.0-2115.121"
},
{
"binary_name": "linux-buildinfo-4.15.0-2115-azure-fips",
"binary_version": "4.15.0-2115.121"
},
{
"binary_name": "linux-cloud-tools-4.15.0-2115-azure-fips",
"binary_version": "4.15.0-2115.121"
},
{
"binary_name": "linux-headers-4.15.0-2115-azure-fips",
"binary_version": "4.15.0-2115.121"
},
{
"binary_name": "linux-image-unsigned-4.15.0-2115-azure-fips",
"binary_version": "4.15.0-2115.121"
},
{
"binary_name": "linux-image-unsigned-hmac-4.15.0-2115-azure-fips",
"binary_version": "4.15.0-2115.121"
},
{
"binary_name": "linux-modules-4.15.0-2115-azure-fips",
"binary_version": "4.15.0-2115.121"
},
{
"binary_name": "linux-modules-extra-4.15.0-2115-azure-fips",
"binary_version": "4.15.0-2115.121"
},
{
"binary_name": "linux-tools-4.15.0-2115-azure-fips",
"binary_version": "4.15.0-2115.121"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:18.04:LTS",
"name": "linux-azure-fips",
"purl": "pkg:deb/ubuntu/linux-azure-fips@4.15.0-2115.121?arch=source\u0026distro=fips-updates/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1002.2",
"4.15.0-2006.7",
"4.15.0-2007.8",
"4.15.0-2008.9",
"4.15.0-2009.10",
"4.15.0-2012.14",
"4.15.0-2013.15",
"4.15.0-2015.17",
"4.15.0-2016.18",
"4.15.0-2017.20",
"4.15.0-2018.21",
"4.15.0-2020.23",
"4.15.0-2021.24",
"4.15.0-2022.25",
"4.15.0-2023.26",
"4.15.0-2024.27",
"4.15.0-2025.28",
"4.15.0-2026.29",
"4.15.0-2027.30",
"4.15.0-2030.33",
"4.15.0-2033.37",
"4.15.0-2034.38",
"4.15.0-2035.39",
"4.15.0-2036.40",
"4.15.0-2037.41",
"4.15.0-2038.42",
"4.15.0-2039.43",
"4.15.0-2041.45",
"4.15.0-2042.46",
"4.15.0-2043.47",
"4.15.0-2045.49",
"4.15.0-2046.50",
"4.15.0-2047.51",
"4.15.0-2048.52",
"4.15.0-2049.53",
"4.15.0-2050.54",
"4.15.0-2053.58",
"4.15.0-2056.62",
"4.15.0-2057.63",
"4.15.0-2059.65",
"4.15.0-2060.66",
"4.15.0-2062.68",
"4.15.0-2066.72",
"4.15.0-2067.73",
"4.15.0-2068.74",
"4.15.0-2070.76",
"4.15.0-2071.77",
"4.15.0-2072.78",
"4.15.0-2073.79",
"4.15.0-2074.80",
"4.15.0-2075.81",
"4.15.0-2076.82",
"4.15.0-2077.83",
"4.15.0-2078.84",
"4.15.0-2079.85",
"4.15.0-2080.86",
"4.15.0-2081.87",
"4.15.0-2082.88",
"4.15.0-2084.90",
"4.15.0-2085.91",
"4.15.0-2086.92",
"4.15.0-2087.93",
"4.15.0-2088.94",
"4.15.0-2089.95",
"4.15.0-2090.96",
"4.15.0-2091.97",
"4.15.0-2092.98",
"4.15.0-2093.99",
"4.15.0-2094.100",
"4.15.0-2095.101",
"4.15.0-2096.102",
"4.15.0-2097.103",
"4.15.0-2098.104",
"4.15.0-2099.105",
"4.15.0-2100.106",
"4.15.0-2101.107",
"4.15.0-2102.108",
"4.15.0-2104.110",
"4.15.0-2105.111",
"4.15.0-2106.112",
"4.15.0-2109.115",
"4.15.0-2110.116",
"4.15.0-2111.117",
"4.15.0-2112.118",
"4.15.0-2113.119",
"4.15.0-2114.120",
"4.15.0-2115.121"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-1152-fips",
"binary_version": "4.15.0-1152.164"
},
{
"binary_name": "linux-fips-headers-4.15.0-1152",
"binary_version": "4.15.0-1152.164"
},
{
"binary_name": "linux-fips-tools-4.15.0-1152",
"binary_version": "4.15.0-1152.164"
},
{
"binary_name": "linux-fips-tools-host",
"binary_version": "4.15.0-1152.164"
},
{
"binary_name": "linux-headers-4.15.0-1152-fips",
"binary_version": "4.15.0-1152.164"
},
{
"binary_name": "linux-image-4.15.0-1152-fips",
"binary_version": "4.15.0-1152.164"
},
{
"binary_name": "linux-image-hmac-4.15.0-1152-fips",
"binary_version": "4.15.0-1152.164"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1152-fips",
"binary_version": "4.15.0-1152.164"
},
{
"binary_name": "linux-image-unsigned-hmac-4.15.0-1152-fips",
"binary_version": "4.15.0-1152.164"
},
{
"binary_name": "linux-modules-4.15.0-1152-fips",
"binary_version": "4.15.0-1152.164"
},
{
"binary_name": "linux-modules-extra-4.15.0-1152-fips",
"binary_version": "4.15.0-1152.164"
},
{
"binary_name": "linux-tools-4.15.0-1152-fips",
"binary_version": "4.15.0-1152.164"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:18.04:LTS",
"name": "linux-fips",
"purl": "pkg:deb/ubuntu/linux-fips@4.15.0-1152.164?arch=source\u0026distro=fips-updates/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1027.32",
"4.15.0-1029.34",
"4.15.0-1034.39",
"4.15.0-1035.40",
"4.15.0-1037.42",
"4.15.0-1038.43",
"4.15.0-1039.44",
"4.15.0-1040.45",
"4.15.0-1041.46",
"4.15.0-1044.50",
"4.15.0-1045.52",
"4.15.0-1046.53",
"4.15.0-1048.55",
"4.15.0-1049.56",
"4.15.0-1050.58",
"4.15.0-1051.59",
"4.15.0-1052.60",
"4.15.0-1053.61",
"4.15.0-1054.62",
"4.15.0-1055.63",
"4.15.0-1056.64",
"4.15.0-1057.65",
"4.15.0-1058.66",
"4.15.0-1059.67",
"4.15.0-1060.68",
"4.15.0-1063.71",
"4.15.0-1066.75",
"4.15.0-1067.76",
"4.15.0-1068.77",
"4.15.0-1069.78",
"4.15.0-1070.79",
"4.15.0-1071.80",
"4.15.0-1072.81",
"4.15.0-1073.82",
"4.15.0-1075.84",
"4.15.0-1076.85",
"4.15.0-1078.87",
"4.15.0-1080.89",
"4.15.0-1081.90",
"4.15.0-1083.92",
"4.15.0-1084.93",
"4.15.0-1085.94",
"4.15.0-1087.96",
"4.15.0-1090.100",
"4.15.0-1093.104",
"4.15.0-1094.105",
"4.15.0-1096.107",
"4.15.0-1097.108",
"4.15.0-1098.109",
"4.15.0-1099.110",
"4.15.0-1100.111",
"4.15.0-1103.114",
"4.15.0-1104.115",
"4.15.0-1105.116",
"4.15.0-1107.118",
"4.15.0-1108.119",
"4.15.0-1109.120",
"4.15.0-1110.121",
"4.15.0-1111.122",
"4.15.0-1112.123",
"4.15.0-1113.124",
"4.15.0-1114.125",
"4.15.0-1115.126",
"4.15.0-1116.127",
"4.15.0-1117.128",
"4.15.0-1118.129",
"4.15.0-1119.130",
"4.15.0-1121.132",
"4.15.0-1122.133",
"4.15.0-1123.134",
"4.15.0-1124.135",
"4.15.0-1125.136",
"4.15.0-1126.137",
"4.15.0-1127.138",
"4.15.0-1128.139",
"4.15.0-1129.140",
"4.15.0-1130.141",
"4.15.0-1131.142",
"4.15.0-1132.143",
"4.15.0-1133.144",
"4.15.0-1134.145",
"4.15.0-1135.146",
"4.15.0-1136.147",
"4.15.0-1137.148",
"4.15.0-1138.149",
"4.15.0-1139.150",
"4.15.0-1140.151",
"4.15.0-1141.153",
"4.15.0-1142.154",
"4.15.0-1143.155",
"4.15.0-1144.156",
"4.15.0-1145.157",
"4.15.0-1146.158",
"4.15.0-1147.159",
"4.15.0-1148.160",
"4.15.0-1149.161",
"4.15.0-1150.162",
"4.15.0-1151.163",
"4.15.0-1152.164"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-2098-gcp-fips",
"binary_version": "4.15.0-2098.104"
},
{
"binary_name": "linux-gcp-fips-headers-4.15.0-2098",
"binary_version": "4.15.0-2098.104"
},
{
"binary_name": "linux-gcp-fips-tools-4.15.0-2098",
"binary_version": "4.15.0-2098.104"
},
{
"binary_name": "linux-headers-4.15.0-2098-gcp-fips",
"binary_version": "4.15.0-2098.104"
},
{
"binary_name": "linux-image-unsigned-4.15.0-2098-gcp-fips",
"binary_version": "4.15.0-2098.104"
},
{
"binary_name": "linux-image-unsigned-hmac-4.15.0-2098-gcp-fips",
"binary_version": "4.15.0-2098.104"
},
{
"binary_name": "linux-modules-4.15.0-2098-gcp-fips",
"binary_version": "4.15.0-2098.104"
},
{
"binary_name": "linux-modules-extra-4.15.0-2098-gcp-fips",
"binary_version": "4.15.0-2098.104"
},
{
"binary_name": "linux-tools-4.15.0-2098-gcp-fips",
"binary_version": "4.15.0-2098.104"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:18.04:LTS",
"name": "linux-gcp-fips",
"purl": "pkg:deb/ubuntu/linux-gcp-fips@4.15.0-2098.104?arch=source\u0026distro=fips-updates/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-2013.14",
"4.15.0-2016.18",
"4.15.0-2017.19",
"4.15.0-2018.20",
"4.15.0-2019.21",
"4.15.0-2020.22",
"4.15.0-2021.23",
"4.15.0-2022.24",
"4.15.0-2024.26",
"4.15.0-2025.27",
"4.15.0-2026.28",
"4.15.0-2028.31",
"4.15.0-2029.32",
"4.15.0-2030.33",
"4.15.0-2031.34",
"4.15.0-2032.35",
"4.15.0-2034.37",
"4.15.0-2037.41",
"4.15.0-2040.45",
"4.15.0-2041.46",
"4.15.0-2043.48",
"4.15.0-2044.49",
"4.15.0-2045.50",
"4.15.0-2047.52",
"4.15.0-2050.55",
"4.15.0-2052.57",
"4.15.0-2054.59",
"4.15.0-2055.60",
"4.15.0-2056.61",
"4.15.0-2057.62",
"4.15.0-2058.63",
"4.15.0-2059.64",
"4.15.0-2060.65",
"4.15.0-2061.66",
"4.15.0-2062.67",
"4.15.0-2063.68",
"4.15.0-2064.69",
"4.15.0-2065.70",
"4.15.0-2066.71",
"4.15.0-2067.72",
"4.15.0-2068.73",
"4.15.0-2069.74",
"4.15.0-2070.75",
"4.15.0-2071.76",
"4.15.0-2072.77",
"4.15.0-2073.78",
"4.15.0-2074.79",
"4.15.0-2075.80",
"4.15.0-2076.81",
"4.15.0-2077.83",
"4.15.0-2078.84",
"4.15.0-2079.85",
"4.15.0-2080.86",
"4.15.0-2081.87",
"4.15.0-2082.88",
"4.15.0-2083.89",
"4.15.0-2084.90",
"4.15.0-2085.91",
"4.15.0-2086.92",
"4.15.0-2087.93",
"4.15.0-2088.94",
"4.15.0-2089.95",
"4.15.0-2090.96",
"4.15.0-2091.97",
"4.15.0-2092.98",
"4.15.0-2093.99",
"4.15.0-2094.100",
"4.15.0-2095.101",
"4.15.0-2096.102",
"4.15.0-2097.103",
"4.15.0-2098.104"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-aws-fips-headers-4.15.0-2000",
"binary_version": "4.15.0-2000.4"
},
{
"binary_name": "linux-aws-fips-tools-4.15.0-2000",
"binary_version": "4.15.0-2000.4"
},
{
"binary_name": "linux-buildinfo-4.15.0-2000-aws-fips",
"binary_version": "4.15.0-2000.4"
},
{
"binary_name": "linux-headers-4.15.0-2000-aws-fips",
"binary_version": "4.15.0-2000.4"
},
{
"binary_name": "linux-image-unsigned-4.15.0-2000-aws-fips",
"binary_version": "4.15.0-2000.4"
},
{
"binary_name": "linux-image-unsigned-hmac-4.15.0-2000-aws-fips",
"binary_version": "4.15.0-2000.4"
},
{
"binary_name": "linux-modules-4.15.0-2000-aws-fips",
"binary_version": "4.15.0-2000.4"
},
{
"binary_name": "linux-modules-extra-4.15.0-2000-aws-fips",
"binary_version": "4.15.0-2000.4"
},
{
"binary_name": "linux-tools-4.15.0-2000-aws-fips",
"binary_version": "4.15.0-2000.4"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS:18.04:LTS",
"name": "linux-aws-fips",
"purl": "pkg:deb/ubuntu/linux-aws-fips@4.15.0-2000.4?arch=source\u0026distro=fips/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-2000.4"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-azure-fips-cloud-tools-4.15.0-1002",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-azure-fips-headers-4.15.0-1002",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-azure-fips-tools-4.15.0-1002",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-buildinfo-4.15.0-1002-azure-fips",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-cloud-tools-4.15.0-1002-azure-fips",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-headers-4.15.0-1002-azure-fips",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1002-azure-fips",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-image-unsigned-hmac-4.15.0-1002-azure-fips",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-modules-4.15.0-1002-azure-fips",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-modules-extra-4.15.0-1002-azure-fips",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-tools-4.15.0-1002-azure-fips",
"binary_version": "4.15.0-1002.2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS:18.04:LTS",
"name": "linux-azure-fips",
"purl": "pkg:deb/ubuntu/linux-azure-fips@4.15.0-1002.2?arch=source\u0026distro=fips/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1002.2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-1011-fips",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-fips-headers-4.15.0-1011",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-fips-tools-4.15.0-1011",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-fips-tools-host",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-headers-4.15.0-1011-fips",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-image-4.15.0-1011-fips",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-image-hmac-4.15.0-1011-fips",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1011-fips",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-image-unsigned-hmac-4.15.0-1011-fips",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-modules-4.15.0-1011-fips",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-modules-extra-4.15.0-1011-fips",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-tools-4.15.0-1011-fips",
"binary_version": "4.15.0-1011.12"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS:18.04:LTS",
"name": "linux-fips",
"purl": "pkg:deb/ubuntu/linux-fips@4.15.0-1011.12?arch=source\u0026distro=fips/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1011.12"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-1001-gcp-fips",
"binary_version": "4.15.0-1001.1"
},
{
"binary_name": "linux-gcp-fips-headers-4.15.0-1001",
"binary_version": "4.15.0-1001.1"
},
{
"binary_name": "linux-gcp-fips-tools-4.15.0-1001",
"binary_version": "4.15.0-1001.1"
},
{
"binary_name": "linux-headers-4.15.0-1001-gcp-fips",
"binary_version": "4.15.0-1001.1"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1001-gcp-fips",
"binary_version": "4.15.0-1001.1"
},
{
"binary_name": "linux-image-unsigned-hmac-4.15.0-1001-gcp-fips",
"binary_version": "4.15.0-1001.1"
},
{
"binary_name": "linux-modules-4.15.0-1001-gcp-fips",
"binary_version": "4.15.0-1001.1"
},
{
"binary_name": "linux-modules-extra-4.15.0-1001-gcp-fips",
"binary_version": "4.15.0-1001.1"
},
{
"binary_name": "linux-tools-4.15.0-1001-gcp-fips",
"binary_version": "4.15.0-1001.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS:18.04:LTS",
"name": "linux-gcp-fips",
"purl": "pkg:deb/ubuntu/linux-gcp-fips@4.15.0-1001.1?arch=source\u0026distro=fips/bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.15.0-1001.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "block-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "block-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "crypto-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "crypto-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "dasd-extra-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "dasd-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "fat-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "fat-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "fb-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "firewire-core-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "floppy-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "fs-core-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "fs-core-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "fs-secondary-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "fs-secondary-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "input-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "input-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "ipmi-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "ipmi-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "kernel-image-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "kernel-image-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-buildinfo-5.4.0-200-generic",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-buildinfo-5.4.0-200-generic-lpae",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-buildinfo-5.4.0-200-lowlatency",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-cloud-tools-5.4.0-200",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-cloud-tools-5.4.0-200-generic",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-cloud-tools-5.4.0-200-lowlatency",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-cloud-tools-common",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-headers-5.4.0-200",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-headers-5.4.0-200-generic",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-headers-5.4.0-200-generic-lpae",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-headers-5.4.0-200-lowlatency",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-image-5.4.0-200-generic",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-image-5.4.0-200-generic-lpae",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-image-unsigned-5.4.0-200-generic",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-image-unsigned-5.4.0-200-lowlatency",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-modules-5.4.0-200-generic",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-modules-5.4.0-200-generic-lpae",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-modules-5.4.0-200-lowlatency",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-modules-extra-5.4.0-200-generic",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-source-5.4.0",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-tools-5.4.0-200",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-tools-5.4.0-200-generic",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-tools-5.4.0-200-generic-lpae",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-tools-5.4.0-200-lowlatency",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-tools-common",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-tools-host",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-udebs-generic",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "linux-udebs-generic-lpae",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "md-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "md-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "message-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "mouse-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "mouse-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "multipath-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "multipath-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "nfs-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "nfs-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "nic-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "nic-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "nic-pcmcia-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "nic-shared-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "nic-shared-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "nic-usb-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "nic-usb-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "parport-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "parport-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "pata-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "pcmcia-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "pcmcia-storage-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "plip-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "plip-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "ppp-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "ppp-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "sata-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "sata-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "scsi-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "scsi-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "serial-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "storage-core-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "storage-core-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "usb-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "usb-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "virtio-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "vlan-modules-5.4.0-200-generic-di",
"binary_version": "5.4.0-200.220"
},
{
"binary_name": "vlan-modules-5.4.0-200-generic-lpae-di",
"binary_version": "5.4.0-200.220"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux",
"purl": "pkg:deb/ubuntu/linux@5.4.0-200.220?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-200.220"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.3.0-18.19",
"5.3.0-24.26",
"5.4.0-9.12",
"5.4.0-18.22",
"5.4.0-21.25",
"5.4.0-24.28",
"5.4.0-25.29",
"5.4.0-26.30",
"5.4.0-28.32",
"5.4.0-29.33",
"5.4.0-31.35",
"5.4.0-33.37",
"5.4.0-37.41",
"5.4.0-39.43",
"5.4.0-40.44",
"5.4.0-42.46",
"5.4.0-45.49",
"5.4.0-47.51",
"5.4.0-48.52",
"5.4.0-51.56",
"5.4.0-52.57",
"5.4.0-53.59",
"5.4.0-54.60",
"5.4.0-56.62",
"5.4.0-58.64",
"5.4.0-59.65",
"5.4.0-60.67",
"5.4.0-62.70",
"5.4.0-64.72",
"5.4.0-65.73",
"5.4.0-66.74",
"5.4.0-67.75",
"5.4.0-70.78",
"5.4.0-71.79",
"5.4.0-72.80",
"5.4.0-73.82",
"5.4.0-74.83",
"5.4.0-77.86",
"5.4.0-80.90",
"5.4.0-81.91",
"5.4.0-84.94",
"5.4.0-86.97",
"5.4.0-88.99",
"5.4.0-89.100",
"5.4.0-90.101",
"5.4.0-91.102",
"5.4.0-92.103",
"5.4.0-94.106",
"5.4.0-96.109",
"5.4.0-97.110",
"5.4.0-99.112",
"5.4.0-100.113",
"5.4.0-104.118",
"5.4.0-105.119",
"5.4.0-107.121",
"5.4.0-109.123",
"5.4.0-110.124",
"5.4.0-113.127",
"5.4.0-117.132",
"5.4.0-120.136",
"5.4.0-121.137",
"5.4.0-122.138",
"5.4.0-124.140",
"5.4.0-125.141",
"5.4.0-126.142",
"5.4.0-128.144",
"5.4.0-131.147",
"5.4.0-132.148",
"5.4.0-135.152",
"5.4.0-136.153",
"5.4.0-137.154",
"5.4.0-139.156",
"5.4.0-144.161",
"5.4.0-146.163",
"5.4.0-147.164",
"5.4.0-148.165",
"5.4.0-149.166",
"5.4.0-150.167",
"5.4.0-152.169",
"5.4.0-153.170",
"5.4.0-155.172",
"5.4.0-156.173",
"5.4.0-159.176",
"5.4.0-162.179",
"5.4.0-163.180",
"5.4.0-164.181",
"5.4.0-165.182",
"5.4.0-166.183",
"5.4.0-167.184",
"5.4.0-169.187",
"5.4.0-170.188",
"5.4.0-171.189",
"5.4.0-172.190",
"5.4.0-173.191",
"5.4.0-174.193",
"5.4.0-176.196",
"5.4.0-177.197",
"5.4.0-181.201",
"5.4.0-182.202",
"5.4.0-186.206",
"5.4.0-187.207",
"5.4.0-189.209",
"5.4.0-190.210",
"5.4.0-192.212",
"5.4.0-193.213",
"5.4.0-195.215",
"5.4.0-196.216",
"5.4.0-198.218"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-aws-cloud-tools-5.4.0-1135",
"binary_version": "5.4.0-1135.145"
},
{
"binary_name": "linux-aws-headers-5.4.0-1135",
"binary_version": "5.4.0-1135.145"
},
{
"binary_name": "linux-aws-tools-5.4.0-1135",
"binary_version": "5.4.0-1135.145"
},
{
"binary_name": "linux-buildinfo-5.4.0-1135-aws",
"binary_version": "5.4.0-1135.145"
},
{
"binary_name": "linux-cloud-tools-5.4.0-1135-aws",
"binary_version": "5.4.0-1135.145"
},
{
"binary_name": "linux-headers-5.4.0-1135-aws",
"binary_version": "5.4.0-1135.145"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1135-aws",
"binary_version": "5.4.0-1135.145"
},
{
"binary_name": "linux-modules-5.4.0-1135-aws",
"binary_version": "5.4.0-1135.145"
},
{
"binary_name": "linux-modules-extra-5.4.0-1135-aws",
"binary_version": "5.4.0-1135.145"
},
{
"binary_name": "linux-tools-5.4.0-1135-aws",
"binary_version": "5.4.0-1135.145"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-aws",
"purl": "pkg:deb/ubuntu/linux-aws@5.4.0-1135.145?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1135.145"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.3.0-1003.3",
"5.3.0-1008.9",
"5.3.0-1009.10",
"5.3.0-1010.11",
"5.4.0-1005.5",
"5.4.0-1007.7",
"5.4.0-1008.8",
"5.4.0-1009.9",
"5.4.0-1011.11",
"5.4.0-1015.15",
"5.4.0-1017.17",
"5.4.0-1018.18",
"5.4.0-1020.20",
"5.4.0-1021.21",
"5.4.0-1022.22",
"5.4.0-1024.24",
"5.4.0-1025.25",
"5.4.0-1028.29",
"5.4.0-1029.30",
"5.4.0-1030.31",
"5.4.0-1032.33",
"5.4.0-1034.35",
"5.4.0-1035.37",
"5.4.0-1037.39",
"5.4.0-1038.40",
"5.4.0-1039.41",
"5.4.0-1041.43",
"5.4.0-1043.45",
"5.4.0-1045.47",
"5.4.0-1047.49",
"5.4.0-1048.50",
"5.4.0-1049.51",
"5.4.0-1051.53",
"5.4.0-1054.57",
"5.4.0-1055.58",
"5.4.0-1056.59",
"5.4.0-1057.60",
"5.4.0-1058.61",
"5.4.0-1059.62",
"5.4.0-1060.63",
"5.4.0-1061.64",
"5.4.0-1063.66",
"5.4.0-1064.67",
"5.4.0-1065.68",
"5.4.0-1066.69",
"5.4.0-1068.72",
"5.4.0-1069.73",
"5.4.0-1071.76",
"5.4.0-1072.77",
"5.4.0-1073.78",
"5.4.0-1075.80",
"5.4.0-1078.84",
"5.4.0-1080.87",
"5.4.0-1081.88",
"5.4.0-1083.90",
"5.4.0-1084.91",
"5.4.0-1085.92",
"5.4.0-1086.93",
"5.4.0-1088.96",
"5.4.0-1089.97",
"5.4.0-1092.100",
"5.4.0-1093.101",
"5.4.0-1094.102",
"5.4.0-1096.104",
"5.4.0-1097.105",
"5.4.0-1099.107",
"5.4.0-1100.108",
"5.4.0-1101.109",
"5.4.0-1102.110",
"5.4.0-1103.111",
"5.4.0-1104.112",
"5.4.0-1105.113",
"5.4.0-1106.114",
"5.4.0-1107.115",
"5.4.0-1108.116",
"5.4.0-1109.118",
"5.4.0-1110.119",
"5.4.0-1111.120",
"5.4.0-1112.121",
"5.4.0-1113.123",
"5.4.0-1114.124",
"5.4.0-1116.126",
"5.4.0-1117.127",
"5.4.0-1118.128",
"5.4.0-1119.129",
"5.4.0-1120.130",
"5.4.0-1121.131",
"5.4.0-1122.132",
"5.4.0-1123.133",
"5.4.0-1124.134",
"5.4.0-1125.135",
"5.4.0-1126.136",
"5.4.0-1127.137",
"5.4.0-1128.138",
"5.4.0-1129.139",
"5.4.0-1130.140",
"5.4.0-1131.141",
"5.4.0-1132.142",
"5.4.0-1133.143",
"5.4.0-1134.144"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-aws-5.15-cloud-tools-5.15.0-1072",
"binary_version": "5.15.0-1072.78~20.04.1"
},
{
"binary_name": "linux-aws-5.15-headers-5.15.0-1072",
"binary_version": "5.15.0-1072.78~20.04.1"
},
{
"binary_name": "linux-aws-5.15-tools-5.15.0-1072",
"binary_version": "5.15.0-1072.78~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.15.0-1072-aws",
"binary_version": "5.15.0-1072.78~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1072-aws",
"binary_version": "5.15.0-1072.78~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1072-aws",
"binary_version": "5.15.0-1072.78~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1072-aws",
"binary_version": "5.15.0-1072.78~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1072-aws",
"binary_version": "5.15.0-1072.78~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1072-aws",
"binary_version": "5.15.0-1072.78~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1072-aws",
"binary_version": "5.15.0-1072.78~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-aws-5.15",
"purl": "pkg:deb/ubuntu/linux-aws-5.15@5.15.0-1072.78~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1072.78~20.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1014.18~20.04.1",
"5.15.0-1015.19~20.04.1",
"5.15.0-1017.21~20.04.1",
"5.15.0-1019.23~20.04.1",
"5.15.0-1020.24~20.04.1",
"5.15.0-1021.25~20.04.1",
"5.15.0-1022.26~20.04.1",
"5.15.0-1023.27~20.04.1",
"5.15.0-1026.30~20.04.2",
"5.15.0-1027.31~20.04.1",
"5.15.0-1028.32~20.04.1",
"5.15.0-1030.34~20.04.1",
"5.15.0-1031.35~20.04.1",
"5.15.0-1033.37~20.04.1",
"5.15.0-1034.38~20.04.1",
"5.15.0-1035.39~20.04.1",
"5.15.0-1036.40~20.04.1",
"5.15.0-1037.41~20.04.1",
"5.15.0-1038.43~20.04.1",
"5.15.0-1039.44~20.04.1",
"5.15.0-1040.45~20.04.1",
"5.15.0-1041.46~20.04.1",
"5.15.0-1043.48~20.04.1",
"5.15.0-1044.49~20.04.1",
"5.15.0-1045.50~20.04.1",
"5.15.0-1047.52~20.04.1",
"5.15.0-1048.53~20.04.1",
"5.15.0-1049.54~20.04.1",
"5.15.0-1050.55~20.04.1",
"5.15.0-1051.56~20.04.1",
"5.15.0-1052.57~20.04.1",
"5.15.0-1053.58~20.04.1",
"5.15.0-1055.60~20.04.1",
"5.15.0-1056.61~20.04.1",
"5.15.0-1057.63~20.04.1",
"5.15.0-1058.64~20.04.1",
"5.15.0-1061.67~20.04.1",
"5.15.0-1062.68~20.04.1",
"5.15.0-1063.69~20.04.1",
"5.15.0-1064.70~20.04.1",
"5.15.0-1065.71~20.04.1",
"5.15.0-1066.72~20.04.1",
"5.15.0-1067.73~20.04.1",
"5.15.0-1068.74~20.04.1",
"5.15.0-1069.75~20.04.1",
"5.15.0-1070.76~20.04.1",
"5.15.0-1071.77~20.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-azure-cloud-tools-5.4.0-1140",
"binary_version": "5.4.0-1140.147"
},
{
"binary_name": "linux-azure-headers-5.4.0-1140",
"binary_version": "5.4.0-1140.147"
},
{
"binary_name": "linux-azure-tools-5.4.0-1140",
"binary_version": "5.4.0-1140.147"
},
{
"binary_name": "linux-buildinfo-5.4.0-1140-azure",
"binary_version": "5.4.0-1140.147"
},
{
"binary_name": "linux-cloud-tools-5.4.0-1140-azure",
"binary_version": "5.4.0-1140.147"
},
{
"binary_name": "linux-headers-5.4.0-1140-azure",
"binary_version": "5.4.0-1140.147"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1140-azure",
"binary_version": "5.4.0-1140.147"
},
{
"binary_name": "linux-modules-5.4.0-1140-azure",
"binary_version": "5.4.0-1140.147"
},
{
"binary_name": "linux-modules-extra-5.4.0-1140-azure",
"binary_version": "5.4.0-1140.147"
},
{
"binary_name": "linux-tools-5.4.0-1140-azure",
"binary_version": "5.4.0-1140.147"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-azure",
"purl": "pkg:deb/ubuntu/linux-azure@5.4.0-1140.147?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1140.147"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.3.0-1003.3",
"5.3.0-1008.9",
"5.3.0-1009.10",
"5.4.0-1006.6",
"5.4.0-1008.8",
"5.4.0-1009.9",
"5.4.0-1010.10",
"5.4.0-1012.12",
"5.4.0-1016.16",
"5.4.0-1019.19",
"5.4.0-1020.20",
"5.4.0-1022.22",
"5.4.0-1023.23",
"5.4.0-1025.25",
"5.4.0-1026.26",
"5.4.0-1031.32",
"5.4.0-1032.33",
"5.4.0-1034.35",
"5.4.0-1035.36",
"5.4.0-1036.38",
"5.4.0-1039.41",
"5.4.0-1040.42",
"5.4.0-1041.43",
"5.4.0-1043.45",
"5.4.0-1044.46",
"5.4.0-1046.48",
"5.4.0-1047.49",
"5.4.0-1048.50",
"5.4.0-1049.51",
"5.4.0-1051.53",
"5.4.0-1055.57",
"5.4.0-1056.58",
"5.4.0-1058.60",
"5.4.0-1059.62",
"5.4.0-1061.64",
"5.4.0-1062.65",
"5.4.0-1063.66",
"5.4.0-1064.67",
"5.4.0-1065.68",
"5.4.0-1067.70",
"5.4.0-1068.71",
"5.4.0-1069.72",
"5.4.0-1070.73",
"5.4.0-1072.75",
"5.4.0-1073.76",
"5.4.0-1074.77",
"5.4.0-1077.80",
"5.4.0-1078.81",
"5.4.0-1080.83",
"5.4.0-1083.87",
"5.4.0-1085.90",
"5.4.0-1086.91",
"5.4.0-1089.94",
"5.4.0-1090.95",
"5.4.0-1091.96",
"5.4.0-1094.100",
"5.4.0-1095.101",
"5.4.0-1098.104",
"5.4.0-1100.106",
"5.4.0-1101.107",
"5.4.0-1103.109",
"5.4.0-1104.110",
"5.4.0-1105.111",
"5.4.0-1106.112",
"5.4.0-1107.113",
"5.4.0-1108.114",
"5.4.0-1109.115",
"5.4.0-1110.116",
"5.4.0-1111.117",
"5.4.0-1112.118",
"5.4.0-1113.119",
"5.4.0-1114.120",
"5.4.0-1115.122",
"5.4.0-1116.123",
"5.4.0-1117.124",
"5.4.0-1118.125",
"5.4.0-1119.126",
"5.4.0-1120.127",
"5.4.0-1121.128",
"5.4.0-1122.129",
"5.4.0-1123.130",
"5.4.0-1124.131",
"5.4.0-1126.133",
"5.4.0-1127.134",
"5.4.0-1128.135",
"5.4.0-1129.136",
"5.4.0-1130.137",
"5.4.0-1131.138",
"5.4.0-1132.139",
"5.4.0-1133.140",
"5.4.0-1134.141",
"5.4.0-1135.142",
"5.4.0-1136.143",
"5.4.0-1137.144",
"5.4.0-1138.145",
"5.4.0-1139.146"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-azure-5.15-cloud-tools-5.15.0-1078",
"binary_version": "5.15.0-1078.87~20.04.1"
},
{
"binary_name": "linux-azure-5.15-headers-5.15.0-1078",
"binary_version": "5.15.0-1078.87~20.04.1"
},
{
"binary_name": "linux-azure-5.15-tools-5.15.0-1078",
"binary_version": "5.15.0-1078.87~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.15.0-1078-azure",
"binary_version": "5.15.0-1078.87~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1078-azure",
"binary_version": "5.15.0-1078.87~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1078-azure",
"binary_version": "5.15.0-1078.87~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1078-azure",
"binary_version": "5.15.0-1078.87~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1078-azure",
"binary_version": "5.15.0-1078.87~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1078-azure",
"binary_version": "5.15.0-1078.87~20.04.1"
},
{
"binary_name": "linux-modules-involflt-5.15.0-1078-azure",
"binary_version": "5.15.0-1078.87~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1078-azure",
"binary_version": "5.15.0-1078.87~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-azure-5.15",
"purl": "pkg:deb/ubuntu/linux-azure-5.15@5.15.0-1078.87~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1078.87~20.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1007.8~20.04.1",
"5.15.0-1008.9~20.04.1",
"5.15.0-1013.16~20.04.1",
"5.15.0-1014.17~20.04.1",
"5.15.0-1017.20~20.04.1",
"5.15.0-1019.24~20.04.1",
"5.15.0-1020.25~20.04.1",
"5.15.0-1021.26~20.04.1",
"5.15.0-1022.27~20.04.1",
"5.15.0-1023.29~20.04.1",
"5.15.0-1029.36~20.04.1",
"5.15.0-1030.37~20.04.1",
"5.15.0-1031.38~20.04.1",
"5.15.0-1033.40~20.04.1",
"5.15.0-1034.41~20.04.1",
"5.15.0-1035.42~20.04.1",
"5.15.0-1036.43~20.04.1",
"5.15.0-1037.44~20.04.1",
"5.15.0-1038.45~20.04.1",
"5.15.0-1039.46~20.04.1",
"5.15.0-1040.47~20.04.1",
"5.15.0-1041.48~20.04.1",
"5.15.0-1042.49~20.04.1",
"5.15.0-1043.50~20.04.1",
"5.15.0-1045.52~20.04.1",
"5.15.0-1046.53~20.04.1",
"5.15.0-1047.54~20.04.1",
"5.15.0-1049.56~20.04.1",
"5.15.0-1050.57~20.04.1",
"5.15.0-1051.59~20.04.1",
"5.15.0-1052.60~20.04.1",
"5.15.0-1053.61~20.04.1",
"5.15.0-1054.62~20.04.1",
"5.15.0-1056.64~20.04.1",
"5.15.0-1057.65~20.04.1",
"5.15.0-1058.66~20.04.2",
"5.15.0-1059.67~20.04.1",
"5.15.0-1060.69~20.04.1",
"5.15.0-1061.70~20.04.1",
"5.15.0-1063.72~20.04.1",
"5.15.0-1064.73~20.04.1",
"5.15.0-1065.74~20.04.1",
"5.15.0-1067.76~20.04.1",
"5.15.0-1068.77~20.04.1",
"5.15.0-1070.79~20.04.1",
"5.15.0-1071.80~20.04.1",
"5.15.0-1072.81~20.04.1",
"5.15.0-1073.82~20.04.1",
"5.15.0-1074.83~20.04.1",
"5.15.0-1075.84~20.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-bluefield-headers-5.4.0-1095",
"binary_version": "5.4.0-1095.102"
},
{
"binary_name": "linux-bluefield-tools-5.4.0-1095",
"binary_version": "5.4.0-1095.102"
},
{
"binary_name": "linux-buildinfo-5.4.0-1095-bluefield",
"binary_version": "5.4.0-1095.102"
},
{
"binary_name": "linux-headers-5.4.0-1095-bluefield",
"binary_version": "5.4.0-1095.102"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1095-bluefield",
"binary_version": "5.4.0-1095.102"
},
{
"binary_name": "linux-modules-5.4.0-1095-bluefield",
"binary_version": "5.4.0-1095.102"
},
{
"binary_name": "linux-tools-5.4.0-1095-bluefield",
"binary_version": "5.4.0-1095.102"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-bluefield",
"purl": "pkg:deb/ubuntu/linux-bluefield@5.4.0-1095.102?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1095.102"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1007.10",
"5.4.0-1011.14",
"5.4.0-1012.15",
"5.4.0-1013.16",
"5.4.0-1016.19",
"5.4.0-1019.22",
"5.4.0-1020.23",
"5.4.0-1021.24",
"5.4.0-1022.25",
"5.4.0-1023.26",
"5.4.0-1025.28",
"5.4.0-1026.29",
"5.4.0-1028.31",
"5.4.0-1030.33",
"5.4.0-1032.35",
"5.4.0-1035.38",
"5.4.0-1036.39",
"5.4.0-1040.44",
"5.4.0-1042.47",
"5.4.0-1044.49",
"5.4.0-1045.50",
"5.4.0-1046.51",
"5.4.0-1047.52",
"5.4.0-1049.55",
"5.4.0-1050.56",
"5.4.0-1054.60",
"5.4.0-1058.64",
"5.4.0-1059.65",
"5.4.0-1060.66",
"5.4.0-1062.68",
"5.4.0-1064.70",
"5.4.0-1065.71",
"5.4.0-1066.72",
"5.4.0-1068.74",
"5.4.0-1070.76",
"5.4.0-1071.77",
"5.4.0-1072.78",
"5.4.0-1073.79",
"5.4.0-1074.80",
"5.4.0-1075.81",
"5.4.0-1076.82",
"5.4.0-1077.83",
"5.4.0-1078.84",
"5.4.0-1079.85",
"5.4.0-1080.87",
"5.4.0-1081.88",
"5.4.0-1082.89",
"5.4.0-1083.90",
"5.4.0-1084.91",
"5.4.0-1085.92",
"5.4.0-1086.93",
"5.4.0-1087.94",
"5.4.0-1088.95",
"5.4.0-1089.96",
"5.4.0-1090.97",
"5.4.0-1091.98",
"5.4.0-1092.99",
"5.4.0-1093.100",
"5.4.0-1094.101"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1139-gcp",
"binary_version": "5.4.0-1139.148"
},
{
"binary_name": "linux-gcp-headers-5.4.0-1139",
"binary_version": "5.4.0-1139.148"
},
{
"binary_name": "linux-gcp-tools-5.4.0-1139",
"binary_version": "5.4.0-1139.148"
},
{
"binary_name": "linux-headers-5.4.0-1139-gcp",
"binary_version": "5.4.0-1139.148"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1139-gcp",
"binary_version": "5.4.0-1139.148"
},
{
"binary_name": "linux-modules-5.4.0-1139-gcp",
"binary_version": "5.4.0-1139.148"
},
{
"binary_name": "linux-modules-extra-5.4.0-1139-gcp",
"binary_version": "5.4.0-1139.148"
},
{
"binary_name": "linux-tools-5.4.0-1139-gcp",
"binary_version": "5.4.0-1139.148"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-gcp",
"purl": "pkg:deb/ubuntu/linux-gcp@5.4.0-1139.148?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1139.148"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.3.0-1004.4",
"5.3.0-1009.10",
"5.3.0-1011.12",
"5.4.0-1005.5",
"5.4.0-1007.7",
"5.4.0-1008.8",
"5.4.0-1009.9",
"5.4.0-1011.11",
"5.4.0-1015.15",
"5.4.0-1018.18",
"5.4.0-1019.19",
"5.4.0-1021.21",
"5.4.0-1022.22",
"5.4.0-1024.24",
"5.4.0-1025.25",
"5.4.0-1028.29",
"5.4.0-1029.31",
"5.4.0-1030.32",
"5.4.0-1032.34",
"5.4.0-1033.35",
"5.4.0-1034.37",
"5.4.0-1036.39",
"5.4.0-1037.40",
"5.4.0-1038.41",
"5.4.0-1040.43",
"5.4.0-1041.44",
"5.4.0-1042.45",
"5.4.0-1043.46",
"5.4.0-1044.47",
"5.4.0-1046.49",
"5.4.0-1049.53",
"5.4.0-1051.55",
"5.4.0-1052.56",
"5.4.0-1053.57",
"5.4.0-1055.59",
"5.4.0-1056.60",
"5.4.0-1057.61",
"5.4.0-1058.62",
"5.4.0-1059.63",
"5.4.0-1060.64",
"5.4.0-1062.66",
"5.4.0-1063.67",
"5.4.0-1064.68",
"5.4.0-1065.69",
"5.4.0-1067.71",
"5.4.0-1068.72",
"5.4.0-1069.73",
"5.4.0-1072.77",
"5.4.0-1073.78",
"5.4.0-1075.80",
"5.4.0-1078.84",
"5.4.0-1080.87",
"5.4.0-1083.91",
"5.4.0-1084.92",
"5.4.0-1086.94",
"5.4.0-1087.95",
"5.4.0-1089.97",
"5.4.0-1090.98",
"5.4.0-1092.101",
"5.4.0-1093.102",
"5.4.0-1096.105",
"5.4.0-1097.106",
"5.4.0-1098.107",
"5.4.0-1100.109",
"5.4.0-1101.110",
"5.4.0-1102.111",
"5.4.0-1103.112",
"5.4.0-1104.113",
"5.4.0-1105.114",
"5.4.0-1106.115",
"5.4.0-1107.116",
"5.4.0-1108.117",
"5.4.0-1109.118",
"5.4.0-1110.119",
"5.4.0-1111.120",
"5.4.0-1112.121",
"5.4.0-1113.122",
"5.4.0-1115.124",
"5.4.0-1116.125",
"5.4.0-1117.126",
"5.4.0-1118.127",
"5.4.0-1120.129",
"5.4.0-1121.130",
"5.4.0-1122.131",
"5.4.0-1123.132",
"5.4.0-1124.133",
"5.4.0-1125.134",
"5.4.0-1126.135",
"5.4.0-1127.136",
"5.4.0-1128.137",
"5.4.0-1129.138",
"5.4.0-1130.139",
"5.4.0-1131.140",
"5.4.0-1132.141",
"5.4.0-1133.142",
"5.4.0-1134.143",
"5.4.0-1135.144",
"5.4.0-1136.145",
"5.4.0-1137.146",
"5.4.0-1138.147"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1071-gcp",
"binary_version": "5.15.0-1071.79~20.04.1"
},
{
"binary_name": "linux-gcp-5.15-headers-5.15.0-1071",
"binary_version": "5.15.0-1071.79~20.04.1"
},
{
"binary_name": "linux-gcp-5.15-tools-5.15.0-1071",
"binary_version": "5.15.0-1071.79~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1071-gcp",
"binary_version": "5.15.0-1071.79~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1071-gcp",
"binary_version": "5.15.0-1071.79~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1071-gcp",
"binary_version": "5.15.0-1071.79~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1071-gcp",
"binary_version": "5.15.0-1071.79~20.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-1071-gcp",
"binary_version": "5.15.0-1071.79~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1071-gcp",
"binary_version": "5.15.0-1071.79~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-gcp-5.15",
"purl": "pkg:deb/ubuntu/linux-gcp-5.15@5.15.0-1071.79~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1071.79~20.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1006.9~20.04.1",
"5.15.0-1012.17~20.04.1",
"5.15.0-1013.18~20.04.1",
"5.15.0-1016.21~20.04.1",
"5.15.0-1017.23~20.04.2",
"5.15.0-1018.24~20.04.1",
"5.15.0-1021.28~20.04.1",
"5.15.0-1022.29~20.04.1",
"5.15.0-1025.32~20.04.2",
"5.15.0-1026.33~20.04.1",
"5.15.0-1027.34~20.04.1",
"5.15.0-1029.36~20.04.1",
"5.15.0-1030.37~20.04.1",
"5.15.0-1031.38~20.04.1",
"5.15.0-1032.40~20.04.1",
"5.15.0-1033.41~20.04.1",
"5.15.0-1034.42~20.04.1",
"5.15.0-1035.43~20.04.1",
"5.15.0-1036.44~20.04.1",
"5.15.0-1037.45~20.04.1",
"5.15.0-1038.46~20.04.1",
"5.15.0-1039.47~20.04.1",
"5.15.0-1040.48~20.04.1",
"5.15.0-1041.49~20.04.1",
"5.15.0-1042.50~20.04.1",
"5.15.0-1044.52~20.04.1",
"5.15.0-1045.53~20.04.2",
"5.15.0-1046.54~20.04.1",
"5.15.0-1047.55~20.04.1",
"5.15.0-1048.56~20.04.1",
"5.15.0-1049.57~20.04.1",
"5.15.0-1051.59~20.04.1",
"5.15.0-1052.60~20.04.1",
"5.15.0-1053.61~20.04.1",
"5.15.0-1054.62~20.04.1",
"5.15.0-1055.63~20.04.1",
"5.15.0-1058.66~20.04.1",
"5.15.0-1059.67~20.04.1",
"5.15.0-1060.68~20.04.1",
"5.15.0-1062.70~20.04.1",
"5.15.0-1065.73~20.04.1",
"5.15.0-1066.74~20.04.1",
"5.15.0-1067.75~20.04.1",
"5.15.0-1068.76~20.04.1",
"5.15.0-1069.77~20.04.1",
"5.15.0-1070.78~20.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1102-gkeop",
"binary_version": "5.4.0-1102.106"
},
{
"binary_name": "linux-cloud-tools-5.4.0-1102-gkeop",
"binary_version": "5.4.0-1102.106"
},
{
"binary_name": "linux-gkeop-cloud-tools-5.4.0-1102",
"binary_version": "5.4.0-1102.106"
},
{
"binary_name": "linux-gkeop-headers-5.4.0-1102",
"binary_version": "5.4.0-1102.106"
},
{
"binary_name": "linux-gkeop-source-5.4.0",
"binary_version": "5.4.0-1102.106"
},
{
"binary_name": "linux-gkeop-tools-5.4.0-1102",
"binary_version": "5.4.0-1102.106"
},
{
"binary_name": "linux-headers-5.4.0-1102-gkeop",
"binary_version": "5.4.0-1102.106"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1102-gkeop",
"binary_version": "5.4.0-1102.106"
},
{
"binary_name": "linux-modules-5.4.0-1102-gkeop",
"binary_version": "5.4.0-1102.106"
},
{
"binary_name": "linux-modules-extra-5.4.0-1102-gkeop",
"binary_version": "5.4.0-1102.106"
},
{
"binary_name": "linux-tools-5.4.0-1102-gkeop",
"binary_version": "5.4.0-1102.106"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-gkeop",
"purl": "pkg:deb/ubuntu/linux-gkeop@5.4.0-1102.106?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1102.106"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1008.9",
"5.4.0-1009.10",
"5.4.0-1010.11",
"5.4.0-1011.12",
"5.4.0-1012.13",
"5.4.0-1013.14",
"5.4.0-1014.15",
"5.4.0-1015.16",
"5.4.0-1016.17",
"5.4.0-1018.19",
"5.4.0-1021.22",
"5.4.0-1022.23",
"5.4.0-1023.24",
"5.4.0-1024.25",
"5.4.0-1025.26",
"5.4.0-1026.27",
"5.4.0-1027.28",
"5.4.0-1029.30",
"5.4.0-1031.32",
"5.4.0-1032.33",
"5.4.0-1033.34",
"5.4.0-1034.35",
"5.4.0-1036.37",
"5.4.0-1037.38",
"5.4.0-1038.39",
"5.4.0-1039.40",
"5.4.0-1040.41",
"5.4.0-1043.44",
"5.4.0-1046.48",
"5.4.0-1048.51",
"5.4.0-1049.52",
"5.4.0-1051.54",
"5.4.0-1052.55",
"5.4.0-1053.56",
"5.4.0-1054.57",
"5.4.0-1056.60",
"5.4.0-1057.61",
"5.4.0-1060.64",
"5.4.0-1061.65",
"5.4.0-1062.66",
"5.4.0-1064.68",
"5.4.0-1065.69",
"5.4.0-1066.70",
"5.4.0-1067.71",
"5.4.0-1068.72",
"5.4.0-1069.73",
"5.4.0-1070.74",
"5.4.0-1071.75",
"5.4.0-1072.76",
"5.4.0-1073.77",
"5.4.0-1074.78",
"5.4.0-1075.79",
"5.4.0-1076.80",
"5.4.0-1077.81",
"5.4.0-1078.82",
"5.4.0-1079.83",
"5.4.0-1080.84",
"5.4.0-1081.85",
"5.4.0-1083.87",
"5.4.0-1084.88",
"5.4.0-1085.89",
"5.4.0-1086.90",
"5.4.0-1087.91",
"5.4.0-1088.92",
"5.4.0-1089.93",
"5.4.0-1090.94",
"5.4.0-1091.95",
"5.4.0-1092.96",
"5.4.0-1093.97",
"5.4.0-1094.98",
"5.4.0-1095.99",
"5.4.0-1096.100",
"5.4.0-1097.101",
"5.4.0-1098.102",
"5.4.0-1099.103",
"5.4.0-1100.104",
"5.4.0-1101.105"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1055-gkeop",
"binary_version": "5.15.0-1055.62~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1055-gkeop",
"binary_version": "5.15.0-1055.62~20.04.1"
},
{
"binary_name": "linux-gkeop-5.15-cloud-tools-5.15.0-1055",
"binary_version": "5.15.0-1055.62~20.04.1"
},
{
"binary_name": "linux-gkeop-5.15-headers-5.15.0-1055",
"binary_version": "5.15.0-1055.62~20.04.1"
},
{
"binary_name": "linux-gkeop-5.15-tools-5.15.0-1055",
"binary_version": "5.15.0-1055.62~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1055-gkeop",
"binary_version": "5.15.0-1055.62~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1055-gkeop",
"binary_version": "5.15.0-1055.62~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1055-gkeop",
"binary_version": "5.15.0-1055.62~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1055-gkeop",
"binary_version": "5.15.0-1055.62~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1055-gkeop",
"binary_version": "5.15.0-1055.62~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-gkeop-5.15",
"purl": "pkg:deb/ubuntu/linux-gkeop-5.15@5.15.0-1055.62~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1055.62~20.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1003.5~20.04.2",
"5.15.0-1005.7~20.04.1",
"5.15.0-1007.10~20.04.1",
"5.15.0-1008.12~20.04.1",
"5.15.0-1011.15~20.04.2",
"5.15.0-1012.16~20.04.1",
"5.15.0-1013.17~20.04.1",
"5.15.0-1015.19~20.04.1",
"5.15.0-1016.21~20.04.1",
"5.15.0-1017.22~20.04.1",
"5.15.0-1018.23~20.04.1",
"5.15.0-1019.24~20.04.1",
"5.15.0-1020.25~20.04.1",
"5.15.0-1021.26~20.04.1",
"5.15.0-1022.27~20.04.1",
"5.15.0-1023.28~20.04.1",
"5.15.0-1024.29~20.04.1",
"5.15.0-1025.30~20.04.1",
"5.15.0-1026.31~20.04.1",
"5.15.0-1027.32~20.04.1",
"5.15.0-1028.33~20.04.1",
"5.15.0-1030.35~20.04.1",
"5.15.0-1031.37~20.04.1",
"5.15.0-1032.38~20.04.1",
"5.15.0-1033.39~20.04.1",
"5.15.0-1034.40~20.04.1",
"5.15.0-1035.41~20.04.1",
"5.15.0-1036.42~20.04.1",
"5.15.0-1037.43~20.04.1",
"5.15.0-1038.44~20.04.1",
"5.15.0-1039.45~20.04.1",
"5.15.0-1040.46~20.04.1",
"5.15.0-1043.50~20.04.1",
"5.15.0-1044.51~20.04.1",
"5.15.0-1045.52~20.04.1",
"5.15.0-1046.53~20.04.1",
"5.15.0-1047.54~20.04.1",
"5.15.0-1048.55~20.04.1",
"5.15.0-1049.56~20.04.1",
"5.15.0-1050.57~20.04.1",
"5.15.0-1051.58~20.04.1",
"5.15.0-1052.59~20.04.1",
"5.15.0-1053.60~20.04.1",
"5.15.0-1054.61~20.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-125-generic",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.15.0-125-generic-64k",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.15.0-125-generic-lpae",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-125-generic",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-125-generic",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-125-generic-64k",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-125-generic-lpae",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-hwe-5.15-cloud-tools-5.15.0-125",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-hwe-5.15-cloud-tools-common",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-hwe-5.15-headers-5.15.0-125",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-hwe-5.15-source-5.15.0",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-hwe-5.15-tools-5.15.0-125",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-hwe-5.15-tools-common",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-hwe-5.15-tools-host",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-image-5.15.0-125-generic",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-image-5.15.0-125-generic-lpae",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-125-generic",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-125-generic-64k",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-125-generic",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-125-generic-64k",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-125-generic-lpae",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-125-generic",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-125-generic",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-125-generic",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-125-generic-64k",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-125-generic-lpae",
"binary_version": "5.15.0-125.135~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-hwe-5.15",
"purl": "pkg:deb/ubuntu/linux-hwe-5.15@5.15.0-125.135~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-125.135~20.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-33.34~20.04.1",
"5.15.0-41.44~20.04.1",
"5.15.0-43.46~20.04.1",
"5.15.0-46.49~20.04.1",
"5.15.0-48.54~20.04.1",
"5.15.0-50.56~20.04.1",
"5.15.0-52.58~20.04.1",
"5.15.0-53.59~20.04.1",
"5.15.0-56.62~20.04.1",
"5.15.0-57.63~20.04.1",
"5.15.0-58.64~20.04.1",
"5.15.0-60.66~20.04.1",
"5.15.0-67.74~20.04.1",
"5.15.0-69.76~20.04.1",
"5.15.0-70.77~20.04.1",
"5.15.0-71.78~20.04.1",
"5.15.0-72.79~20.04.1",
"5.15.0-73.80~20.04.1",
"5.15.0-75.82~20.04.1",
"5.15.0-76.83~20.04.1",
"5.15.0-78.85~20.04.1",
"5.15.0-79.86~20.04.2",
"5.15.0-82.91~20.04.1",
"5.15.0-83.92~20.04.1",
"5.15.0-84.93~20.04.1",
"5.15.0-86.96~20.04.1",
"5.15.0-87.97~20.04.1",
"5.15.0-88.98~20.04.1",
"5.15.0-89.99~20.04.1",
"5.15.0-91.101~20.04.1",
"5.15.0-92.102~20.04.1",
"5.15.0-94.104~20.04.1",
"5.15.0-97.107~20.04.1",
"5.15.0-100.110~20.04.1",
"5.15.0-101.111~20.04.1",
"5.15.0-102.112~20.04.1",
"5.15.0-105.115~20.04.1",
"5.15.0-106.116~20.04.1",
"5.15.0-107.117~20.04.1",
"5.15.0-113.123~20.04.1",
"5.15.0-116.126~20.04.1",
"5.15.0-117.127~20.04.1",
"5.15.0-118.128~20.04.1",
"5.15.0-119.129~20.04.1",
"5.15.0-121.131~20.04.1",
"5.15.0-122.132~20.04.1",
"5.15.0-124.134~20.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1082-ibm",
"binary_version": "5.4.0-1082.87"
},
{
"binary_name": "linux-headers-5.4.0-1082-ibm",
"binary_version": "5.4.0-1082.87"
},
{
"binary_name": "linux-ibm-cloud-tools-common",
"binary_version": "5.4.0-1082.87"
},
{
"binary_name": "linux-ibm-headers-5.4.0-1082",
"binary_version": "5.4.0-1082.87"
},
{
"binary_name": "linux-ibm-source-5.4.0",
"binary_version": "5.4.0-1082.87"
},
{
"binary_name": "linux-ibm-tools-5.4.0-1082",
"binary_version": "5.4.0-1082.87"
},
{
"binary_name": "linux-ibm-tools-common",
"binary_version": "5.4.0-1082.87"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1082-ibm",
"binary_version": "5.4.0-1082.87"
},
{
"binary_name": "linux-modules-5.4.0-1082-ibm",
"binary_version": "5.4.0-1082.87"
},
{
"binary_name": "linux-modules-extra-5.4.0-1082-ibm",
"binary_version": "5.4.0-1082.87"
},
{
"binary_name": "linux-tools-5.4.0-1082-ibm",
"binary_version": "5.4.0-1082.87"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-ibm",
"purl": "pkg:deb/ubuntu/linux-ibm@5.4.0-1082.87?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1082.87"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1003.4",
"5.4.0-1004.5",
"5.4.0-1005.6",
"5.4.0-1006.7",
"5.4.0-1007.8",
"5.4.0-1008.9",
"5.4.0-1010.11",
"5.4.0-1012.13",
"5.4.0-1013.14",
"5.4.0-1014.15",
"5.4.0-1015.16",
"5.4.0-1017.19",
"5.4.0-1018.20",
"5.4.0-1019.21",
"5.4.0-1020.22",
"5.4.0-1021.23",
"5.4.0-1023.25",
"5.4.0-1026.29",
"5.4.0-1028.32",
"5.4.0-1029.33",
"5.4.0-1031.35",
"5.4.0-1032.36",
"5.4.0-1033.37",
"5.4.0-1034.38",
"5.4.0-1036.41",
"5.4.0-1037.42",
"5.4.0-1040.45",
"5.4.0-1041.46",
"5.4.0-1042.47",
"5.4.0-1044.49",
"5.4.0-1045.50",
"5.4.0-1046.51",
"5.4.0-1047.52",
"5.4.0-1048.53",
"5.4.0-1049.54",
"5.4.0-1050.55",
"5.4.0-1051.56",
"5.4.0-1052.57",
"5.4.0-1053.58",
"5.4.0-1054.59",
"5.4.0-1056.61",
"5.4.0-1057.62",
"5.4.0-1058.63",
"5.4.0-1059.64",
"5.4.0-1060.65",
"5.4.0-1061.66",
"5.4.0-1063.68",
"5.4.0-1064.69",
"5.4.0-1065.70",
"5.4.0-1066.71",
"5.4.0-1067.72",
"5.4.0-1068.73",
"5.4.0-1069.74",
"5.4.0-1070.75",
"5.4.0-1071.76",
"5.4.0-1072.77",
"5.4.0-1073.78",
"5.4.0-1074.79",
"5.4.0-1075.80",
"5.4.0-1076.81",
"5.4.0-1077.82",
"5.4.0-1078.83",
"5.4.0-1079.84",
"5.4.0-1080.85",
"5.4.0-1081.86"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1065-ibm",
"binary_version": "5.15.0-1065.68~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1065-ibm",
"binary_version": "5.15.0-1065.68~20.04.1"
},
{
"binary_name": "linux-ibm-5.15-headers-5.15.0-1065",
"binary_version": "5.15.0-1065.68~20.04.1"
},
{
"binary_name": "linux-ibm-5.15-source-5.15.0",
"binary_version": "5.15.0-1065.68~20.04.1"
},
{
"binary_name": "linux-ibm-5.15-tools-5.15.0-1065",
"binary_version": "5.15.0-1065.68~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1065-ibm",
"binary_version": "5.15.0-1065.68~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1065-ibm",
"binary_version": "5.15.0-1065.68~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1065-ibm",
"binary_version": "5.15.0-1065.68~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1065-ibm",
"binary_version": "5.15.0-1065.68~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-ibm-5.15",
"purl": "pkg:deb/ubuntu/linux-ibm-5.15@5.15.0-1065.68~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1065.68~20.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1033.36~20.04.1",
"5.15.0-1034.37~20.04.1",
"5.15.0-1035.38~20.04.1",
"5.15.0-1036.39~20.04.1",
"5.15.0-1037.40~20.04.1",
"5.15.0-1038.41~20.04.1",
"5.15.0-1040.43~20.04.1",
"5.15.0-1041.44~20.04.1",
"5.15.0-1042.45~20.04.1",
"5.15.0-1043.46~20.04.1",
"5.15.0-1044.47~20.04.1",
"5.15.0-1045.48~20.04.1",
"5.15.0-1046.49~20.04.1",
"5.15.0-1047.50~20.04.1",
"5.15.0-1048.51~20.04.1",
"5.15.0-1049.52~20.04.1",
"5.15.0-1050.53~20.04.1",
"5.15.0-1053.56~20.04.1",
"5.15.0-1054.57~20.04.1",
"5.15.0-1055.58~20.04.1",
"5.15.0-1057.60~20.04.1",
"5.15.0-1058.61~20.04.1",
"5.15.0-1059.62~20.04.1",
"5.15.0-1060.63~20.04.1",
"5.15.0-1061.64~20.04.1",
"5.15.0-1062.65~20.04.1",
"5.15.0-1063.66~20.04.1",
"5.15.0-1064.67~20.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-intel-iotg-5.15-cloud-tools-5.15.0-1067",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-intel-iotg-5.15-cloud-tools-common",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-intel-iotg-5.15-headers-5.15.0-1067",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-intel-iotg-5.15-tools-5.15.0-1067",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-intel-iotg-5.15-tools-common",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-intel-iotg-5.15-tools-host",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-intel-iotg-5.15",
"purl": "pkg:deb/ubuntu/linux-intel-iotg-5.15@5.15.0-1067.73~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1067.73~20.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1003.5~20.04.1",
"5.15.0-1008.11~20.04.1",
"5.15.0-1010.14~20.04.1",
"5.15.0-1015.20~20.04.2",
"5.15.0-1016.21~20.04.1",
"5.15.0-1017.22~20.04.1",
"5.15.0-1018.23~20.04.1",
"5.15.0-1021.26~20.04.1",
"5.15.0-1023.28~20.04.1",
"5.15.0-1025.30~20.04.1",
"5.15.0-1026.31~20.04.1",
"5.15.0-1027.32~20.04.1",
"5.15.0-1030.35~20.04.1",
"5.15.0-1031.36~20.04.1",
"5.15.0-1033.38~20.04.1",
"5.15.0-1034.39~20.04.1",
"5.15.0-1036.41~20.04.1",
"5.15.0-1037.42~20.04.1",
"5.15.0-1038.43~20.04.1",
"5.15.0-1040.46~20.04.1",
"5.15.0-1043.49~20.04.1",
"5.15.0-1045.51~20.04.1",
"5.15.0-1046.52~20.04.1",
"5.15.0-1048.54~20.04.1",
"5.15.0-1049.55~20.04.1",
"5.15.0-1050.56~20.04.1",
"5.15.0-1051.57~20.04.1",
"5.15.0-1052.58~20.04.1",
"5.15.0-1055.61~20.04.1",
"5.15.0-1058.64~20.04.1",
"5.15.0-1059.65~20.04.1",
"5.15.0-1060.66~20.04.1",
"5.15.0-1061.67~20.04.1",
"5.15.0-1062.68~20.04.1",
"5.15.0-1063.69~20.04.1",
"5.15.0-1064.70~20.04.1",
"5.15.0-1065.71~20.04.1",
"5.15.0-1066.72~20.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1044-iot",
"binary_version": "5.4.0-1044.45"
},
{
"binary_name": "linux-headers-5.4.0-1044-iot",
"binary_version": "5.4.0-1044.45"
},
{
"binary_name": "linux-image-5.4.0-1044-iot",
"binary_version": "5.4.0-1044.45"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1044-iot",
"binary_version": "5.4.0-1044.45"
},
{
"binary_name": "linux-iot-headers-5.4.0-1044",
"binary_version": "5.4.0-1044.45"
},
{
"binary_name": "linux-iot-tools-5.4.0-1044",
"binary_version": "5.4.0-1044.45"
},
{
"binary_name": "linux-modules-5.4.0-1044-iot",
"binary_version": "5.4.0-1044.45"
},
{
"binary_name": "linux-tools-5.4.0-1044-iot",
"binary_version": "5.4.0-1044.45"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-iot",
"purl": "pkg:deb/ubuntu/linux-iot@5.4.0-1044.45?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1044.45"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1001.3",
"5.4.0-1004.6",
"5.4.0-1005.7",
"5.4.0-1006.8",
"5.4.0-1009.11",
"5.4.0-1010.12",
"5.4.0-1011.13",
"5.4.0-1012.14",
"5.4.0-1013.15",
"5.4.0-1014.16",
"5.4.0-1017.18",
"5.4.0-1018.19",
"5.4.0-1019.20",
"5.4.0-1021.22",
"5.4.0-1022.23",
"5.4.0-1023.24",
"5.4.0-1024.25",
"5.4.0-1025.26",
"5.4.0-1026.27",
"5.4.0-1028.29",
"5.4.0-1029.30",
"5.4.0-1030.31",
"5.4.0-1031.32",
"5.4.0-1032.33",
"5.4.0-1033.34",
"5.4.0-1034.35",
"5.4.0-1035.36",
"5.4.0-1036.37",
"5.4.0-1037.38",
"5.4.0-1038.39",
"5.4.0-1039.40",
"5.4.0-1040.41",
"5.4.0-1041.42",
"5.4.0-1042.43",
"5.4.0-1043.44"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1123-kvm",
"binary_version": "5.4.0-1123.131"
},
{
"binary_name": "linux-headers-5.4.0-1123-kvm",
"binary_version": "5.4.0-1123.131"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1123-kvm",
"binary_version": "5.4.0-1123.131"
},
{
"binary_name": "linux-kvm-headers-5.4.0-1123",
"binary_version": "5.4.0-1123.131"
},
{
"binary_name": "linux-kvm-tools-5.4.0-1123",
"binary_version": "5.4.0-1123.131"
},
{
"binary_name": "linux-modules-5.4.0-1123-kvm",
"binary_version": "5.4.0-1123.131"
},
{
"binary_name": "linux-tools-5.4.0-1123-kvm",
"binary_version": "5.4.0-1123.131"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-kvm",
"purl": "pkg:deb/ubuntu/linux-kvm@5.4.0-1123.131?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1123.131"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.3.0-1003.3",
"5.3.0-1008.9",
"5.3.0-1009.10",
"5.4.0-1004.4",
"5.4.0-1006.6",
"5.4.0-1007.7",
"5.4.0-1008.8",
"5.4.0-1009.9",
"5.4.0-1011.11",
"5.4.0-1015.15",
"5.4.0-1018.18",
"5.4.0-1020.20",
"5.4.0-1021.21",
"5.4.0-1023.23",
"5.4.0-1024.24",
"5.4.0-1026.27",
"5.4.0-1028.29",
"5.4.0-1030.31",
"5.4.0-1031.32",
"5.4.0-1032.33",
"5.4.0-1033.34",
"5.4.0-1034.35",
"5.4.0-1036.37",
"5.4.0-1037.38",
"5.4.0-1038.39",
"5.4.0-1039.40",
"5.4.0-1040.41",
"5.4.0-1041.42",
"5.4.0-1044.46",
"5.4.0-1045.47",
"5.4.0-1046.48",
"5.4.0-1047.49",
"5.4.0-1048.50",
"5.4.0-1049.51",
"5.4.0-1050.52",
"5.4.0-1051.53",
"5.4.0-1053.55",
"5.4.0-1054.56",
"5.4.0-1055.57",
"5.4.0-1056.58",
"5.4.0-1058.61",
"5.4.0-1059.62",
"5.4.0-1061.64",
"5.4.0-1062.65",
"5.4.0-1063.66",
"5.4.0-1065.68",
"5.4.0-1068.72",
"5.4.0-1070.75",
"5.4.0-1071.76",
"5.4.0-1073.78",
"5.4.0-1074.79",
"5.4.0-1075.80",
"5.4.0-1076.81",
"5.4.0-1078.84",
"5.4.0-1079.85",
"5.4.0-1082.88",
"5.4.0-1083.89",
"5.4.0-1084.90",
"5.4.0-1086.92",
"5.4.0-1087.93",
"5.4.0-1088.94",
"5.4.0-1089.95",
"5.4.0-1090.96",
"5.4.0-1091.97",
"5.4.0-1092.98",
"5.4.0-1093.99",
"5.4.0-1094.100",
"5.4.0-1095.101",
"5.4.0-1096.102",
"5.4.0-1097.103",
"5.4.0-1098.104",
"5.4.0-1099.105",
"5.4.0-1100.106",
"5.4.0-1101.107",
"5.4.0-1102.108",
"5.4.0-1103.110",
"5.4.0-1104.111",
"5.4.0-1105.112",
"5.4.0-1106.113",
"5.4.0-1107.114",
"5.4.0-1108.115",
"5.4.0-1109.116",
"5.4.0-1110.117",
"5.4.0-1111.118",
"5.4.0-1112.119",
"5.4.0-1113.120",
"5.4.0-1114.121",
"5.4.0-1115.122",
"5.4.0-1116.123",
"5.4.0-1117.124",
"5.4.0-1118.125",
"5.4.0-1119.127",
"5.4.0-1120.128",
"5.4.0-1121.129",
"5.4.0-1122.130"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-125-lowlatency",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.15.0-125-lowlatency-64k",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-125-lowlatency",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-125-lowlatency",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-125-lowlatency-64k",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-125-lowlatency",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-125-lowlatency-64k",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-5.15-cloud-tools-5.15.0-125",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-5.15-cloud-tools-common",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-5.15-headers-5.15.0-125",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-5.15-tools-5.15.0-125",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-5.15-tools-common",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-5.15-tools-host",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-125-lowlatency",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-125-lowlatency-64k",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-125-lowlatency",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-125-lowlatency",
"binary_version": "5.15.0-125.135~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-125-lowlatency-64k",
"binary_version": "5.15.0-125.135~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-lowlatency-hwe-5.15",
"purl": "pkg:deb/ubuntu/linux-lowlatency-hwe-5.15@5.15.0-125.135~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-125.135~20.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-33.34~20.04.1",
"5.15.0-42.45~20.04.1",
"5.15.0-43.46~20.04.1",
"5.15.0-46.49~20.04.1",
"5.15.0-48.54~20.04.1",
"5.15.0-50.56~20.04.1",
"5.15.0-52.58~20.04.1",
"5.15.0-53.59~20.04.1",
"5.15.0-56.62~20.04.1",
"5.15.0-58.64~20.04.1",
"5.15.0-60.66~20.04.1",
"5.15.0-67.74~20.04.1",
"5.15.0-69.76~20.04.1",
"5.15.0-70.77~20.04.1",
"5.15.0-71.78~20.04.1",
"5.15.0-72.79~20.04.1",
"5.15.0-73.80~20.04.1",
"5.15.0-75.82~20.04.1",
"5.15.0-76.83~20.04.1",
"5.15.0-78.85~20.04.1",
"5.15.0-79.88~20.04.1",
"5.15.0-82.91~20.04.1",
"5.15.0-83.92~20.04.1",
"5.15.0-84.93~20.04.1",
"5.15.0-86.95~20.04.1",
"5.15.0-87.96~20.04.1",
"5.15.0-88.98~20.04.1",
"5.15.0-89.99~20.04.1",
"5.15.0-91.101~20.04.1",
"5.15.0-92.102~20.04.1",
"5.15.0-94.104~20.04.1",
"5.15.0-97.107~20.04.1",
"5.15.0-100.110~20.04.1",
"5.15.0-101.111~20.04.1",
"5.15.0-102.112~20.04.1",
"5.15.0-105.115~20.04.1",
"5.15.0-106.116~20.04.1",
"5.15.0-107.117~20.04.1",
"5.15.0-110.120~20.04.1",
"5.15.0-113.123~20.04.1",
"5.15.0-116.126~20.04.1",
"5.15.0-117.127~20.04.1",
"5.15.0-118.128~20.04.1",
"5.15.0-119.129~20.04.1",
"5.15.0-121.131~20.04.1",
"5.15.0-122.132~20.04.1",
"5.15.0-124.134~20.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1032-nvidia-tegra",
"binary_version": "5.15.0-1032.32~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.15.0-1032-nvidia-tegra-rt",
"binary_version": "5.15.0-1032.32~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1032-nvidia-tegra",
"binary_version": "5.15.0-1032.32~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1032-nvidia-tegra-rt",
"binary_version": "5.15.0-1032.32~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1032-nvidia-tegra",
"binary_version": "5.15.0-1032.32~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1032-nvidia-tegra-rt",
"binary_version": "5.15.0-1032.32~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1032-nvidia-tegra",
"binary_version": "5.15.0-1032.32~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1032-nvidia-tegra-rt",
"binary_version": "5.15.0-1032.32~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1032-nvidia-tegra",
"binary_version": "5.15.0-1032.32~20.04.1"
},
{
"binary_name": "linux-nvidia-tegra-5.15-headers-5.15.0-1032",
"binary_version": "5.15.0-1032.32~20.04.1"
},
{
"binary_name": "linux-nvidia-tegra-5.15-tools-5.15.0-1032",
"binary_version": "5.15.0-1032.32~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1032-nvidia-tegra",
"binary_version": "5.15.0-1032.32~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1032-nvidia-tegra-rt",
"binary_version": "5.15.0-1032.32~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-nvidia-tegra-5.15",
"purl": "pkg:deb/ubuntu/linux-nvidia-tegra-5.15@5.15.0-1032.32~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1032.32~20.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1009.9~20.04.1",
"5.15.0-1010.10~20.04.1",
"5.15.0-1012.12~20.04.1",
"5.15.0-1014.14~20.04.1",
"5.15.0-1015.15~20.04.1",
"5.15.0-1016.16~20.04.1",
"5.15.0-1017.17~20.04.1",
"5.15.0-1018.18~20.04.1",
"5.15.0-1019.19~20.04.1",
"5.15.0-1020.20~20.04.1",
"5.15.0-1022.22~20.04.1",
"5.15.0-1025.25~20.04.1",
"5.15.0-1027.27~20.04.1",
"5.15.0-1030.30~20.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1134-oracle",
"binary_version": "5.4.0-1134.143"
},
{
"binary_name": "linux-headers-5.4.0-1134-oracle",
"binary_version": "5.4.0-1134.143"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1134-oracle",
"binary_version": "5.4.0-1134.143"
},
{
"binary_name": "linux-modules-5.4.0-1134-oracle",
"binary_version": "5.4.0-1134.143"
},
{
"binary_name": "linux-modules-extra-5.4.0-1134-oracle",
"binary_version": "5.4.0-1134.143"
},
{
"binary_name": "linux-oracle-headers-5.4.0-1134",
"binary_version": "5.4.0-1134.143"
},
{
"binary_name": "linux-oracle-tools-5.4.0-1134",
"binary_version": "5.4.0-1134.143"
},
{
"binary_name": "linux-tools-5.4.0-1134-oracle",
"binary_version": "5.4.0-1134.143"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-oracle",
"purl": "pkg:deb/ubuntu/linux-oracle@5.4.0-1134.143?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1134.143"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.3.0-1002.2",
"5.3.0-1007.8",
"5.3.0-1008.9",
"5.4.0-1005.5",
"5.4.0-1007.7",
"5.4.0-1008.8",
"5.4.0-1009.9",
"5.4.0-1011.11",
"5.4.0-1015.15",
"5.4.0-1018.18",
"5.4.0-1019.19",
"5.4.0-1021.21",
"5.4.0-1022.22",
"5.4.0-1024.24",
"5.4.0-1025.25",
"5.4.0-1028.29",
"5.4.0-1029.31",
"5.4.0-1030.32",
"5.4.0-1032.34",
"5.4.0-1034.36",
"5.4.0-1035.38",
"5.4.0-1037.40",
"5.4.0-1038.41",
"5.4.0-1039.42",
"5.4.0-1041.44",
"5.4.0-1042.45",
"5.4.0-1043.46",
"5.4.0-1045.49",
"5.4.0-1046.50",
"5.4.0-1048.52",
"5.4.0-1049.53",
"5.4.0-1052.56",
"5.4.0-1053.57",
"5.4.0-1054.58",
"5.4.0-1055.59",
"5.4.0-1056.60",
"5.4.0-1057.61",
"5.4.0-1058.62",
"5.4.0-1059.63",
"5.4.0-1061.65",
"5.4.0-1062.66",
"5.4.0-1063.67",
"5.4.0-1064.68",
"5.4.0-1066.71",
"5.4.0-1067.72",
"5.4.0-1069.75",
"5.4.0-1070.76",
"5.4.0-1071.77",
"5.4.0-1073.79",
"5.4.0-1076.83",
"5.4.0-1078.86",
"5.4.0-1079.87",
"5.4.0-1081.89",
"5.4.0-1082.90",
"5.4.0-1083.91",
"5.4.0-1084.92",
"5.4.0-1086.95",
"5.4.0-1087.96",
"5.4.0-1090.99",
"5.4.0-1091.100",
"5.4.0-1092.101",
"5.4.0-1093.102",
"5.4.0-1094.103",
"5.4.0-1097.106",
"5.4.0-1098.107",
"5.4.0-1099.108",
"5.4.0-1100.109",
"5.4.0-1101.110",
"5.4.0-1102.111",
"5.4.0-1103.112",
"5.4.0-1104.113",
"5.4.0-1105.114",
"5.4.0-1106.115",
"5.4.0-1107.116",
"5.4.0-1108.117",
"5.4.0-1109.118",
"5.4.0-1110.119",
"5.4.0-1111.120",
"5.4.0-1112.121",
"5.4.0-1113.122",
"5.4.0-1115.124",
"5.4.0-1116.125",
"5.4.0-1117.126",
"5.4.0-1118.127",
"5.4.0-1119.128",
"5.4.0-1120.129",
"5.4.0-1121.130",
"5.4.0-1122.131",
"5.4.0-1123.132",
"5.4.0-1124.133",
"5.4.0-1125.134",
"5.4.0-1126.135",
"5.4.0-1127.136",
"5.4.0-1129.138",
"5.4.0-1130.139",
"5.4.0-1131.140",
"5.4.0-1132.141",
"5.4.0-1133.142"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1070-oracle",
"binary_version": "5.15.0-1070.76~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1070-oracle",
"binary_version": "5.15.0-1070.76~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1070-oracle",
"binary_version": "5.15.0-1070.76~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1070-oracle",
"binary_version": "5.15.0-1070.76~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1070-oracle",
"binary_version": "5.15.0-1070.76~20.04.1"
},
{
"binary_name": "linux-oracle-5.15-headers-5.15.0-1070",
"binary_version": "5.15.0-1070.76~20.04.1"
},
{
"binary_name": "linux-oracle-5.15-tools-5.15.0-1070",
"binary_version": "5.15.0-1070.76~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1070-oracle",
"binary_version": "5.15.0-1070.76~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-oracle-5.15",
"purl": "pkg:deb/ubuntu/linux-oracle-5.15@5.15.0-1070.76~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1070.76~20.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1007.9~20.04.1",
"5.15.0-1013.17~20.04.1",
"5.15.0-1016.20~20.04.1",
"5.15.0-1017.22~20.04.1",
"5.15.0-1018.23~20.04.1",
"5.15.0-1019.24~20.04.1",
"5.15.0-1021.27~20.04.1",
"5.15.0-1022.28~20.04.1",
"5.15.0-1025.31~20.04.2",
"5.15.0-1027.33~20.04.1",
"5.15.0-1029.35~20.04.1",
"5.15.0-1030.36~20.04.1",
"5.15.0-1032.38~20.04.1",
"5.15.0-1033.39~20.04.1",
"5.15.0-1034.40~20.04.1",
"5.15.0-1035.41~20.04.1",
"5.15.0-1036.42~20.04.1",
"5.15.0-1037.43~20.04.1",
"5.15.0-1038.44~20.04.1",
"5.15.0-1039.45~20.04.1",
"5.15.0-1040.46~20.04.1",
"5.15.0-1041.47~20.04.1",
"5.15.0-1042.48~20.04.1",
"5.15.0-1044.50~20.04.1",
"5.15.0-1045.51~20.04.1",
"5.15.0-1046.52~20.04.1",
"5.15.0-1047.53~20.04.1",
"5.15.0-1048.54~20.04.1",
"5.15.0-1049.55~20.04.1",
"5.15.0-1050.56~20.04.1",
"5.15.0-1051.57~20.04.1",
"5.15.0-1052.58~20.04.1",
"5.15.0-1053.59~20.04.1",
"5.15.0-1054.60~20.04.1",
"5.15.0-1055.61~20.04.1",
"5.15.0-1058.64~20.04.1",
"5.15.0-1059.65~20.04.1",
"5.15.0-1061.67~20.04.1",
"5.15.0-1062.68~20.04.1",
"5.15.0-1063.69~20.04.1",
"5.15.0-1065.71~20.04.1",
"5.15.0-1066.72~20.04.1",
"5.15.0-1067.73~20.04.1",
"5.15.0-1068.74~20.04.1",
"5.15.0-1069.75~20.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1119-raspi",
"binary_version": "5.4.0-1119.131"
},
{
"binary_name": "linux-headers-5.4.0-1119-raspi",
"binary_version": "5.4.0-1119.131"
},
{
"binary_name": "linux-image-5.4.0-1119-raspi",
"binary_version": "5.4.0-1119.131"
},
{
"binary_name": "linux-modules-5.4.0-1119-raspi",
"binary_version": "5.4.0-1119.131"
},
{
"binary_name": "linux-raspi-headers-5.4.0-1119",
"binary_version": "5.4.0-1119.131"
},
{
"binary_name": "linux-raspi-tools-5.4.0-1119",
"binary_version": "5.4.0-1119.131"
},
{
"binary_name": "linux-tools-5.4.0-1119-raspi",
"binary_version": "5.4.0-1119.131"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-raspi",
"purl": "pkg:deb/ubuntu/linux-raspi@5.4.0-1119.131?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1119.131"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1007.7",
"5.4.0-1008.8",
"5.4.0-1011.11",
"5.4.0-1012.12",
"5.4.0-1013.13",
"5.4.0-1015.15",
"5.4.0-1016.17",
"5.4.0-1018.20",
"5.4.0-1019.21",
"5.4.0-1021.24",
"5.4.0-1022.25",
"5.4.0-1023.26",
"5.4.0-1025.28",
"5.4.0-1026.29",
"5.4.0-1028.31",
"5.4.0-1029.32",
"5.4.0-1030.33",
"5.4.0-1032.35",
"5.4.0-1033.36",
"5.4.0-1034.37",
"5.4.0-1035.38",
"5.4.0-1036.39",
"5.4.0-1038.41",
"5.4.0-1041.45",
"5.4.0-1042.46",
"5.4.0-1043.47",
"5.4.0-1044.48",
"5.4.0-1045.49",
"5.4.0-1046.50",
"5.4.0-1047.52",
"5.4.0-1048.53",
"5.4.0-1050.56",
"5.4.0-1052.58",
"5.4.0-1053.60",
"5.4.0-1055.62",
"5.4.0-1056.63",
"5.4.0-1058.65",
"5.4.0-1059.67",
"5.4.0-1060.68",
"5.4.0-1062.70",
"5.4.0-1065.75",
"5.4.0-1066.76",
"5.4.0-1068.78",
"5.4.0-1069.79",
"5.4.0-1070.80",
"5.4.0-1071.81",
"5.4.0-1073.84",
"5.4.0-1074.85",
"5.4.0-1077.88",
"5.4.0-1078.89",
"5.4.0-1079.90",
"5.4.0-1080.91",
"5.4.0-1081.92",
"5.4.0-1082.93",
"5.4.0-1083.94",
"5.4.0-1084.95",
"5.4.0-1085.96",
"5.4.0-1086.97",
"5.4.0-1088.99",
"5.4.0-1089.100",
"5.4.0-1090.101",
"5.4.0-1091.102",
"5.4.0-1092.103",
"5.4.0-1093.104",
"5.4.0-1094.105",
"5.4.0-1095.106",
"5.4.0-1096.107",
"5.4.0-1097.109",
"5.4.0-1098.110",
"5.4.0-1100.112",
"5.4.0-1101.113",
"5.4.0-1102.114",
"5.4.0-1103.115",
"5.4.0-1104.116",
"5.4.0-1105.117",
"5.4.0-1106.118",
"5.4.0-1107.119",
"5.4.0-1108.120",
"5.4.0-1109.121",
"5.4.0-1110.122",
"5.4.0-1111.123",
"5.4.0-1112.124",
"5.4.0-1113.125",
"5.4.0-1114.126",
"5.4.0-1115.127",
"5.4.0-1116.128",
"5.4.0-1117.129",
"5.4.0-1118.130"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1068-generic",
"binary_version": "5.15.0-1068.72~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1068-generic",
"binary_version": "5.15.0-1068.72~20.04.1"
},
{
"binary_name": "linux-image-5.15.0-1068-generic",
"binary_version": "5.15.0-1068.72~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1068-generic",
"binary_version": "5.15.0-1068.72~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1068-generic",
"binary_version": "5.15.0-1068.72~20.04.1"
},
{
"binary_name": "linux-riscv-5.15-headers-5.15.0-1068",
"binary_version": "5.15.0-1068.72~20.04.1"
},
{
"binary_name": "linux-riscv-5.15-tools-5.15.0-1068",
"binary_version": "5.15.0-1068.72~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1068-generic",
"binary_version": "5.15.0-1068.72~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-riscv-5.15",
"purl": "pkg:deb/ubuntu/linux-riscv-5.15@5.15.0-1068.72~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1068.72~20.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1015.17~20.04.1",
"5.15.0-1017.19~20.04.1",
"5.15.0-1018.21~20.04.1",
"5.15.0-1019.22~20.04.1",
"5.15.0-1022.26~20.04.1",
"5.15.0-1023.27~20.04.1",
"5.15.0-1026.30~20.04.2",
"5.15.0-1027.31~20.04.1",
"5.15.0-1028.32~20.04.1",
"5.15.0-1029.33~20.04.1",
"5.15.0-1030.34~20.04.1",
"5.15.0-1031.35~20.04.1",
"5.15.0-1032.36~20.04.1",
"5.15.0-1033.37~20.04.1",
"5.15.0-1034.38~20.04.1",
"5.15.0-1035.39~20.04.1",
"5.15.0-1036.40~20.04.2",
"5.15.0-1037.41~20.04.2",
"5.15.0-1038.42~20.04.2",
"5.15.0-1039.43~20.04.2",
"5.15.0-1040.44~20.04.3",
"5.15.0-1041.45~20.04.1",
"5.15.0-1043.47~20.04.1",
"5.15.0-1044.48~20.04.1",
"5.15.0-1045.49~20.04.1",
"5.15.0-1046.50~20.04.1",
"5.15.0-1047.51~20.04.1",
"5.15.0-1048.52~20.04.1",
"5.15.0-1049.53~20.04.2",
"5.15.0-1050.54~20.04.1",
"5.15.0-1051.55~20.04.1",
"5.15.0-1052.56~20.04.1",
"5.15.0-1053.57~20.04.1",
"5.15.0-1056.60~20.04.1",
"5.15.0-1057.61~20.04.1",
"5.15.0-1058.62~20.04.1",
"5.15.0-1059.63~20.04.1",
"5.15.0-1060.64~20.04.1",
"5.15.0-1061.65~20.04.1",
"5.15.0-1062.66~20.04.1",
"5.15.0-1063.67~20.04.1",
"5.15.0-1064.68~20.04.1",
"5.15.0-1065.69~20.04.1",
"5.15.0-1066.70~20.04.1",
"5.15.0-1067.71~20.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1054-xilinx-zynqmp",
"binary_version": "5.4.0-1054.58"
},
{
"binary_name": "linux-headers-5.4.0-1054-xilinx-zynqmp",
"binary_version": "5.4.0-1054.58"
},
{
"binary_name": "linux-image-5.4.0-1054-xilinx-zynqmp",
"binary_version": "5.4.0-1054.58"
},
{
"binary_name": "linux-modules-5.4.0-1054-xilinx-zynqmp",
"binary_version": "5.4.0-1054.58"
},
{
"binary_name": "linux-tools-5.4.0-1054-xilinx-zynqmp",
"binary_version": "5.4.0-1054.58"
},
{
"binary_name": "linux-xilinx-zynqmp-headers-5.4.0-1054",
"binary_version": "5.4.0-1054.58"
},
{
"binary_name": "linux-xilinx-zynqmp-tools-5.4.0-1054",
"binary_version": "5.4.0-1054.58"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-xilinx-zynqmp",
"purl": "pkg:deb/ubuntu/linux-xilinx-zynqmp@5.4.0-1054.58?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1054.58"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1020.24",
"5.4.0-1021.25",
"5.4.0-1022.26",
"5.4.0-1023.27",
"5.4.0-1024.28",
"5.4.0-1025.29",
"5.4.0-1026.30",
"5.4.0-1027.31",
"5.4.0-1028.32",
"5.4.0-1029.33",
"5.4.0-1030.34",
"5.4.0-1031.35",
"5.4.0-1032.36",
"5.4.0-1033.37",
"5.4.0-1034.38",
"5.4.0-1035.39",
"5.4.0-1036.40",
"5.4.0-1037.41",
"5.4.0-1038.42",
"5.4.0-1039.43",
"5.4.0-1040.44",
"5.4.0-1041.45",
"5.4.0-1042.46",
"5.4.0-1043.47",
"5.4.0-1044.48",
"5.4.0-1045.49",
"5.4.0-1046.50",
"5.4.0-1047.51",
"5.4.0-1048.52",
"5.4.0-1049.53",
"5.4.0-1050.54",
"5.4.0-1051.55",
"5.4.0-1052.56",
"5.4.0-1053.57"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-aws-5.11-cloud-tools-5.11.0-1028",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-aws-5.11-headers-5.11.0-1028",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-aws-5.11-tools-5.11.0-1028",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.11.0-1028-aws",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.11.0-1028-aws",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-headers-5.11.0-1028-aws",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.11.0-1028-aws",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-modules-5.11.0-1028-aws",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.11.0-1028-aws",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-tools-5.11.0-1028-aws",
"binary_version": "5.11.0-1028.31~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-aws-5.11",
"purl": "pkg:deb/ubuntu/linux-aws-5.11@5.11.0-1028.31~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.11.0-1009.9~20.04.2",
"5.11.0-1014.15~20.04.1",
"5.11.0-1016.17~20.04.1",
"5.11.0-1017.18~20.04.1",
"5.11.0-1019.20~20.04.1",
"5.11.0-1020.21~20.04.2",
"5.11.0-1021.22~20.04.2",
"5.11.0-1022.23~20.04.1",
"5.11.0-1023.24~20.04.1",
"5.11.0-1025.27~20.04.1",
"5.11.0-1027.30~20.04.1",
"5.11.0-1028.31~20.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-aws-5.13-cloud-tools-5.13.0-1031",
"binary_version": "5.13.0-1031.35~20.04.1"
},
{
"binary_name": "linux-aws-5.13-headers-5.13.0-1031",
"binary_version": "5.13.0-1031.35~20.04.1"
},
{
"binary_name": "linux-aws-5.13-tools-5.13.0-1031",
"binary_version": "5.13.0-1031.35~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.13.0-1031-aws",
"binary_version": "5.13.0-1031.35~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.13.0-1031-aws",
"binary_version": "5.13.0-1031.35~20.04.1"
},
{
"binary_name": "linux-headers-5.13.0-1031-aws",
"binary_version": "5.13.0-1031.35~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.13.0-1031-aws",
"binary_version": "5.13.0-1031.35~20.04.1"
},
{
"binary_name": "linux-modules-5.13.0-1031-aws",
"binary_version": "5.13.0-1031.35~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.13.0-1031-aws",
"binary_version": "5.13.0-1031.35~20.04.1"
},
{
"binary_name": "linux-tools-5.13.0-1031-aws",
"binary_version": "5.13.0-1031.35~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-aws-5.13",
"purl": "pkg:deb/ubuntu/linux-aws-5.13@5.13.0-1031.35~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-1008.9~20.04.2",
"5.13.0-1011.12~20.04.1",
"5.13.0-1012.13~20.04.1",
"5.13.0-1014.15~20.04.1",
"5.13.0-1017.19~20.04.1",
"5.13.0-1019.21~20.04.1",
"5.13.0-1021.23~20.04.2",
"5.13.0-1022.24~20.04.1",
"5.13.0-1023.25~20.04.1",
"5.13.0-1025.27~20.04.1",
"5.13.0-1028.31~20.04.1",
"5.13.0-1029.32~20.04.1",
"5.13.0-1031.35~20.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-aws-5.8-cloud-tools-5.8.0-1042",
"binary_version": "5.8.0-1042.44~20.04.1"
},
{
"binary_name": "linux-aws-5.8-headers-5.8.0-1042",
"binary_version": "5.8.0-1042.44~20.04.1"
},
{
"binary_name": "linux-aws-5.8-tools-5.8.0-1042",
"binary_version": "5.8.0-1042.44~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.8.0-1042-aws",
"binary_version": "5.8.0-1042.44~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.8.0-1042-aws",
"binary_version": "5.8.0-1042.44~20.04.1"
},
{
"binary_name": "linux-headers-5.8.0-1042-aws",
"binary_version": "5.8.0-1042.44~20.04.1"
},
{
"binary_name": "linux-image-5.8.0-1042-aws",
"binary_version": "5.8.0-1042.44~20.04.1"
},
{
"binary_name": "linux-modules-5.8.0-1042-aws",
"binary_version": "5.8.0-1042.44~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.8.0-1042-aws",
"binary_version": "5.8.0-1042.44~20.04.1"
},
{
"binary_name": "linux-tools-5.8.0-1042-aws",
"binary_version": "5.8.0-1042.44~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-aws-5.8",
"purl": "pkg:deb/ubuntu/linux-aws-5.8@5.8.0-1042.44~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.8.0-1035.37~20.04.1",
"5.8.0-1038.40~20.04.1",
"5.8.0-1041.43~20.04.1",
"5.8.0-1042.44~20.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-azure-5.11-cloud-tools-5.11.0-1028",
"binary_version": "5.11.0-1028.31~20.04.2"
},
{
"binary_name": "linux-azure-5.11-headers-5.11.0-1028",
"binary_version": "5.11.0-1028.31~20.04.2"
},
{
"binary_name": "linux-azure-5.11-tools-5.11.0-1028",
"binary_version": "5.11.0-1028.31~20.04.2"
},
{
"binary_name": "linux-buildinfo-5.11.0-1028-azure",
"binary_version": "5.11.0-1028.31~20.04.2"
},
{
"binary_name": "linux-cloud-tools-5.11.0-1028-azure",
"binary_version": "5.11.0-1028.31~20.04.2"
},
{
"binary_name": "linux-headers-5.11.0-1028-azure",
"binary_version": "5.11.0-1028.31~20.04.2"
},
{
"binary_name": "linux-image-unsigned-5.11.0-1028-azure",
"binary_version": "5.11.0-1028.31~20.04.2"
},
{
"binary_name": "linux-modules-5.11.0-1028-azure",
"binary_version": "5.11.0-1028.31~20.04.2"
},
{
"binary_name": "linux-modules-extra-5.11.0-1028-azure",
"binary_version": "5.11.0-1028.31~20.04.2"
},
{
"binary_name": "linux-tools-5.11.0-1028-azure",
"binary_version": "5.11.0-1028.31~20.04.2"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-azure-5.11",
"purl": "pkg:deb/ubuntu/linux-azure-5.11@5.11.0-1028.31~20.04.2?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.11.0-1007.7~20.04.2",
"5.11.0-1012.13~20.04.1",
"5.11.0-1013.14~20.04.1",
"5.11.0-1015.16~20.04.1",
"5.11.0-1017.18~20.04.1",
"5.11.0-1019.20~20.04.1",
"5.11.0-1020.21~20.04.1",
"5.11.0-1021.22~20.04.1",
"5.11.0-1022.23~20.04.1",
"5.11.0-1023.24~20.04.1",
"5.11.0-1025.27~20.04.1",
"5.11.0-1027.30~20.04.1",
"5.11.0-1028.31~20.04.2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-azure-5.13-cloud-tools-5.13.0-1031",
"binary_version": "5.13.0-1031.37~20.04.1"
},
{
"binary_name": "linux-azure-5.13-headers-5.13.0-1031",
"binary_version": "5.13.0-1031.37~20.04.1"
},
{
"binary_name": "linux-azure-5.13-tools-5.13.0-1031",
"binary_version": "5.13.0-1031.37~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.13.0-1031-azure",
"binary_version": "5.13.0-1031.37~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.13.0-1031-azure",
"binary_version": "5.13.0-1031.37~20.04.1"
},
{
"binary_name": "linux-headers-5.13.0-1031-azure",
"binary_version": "5.13.0-1031.37~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.13.0-1031-azure",
"binary_version": "5.13.0-1031.37~20.04.1"
},
{
"binary_name": "linux-modules-5.13.0-1031-azure",
"binary_version": "5.13.0-1031.37~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.13.0-1031-azure",
"binary_version": "5.13.0-1031.37~20.04.1"
},
{
"binary_name": "linux-tools-5.13.0-1031-azure",
"binary_version": "5.13.0-1031.37~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-azure-5.13",
"purl": "pkg:deb/ubuntu/linux-azure-5.13@5.13.0-1031.37~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-1009.10~20.04.2",
"5.13.0-1012.14~20.04.1",
"5.13.0-1013.15~20.04.1",
"5.13.0-1014.16~20.04.1",
"5.13.0-1017.19~20.04.1",
"5.13.0-1021.24~20.04.1",
"5.13.0-1022.26~20.04.1",
"5.13.0-1023.27~20.04.1",
"5.13.0-1025.29~20.04.1",
"5.13.0-1028.33~20.04.1",
"5.13.0-1029.34~20.04.1",
"5.13.0-1031.37~20.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-azure-5.8-cloud-tools-5.8.0-1043",
"binary_version": "5.8.0-1043.46~20.04.1"
},
{
"binary_name": "linux-azure-5.8-headers-5.8.0-1043",
"binary_version": "5.8.0-1043.46~20.04.1"
},
{
"binary_name": "linux-azure-5.8-tools-5.8.0-1043",
"binary_version": "5.8.0-1043.46~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.8.0-1043-azure",
"binary_version": "5.8.0-1043.46~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.8.0-1043-azure",
"binary_version": "5.8.0-1043.46~20.04.1"
},
{
"binary_name": "linux-headers-5.8.0-1043-azure",
"binary_version": "5.8.0-1043.46~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.8.0-1043-azure",
"binary_version": "5.8.0-1043.46~20.04.1"
},
{
"binary_name": "linux-modules-5.8.0-1043-azure",
"binary_version": "5.8.0-1043.46~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.8.0-1043-azure",
"binary_version": "5.8.0-1043.46~20.04.1"
},
{
"binary_name": "linux-tools-5.8.0-1043-azure",
"binary_version": "5.8.0-1043.46~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-azure-5.8",
"purl": "pkg:deb/ubuntu/linux-azure-5.8@5.8.0-1043.46~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.8.0-1033.35~20.04.1",
"5.8.0-1036.38~20.04.1",
"5.8.0-1039.42~20.04.1",
"5.8.0-1040.43~20.04.1",
"5.8.0-1041.44~20.04.1",
"5.8.0-1042.45~20.04.1",
"5.8.0-1043.46~20.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-image-unsigned-5.4.0-1103-azure-fde",
"binary_version": "5.4.0-1103.109+cvm1.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-azure-fde",
"purl": "pkg:deb/ubuntu/linux-azure-fde@5.4.0-1103.109+cvm1.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1063.66+cvm2.2",
"5.4.0-1063.66+cvm3.2",
"5.4.0-1064.67+cvm1.1",
"5.4.0-1065.68+cvm2.1",
"5.4.0-1067.70+cvm1.1",
"5.4.0-1068.71+cvm1.1",
"5.4.0-1069.72+cvm1.1",
"5.4.0-1070.73+cvm1.1",
"5.4.0-1072.75+cvm1.1",
"5.4.0-1073.76+cvm1.1",
"5.4.0-1074.77+cvm1.1",
"5.4.0-1076.79+cvm1.1",
"5.4.0-1078.81+cvm1.1",
"5.4.0-1080.83+cvm1.1",
"5.4.0-1083.87+cvm1.1",
"5.4.0-1085.90+cvm1.1",
"5.4.0-1085.90+cvm2.1",
"5.4.0-1086.91+cvm1.1",
"5.4.0-1089.94+cvm1.2",
"5.4.0-1090.95+cvm1.1",
"5.4.0-1091.96+cvm1.1",
"5.4.0-1092.97+cvm1.1",
"5.4.0-1095.101+cvm1.1",
"5.4.0-1098.104+cvm1.1",
"5.4.0-1100.106+cvm1.1",
"5.4.0-1103.109+cvm1.1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-azure-fde-5.15-cloud-tools-5.15.0-1114",
"binary_version": "5.15.0-1114.123~20.04.1"
},
{
"binary_name": "linux-azure-fde-5.15-headers-5.15.0-1114",
"binary_version": "5.15.0-1114.123~20.04.1"
},
{
"binary_name": "linux-azure-fde-5.15-tools-5.15.0-1114",
"binary_version": "5.15.0-1114.123~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.15.0-1114-azure-fde",
"binary_version": "5.15.0-1114.123~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1114-azure-fde",
"binary_version": "5.15.0-1114.123~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1114-azure-fde",
"binary_version": "5.15.0-1114.123~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1114-azure-fde",
"binary_version": "5.15.0-1114.123~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1114-azure-fde",
"binary_version": "5.15.0-1114.123~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1114-azure-fde",
"binary_version": "5.15.0-1114.123~20.04.1"
},
{
"binary_name": "linux-modules-involflt-5.15.0-1114-azure-fde",
"binary_version": "5.15.0-1114.123~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1114-azure-fde",
"binary_version": "5.15.0-1114.123~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:20.04:LTS",
"name": "linux-azure-fde-5.15",
"purl": "pkg:deb/ubuntu/linux-azure-fde-5.15@5.15.0-1114.123~20.04.1?arch=source\u0026distro=esm-infra/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1114.123~20.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1019.24~20.04.1.1",
"5.15.0-1020.25~20.04.1.1",
"5.15.0-1021.26~20.04.1.1",
"5.15.0-1029.36~20.04.1.1",
"5.15.0-1030.37~20.04.1.1",
"5.15.0-1031.38~20.04.1.1",
"5.15.0-1033.40~20.04.1.1",
"5.15.0-1034.41~20.04.1.2",
"5.15.0-1035.42~20.04.1.1",
"5.15.0-1036.43~20.04.1.1",
"5.15.0-1037.44~20.04.1.1",
"5.15.0-1038.45~20.04.1.1",
"5.15.0-1039.46~20.04.1.1",
"5.15.0-1040.47~20.04.1.1",
"5.15.0-1041.48~20.04.1.1",
"5.15.0-1042.49~20.04.1.1",
"5.15.0-1043.50~20.04.1.1",
"5.15.0-1046.53~20.04.1.1",
"5.15.0-1047.54~20.04.1.1",
"5.15.0-1049.56~20.04.1.1",
"5.15.0-1050.57~20.04.1.1",
"5.15.0-1051.59~20.04.1.1",
"5.15.0-1052.60~20.04.1.1",
"5.15.0-1053.61~20.04.1.1",
"5.15.0-1054.62~20.04.1.1",
"5.15.0-1056.64~20.04.1.1",
"5.15.0-1057.65~20.04.1.1",
"5.15.0-1058.66~20.04.2.1",
"5.15.0-1059.67~20.04.1.1",
"5.15.0-1060.69~20.04.1.1",
"5.15.0-1061.70~20.04.1.1",
"5.15.0-1063.72~20.04.1.1",
"5.15.0-1064.73~20.04.1.1",
"5.15.0-1065.74~20.04.1.1",
"5.15.0-1067.76~20.04.1.1",
"5.15.0-1068.77~20.04.1.1",
"5.15.0-1070.79~20.04.1.1",
"5.15.0-1071.80~20.04.1.1",
"5.15.0-1072.81~20.04.1.1",
"5.15.0-1073.82~20.04.1.1",
"5.15.0-1074.83~20.04.1.1",
"5.15.0-1076.85~20.04.1.1",
"5.15.0-1078.87~20.04.1.1",
"5.15.0-1081.90~20.04.1.1",
"5.15.0-1082.91~20.04.1.1",
"5.15.0-1086.95~20.04.1.1",
"5.15.0-1087.96~20.04.1.1",
"5.15.0-1088.97~20.04.1.1",
"5.15.0-1089.98~20.04.1.1",
"5.15.0-1091.100~20.04.1.1",
"5.15.0-1094.103~20.04.1.1",
"5.15.0-1096.105~20.04.1.1",
"5.15.0-1097.106~20.04.1.1",
"5.15.0-1098.107~20.04.1.1",
"5.15.0-1102.111~20.04.1.1",
"5.15.0-1103.112~20.04.1.1",
"5.15.0-1111.120~20.04.1.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.11.0-1029-gcp",
"binary_version": "5.11.0-1029.33~20.04.3"
},
{
"binary_name": "linux-gcp-5.11-headers-5.11.0-1029",
"binary_version": "5.11.0-1029.33~20.04.3"
},
{
"binary_name": "linux-gcp-5.11-tools-5.11.0-1029",
"binary_version": "5.11.0-1029.33~20.04.3"
},
{
"binary_name": "linux-headers-5.11.0-1029-gcp",
"binary_version": "5.11.0-1029.33~20.04.3"
},
{
"binary_name": "linux-image-unsigned-5.11.0-1029-gcp",
"binary_version": "5.11.0-1029.33~20.04.3"
},
{
"binary_name": "linux-modules-5.11.0-1029-gcp",
"binary_version": "5.11.0-1029.33~20.04.3"
},
{
"binary_name": "linux-modules-extra-5.11.0-1029-gcp",
"binary_version": "5.11.0-1029.33~20.04.3"
},
{
"binary_name": "linux-tools-5.11.0-1029-gcp",
"binary_version": "5.11.0-1029.33~20.04.3"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-gcp-5.11",
"purl": "pkg:deb/ubuntu/linux-gcp-5.11@5.11.0-1029.33~20.04.3?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.11.0-1009.10~20.04.1",
"5.11.0-1014.16~20.04.1",
"5.11.0-1017.19~20.04.1",
"5.11.0-1018.20~20.04.2",
"5.11.0-1020.22~20.04.1",
"5.11.0-1021.23~20.04.1",
"5.11.0-1022.24~20.04.1",
"5.11.0-1023.25~20.04.1",
"5.11.0-1024.26~20.04.1",
"5.11.0-1026.29~20.04.1",
"5.11.0-1028.32~20.04.1",
"5.11.0-1029.33~20.04.3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.13.0-1033-gcp",
"binary_version": "5.13.0-1033.40~20.04.1"
},
{
"binary_name": "linux-gcp-5.13-headers-5.13.0-1033",
"binary_version": "5.13.0-1033.40~20.04.1"
},
{
"binary_name": "linux-gcp-5.13-tools-5.13.0-1033",
"binary_version": "5.13.0-1033.40~20.04.1"
},
{
"binary_name": "linux-headers-5.13.0-1033-gcp",
"binary_version": "5.13.0-1033.40~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.13.0-1033-gcp",
"binary_version": "5.13.0-1033.40~20.04.1"
},
{
"binary_name": "linux-modules-5.13.0-1033-gcp",
"binary_version": "5.13.0-1033.40~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.13.0-1033-gcp",
"binary_version": "5.13.0-1033.40~20.04.1"
},
{
"binary_name": "linux-tools-5.13.0-1033-gcp",
"binary_version": "5.13.0-1033.40~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-gcp-5.13",
"purl": "pkg:deb/ubuntu/linux-gcp-5.13@5.13.0-1033.40~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-1008.9~20.04.3",
"5.13.0-1012.15~20.04.1",
"5.13.0-1013.16~20.04.1",
"5.13.0-1015.18~20.04.1",
"5.13.0-1019.23~20.04.1",
"5.13.0-1021.25~20.04.1",
"5.13.0-1023.28~20.04.1",
"5.13.0-1024.29~20.04.1",
"5.13.0-1025.30~20.04.1",
"5.13.0-1027.32~20.04.1",
"5.13.0-1030.36~20.04.1",
"5.13.0-1031.37~20.04.1",
"5.13.0-1033.40~20.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.8.0-1039-gcp",
"binary_version": "5.8.0-1039.41"
},
{
"binary_name": "linux-gcp-5.8-headers-5.8.0-1039",
"binary_version": "5.8.0-1039.41"
},
{
"binary_name": "linux-gcp-5.8-tools-5.8.0-1039",
"binary_version": "5.8.0-1039.41"
},
{
"binary_name": "linux-headers-5.8.0-1039-gcp",
"binary_version": "5.8.0-1039.41"
},
{
"binary_name": "linux-image-unsigned-5.8.0-1039-gcp",
"binary_version": "5.8.0-1039.41"
},
{
"binary_name": "linux-modules-5.8.0-1039-gcp",
"binary_version": "5.8.0-1039.41"
},
{
"binary_name": "linux-modules-extra-5.8.0-1039-gcp",
"binary_version": "5.8.0-1039.41"
},
{
"binary_name": "linux-tools-5.8.0-1039-gcp",
"binary_version": "5.8.0-1039.41"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-gcp-5.8",
"purl": "pkg:deb/ubuntu/linux-gcp-5.8@5.8.0-1039.41?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.8.0-1032.34~20.04.1",
"5.8.0-1035.37~20.04.1",
"5.8.0-1038.40~20.04.1",
"5.8.0-1039.41"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1105-gke",
"binary_version": "5.4.0-1105.112"
},
{
"binary_name": "linux-gke-headers-5.4.0-1105",
"binary_version": "5.4.0-1105.112"
},
{
"binary_name": "linux-gke-tools-5.4.0-1105",
"binary_version": "5.4.0-1105.112"
},
{
"binary_name": "linux-headers-5.4.0-1105-gke",
"binary_version": "5.4.0-1105.112"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1105-gke",
"binary_version": "5.4.0-1105.112"
},
{
"binary_name": "linux-modules-5.4.0-1105-gke",
"binary_version": "5.4.0-1105.112"
},
{
"binary_name": "linux-modules-extra-5.4.0-1105-gke",
"binary_version": "5.4.0-1105.112"
},
{
"binary_name": "linux-tools-5.4.0-1105-gke",
"binary_version": "5.4.0-1105.112"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-gke",
"purl": "pkg:deb/ubuntu/linux-gke@5.4.0-1105.112?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1033.35",
"5.4.0-1035.37",
"5.4.0-1036.38",
"5.4.0-1037.39",
"5.4.0-1039.41",
"5.4.0-1041.43",
"5.4.0-1042.44",
"5.4.0-1043.45",
"5.4.0-1044.46",
"5.4.0-1046.48",
"5.4.0-1049.52",
"5.4.0-1051.54",
"5.4.0-1052.55",
"5.4.0-1053.56",
"5.4.0-1054.57",
"5.4.0-1055.58",
"5.4.0-1056.59",
"5.4.0-1057.60",
"5.4.0-1059.62",
"5.4.0-1061.64",
"5.4.0-1062.65",
"5.4.0-1063.66",
"5.4.0-1065.68",
"5.4.0-1066.69",
"5.4.0-1067.70",
"5.4.0-1068.71",
"5.4.0-1071.76",
"5.4.0-1072.77",
"5.4.0-1074.79",
"5.4.0-1076.82",
"5.4.0-1078.84",
"5.4.0-1080.86",
"5.4.0-1081.87",
"5.4.0-1083.89",
"5.4.0-1084.90",
"5.4.0-1086.93",
"5.4.0-1087.94",
"5.4.0-1090.97",
"5.4.0-1091.98",
"5.4.0-1094.101",
"5.4.0-1095.102",
"5.4.0-1096.103",
"5.4.0-1097.104",
"5.4.0-1098.105",
"5.4.0-1099.106",
"5.4.0-1100.107",
"5.4.0-1101.108",
"5.4.0-1102.109",
"5.4.0-1103.110",
"5.4.0-1104.111",
"5.4.0-1105.112"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1039-gke",
"binary_version": "5.15.0-1039.44~20.04.1"
},
{
"binary_name": "linux-gke-5.15-headers-5.15.0-1039",
"binary_version": "5.15.0-1039.44~20.04.1"
},
{
"binary_name": "linux-gke-5.15-tools-5.15.0-1039",
"binary_version": "5.15.0-1039.44~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1039-gke",
"binary_version": "5.15.0-1039.44~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1039-gke",
"binary_version": "5.15.0-1039.44~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1039-gke",
"binary_version": "5.15.0-1039.44~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1039-gke",
"binary_version": "5.15.0-1039.44~20.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-1039-gke",
"binary_version": "5.15.0-1039.44~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1039-gke",
"binary_version": "5.15.0-1039.44~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-gke-5.15",
"purl": "pkg:deb/ubuntu/linux-gke-5.15@5.15.0-1039.44~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1011.14~20.04.1",
"5.15.0-1014.17~20.04.1",
"5.15.0-1015.18~20.04.1",
"5.15.0-1016.19~20.04.1",
"5.15.0-1019.23~20.04.1",
"5.15.0-1020.25~20.04.1",
"5.15.0-1023.28~20.04.2",
"5.15.0-1027.32~20.04.1",
"5.15.0-1028.33~20.04.1",
"5.15.0-1029.34~20.04.1",
"5.15.0-1031.36~20.04.1",
"5.15.0-1032.37~20.04.1",
"5.15.0-1033.38~20.04.1",
"5.15.0-1034.39~20.04.1",
"5.15.0-1036.41~20.04.1",
"5.15.0-1037.42~20.04.1",
"5.15.0-1038.43~20.04.1",
"5.15.0-1039.44~20.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "block-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "block-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "block-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "crypto-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "crypto-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "crypto-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "dasd-extra-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "dasd-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fat-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fat-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fat-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fb-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "firewire-core-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "floppy-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fs-core-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fs-core-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fs-core-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "input-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "input-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "input-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "ipmi-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "ipmi-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "ipmi-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "kernel-image-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "kernel-image-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "kernel-image-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.11.0-46-generic",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.11.0-46-generic-64k",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.11.0-46-generic-lpae",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.11.0-46-lowlatency",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.11.0-46-generic",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.11.0-46-lowlatency",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-headers-5.11.0-46-generic",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-headers-5.11.0-46-generic-64k",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-headers-5.11.0-46-generic-lpae",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-headers-5.11.0-46-lowlatency",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-cloud-tools-5.11.0-46",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-cloud-tools-common",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-headers-5.11.0-46",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-source-5.11.0",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-tools-5.11.0-46",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-tools-common",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-tools-host",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-udebs-generic",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-udebs-generic-64k",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-udebs-generic-lpae",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-image-5.11.0-46-generic",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-image-5.11.0-46-generic-lpae",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.11.0-46-generic",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.11.0-46-generic-64k",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.11.0-46-lowlatency",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-modules-5.11.0-46-generic",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-modules-5.11.0-46-generic-64k",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-modules-5.11.0-46-generic-lpae",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-modules-5.11.0-46-lowlatency",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.11.0-46-generic",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-tools-5.11.0-46-generic",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-tools-5.11.0-46-generic-64k",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-tools-5.11.0-46-generic-lpae",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-tools-5.11.0-46-lowlatency",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "md-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "md-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "md-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "message-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "message-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "mouse-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "mouse-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "mouse-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "multipath-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "multipath-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "multipath-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nfs-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nfs-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nfs-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-pcmcia-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "parport-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "parport-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "parport-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "pata-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "pcmcia-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "pcmcia-storage-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "plip-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "plip-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "plip-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "ppp-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "ppp-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "ppp-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "sata-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "sata-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "sata-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "scsi-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "scsi-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "scsi-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "serial-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "storage-core-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "storage-core-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "storage-core-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "usb-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "usb-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "usb-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "virtio-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "virtio-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "vlan-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "vlan-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "vlan-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-hwe-5.11",
"purl": "pkg:deb/ubuntu/linux-hwe-5.11@5.11.0-46.51~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.11.0-22.23~20.04.1",
"5.11.0-25.27~20.04.1",
"5.11.0-27.29~20.04.1",
"5.11.0-34.36~20.04.1",
"5.11.0-36.40~20.04.1",
"5.11.0-37.41~20.04.2",
"5.11.0-38.42~20.04.1",
"5.11.0-40.44~20.04.2",
"5.11.0-41.45~20.04.1",
"5.11.0-43.47~20.04.2",
"5.11.0-44.48~20.04.2",
"5.11.0-46.51~20.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "block-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "block-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "block-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "crypto-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "crypto-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "crypto-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "dasd-extra-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "dasd-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fat-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fat-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fat-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fb-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "firewire-core-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "floppy-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fs-core-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fs-core-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fs-core-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "input-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "input-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "input-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "ipmi-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "ipmi-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "ipmi-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "kernel-image-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "kernel-image-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "kernel-image-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.13.0-52-generic",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.13.0-52-generic-64k",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.13.0-52-generic-lpae",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.13.0-52-lowlatency",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.13.0-52-generic",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.13.0-52-lowlatency",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-headers-5.13.0-52-generic",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-headers-5.13.0-52-generic-64k",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-headers-5.13.0-52-generic-lpae",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-headers-5.13.0-52-lowlatency",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-cloud-tools-5.13.0-52",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-cloud-tools-common",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-headers-5.13.0-52",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-source-5.13.0",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-tools-5.13.0-52",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-tools-common",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-tools-host",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-udebs-generic",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-udebs-generic-64k",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-udebs-generic-lpae",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-image-5.13.0-52-generic",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-image-5.13.0-52-generic-lpae",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.13.0-52-generic",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.13.0-52-generic-64k",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.13.0-52-lowlatency",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-modules-5.13.0-52-generic",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-modules-5.13.0-52-generic-64k",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-modules-5.13.0-52-generic-lpae",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-modules-5.13.0-52-lowlatency",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.13.0-52-generic",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-tools-5.13.0-52-generic",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-tools-5.13.0-52-generic-64k",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-tools-5.13.0-52-generic-lpae",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-tools-5.13.0-52-lowlatency",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "md-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "md-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "md-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "message-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "message-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "mouse-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "mouse-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "mouse-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "multipath-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "multipath-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "multipath-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nfs-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nfs-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nfs-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-pcmcia-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "parport-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "parport-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "parport-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "pata-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "pcmcia-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "pcmcia-storage-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "plip-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "plip-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "plip-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "ppp-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "ppp-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "ppp-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "sata-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "sata-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "sata-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "scsi-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "scsi-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "scsi-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "serial-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "storage-core-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "storage-core-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "storage-core-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "usb-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "usb-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "usb-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "virtio-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "virtio-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "vlan-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "vlan-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "vlan-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-hwe-5.13",
"purl": "pkg:deb/ubuntu/linux-hwe-5.13@5.13.0-52.59~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-21.21~20.04.1",
"5.13.0-22.22~20.04.1",
"5.13.0-23.23~20.04.2",
"5.13.0-25.26~20.04.1",
"5.13.0-27.29~20.04.1",
"5.13.0-28.31~20.04.1",
"5.13.0-30.33~20.04.1",
"5.13.0-35.40~20.04.1",
"5.13.0-37.42~20.04.1",
"5.13.0-39.44~20.04.1",
"5.13.0-40.45~20.04.1",
"5.13.0-41.46~20.04.1",
"5.13.0-44.49~20.04.1",
"5.13.0-48.54~20.04.1",
"5.13.0-51.58~20.04.1",
"5.13.0-52.59~20.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "block-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "block-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "block-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "crypto-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "crypto-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "crypto-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "dasd-extra-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "dasd-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fat-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fat-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fat-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fb-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "firewire-core-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "floppy-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fs-core-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fs-core-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fs-core-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "input-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "input-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "input-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "ipmi-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "ipmi-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "ipmi-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "kernel-image-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "kernel-image-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "kernel-image-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.8.0-63-generic",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.8.0-63-generic-64k",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.8.0-63-generic-lpae",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.8.0-63-lowlatency",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.8.0-63-generic",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.8.0-63-lowlatency",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-headers-5.8.0-63-generic",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-headers-5.8.0-63-generic-64k",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-headers-5.8.0-63-generic-lpae",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-headers-5.8.0-63-lowlatency",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-cloud-tools-5.8.0-63",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-cloud-tools-common",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-headers-5.8.0-63",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-source-5.8.0",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-tools-5.8.0-63",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-tools-common",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-tools-host",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-udebs-generic",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-udebs-generic-64k",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-udebs-generic-lpae",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-image-5.8.0-63-generic",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-image-5.8.0-63-generic-lpae",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.8.0-63-generic",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.8.0-63-generic-64k",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.8.0-63-lowlatency",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-modules-5.8.0-63-generic",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-modules-5.8.0-63-generic-64k",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-modules-5.8.0-63-generic-lpae",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-modules-5.8.0-63-lowlatency",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.8.0-63-generic",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-tools-5.8.0-63-generic",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-tools-5.8.0-63-generic-64k",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-tools-5.8.0-63-generic-lpae",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-tools-5.8.0-63-lowlatency",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "md-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "md-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "md-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "message-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "message-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "mouse-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "mouse-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "mouse-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "multipath-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "multipath-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "multipath-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nfs-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nfs-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nfs-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-pcmcia-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "parport-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "parport-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "parport-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "pata-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "pcmcia-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "pcmcia-storage-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "plip-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "plip-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "plip-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "ppp-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "ppp-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "ppp-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "sata-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "sata-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "sata-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "scsi-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "scsi-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "scsi-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "serial-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "storage-core-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "storage-core-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "storage-core-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "usb-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "usb-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "usb-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "virtio-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "virtio-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "vlan-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "vlan-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "vlan-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-hwe-5.8",
"purl": "pkg:deb/ubuntu/linux-hwe-5.8@5.8.0-63.71~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.8.0-23.24~20.04.1",
"5.8.0-25.26~20.04.1",
"5.8.0-28.30~20.04.1",
"5.8.0-29.31~20.04.1",
"5.8.0-31.33~20.04.1",
"5.8.0-33.36~20.04.1",
"5.8.0-34.37~20.04.2",
"5.8.0-36.40~20.04.1",
"5.8.0-38.43~20.04.1",
"5.8.0-40.45~20.04.1",
"5.8.0-41.46~20.04.1",
"5.8.0-43.49~20.04.1",
"5.8.0-44.50~20.04.1",
"5.8.0-45.51~20.04.1",
"5.8.0-48.54~20.04.1",
"5.8.0-49.55~20.04.1",
"5.8.0-50.56~20.04.1",
"5.8.0-53.60~20.04.1",
"5.8.0-55.62~20.04.1",
"5.8.0-59.66~20.04.1",
"5.8.0-63.71~20.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.13.0-1017-intel",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-cloud-tools-5.13.0-1017-intel",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-headers-5.13.0-1017-intel",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-image-unsigned-5.13.0-1017-intel",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-intel-5.13-cloud-tools-5.13.0-1017",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-intel-5.13-cloud-tools-common",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-intel-5.13-headers-5.13.0-1017",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-intel-5.13-source-5.13.0",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-intel-5.13-tools-5.13.0-1017",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-intel-5.13-tools-common",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-intel-5.13-tools-host",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-modules-5.13.0-1017-intel",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-modules-extra-5.13.0-1017-intel",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-tools-5.13.0-1017-intel",
"binary_version": "5.13.0-1017.19"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-intel-5.13",
"purl": "pkg:deb/ubuntu/linux-intel-5.13@5.13.0-1017.19?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-1007.7",
"5.13.0-1008.8",
"5.13.0-1009.9",
"5.13.0-1010.10",
"5.13.0-1011.11",
"5.13.0-1014.15",
"5.13.0-1017.19"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.10.0-1057-oem",
"binary_version": "5.10.0-1057.61"
},
{
"binary_name": "linux-headers-5.10.0-1057-oem",
"binary_version": "5.10.0-1057.61"
},
{
"binary_name": "linux-image-unsigned-5.10.0-1057-oem",
"binary_version": "5.10.0-1057.61"
},
{
"binary_name": "linux-modules-5.10.0-1057-oem",
"binary_version": "5.10.0-1057.61"
},
{
"binary_name": "linux-oem-5.10-headers-5.10.0-1057",
"binary_version": "5.10.0-1057.61"
},
{
"binary_name": "linux-oem-5.10-tools-5.10.0-1057",
"binary_version": "5.10.0-1057.61"
},
{
"binary_name": "linux-oem-5.10-tools-host",
"binary_version": "5.10.0-1057.61"
},
{
"binary_name": "linux-tools-5.10.0-1057-oem",
"binary_version": "5.10.0-1057.61"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-oem-5.10",
"purl": "pkg:deb/ubuntu/linux-oem-5.10@5.10.0-1057.61?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.10.0-1008.9",
"5.10.0-1011.12",
"5.10.0-1013.14",
"5.10.0-1014.15",
"5.10.0-1016.17",
"5.10.0-1017.18",
"5.10.0-1019.20",
"5.10.0-1021.22",
"5.10.0-1022.23",
"5.10.0-1023.24",
"5.10.0-1025.26",
"5.10.0-1026.27",
"5.10.0-1029.30",
"5.10.0-1032.33",
"5.10.0-1033.34",
"5.10.0-1034.35",
"5.10.0-1038.40",
"5.10.0-1044.46",
"5.10.0-1045.47",
"5.10.0-1049.51",
"5.10.0-1050.52",
"5.10.0-1051.53",
"5.10.0-1052.54",
"5.10.0-1053.55",
"5.10.0-1055.58",
"5.10.0-1057.61"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.13.0-1029-oem",
"binary_version": "5.13.0-1029.36"
},
{
"binary_name": "linux-headers-5.13.0-1029-oem",
"binary_version": "5.13.0-1029.36"
},
{
"binary_name": "linux-image-unsigned-5.13.0-1029-oem",
"binary_version": "5.13.0-1029.36"
},
{
"binary_name": "linux-modules-5.13.0-1029-oem",
"binary_version": "5.13.0-1029.36"
},
{
"binary_name": "linux-oem-5.13-headers-5.13.0-1029",
"binary_version": "5.13.0-1029.36"
},
{
"binary_name": "linux-oem-5.13-tools-5.13.0-1029",
"binary_version": "5.13.0-1029.36"
},
{
"binary_name": "linux-oem-5.13-tools-host",
"binary_version": "5.13.0-1029.36"
},
{
"binary_name": "linux-tools-5.13.0-1029-oem",
"binary_version": "5.13.0-1029.36"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-oem-5.13",
"purl": "pkg:deb/ubuntu/linux-oem-5.13@5.13.0-1029.36?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-1009.10",
"5.13.0-1010.11",
"5.13.0-1012.16",
"5.13.0-1014.18",
"5.13.0-1017.21",
"5.13.0-1019.23",
"5.13.0-1020.24",
"5.13.0-1021.25",
"5.13.0-1022.26",
"5.13.0-1026.32",
"5.13.0-1028.35",
"5.13.0-1029.36"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.14.0-1059-oem",
"binary_version": "5.14.0-1059.67"
},
{
"binary_name": "linux-headers-5.14.0-1059-oem",
"binary_version": "5.14.0-1059.67"
},
{
"binary_name": "linux-image-unsigned-5.14.0-1059-oem",
"binary_version": "5.14.0-1059.67"
},
{
"binary_name": "linux-modules-5.14.0-1059-oem",
"binary_version": "5.14.0-1059.67"
},
{
"binary_name": "linux-modules-iwlwifi-5.14.0-1059-oem",
"binary_version": "5.14.0-1059.67"
},
{
"binary_name": "linux-oem-5.14-headers-5.14.0-1059",
"binary_version": "5.14.0-1059.67"
},
{
"binary_name": "linux-oem-5.14-tools-5.14.0-1059",
"binary_version": "5.14.0-1059.67"
},
{
"binary_name": "linux-oem-5.14-tools-host",
"binary_version": "5.14.0-1059.67"
},
{
"binary_name": "linux-tools-5.14.0-1059-oem",
"binary_version": "5.14.0-1059.67"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-oem-5.14",
"purl": "pkg:deb/ubuntu/linux-oem-5.14@5.14.0-1059.67?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.14.0-1004.4",
"5.14.0-1005.5",
"5.14.0-1007.7",
"5.14.0-1008.8",
"5.14.0-1010.10",
"5.14.0-1011.11",
"5.14.0-1013.13",
"5.14.0-1018.19",
"5.14.0-1020.22",
"5.14.0-1022.24",
"5.14.0-1024.26",
"5.14.0-1027.30",
"5.14.0-1029.32",
"5.14.0-1031.34",
"5.14.0-1032.35",
"5.14.0-1033.36",
"5.14.0-1034.37",
"5.14.0-1036.40",
"5.14.0-1038.42",
"5.14.0-1042.47",
"5.14.0-1044.49",
"5.14.0-1045.51",
"5.14.0-1046.53",
"5.14.0-1047.54",
"5.14.0-1048.55",
"5.14.0-1049.56",
"5.14.0-1050.57",
"5.14.0-1051.58",
"5.14.0-1052.59",
"5.14.0-1054.61",
"5.14.0-1055.62",
"5.14.0-1056.63",
"5.14.0-1057.64",
"5.14.0-1058.66",
"5.14.0-1059.67"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.6.0-1056-oem",
"binary_version": "5.6.0-1056.60"
},
{
"binary_name": "linux-headers-5.6.0-1056-oem",
"binary_version": "5.6.0-1056.60"
},
{
"binary_name": "linux-image-unsigned-5.6.0-1056-oem",
"binary_version": "5.6.0-1056.60"
},
{
"binary_name": "linux-modules-5.6.0-1056-oem",
"binary_version": "5.6.0-1056.60"
},
{
"binary_name": "linux-oem-5.6-headers-5.6.0-1056",
"binary_version": "5.6.0-1056.60"
},
{
"binary_name": "linux-oem-5.6-tools-5.6.0-1056",
"binary_version": "5.6.0-1056.60"
},
{
"binary_name": "linux-oem-5.6-tools-host",
"binary_version": "5.6.0-1056.60"
},
{
"binary_name": "linux-tools-5.6.0-1056-oem",
"binary_version": "5.6.0-1056.60"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-oem-5.6",
"purl": "pkg:deb/ubuntu/linux-oem-5.6@5.6.0-1056.60?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.6.0-1007.7",
"5.6.0-1008.8",
"5.6.0-1010.10",
"5.6.0-1011.11",
"5.6.0-1013.13",
"5.6.0-1017.17",
"5.6.0-1018.18",
"5.6.0-1020.20",
"5.6.0-1021.21",
"5.6.0-1023.23",
"5.6.0-1026.26",
"5.6.0-1027.27",
"5.6.0-1028.28",
"5.6.0-1031.32",
"5.6.0-1032.33",
"5.6.0-1033.35",
"5.6.0-1034.36",
"5.6.0-1035.37",
"5.6.0-1036.39",
"5.6.0-1039.43",
"5.6.0-1042.46",
"5.6.0-1047.51",
"5.6.0-1048.52",
"5.6.0-1050.54",
"5.6.0-1052.56",
"5.6.0-1053.57",
"5.6.0-1054.58",
"5.6.0-1055.59",
"5.6.0-1056.60"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.11.0-1028-oracle",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-headers-5.11.0-1028-oracle",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.11.0-1028-oracle",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-modules-5.11.0-1028-oracle",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.11.0-1028-oracle",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-oracle-5.11-headers-5.11.0-1028",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-oracle-5.11-tools-5.11.0-1028",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-tools-5.11.0-1028-oracle",
"binary_version": "5.11.0-1028.31~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-oracle-5.11",
"purl": "pkg:deb/ubuntu/linux-oracle-5.11@5.11.0-1028.31~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.11.0-1008.8~20.04.1",
"5.11.0-1013.14~20.04.1",
"5.11.0-1016.17~20.04.1",
"5.11.0-1017.18~20.04.1",
"5.11.0-1019.20~20.04.1",
"5.11.0-1020.21~20.04.1",
"5.11.0-1021.22~20.04.1",
"5.11.0-1022.23~20.04.1",
"5.11.0-1023.24~20.04.1",
"5.11.0-1025.27~20.04.1",
"5.11.0-1027.30~20.04.1",
"5.11.0-1028.31~20.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.13.0-1036-oracle",
"binary_version": "5.13.0-1036.43~20.04.1"
},
{
"binary_name": "linux-headers-5.13.0-1036-oracle",
"binary_version": "5.13.0-1036.43~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.13.0-1036-oracle",
"binary_version": "5.13.0-1036.43~20.04.1"
},
{
"binary_name": "linux-modules-5.13.0-1036-oracle",
"binary_version": "5.13.0-1036.43~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.13.0-1036-oracle",
"binary_version": "5.13.0-1036.43~20.04.1"
},
{
"binary_name": "linux-oracle-5.13-headers-5.13.0-1036",
"binary_version": "5.13.0-1036.43~20.04.1"
},
{
"binary_name": "linux-oracle-5.13-tools-5.13.0-1036",
"binary_version": "5.13.0-1036.43~20.04.1"
},
{
"binary_name": "linux-tools-5.13.0-1036-oracle",
"binary_version": "5.13.0-1036.43~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-oracle-5.13",
"purl": "pkg:deb/ubuntu/linux-oracle-5.13@5.13.0-1036.43~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-1011.13~20.04.2",
"5.13.0-1015.19~20.04.1",
"5.13.0-1016.20~20.04.1",
"5.13.0-1018.22~20.04.1",
"5.13.0-1021.26~20.04.1",
"5.13.0-1025.30~20.04.1",
"5.13.0-1027.32~20.04.1",
"5.13.0-1028.33~20.04.1",
"5.13.0-1030.35~20.04.1",
"5.13.0-1033.39~20.04.1",
"5.13.0-1034.40~20.04.1",
"5.13.0-1036.43~20.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.8.0-1038-oracle",
"binary_version": "5.8.0-1038.39~20.04.1"
},
{
"binary_name": "linux-headers-5.8.0-1038-oracle",
"binary_version": "5.8.0-1038.39~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.8.0-1038-oracle",
"binary_version": "5.8.0-1038.39~20.04.1"
},
{
"binary_name": "linux-modules-5.8.0-1038-oracle",
"binary_version": "5.8.0-1038.39~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.8.0-1038-oracle",
"binary_version": "5.8.0-1038.39~20.04.1"
},
{
"binary_name": "linux-oracle-5.8-headers-5.8.0-1038",
"binary_version": "5.8.0-1038.39~20.04.1"
},
{
"binary_name": "linux-oracle-5.8-tools-5.8.0-1038",
"binary_version": "5.8.0-1038.39~20.04.1"
},
{
"binary_name": "linux-tools-5.8.0-1038-oracle",
"binary_version": "5.8.0-1038.39~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-oracle-5.8",
"purl": "pkg:deb/ubuntu/linux-oracle-5.8@5.8.0-1038.39~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.8.0-1031.32~20.04.2",
"5.8.0-1033.34~20.04.1",
"5.8.0-1034.35~20.04.2",
"5.8.0-1037.38~20.04.1",
"5.8.0-1038.39~20.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1006-raspi2",
"binary_version": "5.4.0-1006.6"
},
{
"binary_name": "linux-headers-5.4.0-1006-raspi2",
"binary_version": "5.4.0-1006.6"
},
{
"binary_name": "linux-image-5.4.0-1006-raspi2",
"binary_version": "5.4.0-1006.6"
},
{
"binary_name": "linux-modules-5.4.0-1006-raspi2",
"binary_version": "5.4.0-1006.6"
},
{
"binary_name": "linux-raspi2-headers-5.4.0-1006",
"binary_version": "5.4.0-1006.6"
},
{
"binary_name": "linux-raspi2-tools-5.4.0-1006",
"binary_version": "5.4.0-1006.6"
},
{
"binary_name": "linux-tools-5.4.0-1006-raspi2",
"binary_version": "5.4.0-1006.6"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-raspi2",
"purl": "pkg:deb/ubuntu/linux-raspi2@5.4.0-1006.6?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.3.0-1007.8",
"5.3.0-1014.16",
"5.3.0-1015.17",
"5.3.0-1017.19",
"5.4.0-1004.4",
"5.4.0-1006.6"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "block-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "crypto-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "fat-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "firewire-core-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "fs-core-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "fs-secondary-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "input-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "ipmi-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "kernel-image-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "linux-buildinfo-5.4.0-40-generic",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "linux-headers-5.4.0-40-generic",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "linux-image-5.4.0-40-generic",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "linux-modules-5.4.0-40-generic",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "linux-modules-extra-5.4.0-40-generic",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "linux-riscv-headers-5.4.0-40",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "linux-riscv-tools-5.4.0-40",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "linux-tools-5.4.0-40-generic",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "linux-udebs-generic",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "md-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "message-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "mouse-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "multipath-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "nfs-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "nic-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "nic-shared-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "nic-usb-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "parport-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "pata-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "plip-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "ppp-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "sata-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "scsi-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "storage-core-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "usb-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "virtio-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "vlan-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-riscv",
"purl": "pkg:deb/ubuntu/linux-riscv@5.4.0-40.45?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-24.28",
"5.4.0-26.30",
"5.4.0-27.31",
"5.4.0-28.32",
"5.4.0-30.34",
"5.4.0-31.35",
"5.4.0-33.37",
"5.4.0-34.38",
"5.4.0-36.41",
"5.4.0-37.42",
"5.4.0-39.44",
"5.4.0-40.45"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.11.0-1031-generic",
"binary_version": "5.11.0-1031.35"
},
{
"binary_name": "linux-headers-5.11.0-1031-generic",
"binary_version": "5.11.0-1031.35"
},
{
"binary_name": "linux-image-5.11.0-1031-generic",
"binary_version": "5.11.0-1031.35"
},
{
"binary_name": "linux-modules-5.11.0-1031-generic",
"binary_version": "5.11.0-1031.35"
},
{
"binary_name": "linux-modules-extra-5.11.0-1031-generic",
"binary_version": "5.11.0-1031.35"
},
{
"binary_name": "linux-riscv-5.11-headers-5.11.0-1031",
"binary_version": "5.11.0-1031.35"
},
{
"binary_name": "linux-riscv-5.11-tools-5.11.0-1031",
"binary_version": "5.11.0-1031.35"
},
{
"binary_name": "linux-tools-5.11.0-1031-generic",
"binary_version": "5.11.0-1031.35"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-riscv-5.11",
"purl": "pkg:deb/ubuntu/linux-riscv-5.11@5.11.0-1031.35?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.11.0-1015.16~20.04.1",
"5.11.0-1017.18~20.04.1",
"5.11.0-1018.19~20.04.2",
"5.11.0-1020.21~20.04.1",
"5.11.0-1021.22~20.04.1",
"5.11.0-1022.23~20.04.1",
"5.11.0-1023.24~20.04.1",
"5.11.0-1024.25~20.04.1",
"5.11.0-1026.28~20.04.1",
"5.11.0-1028.31~20.04.1",
"5.11.0-1029.32~20.04.1",
"5.11.0-1030.34",
"5.11.0-1031.35"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "block-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "crypto-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "fat-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "firewire-core-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "fs-core-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "input-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "ipmi-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "kernel-image-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.8.0-29-generic",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "linux-headers-5.8.0-29-generic",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "linux-image-5.8.0-29-generic",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "linux-modules-5.8.0-29-generic",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.8.0-29-generic",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "linux-riscv-5.8-headers-5.8.0-29",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "linux-riscv-5.8-tools-5.8.0-29",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "linux-tools-5.8.0-29-generic",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "linux-udebs-generic",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "md-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "message-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "mouse-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "multipath-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "nfs-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "nic-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "parport-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "pata-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "plip-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "ppp-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "sata-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "scsi-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "storage-core-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "usb-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "virtio-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "vlan-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "linux-riscv-5.8",
"purl": "pkg:deb/ubuntu/linux-riscv-5.8@5.8.0-29.31~20.04.1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.8.0-14.16~20.04.1",
"5.8.0-14.16~20.04.3",
"5.8.0-16.18~20.04.1",
"5.8.0-17.19~20.04.1",
"5.8.0-18.20~20.04.1",
"5.8.0-20.22~20.04.1",
"5.8.0-22.24~20.04.1",
"5.8.0-25.27~20.04.1",
"5.8.0-26.28~20.04.1",
"5.8.0-29.31~20.04.1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-aws-fips-headers-5.4.0-1135",
"binary_version": "5.4.0-1135.145+fips1"
},
{
"binary_name": "linux-aws-fips-tools-5.4.0-1135",
"binary_version": "5.4.0-1135.145+fips1"
},
{
"binary_name": "linux-buildinfo-5.4.0-1135-aws-fips",
"binary_version": "5.4.0-1135.145+fips1"
},
{
"binary_name": "linux-headers-5.4.0-1135-aws-fips",
"binary_version": "5.4.0-1135.145+fips1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1135-aws-fips",
"binary_version": "5.4.0-1135.145+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.4.0-1135-aws-fips",
"binary_version": "5.4.0-1135.145+fips1"
},
{
"binary_name": "linux-modules-5.4.0-1135-aws-fips",
"binary_version": "5.4.0-1135.145+fips1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1135-aws-fips",
"binary_version": "5.4.0-1135.145+fips1"
},
{
"binary_name": "linux-tools-5.4.0-1135-aws-fips",
"binary_version": "5.4.0-1135.145+fips1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:20.04:LTS",
"name": "linux-aws-fips",
"purl": "pkg:deb/ubuntu/linux-aws-fips@5.4.0-1135.145+fips1?arch=source\u0026distro=fips-updates/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1135.145+fips1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1021.21+fips2",
"5.4.0-1069.73+fips2",
"5.4.0-1071.76+fips1",
"5.4.0-1072.77+fips1",
"5.4.0-1073.78+fips1",
"5.4.0-1078.84+fips1",
"5.4.0-1080.87+fips1",
"5.4.0-1081.88+fips1",
"5.4.0-1083.90+fips1",
"5.4.0-1085.92+fips1",
"5.4.0-1086.93+fips1",
"5.4.0-1088.96+fips1",
"5.4.0-1089.97+fips1",
"5.4.0-1092.100+fips1",
"5.4.0-1093.101+fips1",
"5.4.0-1094.102+fips1",
"5.4.0-1096.104+fips1",
"5.4.0-1099.107+fips1",
"5.4.0-1100.108+fips1",
"5.4.0-1101.109+fips1",
"5.4.0-1102.110+fips1",
"5.4.0-1103.111+fips1",
"5.4.0-1104.112+fips1",
"5.4.0-1105.113+fips1",
"5.4.0-1106.114+fips1",
"5.4.0-1107.115+fips1",
"5.4.0-1108.116+fips1",
"5.4.0-1109.118+fips1",
"5.4.0-1110.119+fips1",
"5.4.0-1111.120+fips1",
"5.4.0-1112.121+fips1",
"5.4.0-1113.123+fips1",
"5.4.0-1114.124+fips1",
"5.4.0-1116.126+fips1",
"5.4.0-1117.127+fips1",
"5.4.0-1118.128+fips1",
"5.4.0-1119.129+fips1",
"5.4.0-1120.130+fips1",
"5.4.0-1121.131+fips1",
"5.4.0-1122.132+fips1",
"5.4.0-1123.133+fips1",
"5.4.0-1124.134+fips1",
"5.4.0-1125.135+fips1",
"5.4.0-1126.136+fips2",
"5.4.0-1127.137+fips1",
"5.4.0-1128.138+fips1",
"5.4.0-1129.139+fips1",
"5.4.0-1130.140+fips1",
"5.4.0-1131.141+fips1",
"5.4.0-1132.142+fips1",
"5.4.0-1133.143+fips1",
"5.4.0-1134.144+fips1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-azure-fips-cloud-tools-5.4.0-1140",
"binary_version": "5.4.0-1140.147+fips1"
},
{
"binary_name": "linux-azure-fips-headers-5.4.0-1140",
"binary_version": "5.4.0-1140.147+fips1"
},
{
"binary_name": "linux-azure-fips-tools-5.4.0-1140",
"binary_version": "5.4.0-1140.147+fips1"
},
{
"binary_name": "linux-buildinfo-5.4.0-1140-azure-fips",
"binary_version": "5.4.0-1140.147+fips1"
},
{
"binary_name": "linux-cloud-tools-5.4.0-1140-azure-fips",
"binary_version": "5.4.0-1140.147+fips1"
},
{
"binary_name": "linux-headers-5.4.0-1140-azure-fips",
"binary_version": "5.4.0-1140.147+fips1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1140-azure-fips",
"binary_version": "5.4.0-1140.147+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.4.0-1140-azure-fips",
"binary_version": "5.4.0-1140.147+fips1"
},
{
"binary_name": "linux-modules-5.4.0-1140-azure-fips",
"binary_version": "5.4.0-1140.147+fips1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1140-azure-fips",
"binary_version": "5.4.0-1140.147+fips1"
},
{
"binary_name": "linux-tools-5.4.0-1140-azure-fips",
"binary_version": "5.4.0-1140.147+fips1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:20.04:LTS",
"name": "linux-azure-fips",
"purl": "pkg:deb/ubuntu/linux-azure-fips@5.4.0-1140.147+fips1?arch=source\u0026distro=fips-updates/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1140.147+fips1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1022.22+fips1",
"5.4.0-1073.76+fips1",
"5.4.0-1074.77+fips1",
"5.4.0-1076.79+fips1",
"5.4.0-1078.81+fips1",
"5.4.0-1080.83+fips1",
"5.4.0-1083.87+fips1",
"5.4.0-1085.90+fips1",
"5.4.0-1086.91+fips1",
"5.4.0-1089.94+fips1",
"5.4.0-1090.95+fips1",
"5.4.0-1091.96+fips1",
"5.4.0-1094.100+fips1",
"5.4.0-1095.101+fips1",
"5.4.0-1098.104+fips1",
"5.4.0-1100.106+fips1",
"5.4.0-1101.107+fips1",
"5.4.0-1103.109+fips1",
"5.4.0-1104.110+fips1",
"5.4.0-1105.111+fips1",
"5.4.0-1106.112+fips1",
"5.4.0-1107.113+fips1",
"5.4.0-1108.114+fips1",
"5.4.0-1109.115+fips1",
"5.4.0-1110.116+fips1",
"5.4.0-1111.117+fips1",
"5.4.0-1112.118+fips1",
"5.4.0-1113.119+fips1",
"5.4.0-1114.120+fips1",
"5.4.0-1115.122+fips1",
"5.4.0-1116.123+fips1",
"5.4.0-1117.124+fips1",
"5.4.0-1118.125+fips1",
"5.4.0-1119.126+fips1",
"5.4.0-1121.128+fips1",
"5.4.0-1122.129+fips1",
"5.4.0-1123.130+fips1",
"5.4.0-1124.131+fips1",
"5.4.0-1126.133+fips1",
"5.4.0-1127.134+fips1",
"5.4.0-1128.135+fips1",
"5.4.0-1129.136+fips1",
"5.4.0-1130.137+fips1",
"5.4.0-1131.138+fips1",
"5.4.0-1132.139+fips1",
"5.4.0-1133.140+fips1",
"5.4.0-1134.141+fips1",
"5.4.0-1135.142+fips1",
"5.4.0-1136.143+fips1",
"5.4.0-1137.144+fips1",
"5.4.0-1138.145+fips1",
"5.4.0-1139.146+fips1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1109-fips",
"binary_version": "5.4.0-1109.119"
},
{
"binary_name": "linux-fips-headers-5.4.0-1109",
"binary_version": "5.4.0-1109.119"
},
{
"binary_name": "linux-fips-tools-5.4.0-1109",
"binary_version": "5.4.0-1109.119"
},
{
"binary_name": "linux-fips-tools-host",
"binary_version": "5.4.0-1109.119"
},
{
"binary_name": "linux-headers-5.4.0-1109-fips",
"binary_version": "5.4.0-1109.119"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1109-fips",
"binary_version": "5.4.0-1109.119"
},
{
"binary_name": "linux-image-unsigned-hmac-5.4.0-1109-fips",
"binary_version": "5.4.0-1109.119"
},
{
"binary_name": "linux-modules-5.4.0-1109-fips",
"binary_version": "5.4.0-1109.119"
},
{
"binary_name": "linux-modules-extra-5.4.0-1109-fips",
"binary_version": "5.4.0-1109.119"
},
{
"binary_name": "linux-tools-5.4.0-1109-fips",
"binary_version": "5.4.0-1109.119"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:20.04:LTS",
"name": "linux-fips",
"purl": "pkg:deb/ubuntu/linux-fips@5.4.0-1109.119?arch=source\u0026distro=fips-updates/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1109.119"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1026.30",
"5.4.0-1028.32",
"5.4.0-1031.36",
"5.4.0-1032.37",
"5.4.0-1033.38",
"5.4.0-1034.40",
"5.4.0-1035.41",
"5.4.0-1036.42",
"5.4.0-1037.43",
"5.4.0-1038.44",
"5.4.0-1040.46",
"5.4.0-1041.47",
"5.4.0-1042.48",
"5.4.0-1043.49",
"5.4.0-1045.51",
"5.4.0-1046.52",
"5.4.0-1047.53",
"5.4.0-1048.54",
"5.4.0-1049.55",
"5.4.0-1051.57",
"5.4.0-1054.61",
"5.4.0-1056.64",
"5.4.0-1057.65",
"5.4.0-1059.67",
"5.4.0-1060.68",
"5.4.0-1061.69",
"5.4.0-1062.70",
"5.4.0-1064.73",
"5.4.0-1065.74",
"5.4.0-1068.77",
"5.4.0-1069.78",
"5.4.0-1070.79",
"5.4.0-1072.81",
"5.4.0-1073.82",
"5.4.0-1074.83",
"5.4.0-1075.84",
"5.4.0-1076.85",
"5.4.0-1077.86",
"5.4.0-1078.87",
"5.4.0-1079.88",
"5.4.0-1080.89",
"5.4.0-1081.90",
"5.4.0-1082.91",
"5.4.0-1083.92",
"5.4.0-1084.93",
"5.4.0-1085.94",
"5.4.0-1086.95",
"5.4.0-1087.96",
"5.4.0-1088.97",
"5.4.0-1089.98",
"5.4.0-1090.100",
"5.4.0-1091.101",
"5.4.0-1092.102",
"5.4.0-1094.104",
"5.4.0-1095.105",
"5.4.0-1096.106",
"5.4.0-1097.107",
"5.4.0-1098.108",
"5.4.0-1099.109",
"5.4.0-1100.110",
"5.4.0-1101.111",
"5.4.0-1102.112",
"5.4.0-1103.113",
"5.4.0-1104.114",
"5.4.0-1105.115",
"5.4.0-1106.116",
"5.4.0-1107.117",
"5.4.0-1108.118"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1139-gcp-fips",
"binary_version": "5.4.0-1139.148+fips1"
},
{
"binary_name": "linux-gcp-fips-headers-5.4.0-1139",
"binary_version": "5.4.0-1139.148+fips1"
},
{
"binary_name": "linux-gcp-fips-tools-5.4.0-1139",
"binary_version": "5.4.0-1139.148+fips1"
},
{
"binary_name": "linux-headers-5.4.0-1139-gcp-fips",
"binary_version": "5.4.0-1139.148+fips1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1139-gcp-fips",
"binary_version": "5.4.0-1139.148+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.4.0-1139-gcp-fips",
"binary_version": "5.4.0-1139.148+fips1"
},
{
"binary_name": "linux-modules-5.4.0-1139-gcp-fips",
"binary_version": "5.4.0-1139.148+fips1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1139-gcp-fips",
"binary_version": "5.4.0-1139.148+fips1"
},
{
"binary_name": "linux-tools-5.4.0-1139-gcp-fips",
"binary_version": "5.4.0-1139.148+fips1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:20.04:LTS",
"name": "linux-gcp-fips",
"purl": "pkg:deb/ubuntu/linux-gcp-fips@5.4.0-1139.148+fips1?arch=source\u0026distro=fips-updates/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.0-1139.148+fips1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1021.21+fips1",
"5.4.0-1067.71~20.04.1",
"5.4.0-1069.73+fips2",
"5.4.0-1071.75+fips1",
"5.4.0-1073.78+fips1",
"5.4.0-1075.80+fips1",
"5.4.0-1078.84+fips1",
"5.4.0-1080.87+fips1",
"5.4.0-1081.88+fips1",
"5.4.0-1086.94+fips1",
"5.4.0-1087.95+fips1",
"5.4.0-1089.97+fips1",
"5.4.0-1092.101+fips1",
"5.4.0-1093.102+fips1",
"5.4.0-1096.105+fips1",
"5.4.0-1097.106+fips1",
"5.4.0-1098.107+fips1",
"5.4.0-1100.109+fips1",
"5.4.0-1101.110+fips1",
"5.4.0-1102.111+fips1",
"5.4.0-1103.112+fips1",
"5.4.0-1104.113+fips1",
"5.4.0-1105.114+fips1",
"5.4.0-1106.115+fips1",
"5.4.0-1107.116+fips1",
"5.4.0-1108.117+fips1",
"5.4.0-1109.118+fips1",
"5.4.0-1110.119+fips1",
"5.4.0-1111.120+fips1",
"5.4.0-1112.121+fips1",
"5.4.0-1113.122+fips1",
"5.4.0-1115.124+fips1",
"5.4.0-1116.125+fips1",
"5.4.0-1117.126+fips1",
"5.4.0-1118.127+fips1",
"5.4.0-1120.129+fips1",
"5.4.0-1121.130+fips1",
"5.4.0-1122.131+fips1",
"5.4.0-1124.133+fips1",
"5.4.0-1125.134+fips1",
"5.4.0-1126.135+fips1",
"5.4.0-1127.136+fips1",
"5.4.0-1128.137+fips1",
"5.4.0-1129.138+fips1",
"5.4.0-1130.139+fips1",
"5.4.0-1131.140+fips1",
"5.4.0-1132.141+fips1",
"5.4.0-1133.142+fips1",
"5.4.0-1134.143+fips1",
"5.4.0-1135.144+fips1",
"5.4.0-1136.145+fips1",
"5.4.0-1137.146+fips1",
"5.4.0-1138.147+fips1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-aws-fips-headers-5.4.0-1021",
"binary_version": "5.4.0-1021.21+fips2"
},
{
"binary_name": "linux-aws-fips-tools-5.4.0-1021",
"binary_version": "5.4.0-1021.21+fips2"
},
{
"binary_name": "linux-buildinfo-5.4.0-1021-aws-fips",
"binary_version": "5.4.0-1021.21+fips2"
},
{
"binary_name": "linux-headers-5.4.0-1021-aws-fips",
"binary_version": "5.4.0-1021.21+fips2"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1021-aws-fips",
"binary_version": "5.4.0-1021.21+fips2"
},
{
"binary_name": "linux-image-unsigned-hmac-5.4.0-1021-aws-fips",
"binary_version": "5.4.0-1021.21+fips2"
},
{
"binary_name": "linux-modules-5.4.0-1021-aws-fips",
"binary_version": "5.4.0-1021.21+fips2"
},
{
"binary_name": "linux-modules-extra-5.4.0-1021-aws-fips",
"binary_version": "5.4.0-1021.21+fips2"
},
{
"binary_name": "linux-tools-5.4.0-1021-aws-fips",
"binary_version": "5.4.0-1021.21+fips2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS:20.04:LTS",
"name": "linux-aws-fips",
"purl": "pkg:deb/ubuntu/linux-aws-fips@5.4.0-1021.21+fips2?arch=source\u0026distro=fips/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1021.21+fips2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-azure-fips-cloud-tools-5.4.0-1022",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-azure-fips-headers-5.4.0-1022",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-azure-fips-tools-5.4.0-1022",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-buildinfo-5.4.0-1022-azure-fips",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-cloud-tools-5.4.0-1022-azure-fips",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-headers-5.4.0-1022-azure-fips",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1022-azure-fips",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.4.0-1022-azure-fips",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-modules-5.4.0-1022-azure-fips",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1022-azure-fips",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-tools-5.4.0-1022-azure-fips",
"binary_version": "5.4.0-1022.22+fips1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS:20.04:LTS",
"name": "linux-azure-fips",
"purl": "pkg:deb/ubuntu/linux-azure-fips@5.4.0-1022.22+fips1?arch=source\u0026distro=fips/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1022.22+fips1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1007-fips",
"binary_version": "5.4.0-1007.8"
},
{
"binary_name": "linux-fips-headers-5.4.0-1007",
"binary_version": "5.4.0-1007.8"
},
{
"binary_name": "linux-fips-tools-5.4.0-1007",
"binary_version": "5.4.0-1007.8"
},
{
"binary_name": "linux-fips-tools-host",
"binary_version": "5.4.0-1007.8"
},
{
"binary_name": "linux-headers-5.4.0-1007-fips",
"binary_version": "5.4.0-1007.8"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1007-fips",
"binary_version": "5.4.0-1007.8"
},
{
"binary_name": "linux-image-unsigned-hmac-5.4.0-1007-fips",
"binary_version": "5.4.0-1007.8"
},
{
"binary_name": "linux-modules-5.4.0-1007-fips",
"binary_version": "5.4.0-1007.8"
},
{
"binary_name": "linux-modules-extra-5.4.0-1007-fips",
"binary_version": "5.4.0-1007.8"
},
{
"binary_name": "linux-tools-5.4.0-1007-fips",
"binary_version": "5.4.0-1007.8"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS:20.04:LTS",
"name": "linux-fips",
"purl": "pkg:deb/ubuntu/linux-fips@5.4.0-1007.8?arch=source\u0026distro=fips/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1007.8"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1021-gcp-fips",
"binary_version": "5.4.0-1021.21+fips1"
},
{
"binary_name": "linux-gcp-fips-headers-5.4.0-1021",
"binary_version": "5.4.0-1021.21+fips1"
},
{
"binary_name": "linux-gcp-fips-tools-5.4.0-1021",
"binary_version": "5.4.0-1021.21+fips1"
},
{
"binary_name": "linux-headers-5.4.0-1021-gcp-fips",
"binary_version": "5.4.0-1021.21+fips1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1021-gcp-fips",
"binary_version": "5.4.0-1021.21+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.4.0-1021-gcp-fips",
"binary_version": "5.4.0-1021.21+fips1"
},
{
"binary_name": "linux-modules-5.4.0-1021-gcp-fips",
"binary_version": "5.4.0-1021.21+fips1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1021-gcp-fips",
"binary_version": "5.4.0-1021.21+fips1"
},
{
"binary_name": "linux-tools-5.4.0-1021-gcp-fips",
"binary_version": "5.4.0-1021.21+fips1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS:20.04:LTS",
"name": "linux-gcp-fips",
"purl": "pkg:deb/ubuntu/linux-gcp-fips@5.4.0-1021.21+fips1?arch=source\u0026distro=fips/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.4.0-1021.21+fips1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-125-generic",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-buildinfo-5.15.0-125-generic-64k",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-buildinfo-5.15.0-125-generic-lpae",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-cloud-tools-5.15.0-125",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-cloud-tools-5.15.0-125-generic",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-cloud-tools-common",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-headers-5.15.0-125",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-headers-5.15.0-125-generic",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-headers-5.15.0-125-generic-64k",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-headers-5.15.0-125-generic-lpae",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-image-5.15.0-125-generic",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-image-5.15.0-125-generic-lpae",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-image-unsigned-5.15.0-125-generic",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-image-unsigned-5.15.0-125-generic-64k",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-modules-5.15.0-125-generic",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-modules-5.15.0-125-generic-64k",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-modules-5.15.0-125-generic-lpae",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-modules-extra-5.15.0-125-generic",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-125-generic",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-source-5.15.0",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-tools-5.15.0-125",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-tools-5.15.0-125-generic",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-tools-5.15.0-125-generic-64k",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-tools-5.15.0-125-generic-lpae",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-tools-common",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-tools-host",
"binary_version": "5.15.0-125.135"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux",
"purl": "pkg:deb/ubuntu/linux@5.15.0-125.135?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-125.135"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-19.19",
"5.15.0-17.17",
"5.15.0-18.18",
"5.15.0-22.22",
"5.15.0-23.23",
"5.15.0-25.25",
"5.15.0-27.28",
"5.15.0-30.31",
"5.15.0-33.34",
"5.15.0-35.36",
"5.15.0-37.39",
"5.15.0-39.42",
"5.15.0-40.43",
"5.15.0-41.44",
"5.15.0-43.46",
"5.15.0-46.49",
"5.15.0-47.51",
"5.15.0-48.54",
"5.15.0-50.56",
"5.15.0-52.58",
"5.15.0-53.59",
"5.15.0-56.62",
"5.15.0-57.63",
"5.15.0-58.64",
"5.15.0-60.66",
"5.15.0-67.74",
"5.15.0-69.76",
"5.15.0-70.77",
"5.15.0-71.78",
"5.15.0-72.79",
"5.15.0-73.80",
"5.15.0-75.82",
"5.15.0-76.83",
"5.15.0-78.85",
"5.15.0-79.86",
"5.15.0-82.91",
"5.15.0-83.92",
"5.15.0-84.93",
"5.15.0-86.96",
"5.15.0-87.97",
"5.15.0-88.98",
"5.15.0-89.99",
"5.15.0-91.101",
"5.15.0-92.102",
"5.15.0-94.104",
"5.15.0-97.107",
"5.15.0-100.110",
"5.15.0-101.111",
"5.15.0-102.112",
"5.15.0-105.115",
"5.15.0-106.116",
"5.15.0-107.117",
"5.15.0-112.122",
"5.15.0-113.123",
"5.15.0-116.126",
"5.15.0-117.127",
"5.15.0-118.128",
"5.15.0-119.129",
"5.15.0-121.131",
"5.15.0-122.132",
"5.15.0-124.134"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-allwinner-5.19-headers-5.19.0-1015",
"binary_version": "5.19.0-1015.15~22.04.1"
},
{
"binary_name": "linux-allwinner-5.19-tools-5.19.0-1015",
"binary_version": "5.19.0-1015.15~22.04.1"
},
{
"binary_name": "linux-buildinfo-5.19.0-1015-allwinner",
"binary_version": "5.19.0-1015.15~22.04.1"
},
{
"binary_name": "linux-headers-5.19.0-1015-allwinner",
"binary_version": "5.19.0-1015.15~22.04.1"
},
{
"binary_name": "linux-image-5.19.0-1015-allwinner",
"binary_version": "5.19.0-1015.15~22.04.1"
},
{
"binary_name": "linux-modules-5.19.0-1015-allwinner",
"binary_version": "5.19.0-1015.15~22.04.1"
},
{
"binary_name": "linux-modules-extra-5.19.0-1015-allwinner",
"binary_version": "5.19.0-1015.15~22.04.1"
},
{
"binary_name": "linux-tools-5.19.0-1015-allwinner",
"binary_version": "5.19.0-1015.15~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-allwinner-5.19",
"purl": "pkg:deb/ubuntu/linux-allwinner-5.19@5.19.0-1015.15~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.19.0-1007.7~22.04.1",
"5.19.0-1009.9~22.04.1",
"5.19.0-1010.10~22.04.1",
"5.19.0-1011.11~22.04.1",
"5.19.0-1012.12~22.04.1",
"5.19.0-1013.13~22.04.1",
"5.19.0-1014.14~22.04.1",
"5.19.0-1015.15~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-aws-cloud-tools-5.15.0-1072",
"binary_version": "5.15.0-1072.78"
},
{
"binary_name": "linux-aws-headers-5.15.0-1072",
"binary_version": "5.15.0-1072.78"
},
{
"binary_name": "linux-aws-tools-5.15.0-1072",
"binary_version": "5.15.0-1072.78"
},
{
"binary_name": "linux-buildinfo-5.15.0-1072-aws",
"binary_version": "5.15.0-1072.78"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1072-aws",
"binary_version": "5.15.0-1072.78"
},
{
"binary_name": "linux-headers-5.15.0-1072-aws",
"binary_version": "5.15.0-1072.78"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1072-aws",
"binary_version": "5.15.0-1072.78"
},
{
"binary_name": "linux-modules-5.15.0-1072-aws",
"binary_version": "5.15.0-1072.78"
},
{
"binary_name": "linux-modules-extra-5.15.0-1072-aws",
"binary_version": "5.15.0-1072.78"
},
{
"binary_name": "linux-tools-5.15.0-1072-aws",
"binary_version": "5.15.0-1072.78"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-aws",
"purl": "pkg:deb/ubuntu/linux-aws@5.15.0-1072.78?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1072.78"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-1005.6",
"5.15.0-1002.4",
"5.15.0-1003.5",
"5.15.0-1004.6",
"5.15.0-1005.7",
"5.15.0-1008.10",
"5.15.0-1009.11",
"5.15.0-1011.14",
"5.15.0-1013.17",
"5.15.0-1014.18",
"5.15.0-1015.19",
"5.15.0-1017.21",
"5.15.0-1019.23",
"5.15.0-1020.24",
"5.15.0-1021.25",
"5.15.0-1022.26",
"5.15.0-1023.27",
"5.15.0-1026.30",
"5.15.0-1027.31",
"5.15.0-1028.32",
"5.15.0-1030.34",
"5.15.0-1031.35",
"5.15.0-1033.37",
"5.15.0-1034.38",
"5.15.0-1035.39",
"5.15.0-1036.40",
"5.15.0-1037.41",
"5.15.0-1038.43",
"5.15.0-1039.44",
"5.15.0-1040.45",
"5.15.0-1042.47",
"5.15.0-1043.48",
"5.15.0-1044.49",
"5.15.0-1045.50",
"5.15.0-1047.52",
"5.15.0-1048.53",
"5.15.0-1049.54",
"5.15.0-1050.55",
"5.15.0-1051.56",
"5.15.0-1052.57",
"5.15.0-1053.58",
"5.15.0-1055.60",
"5.15.0-1056.61",
"5.15.0-1057.63",
"5.15.0-1060.66",
"5.15.0-1061.67",
"5.15.0-1062.68",
"5.15.0-1063.69",
"5.15.0-1064.70",
"5.15.0-1065.71",
"5.15.0-1066.72",
"5.15.0-1067.73",
"5.15.0-1068.74",
"5.15.0-1069.75",
"5.15.0-1070.76",
"5.15.0-1071.77"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-aws-5.19-cloud-tools-5.19.0-1029",
"binary_version": "5.19.0-1029.30~22.04.1"
},
{
"binary_name": "linux-aws-5.19-headers-5.19.0-1029",
"binary_version": "5.19.0-1029.30~22.04.1"
},
{
"binary_name": "linux-aws-5.19-tools-5.19.0-1029",
"binary_version": "5.19.0-1029.30~22.04.1"
},
{
"binary_name": "linux-buildinfo-5.19.0-1029-aws",
"binary_version": "5.19.0-1029.30~22.04.1"
},
{
"binary_name": "linux-cloud-tools-5.19.0-1029-aws",
"binary_version": "5.19.0-1029.30~22.04.1"
},
{
"binary_name": "linux-headers-5.19.0-1029-aws",
"binary_version": "5.19.0-1029.30~22.04.1"
},
{
"binary_name": "linux-image-unsigned-5.19.0-1029-aws",
"binary_version": "5.19.0-1029.30~22.04.1"
},
{
"binary_name": "linux-modules-5.19.0-1029-aws",
"binary_version": "5.19.0-1029.30~22.04.1"
},
{
"binary_name": "linux-modules-extra-5.19.0-1029-aws",
"binary_version": "5.19.0-1029.30~22.04.1"
},
{
"binary_name": "linux-tools-5.19.0-1029-aws",
"binary_version": "5.19.0-1029.30~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-aws-5.19",
"purl": "pkg:deb/ubuntu/linux-aws-5.19@5.19.0-1029.30~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.19.0-1019.20~22.04.1",
"5.19.0-1020.21~22.04.1",
"5.19.0-1022.23~22.04.1",
"5.19.0-1023.24~22.04.1",
"5.19.0-1024.25~22.04.1",
"5.19.0-1025.26~22.04.1",
"5.19.0-1026.27~22.04.1",
"5.19.0-1027.28~22.04.1",
"5.19.0-1028.29~22.04.1",
"5.19.0-1029.30~22.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-aws-6.2-cloud-tools-6.2.0-1018",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-aws-6.2-headers-6.2.0-1018",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-aws-6.2-tools-6.2.0-1018",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.2.0-1018-aws",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.2.0-1018-aws",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-headers-6.2.0-1018-aws",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.2.0-1018-aws",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-modules-6.2.0-1018-aws",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.2.0-1018-aws",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-tools-6.2.0-1018-aws",
"binary_version": "6.2.0-1018.18~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-aws-6.2",
"purl": "pkg:deb/ubuntu/linux-aws-6.2@6.2.0-1018.18~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.2.0-1005.5~22.04.1",
"6.2.0-1006.6~22.04.1",
"6.2.0-1007.7~22.04.1",
"6.2.0-1008.8~22.04.1",
"6.2.0-1009.9~22.04.3",
"6.2.0-1010.10~22.04.1",
"6.2.0-1011.11~22.04.1",
"6.2.0-1012.12~22.04.1",
"6.2.0-1013.13~22.04.1",
"6.2.0-1014.14~22.04.1",
"6.2.0-1015.15~22.04.1",
"6.2.0-1016.16~22.04.1",
"6.2.0-1017.17~22.04.1",
"6.2.0-1018.18~22.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-aws-6.5-cloud-tools-6.5.0-1024",
"binary_version": "6.5.0-1024.24~22.04.1"
},
{
"binary_name": "linux-aws-6.5-headers-6.5.0-1024",
"binary_version": "6.5.0-1024.24~22.04.1"
},
{
"binary_name": "linux-aws-6.5-tools-6.5.0-1024",
"binary_version": "6.5.0-1024.24~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.5.0-1024-aws",
"binary_version": "6.5.0-1024.24~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.5.0-1024-aws",
"binary_version": "6.5.0-1024.24~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-1024-aws",
"binary_version": "6.5.0-1024.24~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.5.0-1024-aws",
"binary_version": "6.5.0-1024.24~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-1024-aws",
"binary_version": "6.5.0-1024.24~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.5.0-1024-aws",
"binary_version": "6.5.0-1024.24~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-1024-aws",
"binary_version": "6.5.0-1024.24~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-aws-6.5",
"purl": "pkg:deb/ubuntu/linux-aws-6.5@6.5.0-1024.24~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-1008.8~22.04.1",
"6.5.0-1010.10~22.04.1",
"6.5.0-1011.11~22.04.1",
"6.5.0-1012.12~22.04.1",
"6.5.0-1014.14~22.04.1",
"6.5.0-1015.15~22.04.1",
"6.5.0-1016.16~22.04.1",
"6.5.0-1017.17~22.04.2",
"6.5.0-1018.18~22.04.1",
"6.5.0-1020.20~22.04.1",
"6.5.0-1021.21~22.04.1",
"6.5.0-1022.22~22.04.1",
"6.5.0-1023.23~22.04.1",
"6.5.0-1024.24~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-aws-6.8-cloud-tools-6.8.0-1020",
"binary_version": "6.8.0-1020.22~22.04.1"
},
{
"binary_name": "linux-aws-6.8-headers-6.8.0-1020",
"binary_version": "6.8.0-1020.22~22.04.1"
},
{
"binary_name": "linux-aws-6.8-tools-6.8.0-1020",
"binary_version": "6.8.0-1020.22~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.8.0-1020-aws",
"binary_version": "6.8.0-1020.22~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.8.0-1020-aws",
"binary_version": "6.8.0-1020.22~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1020-aws",
"binary_version": "6.8.0-1020.22~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1020-aws",
"binary_version": "6.8.0-1020.22~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1020-aws",
"binary_version": "6.8.0-1020.22~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1020-aws",
"binary_version": "6.8.0-1020.22~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1020-aws",
"binary_version": "6.8.0-1020.22~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-aws-6.8",
"purl": "pkg:deb/ubuntu/linux-aws-6.8@6.8.0-1020.22~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1020.22~22.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1009.9~22.04.2",
"6.8.0-1010.10~22.04.2",
"6.8.0-1011.12~22.04.1",
"6.8.0-1013.14~22.04.1",
"6.8.0-1014.15~22.04.1",
"6.8.0-1015.16~22.04.1",
"6.8.0-1016.17~22.04.2",
"6.8.0-1017.18~22.04.1",
"6.8.0-1018.19~22.04.1",
"6.8.0-1019.21~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-azure-cloud-tools-5.15.0-1075",
"binary_version": "5.15.0-1075.84"
},
{
"binary_name": "linux-azure-headers-5.15.0-1075",
"binary_version": "5.15.0-1075.84"
},
{
"binary_name": "linux-azure-tools-5.15.0-1075",
"binary_version": "5.15.0-1075.84"
},
{
"binary_name": "linux-buildinfo-5.15.0-1075-azure",
"binary_version": "5.15.0-1075.84"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1075-azure",
"binary_version": "5.15.0-1075.84"
},
{
"binary_name": "linux-headers-5.15.0-1075-azure",
"binary_version": "5.15.0-1075.84"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1075-azure",
"binary_version": "5.15.0-1075.84"
},
{
"binary_name": "linux-modules-5.15.0-1075-azure",
"binary_version": "5.15.0-1075.84"
},
{
"binary_name": "linux-modules-extra-5.15.0-1075-azure",
"binary_version": "5.15.0-1075.84"
},
{
"binary_name": "linux-modules-involflt-5.15.0-1075-azure",
"binary_version": "5.15.0-1075.84"
},
{
"binary_name": "linux-tools-5.15.0-1075-azure",
"binary_version": "5.15.0-1075.84"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-azure",
"purl": "pkg:deb/ubuntu/linux-azure@5.15.0-1075.84?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1075.84"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-1006.7",
"5.15.0-1001.2",
"5.15.0-1002.3",
"5.15.0-1003.4",
"5.15.0-1005.6",
"5.15.0-1007.8",
"5.15.0-1008.9",
"5.15.0-1010.12",
"5.15.0-1012.15",
"5.15.0-1013.16",
"5.15.0-1014.17",
"5.15.0-1017.20",
"5.15.0-1019.24",
"5.15.0-1020.25",
"5.15.0-1021.26",
"5.15.0-1022.27",
"5.15.0-1023.29",
"5.15.0-1024.30",
"5.15.0-1029.36",
"5.15.0-1030.37",
"5.15.0-1031.38",
"5.15.0-1033.40",
"5.15.0-1034.41",
"5.15.0-1035.42",
"5.15.0-1036.43",
"5.15.0-1037.44",
"5.15.0-1038.45",
"5.15.0-1039.46",
"5.15.0-1040.47",
"5.15.0-1041.48",
"5.15.0-1042.49",
"5.15.0-1044.51",
"5.15.0-1045.52",
"5.15.0-1046.53",
"5.15.0-1047.54",
"5.15.0-1049.56",
"5.15.0-1050.57",
"5.15.0-1051.59",
"5.15.0-1052.60",
"5.15.0-1053.61",
"5.15.0-1054.62",
"5.15.0-1056.64",
"5.15.0-1057.65",
"5.15.0-1058.66",
"5.15.0-1059.67",
"5.15.0-1060.69",
"5.15.0-1061.70",
"5.15.0-1063.72",
"5.15.0-1064.73",
"5.15.0-1066.75",
"5.15.0-1067.76",
"5.15.0-1068.77",
"5.15.0-1070.79",
"5.15.0-1071.80",
"5.15.0-1072.81",
"5.15.0-1073.82",
"5.15.0-1074.83"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-azure-5.19-cloud-tools-5.19.0-1027",
"binary_version": "5.19.0-1027.30~22.04.2"
},
{
"binary_name": "linux-azure-5.19-headers-5.19.0-1027",
"binary_version": "5.19.0-1027.30~22.04.2"
},
{
"binary_name": "linux-azure-5.19-tools-5.19.0-1027",
"binary_version": "5.19.0-1027.30~22.04.2"
},
{
"binary_name": "linux-buildinfo-5.19.0-1027-azure",
"binary_version": "5.19.0-1027.30~22.04.2"
},
{
"binary_name": "linux-cloud-tools-5.19.0-1027-azure",
"binary_version": "5.19.0-1027.30~22.04.2"
},
{
"binary_name": "linux-headers-5.19.0-1027-azure",
"binary_version": "5.19.0-1027.30~22.04.2"
},
{
"binary_name": "linux-image-unsigned-5.19.0-1027-azure",
"binary_version": "5.19.0-1027.30~22.04.2"
},
{
"binary_name": "linux-modules-5.19.0-1027-azure",
"binary_version": "5.19.0-1027.30~22.04.2"
},
{
"binary_name": "linux-modules-extra-5.19.0-1027-azure",
"binary_version": "5.19.0-1027.30~22.04.2"
},
{
"binary_name": "linux-tools-5.19.0-1027-azure",
"binary_version": "5.19.0-1027.30~22.04.2"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-azure-5.19",
"purl": "pkg:deb/ubuntu/linux-azure-5.19@5.19.0-1027.30~22.04.2?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.19.0-1020.21~22.04.1",
"5.19.0-1021.22~22.04.1",
"5.19.0-1022.23~22.04.1",
"5.19.0-1023.24~22.04.1",
"5.19.0-1025.28~22.04.1",
"5.19.0-1026.29~22.04.1",
"5.19.0-1027.30~22.04.2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-azure-6.2-cloud-tools-6.2.0-1019",
"binary_version": "6.2.0-1019.19~22.04.1"
},
{
"binary_name": "linux-azure-6.2-headers-6.2.0-1019",
"binary_version": "6.2.0-1019.19~22.04.1"
},
{
"binary_name": "linux-azure-6.2-tools-6.2.0-1019",
"binary_version": "6.2.0-1019.19~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.2.0-1019-azure",
"binary_version": "6.2.0-1019.19~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.2.0-1019-azure",
"binary_version": "6.2.0-1019.19~22.04.1"
},
{
"binary_name": "linux-headers-6.2.0-1019-azure",
"binary_version": "6.2.0-1019.19~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.2.0-1019-azure",
"binary_version": "6.2.0-1019.19~22.04.1"
},
{
"binary_name": "linux-modules-6.2.0-1019-azure",
"binary_version": "6.2.0-1019.19~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.2.0-1019-azure",
"binary_version": "6.2.0-1019.19~22.04.1"
},
{
"binary_name": "linux-tools-6.2.0-1019-azure",
"binary_version": "6.2.0-1019.19~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-azure-6.2",
"purl": "pkg:deb/ubuntu/linux-azure-6.2@6.2.0-1019.19~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.2.0-1005.5~22.04.1",
"6.2.0-1006.6~22.04.1",
"6.2.0-1007.7~22.04.1",
"6.2.0-1008.8~22.04.1",
"6.2.0-1009.9~22.04.3",
"6.2.0-1011.11~22.04.1",
"6.2.0-1012.12~22.04.1",
"6.2.0-1014.14~22.04.1",
"6.2.0-1015.15~22.04.1",
"6.2.0-1016.16~22.04.1",
"6.2.0-1017.17~22.04.1",
"6.2.0-1018.18~22.04.1",
"6.2.0-1019.19~22.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-azure-6.5-cloud-tools-6.5.0-1025",
"binary_version": "6.5.0-1025.26~22.04.1"
},
{
"binary_name": "linux-azure-6.5-headers-6.5.0-1025",
"binary_version": "6.5.0-1025.26~22.04.1"
},
{
"binary_name": "linux-azure-6.5-tools-6.5.0-1025",
"binary_version": "6.5.0-1025.26~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.5.0-1025-azure",
"binary_version": "6.5.0-1025.26~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.5.0-1025-azure",
"binary_version": "6.5.0-1025.26~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-1025-azure",
"binary_version": "6.5.0-1025.26~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.5.0-1025-azure",
"binary_version": "6.5.0-1025.26~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-1025-azure",
"binary_version": "6.5.0-1025.26~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.5.0-1025-azure",
"binary_version": "6.5.0-1025.26~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-1025-azure",
"binary_version": "6.5.0-1025.26~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-azure-6.5",
"purl": "pkg:deb/ubuntu/linux-azure-6.5@6.5.0-1025.26~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-1007.7~22.04.1",
"6.5.0-1009.9~22.04.1",
"6.5.0-1010.10~22.04.1",
"6.5.0-1011.11~22.04.1",
"6.5.0-1015.15~22.04.1",
"6.5.0-1016.16~22.04.1",
"6.5.0-1017.17~22.04.1",
"6.5.0-1018.19~22.04.2",
"6.5.0-1019.20~22.04.1",
"6.5.0-1021.22~22.04.1",
"6.5.0-1022.23~22.04.1",
"6.5.0-1023.24~22.04.1",
"6.5.0-1024.25~22.04.1",
"6.5.0-1025.26~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-azure-6.8-cloud-tools-6.8.0-1020",
"binary_version": "6.8.0-1020.23~22.04.1"
},
{
"binary_name": "linux-azure-6.8-headers-6.8.0-1020",
"binary_version": "6.8.0-1020.23~22.04.1"
},
{
"binary_name": "linux-azure-6.8-tools-6.8.0-1020",
"binary_version": "6.8.0-1020.23~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23~22.04.1"
},
{
"binary_name": "linux-modules-involflt-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-azure-6.8",
"purl": "pkg:deb/ubuntu/linux-azure-6.8@6.8.0-1020.23~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1020.23~22.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1008.8~22.04.1",
"6.8.0-1009.9~22.04.1",
"6.8.0-1010.10~22.04.1",
"6.8.0-1012.14~22.04.1",
"6.8.0-1013.15~22.04.1",
"6.8.0-1014.16~22.04.1",
"6.8.0-1015.17~22.04.2",
"6.8.0-1017.20~22.04.1",
"6.8.0-1018.21~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-image-unsigned-5.15.0-1076-azure-fde",
"binary_version": "5.15.0-1076.85.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-azure-fde",
"purl": "pkg:deb/ubuntu/linux-azure-fde@5.15.0-1076.85.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1076.85.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",
"5.15.0-1072.81.1",
"5.15.0-1073.82.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"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-azure-fde-5.19",
"purl": "pkg:deb/ubuntu/linux-azure-fde-5.19@5.19.0-1027.30~22.04.2.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.19.0-1025.28~22.04.1.1",
"5.19.0-1026.29~22.04.1.1",
"5.19.0-1027.30~22.04.2.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-image-unsigned-6.2.0-1019-azure-fde",
"binary_version": "6.2.0-1019.19~22.04.1.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-azure-fde-6.2",
"purl": "pkg:deb/ubuntu/linux-azure-fde-6.2@6.2.0-1019.19~22.04.1.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.2.0-1008.8~22.04.1.1",
"6.2.0-1009.9~22.04.3.1",
"6.2.0-1011.11~22.04.1.1",
"6.2.0-1012.12~22.04.1.1",
"6.2.0-1014.14~22.04.1.1",
"6.2.0-1015.15~22.04.1.1",
"6.2.0-1016.16~22.04.1.1",
"6.2.0-1017.17~22.04.1.1",
"6.2.0-1018.18~22.04.1.1",
"6.2.0-1019.19~22.04.1.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1071-gcp",
"binary_version": "5.15.0-1071.79"
},
{
"binary_name": "linux-gcp-headers-5.15.0-1071",
"binary_version": "5.15.0-1071.79"
},
{
"binary_name": "linux-gcp-tools-5.15.0-1071",
"binary_version": "5.15.0-1071.79"
},
{
"binary_name": "linux-headers-5.15.0-1071-gcp",
"binary_version": "5.15.0-1071.79"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1071-gcp",
"binary_version": "5.15.0-1071.79"
},
{
"binary_name": "linux-modules-5.15.0-1071-gcp",
"binary_version": "5.15.0-1071.79"
},
{
"binary_name": "linux-modules-extra-5.15.0-1071-gcp",
"binary_version": "5.15.0-1071.79"
},
{
"binary_name": "linux-tools-5.15.0-1071-gcp",
"binary_version": "5.15.0-1071.79"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-gcp",
"purl": "pkg:deb/ubuntu/linux-gcp@5.15.0-1071.79?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1071.79"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-1005.6",
"5.15.0-1001.3",
"5.15.0-1002.5",
"5.15.0-1003.6",
"5.15.0-1004.7",
"5.15.0-1005.8",
"5.15.0-1006.9",
"5.15.0-1008.12",
"5.15.0-1010.15",
"5.15.0-1013.18",
"5.15.0-1016.21",
"5.15.0-1017.23",
"5.15.0-1018.24",
"5.15.0-1019.25",
"5.15.0-1021.28",
"5.15.0-1022.29",
"5.15.0-1025.32",
"5.15.0-1026.33",
"5.15.0-1027.34",
"5.15.0-1029.36",
"5.15.0-1030.37",
"5.15.0-1031.38",
"5.15.0-1032.40",
"5.15.0-1034.42",
"5.15.0-1035.43",
"5.15.0-1036.44",
"5.15.0-1037.45",
"5.15.0-1038.46",
"5.15.0-1039.47",
"5.15.0-1040.48",
"5.15.0-1041.49",
"5.15.0-1042.50",
"5.15.0-1044.52",
"5.15.0-1045.53",
"5.15.0-1046.54",
"5.15.0-1047.55",
"5.15.0-1048.56",
"5.15.0-1049.57",
"5.15.0-1051.59",
"5.15.0-1052.60",
"5.15.0-1053.61",
"5.15.0-1054.62",
"5.15.0-1055.63",
"5.15.0-1058.66",
"5.15.0-1059.67",
"5.15.0-1060.68",
"5.15.0-1062.70",
"5.15.0-1063.71",
"5.15.0-1064.72",
"5.15.0-1065.73",
"5.15.0-1066.74",
"5.15.0-1067.75",
"5.15.0-1068.76",
"5.15.0-1069.77",
"5.15.0-1070.78"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.19.0-1030-gcp",
"binary_version": "5.19.0-1030.32~22.04.1"
},
{
"binary_name": "linux-gcp-5.19-headers-5.19.0-1030",
"binary_version": "5.19.0-1030.32~22.04.1"
},
{
"binary_name": "linux-gcp-5.19-tools-5.19.0-1030",
"binary_version": "5.19.0-1030.32~22.04.1"
},
{
"binary_name": "linux-headers-5.19.0-1030-gcp",
"binary_version": "5.19.0-1030.32~22.04.1"
},
{
"binary_name": "linux-image-unsigned-5.19.0-1030-gcp",
"binary_version": "5.19.0-1030.32~22.04.1"
},
{
"binary_name": "linux-modules-5.19.0-1030-gcp",
"binary_version": "5.19.0-1030.32~22.04.1"
},
{
"binary_name": "linux-modules-extra-5.19.0-1030-gcp",
"binary_version": "5.19.0-1030.32~22.04.1"
},
{
"binary_name": "linux-tools-5.19.0-1030-gcp",
"binary_version": "5.19.0-1030.32~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-gcp-5.19",
"purl": "pkg:deb/ubuntu/linux-gcp-5.19@5.19.0-1030.32~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.19.0-1020.22~22.04.2",
"5.19.0-1021.23~22.04.1",
"5.19.0-1022.24~22.04.1",
"5.19.0-1024.26~22.04.1",
"5.19.0-1025.27~22.04.1",
"5.19.0-1026.28~22.04.1",
"5.19.0-1027.29~22.04.1",
"5.19.0-1030.32~22.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.2.0-1021-gcp",
"binary_version": "6.2.0-1021.23~22.04.1"
},
{
"binary_name": "linux-gcp-6.2-headers-6.2.0-1021",
"binary_version": "6.2.0-1021.23~22.04.1"
},
{
"binary_name": "linux-gcp-6.2-tools-6.2.0-1021",
"binary_version": "6.2.0-1021.23~22.04.1"
},
{
"binary_name": "linux-headers-6.2.0-1021-gcp",
"binary_version": "6.2.0-1021.23~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.2.0-1021-gcp",
"binary_version": "6.2.0-1021.23~22.04.1"
},
{
"binary_name": "linux-modules-6.2.0-1021-gcp",
"binary_version": "6.2.0-1021.23~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.2.0-1021-gcp",
"binary_version": "6.2.0-1021.23~22.04.1"
},
{
"binary_name": "linux-tools-6.2.0-1021-gcp",
"binary_version": "6.2.0-1021.23~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-gcp-6.2",
"purl": "pkg:deb/ubuntu/linux-gcp-6.2@6.2.0-1021.23~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.2.0-1009.9~22.04.3",
"6.2.0-1010.10~22.04.1",
"6.2.0-1011.11~22.04.1",
"6.2.0-1011.11~22.04.3",
"6.2.0-1012.12~22.04.1",
"6.2.0-1013.13~22.04.1",
"6.2.0-1014.14~22.04.1",
"6.2.0-1016.18~22.04.1",
"6.2.0-1017.19~22.04.1",
"6.2.0-1018.20~22.04.1",
"6.2.0-1019.21~22.04.1",
"6.2.0-1021.23~22.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.5.0-1025-gcp",
"binary_version": "6.5.0-1025.27~22.04.1"
},
{
"binary_name": "linux-gcp-6.5-headers-6.5.0-1025",
"binary_version": "6.5.0-1025.27~22.04.1"
},
{
"binary_name": "linux-gcp-6.5-tools-6.5.0-1025",
"binary_version": "6.5.0-1025.27~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-1025-gcp",
"binary_version": "6.5.0-1025.27~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.5.0-1025-gcp",
"binary_version": "6.5.0-1025.27~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-1025-gcp",
"binary_version": "6.5.0-1025.27~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.5.0-1025-gcp",
"binary_version": "6.5.0-1025.27~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.5.0-1025-gcp",
"binary_version": "6.5.0-1025.27~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-1025-gcp",
"binary_version": "6.5.0-1025.27~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-gcp-6.5",
"purl": "pkg:deb/ubuntu/linux-gcp-6.5@6.5.0-1025.27~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-1010.10~22.04.3",
"6.5.0-1011.11~22.04.1",
"6.5.0-1013.13~22.04.1",
"6.5.0-1014.14~22.04.1",
"6.5.0-1015.15~22.04.1",
"6.5.0-1016.16~22.04.1",
"6.5.0-1017.17~22.04.1",
"6.5.0-1018.18~22.04.1",
"6.5.0-1020.20~22.04.1",
"6.5.0-1022.24~22.04.1",
"6.5.0-1023.25~22.04.1",
"6.5.0-1024.26~22.04.1",
"6.5.0-1025.27~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1019-gcp",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-gcp-6.8-headers-6.8.0-1019",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-gcp-6.8-tools-6.8.0-1019",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1019-gcp",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1019-gcp",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1019-gcp",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1019-gcp",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1019-gcp",
"binary_version": "6.8.0-1019.21~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-gcp-6.8",
"purl": "pkg:deb/ubuntu/linux-gcp-6.8@6.8.0-1019.21~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1019.21~22.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1010.11~22.04.1",
"6.8.0-1011.12~22.04.1",
"6.8.0-1012.13~22.04.1",
"6.8.0-1013.14~22.04.1",
"6.8.0-1014.16~22.04.1",
"6.8.0-1015.17~22.04.1",
"6.8.0-1016.18~22.04.1",
"6.8.0-1017.19~22.04.1",
"6.8.0-1018.20~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1069-gke",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-gke-headers-5.15.0-1069",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-gke-tools-5.15.0-1069",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-headers-5.15.0-1069-gke",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1069-gke",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-modules-5.15.0-1069-gke",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-modules-extra-5.15.0-1069-gke",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-tools-5.15.0-1069-gke",
"binary_version": "5.15.0-1069.75"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-gke",
"purl": "pkg:deb/ubuntu/linux-gke@5.15.0-1069.75?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1069.75"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1002.2",
"5.15.0-1003.3",
"5.15.0-1004.5",
"5.15.0-1005.6",
"5.15.0-1006.7",
"5.15.0-1008.10",
"5.15.0-1010.13",
"5.15.0-1011.14",
"5.15.0-1014.17",
"5.15.0-1015.18",
"5.15.0-1016.19",
"5.15.0-1017.20",
"5.15.0-1019.23",
"5.15.0-1020.25",
"5.15.0-1023.28",
"5.15.0-1024.29",
"5.15.0-1027.32",
"5.15.0-1028.33",
"5.15.0-1030.35",
"5.15.0-1031.36",
"5.15.0-1032.37",
"5.15.0-1033.38",
"5.15.0-1034.39",
"5.15.0-1035.40",
"5.15.0-1036.41",
"5.15.0-1037.42",
"5.15.0-1038.43",
"5.15.0-1039.44",
"5.15.0-1040.45",
"5.15.0-1041.46",
"5.15.0-1042.47",
"5.15.0-1044.49",
"5.15.0-1045.50",
"5.15.0-1046.51",
"5.15.0-1047.52",
"5.15.0-1048.53",
"5.15.0-1049.54",
"5.15.0-1050.55",
"5.15.0-1051.56",
"5.15.0-1052.57",
"5.15.0-1053.58",
"5.15.0-1054.59",
"5.15.0-1057.62",
"5.15.0-1058.63",
"5.15.0-1059.64",
"5.15.0-1060.66",
"5.15.0-1061.67",
"5.15.0-1062.68",
"5.15.0-1063.69",
"5.15.0-1064.70",
"5.15.0-1065.71",
"5.15.0-1066.72",
"5.15.0-1067.73",
"5.15.0-1068.74"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1055-gkeop",
"binary_version": "5.15.0-1055.62"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1055-gkeop",
"binary_version": "5.15.0-1055.62"
},
{
"binary_name": "linux-gkeop-cloud-tools-5.15.0-1055",
"binary_version": "5.15.0-1055.62"
},
{
"binary_name": "linux-gkeop-headers-5.15.0-1055",
"binary_version": "5.15.0-1055.62"
},
{
"binary_name": "linux-gkeop-tools-5.15.0-1055",
"binary_version": "5.15.0-1055.62"
},
{
"binary_name": "linux-headers-5.15.0-1055-gkeop",
"binary_version": "5.15.0-1055.62"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1055-gkeop",
"binary_version": "5.15.0-1055.62"
},
{
"binary_name": "linux-modules-5.15.0-1055-gkeop",
"binary_version": "5.15.0-1055.62"
},
{
"binary_name": "linux-modules-extra-5.15.0-1055-gkeop",
"binary_version": "5.15.0-1055.62"
},
{
"binary_name": "linux-tools-5.15.0-1055-gkeop",
"binary_version": "5.15.0-1055.62"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-gkeop",
"purl": "pkg:deb/ubuntu/linux-gkeop@5.15.0-1055.62?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1055.62"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1001.2",
"5.15.0-1002.4",
"5.15.0-1003.5",
"5.15.0-1004.6",
"5.15.0-1005.7",
"5.15.0-1007.10",
"5.15.0-1008.12",
"5.15.0-1011.15",
"5.15.0-1012.16",
"5.15.0-1013.17",
"5.15.0-1015.19",
"5.15.0-1016.21",
"5.15.0-1017.22",
"5.15.0-1018.23",
"5.15.0-1019.24",
"5.15.0-1020.25",
"5.15.0-1021.26",
"5.15.0-1022.27",
"5.15.0-1023.28",
"5.15.0-1024.29",
"5.15.0-1025.30",
"5.15.0-1026.31",
"5.15.0-1027.32",
"5.15.0-1028.33",
"5.15.0-1030.35",
"5.15.0-1031.37",
"5.15.0-1032.38",
"5.15.0-1033.39",
"5.15.0-1034.40",
"5.15.0-1035.41",
"5.15.0-1036.42",
"5.15.0-1037.43",
"5.15.0-1038.44",
"5.15.0-1039.45",
"5.15.0-1040.46",
"5.15.0-1043.50",
"5.15.0-1044.51",
"5.15.0-1045.52",
"5.15.0-1046.53",
"5.15.0-1047.54",
"5.15.0-1048.55",
"5.15.0-1049.56",
"5.15.0-1050.57",
"5.15.0-1051.58",
"5.15.0-1052.59",
"5.15.0-1053.60",
"5.15.0-1054.61"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-buildinfo-5.19.0-50-generic-64k",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-buildinfo-5.19.0-50-generic-lpae",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-cloud-tools-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-headers-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-headers-5.19.0-50-generic-64k",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-headers-5.19.0-50-generic-lpae",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-hwe-5.19-cloud-tools-5.19.0-50",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-hwe-5.19-cloud-tools-common",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-hwe-5.19-headers-5.19.0-50",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-hwe-5.19-tools-5.19.0-50",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-hwe-5.19-tools-common",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-hwe-5.19-tools-host",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-image-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-image-5.19.0-50-generic-lpae",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-image-unsigned-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-image-unsigned-5.19.0-50-generic-64k",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-modules-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-modules-5.19.0-50-generic-64k",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-modules-5.19.0-50-generic-lpae",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-modules-extra-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-modules-ipu6-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-modules-ivsc-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-modules-iwlwifi-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-source-5.19.0",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-tools-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-tools-5.19.0-50-generic-64k",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-tools-5.19.0-50-generic-lpae",
"binary_version": "5.19.0-50.50"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-hwe-5.19",
"purl": "pkg:deb/ubuntu/linux-hwe-5.19@5.19.0-50.50?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.19.0-28.29~22.04.1",
"5.19.0-32.33~22.04.1",
"5.19.0-35.36~22.04.1",
"5.19.0-38.39~22.04.1",
"5.19.0-40.41~22.04.1",
"5.19.0-41.42~22.04.1",
"5.19.0-42.43~22.04.1",
"5.19.0-43.44~22.04.1",
"5.19.0-45.46~22.04.1",
"5.19.0-46.47~22.04.1",
"5.19.0-50.50"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.2.0-39-generic-64k",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.2.0-39-generic-lpae",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-headers-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-headers-6.2.0-39-generic-64k",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-headers-6.2.0-39-generic-lpae",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-hwe-6.2-cloud-tools-6.2.0-39",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-hwe-6.2-cloud-tools-common",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-hwe-6.2-headers-6.2.0-39",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-hwe-6.2-tools-6.2.0-39",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-hwe-6.2-tools-common",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-hwe-6.2-tools-host",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-image-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-image-6.2.0-39-generic-lpae",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.2.0-39-generic-64k",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-modules-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-modules-6.2.0-39-generic-64k",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-modules-6.2.0-39-generic-lpae",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-modules-ipu6-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-modules-ivsc-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-source-6.2.0",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-tools-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-tools-6.2.0-39-generic-64k",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-tools-6.2.0-39-generic-lpae",
"binary_version": "6.2.0-39.40~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-hwe-6.2",
"purl": "pkg:deb/ubuntu/linux-hwe-6.2@6.2.0-39.40~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.2.0-25.25~22.04.2",
"6.2.0-26.26~22.04.1",
"6.2.0-31.31~22.04.1",
"6.2.0-32.32~22.04.1",
"6.2.0-33.33~22.04.1",
"6.2.0-34.34~22.04.1",
"6.2.0-35.35~22.04.1",
"6.2.0-36.37~22.04.1",
"6.2.0-37.38~22.04.1",
"6.2.0-39.40~22.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.5.0-45-generic-64k",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-45-generic-64k",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-hwe-6.5-cloud-tools-6.5.0-45",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-hwe-6.5-cloud-tools-common",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-hwe-6.5-headers-6.5.0-45",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-hwe-6.5-tools-6.5.0-45",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-hwe-6.5-tools-common",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-hwe-6.5-tools-host",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-image-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.5.0-45-generic-64k",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-45-generic-64k",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-modules-ipu6-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-modules-ivsc-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-source-6.5.0",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-45-generic-64k",
"binary_version": "6.5.0-45.45~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-hwe-6.5",
"purl": "pkg:deb/ubuntu/linux-hwe-6.5@6.5.0-45.45~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-14.14~22.04.1",
"6.5.0-15.15~22.04.1",
"6.5.0-17.17~22.04.1",
"6.5.0-18.18~22.04.1",
"6.5.0-21.21~22.04.1",
"6.5.0-25.25~22.04.1",
"6.5.0-26.26~22.04.1",
"6.5.0-27.28~22.04.1",
"6.5.0-28.29~22.04.1",
"6.5.0-35.35~22.04.1",
"6.5.0-41.41~22.04.2",
"6.5.0-44.44~22.04.1",
"6.5.0-45.45~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-50-generic",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.8.0-50-generic-64k",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.8.0-50-generic",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-50-generic",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-50-generic-64k",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-hwe-6.8-cloud-tools-6.8.0-50",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-hwe-6.8-headers-6.8.0-50",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-hwe-6.8-tools-6.8.0-50",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-image-6.8.0-50-generic",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-50-generic",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-50-generic-64k",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-50-generic",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-50-generic-64k",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-50-generic",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-modules-ipu6-6.8.0-50-generic",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-50-generic",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-modules-usbio-6.8.0-50-generic",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-50-generic",
"binary_version": "6.8.0-50.51~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-50-generic-64k",
"binary_version": "6.8.0-50.51~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-hwe-6.8",
"purl": "pkg:deb/ubuntu/linux-hwe-6.8@6.8.0-50.51~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-50.51~22.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-38.38~22.04.1",
"6.8.0-39.39~22.04.1",
"6.8.0-40.40~22.04.3",
"6.8.0-45.45~22.04.1",
"6.8.0-47.47~22.04.1",
"6.8.0-48.48~22.04.1",
"6.8.0-49.49~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1065-ibm",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-headers-5.15.0-1065-ibm",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-ibm-cloud-tools-common",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-ibm-headers-5.15.0-1065",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-ibm-source-5.15.0",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-ibm-tools-5.15.0-1065",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-ibm-tools-common",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1065-ibm",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-modules-5.15.0-1065-ibm",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-modules-extra-5.15.0-1065-ibm",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-tools-5.15.0-1065-ibm",
"binary_version": "5.15.0-1065.68"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-ibm",
"purl": "pkg:deb/ubuntu/linux-ibm@5.15.0-1065.68?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1065.68"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1002.2",
"5.15.0-1003.3",
"5.15.0-1004.4",
"5.15.0-1005.5",
"5.15.0-1007.8",
"5.15.0-1009.11",
"5.15.0-1010.12",
"5.15.0-1012.14",
"5.15.0-1013.15",
"5.15.0-1015.17",
"5.15.0-1017.20",
"5.15.0-1018.21",
"5.15.0-1021.24",
"5.15.0-1022.25",
"5.15.0-1023.26",
"5.15.0-1025.28",
"5.15.0-1026.29",
"5.15.0-1027.30",
"5.15.0-1028.31",
"5.15.0-1029.32",
"5.15.0-1030.33",
"5.15.0-1031.34",
"5.15.0-1032.35",
"5.15.0-1033.36",
"5.15.0-1034.37",
"5.15.0-1035.38",
"5.15.0-1036.39",
"5.15.0-1037.40",
"5.15.0-1038.41",
"5.15.0-1040.43",
"5.15.0-1041.44",
"5.15.0-1042.45",
"5.15.0-1043.46",
"5.15.0-1044.47",
"5.15.0-1045.48",
"5.15.0-1046.49",
"5.15.0-1047.50",
"5.15.0-1048.51",
"5.15.0-1049.52",
"5.15.0-1050.53",
"5.15.0-1053.56",
"5.15.0-1054.57",
"5.15.0-1055.58",
"5.15.0-1056.59",
"5.15.0-1057.60",
"5.15.0-1058.61",
"5.15.0-1059.62",
"5.15.0-1060.63",
"5.15.0-1061.64",
"5.15.0-1062.65",
"5.15.0-1063.66",
"5.15.0-1064.67"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1017-ibm",
"binary_version": "6.8.0-1017.17~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1017-ibm",
"binary_version": "6.8.0-1017.17~22.04.1"
},
{
"binary_name": "linux-ibm-6.8-headers-6.8.0-1017",
"binary_version": "6.8.0-1017.17~22.04.1"
},
{
"binary_name": "linux-ibm-6.8-source-6.8.0",
"binary_version": "6.8.0-1017.17~22.04.1"
},
{
"binary_name": "linux-ibm-6.8-tools-6.8.0-1017",
"binary_version": "6.8.0-1017.17~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1017-ibm",
"binary_version": "6.8.0-1017.17~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1017-ibm",
"binary_version": "6.8.0-1017.17~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1017-ibm",
"binary_version": "6.8.0-1017.17~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-1017-ibm",
"binary_version": "6.8.0-1017.17~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1017-ibm",
"binary_version": "6.8.0-1017.17~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-ibm-6.8",
"purl": "pkg:deb/ubuntu/linux-ibm-6.8@6.8.0-1017.17~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1017.17~22.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1008.8~22.04.1",
"6.8.0-1010.10~22.04.1",
"6.8.0-1011.11~22.04.1",
"6.8.0-1012.12~22.04.1",
"6.8.0-1013.13~22.04.1",
"6.8.0-1014.14~22.04.1",
"6.8.0-1015.15~22.04.1",
"6.8.0-1016.16~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-headers-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-intel-iotg-cloud-tools-5.15.0-1067",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-intel-iotg-cloud-tools-common",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-intel-iotg-headers-5.15.0-1067",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-intel-iotg-tools-5.15.0-1067",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-intel-iotg-tools-common",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-intel-iotg-tools-host",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-modules-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-modules-extra-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-tools-5.15.0-1067-intel-iotg",
"binary_version": "5.15.0-1067.73"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-intel-iotg",
"purl": "pkg:deb/ubuntu/linux-intel-iotg@5.15.0-1067.73?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1067.73"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1004.6",
"5.15.0-1008.11",
"5.15.0-1010.14",
"5.15.0-1013.17",
"5.15.0-1015.20",
"5.15.0-1016.21",
"5.15.0-1017.22",
"5.15.0-1018.23",
"5.15.0-1021.26",
"5.15.0-1023.28",
"5.15.0-1025.30",
"5.15.0-1026.31",
"5.15.0-1027.32",
"5.15.0-1028.33",
"5.15.0-1030.35",
"5.15.0-1031.36",
"5.15.0-1033.38",
"5.15.0-1034.39",
"5.15.0-1035.40",
"5.15.0-1036.41",
"5.15.0-1037.42",
"5.15.0-1038.43",
"5.15.0-1039.45",
"5.15.0-1040.46",
"5.15.0-1043.49",
"5.15.0-1045.51",
"5.15.0-1046.52",
"5.15.0-1047.53",
"5.15.0-1048.54",
"5.15.0-1049.55",
"5.15.0-1050.56",
"5.15.0-1051.57",
"5.15.0-1052.58",
"5.15.0-1055.61",
"5.15.0-1057.63",
"5.15.0-1058.64",
"5.15.0-1059.65",
"5.15.0-1060.66",
"5.15.0-1061.67",
"5.15.0-1062.68",
"5.15.0-1063.69",
"5.15.0-1064.70",
"5.15.0-1065.71",
"5.15.0-1066.72"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1069-kvm",
"binary_version": "5.15.0-1069.74"
},
{
"binary_name": "linux-headers-5.15.0-1069-kvm",
"binary_version": "5.15.0-1069.74"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1069-kvm",
"binary_version": "5.15.0-1069.74"
},
{
"binary_name": "linux-kvm-headers-5.15.0-1069",
"binary_version": "5.15.0-1069.74"
},
{
"binary_name": "linux-kvm-tools-5.15.0-1069",
"binary_version": "5.15.0-1069.74"
},
{
"binary_name": "linux-modules-5.15.0-1069-kvm",
"binary_version": "5.15.0-1069.74"
},
{
"binary_name": "linux-tools-5.15.0-1069-kvm",
"binary_version": "5.15.0-1069.74"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-kvm",
"purl": "pkg:deb/ubuntu/linux-kvm@5.15.0-1069.74?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1069.74"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-1004.4",
"5.13.0-1006.6+22.04.1",
"5.13.0-1007.7+22.04.1",
"5.13.0-1010.11+22.04.1",
"5.15.0-1002.2",
"5.15.0-1004.4",
"5.15.0-1005.5",
"5.15.0-1007.7",
"5.15.0-1008.8",
"5.15.0-1010.11",
"5.15.0-1012.14",
"5.15.0-1013.16",
"5.15.0-1016.19",
"5.15.0-1017.21",
"5.15.0-1018.22",
"5.15.0-1019.23",
"5.15.0-1020.24",
"5.15.0-1021.26",
"5.15.0-1024.29",
"5.15.0-1025.30",
"5.15.0-1026.31",
"5.15.0-1028.33",
"5.15.0-1029.34",
"5.15.0-1030.35",
"5.15.0-1031.36",
"5.15.0-1032.37",
"5.15.0-1033.38",
"5.15.0-1034.39",
"5.15.0-1035.40",
"5.15.0-1037.42",
"5.15.0-1038.43",
"5.15.0-1039.44",
"5.15.0-1040.45",
"5.15.0-1041.46",
"5.15.0-1042.47",
"5.15.0-1044.49",
"5.15.0-1045.50",
"5.15.0-1046.51",
"5.15.0-1047.52",
"5.15.0-1048.53",
"5.15.0-1049.54",
"5.15.0-1050.55",
"5.15.0-1051.56",
"5.15.0-1052.57",
"5.15.0-1053.58",
"5.15.0-1054.59",
"5.15.0-1057.62",
"5.15.0-1058.63",
"5.15.0-1059.64",
"5.15.0-1060.65",
"5.15.0-1061.66",
"5.15.0-1062.67",
"5.15.0-1063.68",
"5.15.0-1064.69",
"5.15.0-1065.70",
"5.15.0-1066.71",
"5.15.0-1067.72",
"5.15.0-1068.73"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-125-lowlatency",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-buildinfo-5.15.0-125-lowlatency-64k",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-cloud-tools-5.15.0-125-lowlatency",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-headers-5.15.0-125-lowlatency",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-headers-5.15.0-125-lowlatency-64k",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-image-unsigned-5.15.0-125-lowlatency",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-image-unsigned-5.15.0-125-lowlatency-64k",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-lowlatency-cloud-tools-5.15.0-125",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-lowlatency-cloud-tools-common",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-lowlatency-headers-5.15.0-125",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-lowlatency-tools-5.15.0-125",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-lowlatency-tools-common",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-lowlatency-tools-host",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-modules-5.15.0-125-lowlatency",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-modules-5.15.0-125-lowlatency-64k",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-125-lowlatency",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-tools-5.15.0-125-lowlatency",
"binary_version": "5.15.0-125.135"
},
{
"binary_name": "linux-tools-5.15.0-125-lowlatency-64k",
"binary_version": "5.15.0-125.135"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-lowlatency",
"purl": "pkg:deb/ubuntu/linux-lowlatency@5.15.0-125.135?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-125.135"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-22.22",
"5.15.0-23.23",
"5.15.0-24.24",
"5.15.0-27.28",
"5.15.0-30.31",
"5.15.0-33.34",
"5.15.0-35.36",
"5.15.0-37.39",
"5.15.0-39.42",
"5.15.0-40.43",
"5.15.0-41.44",
"5.15.0-43.46",
"5.15.0-46.49",
"5.15.0-47.53",
"5.15.0-48.54",
"5.15.0-50.56",
"5.15.0-52.58",
"5.15.0-53.59",
"5.15.0-56.62",
"5.15.0-57.63",
"5.15.0-58.64",
"5.15.0-60.66",
"5.15.0-67.74",
"5.15.0-69.76",
"5.15.0-70.77",
"5.15.0-71.78",
"5.15.0-72.79",
"5.15.0-73.80",
"5.15.0-75.82",
"5.15.0-76.83",
"5.15.0-78.85",
"5.15.0-79.88",
"5.15.0-82.91",
"5.15.0-83.92",
"5.15.0-84.93",
"5.15.0-86.95",
"5.15.0-87.96",
"5.15.0-88.98",
"5.15.0-89.99",
"5.15.0-91.101",
"5.15.0-92.102",
"5.15.0-94.104",
"5.15.0-97.107",
"5.15.0-100.110",
"5.15.0-101.111",
"5.15.0-102.112",
"5.15.0-105.115",
"5.15.0-106.116",
"5.15.0-107.117",
"5.15.0-110.120",
"5.15.0-113.123",
"5.15.0-116.126",
"5.15.0-117.127",
"5.15.0-118.128",
"5.15.0-119.129",
"5.15.0-121.131",
"5.15.0-122.132",
"5.15.0-124.134"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.19.0-1030-lowlatency",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-buildinfo-5.19.0-1030-lowlatency-64k",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-cloud-tools-5.19.0-1030-lowlatency",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-headers-5.19.0-1030-lowlatency",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-headers-5.19.0-1030-lowlatency-64k",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-image-unsigned-5.19.0-1030-lowlatency",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-image-unsigned-5.19.0-1030-lowlatency-64k",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-lowlatency-hwe-5.19-cloud-tools-5.19.0-1030",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-lowlatency-hwe-5.19-cloud-tools-common",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-lowlatency-hwe-5.19-headers-5.19.0-1030",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-lowlatency-hwe-5.19-tools-5.19.0-1030",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-lowlatency-hwe-5.19-tools-common",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-lowlatency-hwe-5.19-tools-host",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-modules-5.19.0-1030-lowlatency",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-modules-5.19.0-1030-lowlatency-64k",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-modules-ipu6-5.19.0-1030-lowlatency",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-modules-ivsc-5.19.0-1030-lowlatency",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-modules-iwlwifi-5.19.0-1030-lowlatency",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-tools-5.19.0-1030-lowlatency",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-tools-5.19.0-1030-lowlatency-64k",
"binary_version": "5.19.0-1030.30"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-lowlatency-hwe-5.19",
"purl": "pkg:deb/ubuntu/linux-lowlatency-hwe-5.19@5.19.0-1030.30?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.19.0-1017.18~22.04.1",
"5.19.0-1018.19~22.04.1",
"5.19.0-1021.22~22.04.1",
"5.19.0-1022.23~22.04.1",
"5.19.0-1023.24~22.04.1",
"5.19.0-1024.25~22.04.1",
"5.19.0-1025.26~22.04.1",
"5.19.0-1027.28~22.04.1",
"5.19.0-1028.29~22.04.1",
"5.19.0-1030.30"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.2.0-1018-lowlatency",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.2.0-1018-lowlatency-64k",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.2.0-1018-lowlatency",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-headers-6.2.0-1018-lowlatency",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-headers-6.2.0-1018-lowlatency-64k",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.2.0-1018-lowlatency",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.2.0-1018-lowlatency-64k",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.2-cloud-tools-6.2.0-1018",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.2-cloud-tools-common",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.2-headers-6.2.0-1018",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.2-tools-6.2.0-1018",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.2-tools-common",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.2-tools-host",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-modules-6.2.0-1018-lowlatency",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-modules-6.2.0-1018-lowlatency-64k",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-modules-ipu6-6.2.0-1018-lowlatency",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-modules-ivsc-6.2.0-1018-lowlatency",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.2.0-1018-lowlatency",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-tools-6.2.0-1018-lowlatency",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-tools-6.2.0-1018-lowlatency-64k",
"binary_version": "6.2.0-1018.18~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-lowlatency-hwe-6.2",
"purl": "pkg:deb/ubuntu/linux-lowlatency-hwe-6.2@6.2.0-1018.18~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.2.0-1008.8~22.04.1",
"6.2.0-1009.9~22.04.1",
"6.2.0-1011.11~22.04.1",
"6.2.0-1012.12~22.04.1",
"6.2.0-1013.13~22.04.1",
"6.2.0-1014.14~22.04.1",
"6.2.0-1015.15~22.04.1",
"6.2.0-1016.16~22.04.1",
"6.2.0-1017.17~22.04.1",
"6.2.0-1018.18~22.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.5.0-45-lowlatency",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.5.0-45-lowlatency-64k",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.5.0-45-lowlatency",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-45-lowlatency",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-45-lowlatency-64k",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.5.0-45-lowlatency",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.5.0-45-lowlatency-64k",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.5-cloud-tools-6.5.0-45",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.5-cloud-tools-common",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.5-headers-6.5.0-45",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.5-lib-rust-6.5.0-45-lowlatency",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.5-tools-6.5.0-45",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.5-tools-common",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.5-tools-host",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-45-lowlatency",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-45-lowlatency-64k",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.5.0-45-lowlatency",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-45-lowlatency",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-45-lowlatency-64k",
"binary_version": "6.5.0-45.45.1~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-lowlatency-hwe-6.5",
"purl": "pkg:deb/ubuntu/linux-lowlatency-hwe-6.5@6.5.0-45.45.1~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-14.14.1~22.04.1",
"6.5.0-15.15.1.1~22.04.1",
"6.5.0-17.17.1.1.1~22.04.1",
"6.5.0-21.21.1~22.04.1",
"6.5.0-25.25.1~22.04.1",
"6.5.0-26.26.1~22.04.1",
"6.5.0-27.28.1~22.04.1",
"6.5.0-28.29.1~22.04.1",
"6.5.0-35.35.1~22.04.1",
"6.5.0-41.41.1~22.04.1",
"6.5.0-42.42.1~22.04.1",
"6.5.0-44.44.1~22.04.1",
"6.5.0-45.45.1~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.8.0-50-lowlatency-64k",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-50-lowlatency-64k",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-50-lowlatency-64k",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.8-cloud-tools-6.8.0-50",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.8-headers-6.8.0-50",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.8-lib-rust-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.8-tools-6.8.0-50",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-50-lowlatency-64k",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-50-lowlatency-64k",
"binary_version": "6.8.0-50.51.1~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-lowlatency-hwe-6.8",
"purl": "pkg:deb/ubuntu/linux-lowlatency-hwe-6.8@6.8.0-50.51.1~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-50.51.1~22.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-38.38.1~22.04.2",
"6.8.0-40.40.1~22.04.1",
"6.8.0-44.44.1~22.04.1",
"6.8.0-45.45.1~22.04.1",
"6.8.0-47.47.1~22.04.1",
"6.8.0-48.48.3~22.04.1",
"6.8.0-49.49.1~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1067-nvidia",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-buildinfo-5.15.0-1067-nvidia-lowlatency",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1067-nvidia",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1067-nvidia-lowlatency",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-headers-5.15.0-1067-nvidia",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-headers-5.15.0-1067-nvidia-lowlatency",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1067-nvidia",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1067-nvidia-lowlatency",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-modules-5.15.0-1067-nvidia",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-modules-5.15.0-1067-nvidia-lowlatency",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-modules-extra-5.15.0-1067-nvidia",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-modules-nvidia-fs-5.15.0-1067-nvidia",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-modules-nvidia-fs-5.15.0-1067-nvidia-lowlatency",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-nvidia-cloud-tools-5.15.0-1067",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-nvidia-cloud-tools-common",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-nvidia-headers-5.15.0-1067",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-nvidia-tools-5.15.0-1067",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-nvidia-tools-common",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-nvidia-tools-host",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-tools-5.15.0-1067-nvidia",
"binary_version": "5.15.0-1067.68"
},
{
"binary_name": "linux-tools-5.15.0-1067-nvidia-lowlatency",
"binary_version": "5.15.0-1067.68"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-nvidia",
"purl": "pkg:deb/ubuntu/linux-nvidia@5.15.0-1067.68?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1067.68"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1005.5",
"5.15.0-1007.7",
"5.15.0-1010.10",
"5.15.0-1015.15",
"5.15.0-1017.17",
"5.15.0-1018.18",
"5.15.0-1023.23",
"5.15.0-1025.25",
"5.15.0-1026.26",
"5.15.0-1027.27",
"5.15.0-1028.28",
"5.15.0-1029.29",
"5.15.0-1030.30",
"5.15.0-1031.31",
"5.15.0-1032.32",
"5.15.0-1033.33",
"5.15.0-1037.37",
"5.15.0-1039.39",
"5.15.0-1040.40",
"5.15.0-1041.41",
"5.15.0-1042.42",
"5.15.0-1043.43",
"5.15.0-1044.44",
"5.15.0-1045.45",
"5.15.0-1046.46",
"5.15.0-1047.47",
"5.15.0-1048.48",
"5.15.0-1053.54",
"5.15.0-1054.55",
"5.15.0-1055.56",
"5.15.0-1058.59",
"5.15.0-1059.60",
"5.15.0-1060.61",
"5.15.0-1061.62",
"5.15.0-1062.63",
"5.15.0-1063.64",
"5.15.0-1064.65",
"5.15.0-1065.66",
"5.15.0-1066.67"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.2.0-1015-nvidia",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-buildinfo-6.2.0-1015-nvidia-64k",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-headers-6.2.0-1015-nvidia",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-headers-6.2.0-1015-nvidia-64k",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-image-unsigned-6.2.0-1015-nvidia",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-image-unsigned-6.2.0-1015-nvidia-64k",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-modules-6.2.0-1015-nvidia",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-modules-6.2.0-1015-nvidia-64k",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-modules-extra-6.2.0-1015-nvidia",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-modules-nvidia-fs-6.2.0-1015-nvidia",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-modules-nvidia-fs-6.2.0-1015-nvidia-64k",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-nvidia-6.2-headers-6.2.0-1015",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-nvidia-6.2-tools-6.2.0-1015",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-nvidia-6.2-tools-host",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-tools-6.2.0-1015-nvidia",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-tools-6.2.0-1015-nvidia-64k",
"binary_version": "6.2.0-1015.15"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-nvidia-6.2",
"purl": "pkg:deb/ubuntu/linux-nvidia-6.2@6.2.0-1015.15?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.2.0-1003.3~22.04.1",
"6.2.0-1009.9",
"6.2.0-1010.10",
"6.2.0-1011.11",
"6.2.0-1012.12",
"6.2.0-1013.13",
"6.2.0-1015.15"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.5.0-1024-nvidia",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-buildinfo-6.5.0-1024-nvidia-64k",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-headers-6.5.0-1024-nvidia",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-headers-6.5.0-1024-nvidia-64k",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-image-unsigned-6.5.0-1024-nvidia",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-image-unsigned-6.5.0-1024-nvidia-64k",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-modules-6.5.0-1024-nvidia",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-modules-6.5.0-1024-nvidia-64k",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-modules-extra-6.5.0-1024-nvidia",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-modules-nvidia-fs-6.5.0-1024-nvidia",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-modules-nvidia-fs-6.5.0-1024-nvidia-64k",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-nvidia-6.5-headers-6.5.0-1024",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-nvidia-6.5-tools-6.5.0-1024",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-nvidia-6.5-tools-host",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-tools-6.5.0-1024-nvidia",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-tools-6.5.0-1024-nvidia-64k",
"binary_version": "6.5.0-1024.25"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-nvidia-6.5",
"purl": "pkg:deb/ubuntu/linux-nvidia-6.5@6.5.0-1024.25?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-1004.4",
"6.5.0-1007.7",
"6.5.0-1013.13",
"6.5.0-1014.14",
"6.5.0-1015.15",
"6.5.0-1018.18",
"6.5.0-1019.19",
"6.5.0-1021.22",
"6.5.0-1022.23",
"6.5.0-1023.24",
"6.5.0-1024.25"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1019-nvidia",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.8.0-1019-nvidia-64k",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1019-nvidia",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1019-nvidia-64k",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1019-nvidia",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1019-nvidia-64k",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1019-nvidia",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1019-nvidia-64k",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1019-nvidia",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-modules-nvidia-fs-6.8.0-1019-nvidia",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-modules-nvidia-fs-6.8.0-1019-nvidia-64k",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-nvidia-6.8-headers-6.8.0-1019",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-nvidia-6.8-tools-6.8.0-1019",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1019-nvidia",
"binary_version": "6.8.0-1019.21~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1019-nvidia-64k",
"binary_version": "6.8.0-1019.21~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-nvidia-6.8",
"purl": "pkg:deb/ubuntu/linux-nvidia-6.8@6.8.0-1019.21~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1019.21~22.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1008.8~22.04.1",
"6.8.0-1009.9~22.04.1",
"6.8.0-1010.10~22.04.1",
"6.8.0-1011.11~22.04.1",
"6.8.0-1012.12~22.04.1",
"6.8.0-1013.14~22.04.1",
"6.8.0-1014.15~22.04.1",
"6.8.0-1015.16~22.04.1",
"6.8.0-1017.19~22.04.1",
"6.8.0-1018.20~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1032-nvidia-tegra",
"binary_version": "5.15.0-1032.32"
},
{
"binary_name": "linux-buildinfo-5.15.0-1032-nvidia-tegra-rt",
"binary_version": "5.15.0-1032.32"
},
{
"binary_name": "linux-headers-5.15.0-1032-nvidia-tegra",
"binary_version": "5.15.0-1032.32"
},
{
"binary_name": "linux-headers-5.15.0-1032-nvidia-tegra-rt",
"binary_version": "5.15.0-1032.32"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1032-nvidia-tegra",
"binary_version": "5.15.0-1032.32"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1032-nvidia-tegra-rt",
"binary_version": "5.15.0-1032.32"
},
{
"binary_name": "linux-modules-5.15.0-1032-nvidia-tegra",
"binary_version": "5.15.0-1032.32"
},
{
"binary_name": "linux-modules-5.15.0-1032-nvidia-tegra-rt",
"binary_version": "5.15.0-1032.32"
},
{
"binary_name": "linux-modules-extra-5.15.0-1032-nvidia-tegra",
"binary_version": "5.15.0-1032.32"
},
{
"binary_name": "linux-nvidia-tegra-headers-5.15.0-1032",
"binary_version": "5.15.0-1032.32"
},
{
"binary_name": "linux-nvidia-tegra-tools-5.15.0-1032",
"binary_version": "5.15.0-1032.32"
},
{
"binary_name": "linux-tools-5.15.0-1032-nvidia-tegra",
"binary_version": "5.15.0-1032.32"
},
{
"binary_name": "linux-tools-5.15.0-1032-nvidia-tegra-rt",
"binary_version": "5.15.0-1032.32"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-nvidia-tegra",
"purl": "pkg:deb/ubuntu/linux-nvidia-tegra@5.15.0-1032.32?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1032.32"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1009.9",
"5.15.0-1010.10",
"5.15.0-1012.12",
"5.15.0-1013.13",
"5.15.0-1014.14",
"5.15.0-1015.15",
"5.15.0-1016.16",
"5.15.0-1017.17",
"5.15.0-1018.18",
"5.15.0-1019.19",
"5.15.0-1020.20",
"5.15.0-1021.21",
"5.15.0-1022.22",
"5.15.0-1025.25",
"5.15.0-1026.26",
"5.15.0-1027.27",
"5.15.0-1028.28",
"5.15.0-1030.30"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1020-nvidia-tegra-igx",
"binary_version": "5.15.0-1020.20"
},
{
"binary_name": "linux-buildinfo-5.15.0-1020-nvidia-tegra-igx-rt",
"binary_version": "5.15.0-1020.20"
},
{
"binary_name": "linux-headers-5.15.0-1020-nvidia-tegra-igx",
"binary_version": "5.15.0-1020.20"
},
{
"binary_name": "linux-headers-5.15.0-1020-nvidia-tegra-igx-rt",
"binary_version": "5.15.0-1020.20"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1020-nvidia-tegra-igx",
"binary_version": "5.15.0-1020.20"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1020-nvidia-tegra-igx-rt",
"binary_version": "5.15.0-1020.20"
},
{
"binary_name": "linux-modules-5.15.0-1020-nvidia-tegra-igx",
"binary_version": "5.15.0-1020.20"
},
{
"binary_name": "linux-modules-5.15.0-1020-nvidia-tegra-igx-rt",
"binary_version": "5.15.0-1020.20"
},
{
"binary_name": "linux-modules-extra-5.15.0-1020-nvidia-tegra-igx",
"binary_version": "5.15.0-1020.20"
},
{
"binary_name": "linux-nvidia-tegra-igx-headers-5.15.0-1020",
"binary_version": "5.15.0-1020.20"
},
{
"binary_name": "linux-nvidia-tegra-igx-tools-5.15.0-1020",
"binary_version": "5.15.0-1020.20"
},
{
"binary_name": "linux-tools-5.15.0-1020-nvidia-tegra-igx",
"binary_version": "5.15.0-1020.20"
},
{
"binary_name": "linux-tools-5.15.0-1020-nvidia-tegra-igx-rt",
"binary_version": "5.15.0-1020.20"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-nvidia-tegra-igx",
"purl": "pkg:deb/ubuntu/linux-nvidia-tegra-igx@5.15.0-1020.20?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1020.20"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1001.1",
"5.15.0-1002.2",
"5.15.0-1004.4",
"5.15.0-1005.5",
"5.15.0-1006.6",
"5.15.0-1007.7",
"5.15.0-1008.8",
"5.15.0-1009.9",
"5.15.0-1012.12",
"5.15.0-1013.13",
"5.15.0-1015.15",
"5.15.0-1016.16",
"5.15.0-1018.18",
"5.15.0-1019.19"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.17.0-1035-oem",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-headers-5.17.0-1035-oem",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-image-unsigned-5.17.0-1035-oem",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-modules-5.17.0-1035-oem",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-modules-ipu6-5.17.0-1035-oem",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-modules-ivsc-5.17.0-1035-oem",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-modules-iwlwifi-5.17.0-1035-oem",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-oem-5.17-headers-5.17.0-1035",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-oem-5.17-tools-5.17.0-1035",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-oem-5.17-tools-host",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-tools-5.17.0-1035-oem",
"binary_version": "5.17.0-1035.36"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-oem-5.17",
"purl": "pkg:deb/ubuntu/linux-oem-5.17@5.17.0-1035.36?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.17.0-1003.3",
"5.17.0-1004.4",
"5.17.0-1006.6",
"5.17.0-1011.12",
"5.17.0-1012.13",
"5.17.0-1013.14",
"5.17.0-1014.15",
"5.17.0-1015.16",
"5.17.0-1016.17",
"5.17.0-1017.18",
"5.17.0-1018.19",
"5.17.0-1019.20",
"5.17.0-1020.21",
"5.17.0-1021.22",
"5.17.0-1024.25",
"5.17.0-1025.26",
"5.17.0-1026.27",
"5.17.0-1027.28",
"5.17.0-1028.29",
"5.17.0-1029.30",
"5.17.0-1030.31",
"5.17.0-1031.32",
"5.17.0-1032.33",
"5.17.0-1033.34",
"5.17.0-1034.35",
"5.17.0-1035.36"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.0.0-1021-oem",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-headers-6.0.0-1021-oem",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-image-unsigned-6.0.0-1021-oem",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-modules-6.0.0-1021-oem",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-modules-ipu6-6.0.0-1021-oem",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-modules-ivsc-6.0.0-1021-oem",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-modules-iwlwifi-6.0.0-1021-oem",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-oem-6.0-headers-6.0.0-1021",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-oem-6.0-tools-6.0.0-1021",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-oem-6.0-tools-host",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-tools-6.0.0-1021-oem",
"binary_version": "6.0.0-1021.21"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-oem-6.0",
"purl": "pkg:deb/ubuntu/linux-oem-6.0@6.0.0-1021.21?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.0.0-1006.6",
"6.0.0-1007.7",
"6.0.0-1008.8",
"6.0.0-1009.9",
"6.0.0-1010.10",
"6.0.0-1011.11",
"6.0.0-1012.12",
"6.0.0-1013.13",
"6.0.0-1014.14",
"6.0.0-1015.15",
"6.0.0-1016.16",
"6.0.0-1017.17",
"6.0.0-1018.18",
"6.0.0-1019.19",
"6.0.0-1020.20",
"6.0.0-1021.21"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.1.0-1036-oem",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-headers-6.1.0-1036-oem",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-image-unsigned-6.1.0-1036-oem",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-modules-6.1.0-1036-oem",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-modules-ipu6-6.1.0-1036-oem",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-modules-ivsc-6.1.0-1036-oem",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-modules-iwlwifi-6.1.0-1036-oem",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-oem-6.1-headers-6.1.0-1036",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-oem-6.1-tools-6.1.0-1036",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-oem-6.1-tools-host",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-tools-6.1.0-1036-oem",
"binary_version": "6.1.0-1036.36"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-oem-6.1",
"purl": "pkg:deb/ubuntu/linux-oem-6.1@6.1.0-1036.36?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.1.0-1004.4",
"6.1.0-1006.6",
"6.1.0-1007.7",
"6.1.0-1008.8",
"6.1.0-1009.9",
"6.1.0-1010.10",
"6.1.0-1012.12",
"6.1.0-1013.13",
"6.1.0-1014.14",
"6.1.0-1015.15",
"6.1.0-1016.16",
"6.1.0-1017.17",
"6.1.0-1019.19",
"6.1.0-1020.20",
"6.1.0-1021.21",
"6.1.0-1022.22",
"6.1.0-1023.23",
"6.1.0-1024.24",
"6.1.0-1025.25",
"6.1.0-1026.26",
"6.1.0-1027.27",
"6.1.0-1028.28",
"6.1.0-1029.29",
"6.1.0-1033.33",
"6.1.0-1034.34",
"6.1.0-1035.35",
"6.1.0-1036.36"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-headers-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-image-unsigned-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-modules-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-modules-ipu6-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-modules-ivsc-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-modules-iwlwifi-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-modules-usbio-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-oem-6.5-headers-6.5.0-1027",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-oem-6.5-lib-rust-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-oem-6.5-tools-6.5.0-1027",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-oem-6.5-tools-host",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-tools-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-oem-6.5",
"purl": "pkg:deb/ubuntu/linux-oem-6.5@6.5.0-1027.28?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-1003.3",
"6.5.0-1004.4",
"6.5.0-1006.6",
"6.5.0-1007.7",
"6.5.0-1008.8",
"6.5.0-1009.10",
"6.5.0-1011.12",
"6.5.0-1013.14",
"6.5.0-1014.15",
"6.5.0-1015.16",
"6.5.0-1016.17",
"6.5.0-1018.19",
"6.5.0-1019.20",
"6.5.0-1020.21",
"6.5.0-1022.23",
"6.5.0-1023.24",
"6.5.0-1024.25",
"6.5.0-1025.26",
"6.5.0-1027.28"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1070-oracle",
"binary_version": "5.15.0-1070.76"
},
{
"binary_name": "linux-headers-5.15.0-1070-oracle",
"binary_version": "5.15.0-1070.76"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1070-oracle",
"binary_version": "5.15.0-1070.76"
},
{
"binary_name": "linux-modules-5.15.0-1070-oracle",
"binary_version": "5.15.0-1070.76"
},
{
"binary_name": "linux-modules-extra-5.15.0-1070-oracle",
"binary_version": "5.15.0-1070.76"
},
{
"binary_name": "linux-oracle-headers-5.15.0-1070",
"binary_version": "5.15.0-1070.76"
},
{
"binary_name": "linux-oracle-tools-5.15.0-1070",
"binary_version": "5.15.0-1070.76"
},
{
"binary_name": "linux-tools-5.15.0-1070-oracle",
"binary_version": "5.15.0-1070.76"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-oracle",
"purl": "pkg:deb/ubuntu/linux-oracle@5.15.0-1070.76?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1070.76"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-1008.10",
"5.15.0-1001.3",
"5.15.0-1002.4",
"5.15.0-1003.5",
"5.15.0-1006.8",
"5.15.0-1007.9",
"5.15.0-1009.12",
"5.15.0-1011.15",
"5.15.0-1013.17",
"5.15.0-1016.20",
"5.15.0-1017.22",
"5.15.0-1018.23",
"5.15.0-1019.24",
"5.15.0-1021.27",
"5.15.0-1022.28",
"5.15.0-1025.31",
"5.15.0-1026.32",
"5.15.0-1027.33",
"5.15.0-1029.35",
"5.15.0-1030.36",
"5.15.0-1032.38",
"5.15.0-1033.39",
"5.15.0-1034.40",
"5.15.0-1035.41",
"5.15.0-1036.42",
"5.15.0-1037.43",
"5.15.0-1038.44",
"5.15.0-1039.45",
"5.15.0-1040.46",
"5.15.0-1041.47",
"5.15.0-1042.48",
"5.15.0-1044.50",
"5.15.0-1045.51",
"5.15.0-1046.52",
"5.15.0-1047.53",
"5.15.0-1048.54",
"5.15.0-1049.55",
"5.15.0-1050.56",
"5.15.0-1051.57",
"5.15.0-1052.58",
"5.15.0-1053.59",
"5.15.0-1054.60",
"5.15.0-1055.61",
"5.15.0-1058.64",
"5.15.0-1059.65",
"5.15.0-1060.66",
"5.15.0-1061.67",
"5.15.0-1062.68",
"5.15.0-1063.69",
"5.15.0-1064.70",
"5.15.0-1065.71",
"5.15.0-1066.72",
"5.15.0-1067.73",
"5.15.0-1068.74",
"5.15.0-1069.75"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.5.0-1027-oracle",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.5.0-1027-oracle-64k",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-1027-oracle",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-1027-oracle-64k",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.5.0-1027-oracle",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.5.0-1027-oracle-64k",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-1027-oracle",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-1027-oracle-64k",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.5.0-1027-oracle",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.5.0-1027-oracle-64k",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-oracle-6.5-headers-6.5.0-1027",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-oracle-6.5-tools-6.5.0-1027",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-1027-oracle",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-1027-oracle-64k",
"binary_version": "6.5.0-1027.27~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-oracle-6.5",
"purl": "pkg:deb/ubuntu/linux-oracle-6.5@6.5.0-1027.27~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-1013.13~22.04.4",
"6.5.0-1014.14~22.04.1",
"6.5.0-1015.15~22.04.1",
"6.5.0-1016.16~22.04.1",
"6.5.0-1018.18~22.04.1",
"6.5.0-1019.19~22.04.1",
"6.5.0-1020.20~22.04.1",
"6.5.0-1021.21~22.04.1",
"6.5.0-1023.23~22.04.1",
"6.5.0-1024.24~22.04.1",
"6.5.0-1025.25~22.04.1",
"6.5.0-1026.26~22.04.1",
"6.5.0-1027.27~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1017-oracle",
"binary_version": "6.8.0-1017.18~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.8.0-1017-oracle-64k",
"binary_version": "6.8.0-1017.18~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1017-oracle",
"binary_version": "6.8.0-1017.18~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1017-oracle-64k",
"binary_version": "6.8.0-1017.18~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1017-oracle",
"binary_version": "6.8.0-1017.18~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1017-oracle-64k",
"binary_version": "6.8.0-1017.18~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1017-oracle",
"binary_version": "6.8.0-1017.18~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1017-oracle-64k",
"binary_version": "6.8.0-1017.18~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1017-oracle",
"binary_version": "6.8.0-1017.18~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1017-oracle-64k",
"binary_version": "6.8.0-1017.18~22.04.1"
},
{
"binary_name": "linux-oracle-6.8-headers-6.8.0-1017",
"binary_version": "6.8.0-1017.18~22.04.1"
},
{
"binary_name": "linux-oracle-6.8-tools-6.8.0-1017",
"binary_version": "6.8.0-1017.18~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1017-oracle",
"binary_version": "6.8.0-1017.18~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1017-oracle-64k",
"binary_version": "6.8.0-1017.18~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-oracle-6.8",
"purl": "pkg:deb/ubuntu/linux-oracle-6.8@6.8.0-1017.18~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1017.18~22.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1006.6~22.04.3",
"6.8.0-1008.8~22.04.1",
"6.8.0-1010.10~22.04.1",
"6.8.0-1011.11~22.04.1",
"6.8.0-1012.12~22.04.1",
"6.8.0-1013.13~22.04.1",
"6.8.0-1014.14~22.04.1",
"6.8.0-1015.15~22.04.1",
"6.8.0-1016.17~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1065-raspi",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-headers-5.15.0-1065-raspi",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-image-5.15.0-1065-raspi",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-modules-5.15.0-1065-raspi",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-modules-extra-5.15.0-1065-raspi",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-raspi-headers-5.15.0-1065",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-raspi-tools-5.15.0-1065",
"binary_version": "5.15.0-1065.68"
},
{
"binary_name": "linux-tools-5.15.0-1065-raspi",
"binary_version": "5.15.0-1065.68"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-raspi",
"purl": "pkg:deb/ubuntu/linux-raspi@5.15.0-1065.68?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1065.68"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-1008.9",
"5.15.0-1002.2",
"5.15.0-1003.3",
"5.15.0-1004.4",
"5.15.0-1005.5",
"5.15.0-1006.6",
"5.15.0-1008.8",
"5.15.0-1011.13",
"5.15.0-1012.14",
"5.15.0-1013.15",
"5.15.0-1014.16",
"5.15.0-1015.17",
"5.15.0-1016.18",
"5.15.0-1017.19",
"5.15.0-1018.20",
"5.15.0-1021.23",
"5.15.0-1022.24",
"5.15.0-1023.25",
"5.15.0-1024.26",
"5.15.0-1025.27",
"5.15.0-1026.28",
"5.15.0-1027.29",
"5.15.0-1028.30",
"5.15.0-1029.31",
"5.15.0-1030.32",
"5.15.0-1032.35",
"5.15.0-1033.36",
"5.15.0-1034.37",
"5.15.0-1035.38",
"5.15.0-1036.39",
"5.15.0-1037.40",
"5.15.0-1038.41",
"5.15.0-1040.43",
"5.15.0-1041.44",
"5.15.0-1042.45",
"5.15.0-1043.46",
"5.15.0-1044.47",
"5.15.0-1045.48",
"5.15.0-1046.49",
"5.15.0-1047.50",
"5.15.0-1048.51",
"5.15.0-1049.52",
"5.15.0-1050.53",
"5.15.0-1053.56",
"5.15.0-1054.57",
"5.15.0-1055.58",
"5.15.0-1058.61",
"5.15.0-1059.62",
"5.15.0-1060.63",
"5.15.0-1061.64",
"5.15.0-1062.65",
"5.15.0-1063.66",
"5.15.0-1064.67"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1032-realtime",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1032-realtime",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-headers-5.15.0-1032-realtime",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1032-realtime",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-modules-5.15.0-1032-realtime",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-modules-extra-5.15.0-1032-realtime",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-realtime-cloud-tools-5.15.0-1032",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-realtime-cloud-tools-common",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-realtime-headers-5.15.0-1032",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-realtime-tools-5.15.0-1032",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-realtime-tools-common",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-realtime-tools-host",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-tools-5.15.0-1032-realtime",
"binary_version": "5.15.0-1032.35"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-realtime",
"purl": "pkg:deb/ubuntu/linux-realtime@5.15.0-1032.35?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1032.35"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1028-generic",
"binary_version": "5.15.0-1028.32"
},
{
"binary_name": "linux-headers-5.15.0-1028-generic",
"binary_version": "5.15.0-1028.32"
},
{
"binary_name": "linux-image-5.15.0-1028-generic",
"binary_version": "5.15.0-1028.32"
},
{
"binary_name": "linux-modules-5.15.0-1028-generic",
"binary_version": "5.15.0-1028.32"
},
{
"binary_name": "linux-modules-extra-5.15.0-1028-generic",
"binary_version": "5.15.0-1028.32"
},
{
"binary_name": "linux-riscv-headers-5.15.0-1028",
"binary_version": "5.15.0-1028.32"
},
{
"binary_name": "linux-riscv-tools-5.15.0-1028",
"binary_version": "5.15.0-1028.32"
},
{
"binary_name": "linux-tools-5.15.0-1028-generic",
"binary_version": "5.15.0-1028.32"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-riscv",
"purl": "pkg:deb/ubuntu/linux-riscv@5.15.0-1028.32?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.13.0-1004.4",
"5.13.0-1006.6+22.04.1",
"5.13.0-1007.7+22.04.1",
"5.13.0-1010.11+22.04.1",
"5.15.0-1004.4",
"5.15.0-1005.5",
"5.15.0-1006.6",
"5.15.0-1007.7",
"5.15.0-1008.8",
"5.15.0-1011.12",
"5.15.0-1012.13",
"5.15.0-1014.16",
"5.15.0-1015.17",
"5.15.0-1016.18",
"5.15.0-1017.19",
"5.15.0-1018.21",
"5.15.0-1019.22",
"5.15.0-1020.23",
"5.15.0-1022.26",
"5.15.0-1023.27",
"5.15.0-1026.30",
"5.15.0-1027.31",
"5.15.0-1028.32"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.19.0-1021-generic",
"binary_version": "5.19.0-1021.23~22.04.1"
},
{
"binary_name": "linux-headers-5.19.0-1021-generic",
"binary_version": "5.19.0-1021.23~22.04.1"
},
{
"binary_name": "linux-image-5.19.0-1021-generic",
"binary_version": "5.19.0-1021.23~22.04.1"
},
{
"binary_name": "linux-modules-5.19.0-1021-generic",
"binary_version": "5.19.0-1021.23~22.04.1"
},
{
"binary_name": "linux-modules-extra-5.19.0-1021-generic",
"binary_version": "5.19.0-1021.23~22.04.1"
},
{
"binary_name": "linux-riscv-5.19-headers-5.19.0-1021",
"binary_version": "5.19.0-1021.23~22.04.1"
},
{
"binary_name": "linux-riscv-5.19-tools-5.19.0-1021",
"binary_version": "5.19.0-1021.23~22.04.1"
},
{
"binary_name": "linux-tools-5.19.0-1021-generic",
"binary_version": "5.19.0-1021.23~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-riscv-5.19",
"purl": "pkg:deb/ubuntu/linux-riscv-5.19@5.19.0-1021.23~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.19.0-1012.13~22.04.1",
"5.19.0-1015.16~22.04.1",
"5.19.0-1016.17~22.04.1",
"5.19.0-1017.18~22.04.1",
"5.19.0-1018.19~22.04.1",
"5.19.0-1019.21~22.04.1",
"5.19.0-1020.22~22.04.1",
"5.19.0-1021.23~22.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.5.0-45-generic",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-45-generic",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-image-6.5.0-45-generic",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-45-generic",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.5.0-45-generic",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-riscv-6.5-headers-6.5.0-45",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-riscv-6.5-tools-6.5.0-45",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-45-generic",
"binary_version": "6.5.0-45.45.1~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-riscv-6.5",
"purl": "pkg:deb/ubuntu/linux-riscv-6.5@6.5.0-45.45.1~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-17.17.1.1~22.04.1",
"6.5.0-21.21.1~22.04.1",
"6.5.0-25.25.1~22.04.1",
"6.5.0-26.26.1~22.04.1",
"6.5.0-27.28.1~22.04.1",
"6.5.0-28.29.1~22.04.1",
"6.5.0-35.35.1~22.04.1",
"6.5.0-40.40.1~22.04.1",
"6.5.0-42.42.1~22.04.1",
"6.5.0-45.45.1~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-50-generic",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-50-generic",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-image-6.8.0-50-generic",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-50-generic",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-riscv-6.8-headers-6.8.0-50",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-riscv-6.8-tools-6.8.0-50",
"binary_version": "6.8.0-50.51.1~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-50-generic",
"binary_version": "6.8.0-50.51.1~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-riscv-6.8",
"purl": "pkg:deb/ubuntu/linux-riscv-6.8@6.8.0-50.51.1~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-50.51.1~22.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-38.38.1~22.04.1",
"6.8.0-39.39.1~22.04.1",
"6.8.0-40.40.1~22.04.1",
"6.8.0-41.41.1~22.04.1",
"6.8.0-44.44.1~22.04.1",
"6.8.0-47.47.1~22.04.1",
"6.8.0-48.48.1~22.04.2",
"6.8.0-49.49.1~22.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.19.0-1020-starfive",
"binary_version": "5.19.0-1020.22~22.04.1"
},
{
"binary_name": "linux-headers-5.19.0-1020-starfive",
"binary_version": "5.19.0-1020.22~22.04.1"
},
{
"binary_name": "linux-image-5.19.0-1020-starfive",
"binary_version": "5.19.0-1020.22~22.04.1"
},
{
"binary_name": "linux-modules-5.19.0-1020-starfive",
"binary_version": "5.19.0-1020.22~22.04.1"
},
{
"binary_name": "linux-modules-extra-5.19.0-1020-starfive",
"binary_version": "5.19.0-1020.22~22.04.1"
},
{
"binary_name": "linux-starfive-5.19-headers-5.19.0-1020",
"binary_version": "5.19.0-1020.22~22.04.1"
},
{
"binary_name": "linux-starfive-5.19-tools-5.19.0-1020",
"binary_version": "5.19.0-1020.22~22.04.1"
},
{
"binary_name": "linux-tools-5.19.0-1020-starfive",
"binary_version": "5.19.0-1020.22~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-starfive-5.19",
"purl": "pkg:deb/ubuntu/linux-starfive-5.19@5.19.0-1020.22~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.19.0-1014.16~22.04.1",
"5.19.0-1015.17~22.04.1",
"5.19.0-1016.18~22.04.1",
"5.19.0-1017.19~22.04.1",
"5.19.0-1018.20~22.04.1",
"5.19.0-1019.21~22.04.1",
"5.19.0-1020.22~22.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.2.0-1009-starfive",
"binary_version": "6.2.0-1009.10~22.04.1"
},
{
"binary_name": "linux-headers-6.2.0-1009-starfive",
"binary_version": "6.2.0-1009.10~22.04.1"
},
{
"binary_name": "linux-image-6.2.0-1009-starfive",
"binary_version": "6.2.0-1009.10~22.04.1"
},
{
"binary_name": "linux-modules-6.2.0-1009-starfive",
"binary_version": "6.2.0-1009.10~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.2.0-1009-starfive",
"binary_version": "6.2.0-1009.10~22.04.1"
},
{
"binary_name": "linux-starfive-6.2-headers-6.2.0-1009",
"binary_version": "6.2.0-1009.10~22.04.1"
},
{
"binary_name": "linux-starfive-6.2-tools-6.2.0-1009",
"binary_version": "6.2.0-1009.10~22.04.1"
},
{
"binary_name": "linux-tools-6.2.0-1009-starfive",
"binary_version": "6.2.0-1009.10~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-starfive-6.2",
"purl": "pkg:deb/ubuntu/linux-starfive-6.2@6.2.0-1009.10~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.2.0-1006.7~22.04.1",
"6.2.0-1007.8~22.04.1",
"6.2.0-1009.10~22.04.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-6.5.0-1018-starfive",
"binary_version": "6.5.0-1018.19~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-1018-starfive",
"binary_version": "6.5.0-1018.19~22.04.1"
},
{
"binary_name": "linux-image-6.5.0-1018-starfive",
"binary_version": "6.5.0-1018.19~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-1018-starfive",
"binary_version": "6.5.0-1018.19~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.5.0-1018-starfive",
"binary_version": "6.5.0-1018.19~22.04.1"
},
{
"binary_name": "linux-starfive-6.5-headers-6.5.0-1018",
"binary_version": "6.5.0-1018.19~22.04.1"
},
{
"binary_name": "linux-starfive-6.5-tools-6.5.0-1018",
"binary_version": "6.5.0-1018.19~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-1018-starfive",
"binary_version": "6.5.0-1018.19~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-starfive-6.5",
"purl": "pkg:deb/ubuntu/linux-starfive-6.5@6.5.0-1018.19~22.04.1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-1007.8~22.04.1",
"6.5.0-1008.9~22.04.1",
"6.5.0-1009.10~22.04.1",
"6.5.0-1010.11~22.04.1",
"6.5.0-1011.12~22.04.1",
"6.5.0-1012.13~22.04.1",
"6.5.0-1014.15~22.04.1",
"6.5.0-1015.16~22.04.1",
"6.5.0-1016.17~22.04.1",
"6.5.0-1017.18~22.04.1",
"6.5.0-1018.19~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1038-xilinx-zynqmp",
"binary_version": "5.15.0-1038.42"
},
{
"binary_name": "linux-headers-5.15.0-1038-xilinx-zynqmp",
"binary_version": "5.15.0-1038.42"
},
{
"binary_name": "linux-image-5.15.0-1038-xilinx-zynqmp",
"binary_version": "5.15.0-1038.42"
},
{
"binary_name": "linux-modules-5.15.0-1038-xilinx-zynqmp",
"binary_version": "5.15.0-1038.42"
},
{
"binary_name": "linux-tools-5.15.0-1038-xilinx-zynqmp",
"binary_version": "5.15.0-1038.42"
},
{
"binary_name": "linux-xilinx-zynqmp-headers-5.15.0-1038",
"binary_version": "5.15.0-1038.42"
},
{
"binary_name": "linux-xilinx-zynqmp-tools-5.15.0-1038",
"binary_version": "5.15.0-1038.42"
},
{
"binary_name": "linux-xilinx-zynqmp-tools-common",
"binary_version": "5.15.0-1038.42"
},
{
"binary_name": "linux-xilinx-zynqmp-tools-host",
"binary_version": "5.15.0-1038.42"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "linux-xilinx-zynqmp",
"purl": "pkg:deb/ubuntu/linux-xilinx-zynqmp@5.15.0-1038.42?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1038.42"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1022.26",
"5.15.0-1023.27",
"5.15.0-1025.29",
"5.15.0-1027.31",
"5.15.0-1030.34",
"5.15.0-1031.35",
"5.15.0-1035.39",
"5.15.0-1036.40",
"5.15.0-1037.41"
]
},
{
"ecosystem_specific": {
"availability": "Available for NVIDIA BlueField platforms",
"binaries": [
{
"binary_name": "linux-bluefield-cloud-tools-common",
"binary_version": "5.15.0-1056.58"
},
{
"binary_name": "linux-bluefield-headers-5.15.0-1056",
"binary_version": "5.15.0-1056.58"
},
{
"binary_name": "linux-bluefield-tools-5.15.0-1056",
"binary_version": "5.15.0-1056.58"
},
{
"binary_name": "linux-bluefield-tools-host",
"binary_version": "5.15.0-1056.58"
},
{
"binary_name": "linux-buildinfo-5.15.0-1056-bluefield",
"binary_version": "5.15.0-1056.58"
},
{
"binary_name": "linux-headers-5.15.0-1056-bluefield",
"binary_version": "5.15.0-1056.58"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1056-bluefield",
"binary_version": "5.15.0-1056.58"
},
{
"binary_name": "linux-modules-5.15.0-1056-bluefield",
"binary_version": "5.15.0-1056.58"
},
{
"binary_name": "linux-modules-extra-5.15.0-1056-bluefield",
"binary_version": "5.15.0-1056.58"
},
{
"binary_name": "linux-tools-5.15.0-1056-bluefield",
"binary_version": "5.15.0-1056.58"
}
]
},
"package": {
"ecosystem": "Ubuntu:Nvidia-BlueField:22.04:LTS",
"name": "linux-bluefield",
"purl": "pkg:deb/ubuntu/linux-bluefield@5.15.0-1056.58?arch=source\u0026distro=bluefield/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1056.58"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1011.13",
"5.15.0-1014.16",
"5.15.0-1015.17",
"5.15.0-1017.19",
"5.15.0-1019.21",
"5.15.0-1021.23",
"5.15.0-1022.24",
"5.15.0-1023.25",
"5.15.0-1024.26",
"5.15.0-1027.29",
"5.15.0-1028.30",
"5.15.0-1031.33",
"5.15.0-1032.34",
"5.15.0-1033.35",
"5.15.0-1035.37",
"5.15.0-1036.38",
"5.15.0-1037.39",
"5.15.0-1038.40",
"5.15.0-1040.42",
"5.15.0-1042.44",
"5.15.0-1043.45",
"5.15.0-1044.46",
"5.15.0-1045.47",
"5.15.0-1047.49",
"5.15.0-1048.50",
"5.15.0-1050.52",
"5.15.0-1051.53",
"5.15.0-1052.54",
"5.15.0-1053.55",
"5.15.0-1054.56"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-aws-fips-cloud-tools-5.15.0-1051",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-aws-fips-headers-5.15.0-1051",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-aws-fips-tools-5.15.0-1051",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-buildinfo-5.15.0-1051-aws-fips",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1051-aws-fips",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-headers-5.15.0-1051-aws-fips",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1051-aws-fips",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.15.0-1051-aws-fips",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-modules-5.15.0-1051-aws-fips",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1051-aws-fips",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-tools-5.15.0-1051-aws-fips",
"binary_version": "5.15.0-1051.56+fips1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-preview:22.04:LTS",
"name": "linux-aws-fips",
"purl": "pkg:deb/ubuntu/linux-aws-fips@5.15.0-1051.56+fips1?arch=source\u0026distro=fips-preview/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1042.47+fips1",
"5.15.0-1051.56+fips1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-azure-fips-cloud-tools-5.15.0-1053",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-azure-fips-headers-5.15.0-1053",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-azure-fips-tools-5.15.0-1053",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-buildinfo-5.15.0-1053-azure-fips",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1053-azure-fips",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-headers-5.15.0-1053-azure-fips",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1053-azure-fips",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.15.0-1053-azure-fips",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-modules-5.15.0-1053-azure-fips",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1053-azure-fips",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-tools-5.15.0-1053-azure-fips",
"binary_version": "5.15.0-1053.61+fips1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-preview:22.04:LTS",
"name": "linux-azure-fips",
"purl": "pkg:deb/ubuntu/linux-azure-fips@5.15.0-1053.61+fips1?arch=source\u0026distro=fips-preview/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1053.61+fips1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-73-fips",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-fips-headers-5.15.0-73",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-fips-tools-5.15.0-73",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-fips-tools-host",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-headers-5.15.0-73-fips",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-73-fips",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.15.0-73-fips",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-modules-5.15.0-73-fips",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-modules-extra-5.15.0-73-fips",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-73-fips",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-tools-5.15.0-73-fips",
"binary_version": "5.15.0-73.80+fips1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-preview:22.04:LTS",
"name": "linux-fips",
"purl": "pkg:deb/ubuntu/linux-fips@5.15.0-73.80+fips1?arch=source\u0026distro=fips-preview/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-73.80+fips1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1048-gcp-fips",
"binary_version": "5.15.0-1048.56+fips1"
},
{
"binary_name": "linux-gcp-fips-headers-5.15.0-1048",
"binary_version": "5.15.0-1048.56+fips1"
},
{
"binary_name": "linux-gcp-fips-tools-5.15.0-1048",
"binary_version": "5.15.0-1048.56+fips1"
},
{
"binary_name": "linux-headers-5.15.0-1048-gcp-fips",
"binary_version": "5.15.0-1048.56+fips1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1048-gcp-fips",
"binary_version": "5.15.0-1048.56+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.15.0-1048-gcp-fips",
"binary_version": "5.15.0-1048.56+fips1"
},
{
"binary_name": "linux-modules-5.15.0-1048-gcp-fips",
"binary_version": "5.15.0-1048.56+fips1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1048-gcp-fips",
"binary_version": "5.15.0-1048.56+fips1"
},
{
"binary_name": "linux-tools-5.15.0-1048-gcp-fips",
"binary_version": "5.15.0-1048.56+fips1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-preview:22.04:LTS",
"name": "linux-gcp-fips",
"purl": "pkg:deb/ubuntu/linux-gcp-fips@5.15.0-1048.56+fips1?arch=source\u0026distro=fips-preview/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1048.56+fips1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-aws-fips-cloud-tools-5.15.0-1072",
"binary_version": "5.15.0-1072.78+fips1"
},
{
"binary_name": "linux-aws-fips-headers-5.15.0-1072",
"binary_version": "5.15.0-1072.78+fips1"
},
{
"binary_name": "linux-aws-fips-tools-5.15.0-1072",
"binary_version": "5.15.0-1072.78+fips1"
},
{
"binary_name": "linux-buildinfo-5.15.0-1072-aws-fips",
"binary_version": "5.15.0-1072.78+fips1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1072-aws-fips",
"binary_version": "5.15.0-1072.78+fips1"
},
{
"binary_name": "linux-headers-5.15.0-1072-aws-fips",
"binary_version": "5.15.0-1072.78+fips1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1072-aws-fips",
"binary_version": "5.15.0-1072.78+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.15.0-1072-aws-fips",
"binary_version": "5.15.0-1072.78+fips1"
},
{
"binary_name": "linux-modules-5.15.0-1072-aws-fips",
"binary_version": "5.15.0-1072.78+fips1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1072-aws-fips",
"binary_version": "5.15.0-1072.78+fips1"
},
{
"binary_name": "linux-tools-5.15.0-1072-aws-fips",
"binary_version": "5.15.0-1072.78+fips1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:22.04:LTS",
"name": "linux-aws-fips",
"purl": "pkg:deb/ubuntu/linux-aws-fips@5.15.0-1072.78+fips1?arch=source\u0026distro=fips-updates/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1072.78+fips1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1051.56+fips1",
"5.15.0-1052.57+fips1",
"5.15.0-1053.58+fips1",
"5.15.0-1055.60+fips1",
"5.15.0-1056.61+fips1",
"5.15.0-1057.63+fips1",
"5.15.0-1060.66+fips1",
"5.15.0-1061.67+fips1",
"5.15.0-1062.68+fips1",
"5.15.0-1063.69+fips1",
"5.15.0-1064.70+fips1",
"5.15.0-1065.71+fips1",
"5.15.0-1066.72+fips1",
"5.15.0-1067.73+fips1",
"5.15.0-1068.74+fips1",
"5.15.0-1069.75+fips1",
"5.15.0-1070.76+fips1",
"5.15.0-1071.77+fips1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-azure-fips-cloud-tools-5.15.0-1075",
"binary_version": "5.15.0-1075.84+fips1"
},
{
"binary_name": "linux-azure-fips-headers-5.15.0-1075",
"binary_version": "5.15.0-1075.84+fips1"
},
{
"binary_name": "linux-azure-fips-tools-5.15.0-1075",
"binary_version": "5.15.0-1075.84+fips1"
},
{
"binary_name": "linux-buildinfo-5.15.0-1075-azure-fips",
"binary_version": "5.15.0-1075.84+fips1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1075-azure-fips",
"binary_version": "5.15.0-1075.84+fips1"
},
{
"binary_name": "linux-headers-5.15.0-1075-azure-fips",
"binary_version": "5.15.0-1075.84+fips1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1075-azure-fips",
"binary_version": "5.15.0-1075.84+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.15.0-1075-azure-fips",
"binary_version": "5.15.0-1075.84+fips1"
},
{
"binary_name": "linux-modules-5.15.0-1075-azure-fips",
"binary_version": "5.15.0-1075.84+fips1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1075-azure-fips",
"binary_version": "5.15.0-1075.84+fips1"
},
{
"binary_name": "linux-modules-involflt-5.15.0-1075-azure-fips",
"binary_version": "5.15.0-1075.84+fips1"
},
{
"binary_name": "linux-tools-5.15.0-1075-azure-fips",
"binary_version": "5.15.0-1075.84+fips1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:22.04:LTS",
"name": "linux-azure-fips",
"purl": "pkg:deb/ubuntu/linux-azure-fips@5.15.0-1075.84+fips1?arch=source\u0026distro=fips-updates/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1075.84+fips1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1053.61+fips1",
"5.15.0-1058.66+fips1",
"5.15.0-1059.67+fips1",
"5.15.0-1060.69+fips1",
"5.15.0-1061.70+fips1",
"5.15.0-1063.72+fips1",
"5.15.0-1064.73+fips1",
"5.15.0-1065.74+fips1",
"5.15.0-1067.76+fips1",
"5.15.0-1068.77+fips1",
"5.15.0-1070.79+fips1",
"5.15.0-1071.80+fips1",
"5.15.0-1072.81+fips1",
"5.15.0-1073.82+fips1",
"5.15.0-1074.83+fips1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-125-fips",
"binary_version": "5.15.0-125.135+fips1"
},
{
"binary_name": "linux-fips-headers-5.15.0-125",
"binary_version": "5.15.0-125.135+fips1"
},
{
"binary_name": "linux-fips-tools-5.15.0-125",
"binary_version": "5.15.0-125.135+fips1"
},
{
"binary_name": "linux-headers-5.15.0-125-fips",
"binary_version": "5.15.0-125.135+fips1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-125-fips",
"binary_version": "5.15.0-125.135+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.15.0-125-fips",
"binary_version": "5.15.0-125.135+fips1"
},
{
"binary_name": "linux-modules-5.15.0-125-fips",
"binary_version": "5.15.0-125.135+fips1"
},
{
"binary_name": "linux-modules-extra-5.15.0-125-fips",
"binary_version": "5.15.0-125.135+fips1"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-125-fips",
"binary_version": "5.15.0-125.135+fips1"
},
{
"binary_name": "linux-tools-5.15.0-125-fips",
"binary_version": "5.15.0-125.135+fips1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:22.04:LTS",
"name": "linux-fips",
"purl": "pkg:deb/ubuntu/linux-fips@5.15.0-125.135+fips1?arch=source\u0026distro=fips-updates/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-125.135+fips1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-73.80+fips1",
"5.15.0-92.102+fips1",
"5.15.0-94.104+fips1",
"5.15.0-97.107+fips1",
"5.15.0-100.110+fips1",
"5.15.0-101.111+fips1",
"5.15.0-102.112+fips1",
"5.15.0-105.115+fips1",
"5.15.0-106.116+fips1",
"5.15.0-107.117+fips1",
"5.15.0-111.121+fips1",
"5.15.0-113.123+fips1",
"5.15.0-115.125+fips1",
"5.15.0-117.127+fips1",
"5.15.0-118.128+fips1",
"5.15.0-119.129+fips1",
"5.15.0-121.131+fips1",
"5.15.0-122.132+fips1",
"5.15.0-124.134+fips1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1071-gcp-fips",
"binary_version": "5.15.0-1071.79+fips1"
},
{
"binary_name": "linux-gcp-fips-headers-5.15.0-1071",
"binary_version": "5.15.0-1071.79+fips1"
},
{
"binary_name": "linux-gcp-fips-tools-5.15.0-1071",
"binary_version": "5.15.0-1071.79+fips1"
},
{
"binary_name": "linux-headers-5.15.0-1071-gcp-fips",
"binary_version": "5.15.0-1071.79+fips1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1071-gcp-fips",
"binary_version": "5.15.0-1071.79+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.15.0-1071-gcp-fips",
"binary_version": "5.15.0-1071.79+fips1"
},
{
"binary_name": "linux-modules-5.15.0-1071-gcp-fips",
"binary_version": "5.15.0-1071.79+fips1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1071-gcp-fips",
"binary_version": "5.15.0-1071.79+fips1"
},
{
"binary_name": "linux-tools-5.15.0-1071-gcp-fips",
"binary_version": "5.15.0-1071.79+fips1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:22.04:LTS",
"name": "linux-gcp-fips",
"purl": "pkg:deb/ubuntu/linux-gcp-fips@5.15.0-1071.79+fips1?arch=source\u0026distro=fips-updates/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1071.79+fips1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1048.56+fips1",
"5.15.0-1055.63+fips2",
"5.15.0-1058.66+fips1",
"5.15.0-1059.67+fips1",
"5.15.0-1060.68+fips1",
"5.15.0-1062.70+fips1",
"5.15.0-1063.71+fips1",
"5.15.0-1064.72+fips1",
"5.15.0-1065.73+fips1",
"5.15.0-1066.74+fips1",
"5.15.0-1067.75+fips1",
"5.15.0-1068.76+fips1",
"5.15.0-1069.77+fips1",
"5.15.0-1070.78+fips1"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1066-intel-iot-realtime",
"binary_version": "5.15.0-1066.68"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1066-intel-iot-realtime",
"binary_version": "5.15.0-1066.68"
},
{
"binary_name": "linux-headers-5.15.0-1066-intel-iot-realtime",
"binary_version": "5.15.0-1066.68"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1066-intel-iot-realtime",
"binary_version": "5.15.0-1066.68"
},
{
"binary_name": "linux-intel-iot-realtime-cloud-tools-5.15.0-1066",
"binary_version": "5.15.0-1066.68"
},
{
"binary_name": "linux-intel-iot-realtime-cloud-tools-common",
"binary_version": "5.15.0-1066.68"
},
{
"binary_name": "linux-intel-iot-realtime-headers-5.15.0-1066",
"binary_version": "5.15.0-1066.68"
},
{
"binary_name": "linux-intel-iot-realtime-tools-5.15.0-1066",
"binary_version": "5.15.0-1066.68"
},
{
"binary_name": "linux-intel-iot-realtime-tools-common",
"binary_version": "5.15.0-1066.68"
},
{
"binary_name": "linux-intel-iot-realtime-tools-host",
"binary_version": "5.15.0-1066.68"
},
{
"binary_name": "linux-modules-5.15.0-1066-intel-iot-realtime",
"binary_version": "5.15.0-1066.68"
},
{
"binary_name": "linux-modules-extra-5.15.0-1066-intel-iot-realtime",
"binary_version": "5.15.0-1066.68"
},
{
"binary_name": "linux-tools-5.15.0-1066-intel-iot-realtime",
"binary_version": "5.15.0-1066.68"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:Realtime:22.04:LTS",
"name": "linux-intel-iot-realtime",
"purl": "pkg:deb/ubuntu/linux-intel-iot-realtime@5.15.0-1066.68?arch=source\u0026distro=realtime/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1066.68"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1021.26",
"5.15.0-1022.27",
"5.15.0-1023.28",
"5.15.0-1024.29",
"5.15.0-1028.33",
"5.15.0-1033.35",
"5.15.0-1034.36",
"5.15.0-1035.37",
"5.15.0-1036.38",
"5.15.0-1037.39",
"5.15.0-1038.40",
"5.15.0-1039.41",
"5.15.0-1040.42",
"5.15.0-1041.43",
"5.15.0-1042.44",
"5.15.0-1043.45",
"5.15.0-1044.46",
"5.15.0-1046.48",
"5.15.0-1047.49",
"5.15.0-1048.50",
"5.15.0-1049.51",
"5.15.0-1050.52",
"5.15.0-1053.55",
"5.15.0-1054.56",
"5.15.0-1055.57",
"5.15.0-1056.58",
"5.15.0-1057.59",
"5.15.0-1058.60",
"5.15.0-1059.61",
"5.15.0-1060.62",
"5.15.0-1061.63",
"5.15.0-1063.65",
"5.15.0-1064.66"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1073-realtime",
"binary_version": "5.15.0-1073.81"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1073-realtime",
"binary_version": "5.15.0-1073.81"
},
{
"binary_name": "linux-headers-5.15.0-1073-realtime",
"binary_version": "5.15.0-1073.81"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1073-realtime",
"binary_version": "5.15.0-1073.81"
},
{
"binary_name": "linux-modules-5.15.0-1073-realtime",
"binary_version": "5.15.0-1073.81"
},
{
"binary_name": "linux-modules-extra-5.15.0-1073-realtime",
"binary_version": "5.15.0-1073.81"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-1073-realtime",
"binary_version": "5.15.0-1073.81"
},
{
"binary_name": "linux-realtime-cloud-tools-5.15.0-1073",
"binary_version": "5.15.0-1073.81"
},
{
"binary_name": "linux-realtime-cloud-tools-common",
"binary_version": "5.15.0-1073.81"
},
{
"binary_name": "linux-realtime-headers-5.15.0-1073",
"binary_version": "5.15.0-1073.81"
},
{
"binary_name": "linux-realtime-tools-5.15.0-1073",
"binary_version": "5.15.0-1073.81"
},
{
"binary_name": "linux-realtime-tools-common",
"binary_version": "5.15.0-1073.81"
},
{
"binary_name": "linux-realtime-tools-host",
"binary_version": "5.15.0-1073.81"
},
{
"binary_name": "linux-tools-5.15.0-1073-realtime",
"binary_version": "5.15.0-1073.81"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:Realtime:22.04:LTS",
"name": "linux-realtime",
"purl": "pkg:deb/ubuntu/linux-realtime@5.15.0-1073.81?arch=source\u0026distro=realtime/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.15.0-1073.81"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.15.0-1006.6",
"5.15.0-1007.7",
"5.15.0-1009.9",
"5.15.0-1011.11",
"5.15.0-1014.14",
"5.15.0-1015.15",
"5.15.0-1016.16",
"5.15.0-1019.19",
"5.15.0-1020.20",
"5.15.0-1021.21",
"5.15.0-1022.22",
"5.15.0-1024.25",
"5.15.0-1025.28",
"5.15.0-1028.31",
"5.15.0-1029.32",
"5.15.0-1030.33",
"5.15.0-1032.35",
"5.15.0-1033.36",
"5.15.0-1034.37",
"5.15.0-1036.39",
"5.15.0-1037.40",
"5.15.0-1038.41",
"5.15.0-1039.42",
"5.15.0-1040.45",
"5.15.0-1041.46",
"5.15.0-1042.47",
"5.15.0-1043.48",
"5.15.0-1044.49",
"5.15.0-1045.50",
"5.15.0-1046.52",
"5.15.0-1048.54",
"5.15.0-1049.55",
"5.15.0-1050.56",
"5.15.0-1051.57",
"5.15.0-1052.58",
"5.15.0-1053.59",
"5.15.0-1054.60",
"5.15.0-1055.62",
"5.15.0-1056.63",
"5.15.0-1057.64",
"5.15.0-1058.66",
"5.15.0-1061.69",
"5.15.0-1062.70",
"5.15.0-1063.71",
"5.15.0-1064.72",
"5.15.0-1065.73",
"5.15.0-1066.74",
"5.15.0-1067.75",
"5.15.0-1068.76",
"5.15.0-1069.77",
"5.15.0-1070.78",
"5.15.0-1071.79",
"5.15.0-1072.80"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14~22.04.1"
},
{
"binary_name": "linux-headers-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14~22.04.1"
},
{
"binary_name": "linux-modules-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14~22.04.1"
},
{
"binary_name": "linux-realtime-6.8-cloud-tools-6.8.1-1013",
"binary_version": "6.8.1-1013.14~22.04.1"
},
{
"binary_name": "linux-realtime-6.8-headers-6.8.1-1013",
"binary_version": "6.8.1-1013.14~22.04.1"
},
{
"binary_name": "linux-realtime-6.8-tools-6.8.1-1013",
"binary_version": "6.8.1-1013.14~22.04.1"
},
{
"binary_name": "linux-tools-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14~22.04.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:Realtime:22.04:LTS",
"name": "linux-realtime-6.8",
"purl": "pkg:deb/ubuntu/linux-realtime-6.8@6.8.1-1013.14~22.04.1?arch=source\u0026distro=realtime/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.1-1013.14~22.04.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.1-1004.4~22.04.1",
"6.8.1-1005.5~22.04.2",
"6.8.1-1006.6~22.04.1",
"6.8.1-1007.7~22.04.1",
"6.8.1-1008.8~22.04.1",
"6.8.1-1009.9~22.04.1",
"6.8.1-1010.10~22.04.1",
"6.8.1-1011.11~22.04.1",
"6.8.1-1012.12~22.04.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-50-generic",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-buildinfo-6.8.0-50-generic-64k",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-cloud-tools-6.8.0-50",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-cloud-tools-6.8.0-50-generic",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-cloud-tools-common",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-headers-6.8.0-50",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-headers-6.8.0-50-generic",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-headers-6.8.0-50-generic-64k",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-image-6.8.0-50-generic",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-image-unsigned-6.8.0-50-generic",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-image-unsigned-6.8.0-50-generic-64k",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-lib-rust-6.8.0-50-generic",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-modules-6.8.0-50-generic",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-modules-6.8.0-50-generic-64k",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-modules-extra-6.8.0-50-generic",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-modules-ipu6-6.8.0-50-generic",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-50-generic",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-modules-usbio-6.8.0-50-generic",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-source-6.8.0",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-tools-6.8.0-50",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-tools-6.8.0-50-generic",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-tools-6.8.0-50-generic-64k",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-tools-common",
"binary_version": "6.8.0-50.51"
},
{
"binary_name": "linux-tools-host",
"binary_version": "6.8.0-50.51"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux",
"purl": "pkg:deb/ubuntu/linux@6.8.0-50.51?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-50.51"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-9.9",
"6.6.0-14.14",
"6.8.0-11.11",
"6.8.0-20.20",
"6.8.0-22.22",
"6.8.0-28.28",
"6.8.0-31.31",
"6.8.0-35.35",
"6.8.0-36.36",
"6.8.0-38.38",
"6.8.0-39.39",
"6.8.0-40.40",
"6.8.0-41.41",
"6.8.0-44.44",
"6.8.0-45.45",
"6.8.0-47.47",
"6.8.0-48.48",
"6.8.0-49.49"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-aws-cloud-tools-6.8.0-1020",
"binary_version": "6.8.0-1020.22"
},
{
"binary_name": "linux-aws-headers-6.8.0-1020",
"binary_version": "6.8.0-1020.22"
},
{
"binary_name": "linux-aws-tools-6.8.0-1020",
"binary_version": "6.8.0-1020.22"
},
{
"binary_name": "linux-buildinfo-6.8.0-1020-aws",
"binary_version": "6.8.0-1020.22"
},
{
"binary_name": "linux-cloud-tools-6.8.0-1020-aws",
"binary_version": "6.8.0-1020.22"
},
{
"binary_name": "linux-headers-6.8.0-1020-aws",
"binary_version": "6.8.0-1020.22"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1020-aws",
"binary_version": "6.8.0-1020.22"
},
{
"binary_name": "linux-modules-6.8.0-1020-aws",
"binary_version": "6.8.0-1020.22"
},
{
"binary_name": "linux-modules-extra-6.8.0-1020-aws",
"binary_version": "6.8.0-1020.22"
},
{
"binary_name": "linux-tools-6.8.0-1020-aws",
"binary_version": "6.8.0-1020.22"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-aws",
"purl": "pkg:deb/ubuntu/linux-aws@6.8.0-1020.22?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1020.22"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-1008.8",
"6.6.0-1001.1",
"6.8.0-1001.1",
"6.8.0-1006.6",
"6.8.0-1008.8",
"6.8.0-1009.9",
"6.8.0-1010.10",
"6.8.0-1011.12",
"6.8.0-1012.13",
"6.8.0-1013.14",
"6.8.0-1014.15",
"6.8.0-1015.16",
"6.8.0-1016.17",
"6.8.0-1017.18",
"6.8.0-1018.20",
"6.8.0-1019.21"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-azure-cloud-tools-6.8.0-1020",
"binary_version": "6.8.0-1020.23"
},
{
"binary_name": "linux-azure-headers-6.8.0-1020",
"binary_version": "6.8.0-1020.23"
},
{
"binary_name": "linux-azure-tools-6.8.0-1020",
"binary_version": "6.8.0-1020.23"
},
{
"binary_name": "linux-buildinfo-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23"
},
{
"binary_name": "linux-cloud-tools-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23"
},
{
"binary_name": "linux-headers-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23"
},
{
"binary_name": "linux-modules-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23"
},
{
"binary_name": "linux-modules-extra-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23"
},
{
"binary_name": "linux-modules-involflt-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23"
},
{
"binary_name": "linux-tools-6.8.0-1020-azure",
"binary_version": "6.8.0-1020.23"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-azure",
"purl": "pkg:deb/ubuntu/linux-azure@6.8.0-1020.23?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1020.23"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-1007.7",
"6.6.0-1001.1",
"6.8.0-1001.1",
"6.8.0-1005.5",
"6.8.0-1006.6",
"6.8.0-1007.7",
"6.8.0-1008.8",
"6.8.0-1009.9",
"6.8.0-1010.10",
"6.8.0-1012.14",
"6.8.0-1013.15",
"6.8.0-1014.16",
"6.8.0-1015.17",
"6.8.0-1016.18",
"6.8.0-1017.20",
"6.8.0-1018.21"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1019-gcp",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-gcp-headers-6.8.0-1019",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-gcp-tools-6.8.0-1019",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-headers-6.8.0-1019-gcp",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1019-gcp",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-modules-6.8.0-1019-gcp",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-modules-extra-6.8.0-1019-gcp",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-tools-6.8.0-1019-gcp",
"binary_version": "6.8.0-1019.21"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-gcp",
"purl": "pkg:deb/ubuntu/linux-gcp@6.8.0-1019.21?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1019.21"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-1007.7",
"6.6.0-1001.1",
"6.8.0-1002.2",
"6.8.0-1005.5",
"6.8.0-1006.6",
"6.8.0-1007.7",
"6.8.0-1008.9",
"6.8.0-1009.10",
"6.8.0-1010.11",
"6.8.0-1011.12",
"6.8.0-1012.13",
"6.8.0-1013.14",
"6.8.0-1014.16",
"6.8.0-1015.17",
"6.8.0-1016.18",
"6.8.0-1017.19",
"6.8.0-1018.20"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1015-gke",
"binary_version": "6.8.0-1015.19"
},
{
"binary_name": "linux-gke-headers-6.8.0-1015",
"binary_version": "6.8.0-1015.19"
},
{
"binary_name": "linux-gke-tools-6.8.0-1015",
"binary_version": "6.8.0-1015.19"
},
{
"binary_name": "linux-headers-6.8.0-1015-gke",
"binary_version": "6.8.0-1015.19"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1015-gke",
"binary_version": "6.8.0-1015.19"
},
{
"binary_name": "linux-modules-6.8.0-1015-gke",
"binary_version": "6.8.0-1015.19"
},
{
"binary_name": "linux-modules-extra-6.8.0-1015-gke",
"binary_version": "6.8.0-1015.19"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-1015-gke",
"binary_version": "6.8.0-1015.19"
},
{
"binary_name": "linux-tools-6.8.0-1015-gke",
"binary_version": "6.8.0-1015.19"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-gke",
"purl": "pkg:deb/ubuntu/linux-gke@6.8.0-1015.19?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1015.19"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1003.5",
"6.8.0-1004.7",
"6.8.0-1005.8",
"6.8.0-1006.9",
"6.8.0-1007.10",
"6.8.0-1008.11",
"6.8.0-1009.12",
"6.8.0-1010.13",
"6.8.0-1011.14",
"6.8.0-1012.15",
"6.8.0-1013.17",
"6.8.0-1014.18"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1002-gkeop",
"binary_version": "6.8.0-1002.4"
},
{
"binary_name": "linux-cloud-tools-6.8.0-1002-gkeop",
"binary_version": "6.8.0-1002.4"
},
{
"binary_name": "linux-gkeop-cloud-tools-6.8.0-1002",
"binary_version": "6.8.0-1002.4"
},
{
"binary_name": "linux-gkeop-headers-6.8.0-1002",
"binary_version": "6.8.0-1002.4"
},
{
"binary_name": "linux-gkeop-tools-6.8.0-1002",
"binary_version": "6.8.0-1002.4"
},
{
"binary_name": "linux-headers-6.8.0-1002-gkeop",
"binary_version": "6.8.0-1002.4"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1002-gkeop",
"binary_version": "6.8.0-1002.4"
},
{
"binary_name": "linux-modules-6.8.0-1002-gkeop",
"binary_version": "6.8.0-1002.4"
},
{
"binary_name": "linux-modules-extra-6.8.0-1002-gkeop",
"binary_version": "6.8.0-1002.4"
},
{
"binary_name": "linux-tools-6.8.0-1002-gkeop",
"binary_version": "6.8.0-1002.4"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-gkeop",
"purl": "pkg:deb/ubuntu/linux-gkeop@6.8.0-1002.4?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1002.4"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1001.3"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1017-ibm",
"binary_version": "6.8.0-1017.17"
},
{
"binary_name": "linux-headers-6.8.0-1017-ibm",
"binary_version": "6.8.0-1017.17"
},
{
"binary_name": "linux-ibm-cloud-tools-common",
"binary_version": "6.8.0-1017.17"
},
{
"binary_name": "linux-ibm-headers-6.8.0-1017",
"binary_version": "6.8.0-1017.17"
},
{
"binary_name": "linux-ibm-source-6.8.0",
"binary_version": "6.8.0-1017.17"
},
{
"binary_name": "linux-ibm-tools-6.8.0-1017",
"binary_version": "6.8.0-1017.17"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1017-ibm",
"binary_version": "6.8.0-1017.17"
},
{
"binary_name": "linux-modules-6.8.0-1017-ibm",
"binary_version": "6.8.0-1017.17"
},
{
"binary_name": "linux-modules-extra-6.8.0-1017-ibm",
"binary_version": "6.8.0-1017.17"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-1017-ibm",
"binary_version": "6.8.0-1017.17"
},
{
"binary_name": "linux-tools-6.8.0-1017-ibm",
"binary_version": "6.8.0-1017.17"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-ibm",
"purl": "pkg:deb/ubuntu/linux-ibm@6.8.0-1017.17?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1017.17"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-1009.9",
"6.8.0-1001.1",
"6.8.0-1003.3",
"6.8.0-1004.4",
"6.8.0-1005.5",
"6.8.0-1006.6",
"6.8.0-1007.7",
"6.8.0-1008.8",
"6.8.0-1009.9",
"6.8.0-1010.10",
"6.8.0-1011.11",
"6.8.0-1012.12",
"6.8.0-1013.13",
"6.8.0-1014.14",
"6.8.0-1015.15",
"6.8.0-1016.16"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-buildinfo-6.8.0-50-lowlatency-64k",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-cloud-tools-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-headers-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-headers-6.8.0-50-lowlatency-64k",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-50-lowlatency-64k",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-lowlatency-cloud-tools-6.8.0-50",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-lowlatency-headers-6.8.0-50",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-lowlatency-lib-rust-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-lowlatency-tools-6.8.0-50",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-modules-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-modules-6.8.0-50-lowlatency-64k",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-tools-6.8.0-50-lowlatency",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-tools-6.8.0-50-lowlatency-64k",
"binary_version": "6.8.0-50.51.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-lowlatency",
"purl": "pkg:deb/ubuntu/linux-lowlatency@6.8.0-50.51.1?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-50.51.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-9.9.1",
"6.6.0-14.14.1",
"6.8.0-7.7.1",
"6.8.0-25.25.3",
"6.8.0-28.28.1",
"6.8.0-31.31.1",
"6.8.0-35.35.1",
"6.8.0-36.36.1",
"6.8.0-38.38.1",
"6.8.0-39.39.1",
"6.8.0-40.40.1",
"6.8.0-41.41.1",
"6.8.0-44.44.1",
"6.8.0-45.45.1",
"6.8.0-47.47.1",
"6.8.0-48.48.3",
"6.8.0-49.49.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1019-nvidia",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-buildinfo-6.8.0-1019-nvidia-64k",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-headers-6.8.0-1019-nvidia",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-headers-6.8.0-1019-nvidia-64k",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1019-nvidia",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1019-nvidia-64k",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-modules-6.8.0-1019-nvidia",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-modules-6.8.0-1019-nvidia-64k",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-modules-extra-6.8.0-1019-nvidia",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-modules-nvidia-fs-6.8.0-1019-nvidia",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-modules-nvidia-fs-6.8.0-1019-nvidia-64k",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-nvidia-headers-6.8.0-1019",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-nvidia-tools-6.8.0-1019",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-tools-6.8.0-1019-nvidia",
"binary_version": "6.8.0-1019.21"
},
{
"binary_name": "linux-tools-6.8.0-1019-nvidia-64k",
"binary_version": "6.8.0-1019.21"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-nvidia",
"purl": "pkg:deb/ubuntu/linux-nvidia@6.8.0-1019.21?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1019.21"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1007.7",
"6.8.0-1008.8",
"6.8.0-1009.9",
"6.8.0-1010.10",
"6.8.0-1011.11",
"6.8.0-1012.12",
"6.8.0-1013.14",
"6.8.0-1014.15",
"6.8.0-1015.16",
"6.8.0-1017.19",
"6.8.0-1018.20"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1019-nvidia-lowlatency",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-buildinfo-6.8.0-1019-nvidia-lowlatency-64k",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-headers-6.8.0-1019-nvidia-lowlatency",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-headers-6.8.0-1019-nvidia-lowlatency-64k",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1019-nvidia-lowlatency",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1019-nvidia-lowlatency-64k",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-modules-6.8.0-1019-nvidia-lowlatency",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-modules-6.8.0-1019-nvidia-lowlatency-64k",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1019-nvidia-lowlatency",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-modules-nvidia-fs-6.8.0-1019-nvidia-lowlatency",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-modules-nvidia-fs-6.8.0-1019-nvidia-lowlatency-64k",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-nvidia-lowlatency-headers-6.8.0-1019",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-nvidia-lowlatency-tools-6.8.0-1019",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-nvidia-lowlatency-tools-host",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-tools-6.8.0-1019-nvidia-lowlatency",
"binary_version": "6.8.0-1019.21.1"
},
{
"binary_name": "linux-tools-6.8.0-1019-nvidia-lowlatency-64k",
"binary_version": "6.8.0-1019.21.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-nvidia-lowlatency",
"purl": "pkg:deb/ubuntu/linux-nvidia-lowlatency@6.8.0-1019.21.1?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1019.21.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1009.9.1",
"6.8.0-1011.11.1",
"6.8.0-1012.12.1",
"6.8.0-1013.14.1",
"6.8.0-1014.15.1",
"6.8.0-1015.16.1",
"6.8.0-1017.19.1",
"6.8.0-1018.20.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1018-oem",
"binary_version": "6.8.0-1018.18"
},
{
"binary_name": "linux-headers-6.8.0-1018-oem",
"binary_version": "6.8.0-1018.18"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1018-oem",
"binary_version": "6.8.0-1018.18"
},
{
"binary_name": "linux-modules-6.8.0-1018-oem",
"binary_version": "6.8.0-1018.18"
},
{
"binary_name": "linux-modules-ipu6-6.8.0-1018-oem",
"binary_version": "6.8.0-1018.18"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-1018-oem",
"binary_version": "6.8.0-1018.18"
},
{
"binary_name": "linux-modules-usbio-6.8.0-1018-oem",
"binary_version": "6.8.0-1018.18"
},
{
"binary_name": "linux-oem-6.8-headers-6.8.0-1018",
"binary_version": "6.8.0-1018.18"
},
{
"binary_name": "linux-oem-6.8-tools-6.8.0-1018",
"binary_version": "6.8.0-1018.18"
},
{
"binary_name": "linux-tools-6.8.0-1018-oem",
"binary_version": "6.8.0-1018.18"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-oem-6.8",
"purl": "pkg:deb/ubuntu/linux-oem-6.8@6.8.0-1018.18?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1018.18"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1003.3",
"6.8.0-1004.4",
"6.8.0-1005.5",
"6.8.0-1006.6",
"6.8.0-1007.7",
"6.8.0-1008.8",
"6.8.0-1009.9",
"6.8.0-1010.10",
"6.8.0-1011.11",
"6.8.0-1012.12",
"6.8.0-1013.13",
"6.8.0-1014.14",
"6.8.0-1016.16",
"6.8.0-1017.17"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1017-oracle",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-buildinfo-6.8.0-1017-oracle-64k",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-headers-6.8.0-1017-oracle",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-headers-6.8.0-1017-oracle-64k",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1017-oracle",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1017-oracle-64k",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-modules-6.8.0-1017-oracle",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-modules-6.8.0-1017-oracle-64k",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-modules-extra-6.8.0-1017-oracle",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-modules-extra-6.8.0-1017-oracle-64k",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-oracle-headers-6.8.0-1017",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-oracle-tools-6.8.0-1017",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-tools-6.8.0-1017-oracle",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-tools-6.8.0-1017-oracle-64k",
"binary_version": "6.8.0-1017.18"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-oracle",
"purl": "pkg:deb/ubuntu/linux-oracle@6.8.0-1017.18?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1017.18"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-1010.10",
"6.6.0-1001.1",
"6.8.0-1001.1",
"6.8.0-1004.4",
"6.8.0-1005.5",
"6.8.0-1006.6",
"6.8.0-1008.8",
"6.8.0-1010.10",
"6.8.0-1011.11",
"6.8.0-1012.12",
"6.8.0-1013.13",
"6.8.0-1014.14",
"6.8.0-1015.16",
"6.8.0-1016.17"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1016-raspi",
"binary_version": "6.8.0-1016.18"
},
{
"binary_name": "linux-headers-6.8.0-1016-raspi",
"binary_version": "6.8.0-1016.18"
},
{
"binary_name": "linux-image-6.8.0-1016-raspi",
"binary_version": "6.8.0-1016.18"
},
{
"binary_name": "linux-modules-6.8.0-1016-raspi",
"binary_version": "6.8.0-1016.18"
},
{
"binary_name": "linux-raspi-headers-6.8.0-1016",
"binary_version": "6.8.0-1016.18"
},
{
"binary_name": "linux-raspi-tools-6.8.0-1016",
"binary_version": "6.8.0-1016.18"
},
{
"binary_name": "linux-tools-6.8.0-1016-raspi",
"binary_version": "6.8.0-1016.18"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-raspi",
"purl": "pkg:deb/ubuntu/linux-raspi@6.8.0-1016.18?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1016.18"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-1005.7",
"6.7.0-1001.1",
"6.8.0-1001.1",
"6.8.0-1002.2",
"6.8.0-1003.3",
"6.8.0-1004.4",
"6.8.0-1005.5",
"6.8.0-1006.6",
"6.8.0-1007.7",
"6.8.0-1008.8",
"6.8.0-1009.10",
"6.8.0-1010.11",
"6.8.0-1011.12",
"6.8.0-1012.13",
"6.8.0-1013.14",
"6.8.0-1014.16",
"6.8.0-1015.17"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-50-generic",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-headers-6.8.0-50-generic",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-image-6.8.0-50-generic",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-modules-6.8.0-50-generic",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-riscv-headers-6.8.0-50",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-riscv-tools-6.8.0-50",
"binary_version": "6.8.0-50.51.1"
},
{
"binary_name": "linux-tools-6.8.0-50-generic",
"binary_version": "6.8.0-50.51.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-riscv",
"purl": "pkg:deb/ubuntu/linux-riscv@6.8.0-50.51.1?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-50.51.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.5.0-9.9.1",
"6.8.0-20.20.1",
"6.8.0-28.28.1",
"6.8.0-31.31.1",
"6.8.0-35.35.1",
"6.8.0-36.36.1",
"6.8.0-38.38.1",
"6.8.0-39.39.1",
"6.8.0-40.40.1",
"6.8.0-41.41.1",
"6.8.0-44.44.1",
"6.8.0-47.47.1",
"6.8.0-48.48.1",
"6.8.0-49.49.1"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1017-xilinx",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-headers-6.8.0-1017-xilinx",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-image-6.8.0-1017-xilinx",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-modules-6.8.0-1017-xilinx",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-tools-6.8.0-1017-xilinx",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-xilinx-headers-6.8.0-1017",
"binary_version": "6.8.0-1017.18"
},
{
"binary_name": "linux-xilinx-tools-6.8.0-1017",
"binary_version": "6.8.0-1017.18"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "linux-xilinx",
"purl": "pkg:deb/ubuntu/linux-xilinx@6.8.0-1017.18?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-1017.18"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1008.9",
"6.8.0-1009.10",
"6.8.0-1011.12",
"6.8.0-1012.13",
"6.8.0-1013.14",
"6.8.0-1014.15",
"6.8.0-1015.16"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-fips-headers-6.8.0-78",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-fips-lib-rust-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-fips-tools-6.8.0-78",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-headers-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-image-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-image-hmac-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-modules-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-modules-extra-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-modules-ipu6-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-modules-usbio-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-tools-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:FIPS-updates:24.04:LTS",
"name": "linux-fips",
"purl": "pkg:deb/ubuntu/linux-fips@6.8.0-78.78+fips1?arch=source\u0026distro=fips-updates/noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-78.78+fips1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-38.38+fips4"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-2015-raspi-realtime",
"binary_version": "6.8.0-2015.16"
},
{
"binary_name": "linux-headers-6.8.0-2015-raspi-realtime",
"binary_version": "6.8.0-2015.16"
},
{
"binary_name": "linux-image-6.8.0-2015-raspi-realtime",
"binary_version": "6.8.0-2015.16"
},
{
"binary_name": "linux-modules-6.8.0-2015-raspi-realtime",
"binary_version": "6.8.0-2015.16"
},
{
"binary_name": "linux-raspi-realtime-headers-6.8.0-2015",
"binary_version": "6.8.0-2015.16"
},
{
"binary_name": "linux-raspi-realtime-tools-6.8.0-2015",
"binary_version": "6.8.0-2015.16"
},
{
"binary_name": "linux-tools-6.8.0-2015-raspi-realtime",
"binary_version": "6.8.0-2015.16"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:Realtime:24.04:LTS",
"name": "linux-raspi-realtime",
"purl": "pkg:deb/ubuntu/linux-raspi-realtime@6.8.0-2015.16?arch=source\u0026distro=realtime/noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.0-2015.16"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.7.0-2001.1",
"6.8.0-2001.1",
"6.8.0-2002.2",
"6.8.0-2004.4",
"6.8.0-2005.5",
"6.8.0-2006.6",
"6.8.0-2007.7",
"6.8.0-2008.8",
"6.8.0-2009.9",
"6.8.0-2010.10",
"6.8.0-2011.11",
"6.8.0-2012.12",
"6.8.0-2013.14",
"6.8.0-2014.15"
]
},
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14"
},
{
"binary_name": "linux-cloud-tools-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14"
},
{
"binary_name": "linux-headers-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14"
},
{
"binary_name": "linux-image-unsigned-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14"
},
{
"binary_name": "linux-modules-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14"
},
{
"binary_name": "linux-modules-extra-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14"
},
{
"binary_name": "linux-realtime-cloud-tools-6.8.1-1013",
"binary_version": "6.8.1-1013.14"
},
{
"binary_name": "linux-realtime-headers-6.8.1-1013",
"binary_version": "6.8.1-1013.14"
},
{
"binary_name": "linux-realtime-tools-6.8.1-1013",
"binary_version": "6.8.1-1013.14"
},
{
"binary_name": "linux-tools-6.8.1-1013-realtime",
"binary_version": "6.8.1-1013.14"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:Realtime:24.04:LTS",
"name": "linux-realtime",
"purl": "pkg:deb/ubuntu/linux-realtime@6.8.1-1013.14?arch=source\u0026distro=realtime/noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.8.1-1013.14"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.8.0-1008.19",
"6.8.1-1001.1",
"6.8.1-1002.2",
"6.8.1-1003.3",
"6.8.1-1004.4",
"6.8.1-1005.5",
"6.8.1-1006.6",
"6.8.1-1007.7",
"6.8.1-1008.8",
"6.8.1-1009.9",
"6.8.1-1010.10",
"6.8.1-1011.11",
"6.8.1-1012.12"
]
}
],
"aliases": [],
"details": "In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to don\u0027t dirty inode for readonly filesystem syzbot reports f2fs bug as below: kernel BUG at fs/f2fs/inode.c:933! RIP: 0010:f2fs_evict_inode+0x1576/0x1590 fs/f2fs/inode.c:933 Call Trace: evict+0x2a4/0x620 fs/inode.c:664 dispose_list fs/inode.c:697 [inline] evict_inodes+0x5f8/0x690 fs/inode.c:747 generic_shutdown_super+0x9d/0x2c0 fs/super.c:675 kill_block_super+0x44/0x90 fs/super.c:1667 kill_f2fs_super+0x303/0x3b0 fs/f2fs/super.c:4894 deactivate_locked_super+0xc1/0x130 fs/super.c:484 cleanup_mnt+0x426/0x4c0 fs/namespace.c:1256 task_work_run+0x24a/0x300 kernel/task_work.c:180 ptrace_notify+0x2cd/0x380 kernel/signal.c:2399 ptrace_report_syscall include/linux/ptrace.h:411 [inline] ptrace_report_syscall_exit include/linux/ptrace.h:473 [inline] syscall_exit_work kernel/entry/common.c:251 [inline] syscall_exit_to_user_mode_prepare kernel/entry/common.c:278 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline] syscall_exit_to_user_mode+0x15c/0x280 kernel/entry/common.c:296 do_syscall_64+0x50/0x110 arch/x86/entry/common.c:88 entry_SYSCALL_64_after_hwframe+0x63/0x6b The root cause is: - do_sys_open - f2fs_lookup - __f2fs_find_entry - f2fs_i_depth_write - f2fs_mark_inode_dirty_sync - f2fs_dirty_inode - set_inode_flag(inode, FI_DIRTY_INODE) - umount - kill_f2fs_super - kill_block_super - generic_shutdown_super - sync_filesystem : sb is readonly, skip sync_filesystem() - evict_inodes - iput - f2fs_evict_inode - f2fs_bug_on(sbi, is_inode_flag_set(inode, FI_DIRTY_INODE)) : trigger kernel panic When we try to repair i_current_depth in readonly filesystem, let\u0027s skip dirty inode to avoid panic in later f2fs_evict_inode().",
"id": "UBUNTU-CVE-2024-42297",
"modified": "2026-10-01T15:52:38Z",
"published": "2024-08-17T09:15:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2024-42297"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-42297"
},
{
"type": "REPORT",
"url": "https://git.kernel.org/linus/192b8fb8d1c8ca3c87366ebbef599fa80bb626b8"
},
{
"type": "REPORT",
"url": "https://git.kernel.org/stable/c/9ce8135accf103f7333af472709125878704fdd4"
},
{
"type": "REPORT",
"url": "https://git.kernel.org/stable/c/e62ff092a42f4a1bae3b310cf46673b4f3aac3b5"
},
{
"type": "REPORT",
"url": "https://git.kernel.org/stable/c/2434344559f6743efb3ac15d11af9a0db9543bd3"
},
{
"type": "REPORT",
"url": "https://git.kernel.org/stable/c/192b8fb8d1c8ca3c87366ebbef599fa80bb626b8"
},
{
"type": "REPORT",
"url": "https://git.kernel.org/stable/c/2d2916516577f2239b3377d9e8d12da5e6ccdfcf"
},
{
"type": "REPORT",
"url": "https://git.kernel.org/stable/c/54162974aea37a8cae00742470a78c7f6bd6f915"
},
{
"type": "REPORT",
"url": "https://git.kernel.org/stable/c/54bc4e88447e385c4d4ffa85d93e0dce628fcfa6"
},
{
"type": "REPORT",
"url": "https://git.kernel.org/stable/c/ec56571b4b146a1cfbedab49d5fcaf19fe8bf4f1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7088-1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7088-2"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7088-3"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7088-4"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7100-1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7100-2"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7088-5"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7119-1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7123-1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7144-1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7154-1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7155-1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7156-1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7154-2"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7194-1"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-7196-1"
}
],
"related": [
"USN-7088-1",
"USN-7088-2",
"USN-7088-3",
"USN-7088-4",
"USN-7100-1",
"USN-7100-2",
"USN-7088-5",
"USN-7119-1",
"USN-7123-1",
"USN-7144-1",
"USN-7154-1",
"USN-7155-1",
"USN-7156-1",
"USN-7154-2",
"USN-7194-1",
"USN-7196-1"
],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2024-42297"
]
}
WID-SEC-W-2024-1875
Vulnerability from csaf_certbund - Published: 2024-08-18 22:00 - Updated: 2026-05-14 22:00Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.