Action not permitted
Modal body text goes here.
Modal Title
Modal Body
CVE-2026-46299 (GCVE-0-2026-46299)
Vulnerability from cvelistv5 – Published: 2026-06-08 15:46 – Updated: 2026-06-14 18:07| Vendor | Product | Version | |
|---|---|---|---|
| Linux | Linux |
Affected:
89ac9b4d3d1a049ae1054f99b1aed81092cd0a82 , < 3ca80e3012c8be85b4f8d0d20eac8d3b17ff257e
(git)
Affected: 89ac9b4d3d1a049ae1054f99b1aed81092cd0a82 , < 041acda6d9f96006703466449c10c9a69590c8b9 (git) Affected: 89ac9b4d3d1a049ae1054f99b1aed81092cd0a82 , < d309d3308de658d87c42d97e044c89a226327526 (git) Affected: 89ac9b4d3d1a049ae1054f99b1aed81092cd0a82 , < bfbcce6a7b0552a390620d9b2c4d2bcb1825cbdc (git) Affected: 89ac9b4d3d1a049ae1054f99b1aed81092cd0a82 , < 90c500e4fd83fa33c09bc7ee23b6d9cc487ac733 (git) |
|
| Linux | Linux |
Affected:
3.19
Unaffected: 0 , < 3.19 (semver) Unaffected: 6.6.140 , ≤ 6.6.* (semver) Unaffected: 6.12.88 , ≤ 6.12.* (semver) Unaffected: 6.18.30 , ≤ 6.18.* (semver) Unaffected: 7.0.7 , ≤ 7.0.* (semver) Unaffected: 7.1 , ≤ * (original_commit_for_fix) |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/hfsplus/super.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "3ca80e3012c8be85b4f8d0d20eac8d3b17ff257e",
"status": "affected",
"version": "89ac9b4d3d1a049ae1054f99b1aed81092cd0a82",
"versionType": "git"
},
{
"lessThan": "041acda6d9f96006703466449c10c9a69590c8b9",
"status": "affected",
"version": "89ac9b4d3d1a049ae1054f99b1aed81092cd0a82",
"versionType": "git"
},
{
"lessThan": "d309d3308de658d87c42d97e044c89a226327526",
"status": "affected",
"version": "89ac9b4d3d1a049ae1054f99b1aed81092cd0a82",
"versionType": "git"
},
{
"lessThan": "bfbcce6a7b0552a390620d9b2c4d2bcb1825cbdc",
"status": "affected",
"version": "89ac9b4d3d1a049ae1054f99b1aed81092cd0a82",
"versionType": "git"
},
{
"lessThan": "90c500e4fd83fa33c09bc7ee23b6d9cc487ac733",
"status": "affected",
"version": "89ac9b4d3d1a049ae1054f99b1aed81092cd0a82",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/hfsplus/super.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "3.19"
},
{
"lessThan": "3.19",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.140",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.88",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.30",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.0.*",
"status": "unaffected",
"version": "7.0.7",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.1",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.6.140",
"versionStartIncluding": "3.19",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.88",
"versionStartIncluding": "3.19",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.30",
"versionStartIncluding": "3.19",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.0.7",
"versionStartIncluding": "3.19",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.1",
"versionStartIncluding": "3.19",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix held lock freed on hfsplus_fill_super()\n\nhfsplus_fill_super() calls hfs_find_init() to initialize a search\nstructure, which acquires tree-\u003etree_lock. If the subsequent call to\nhfsplus_cat_build_key() fails, the function jumps to the out_put_root\nerror label without releasing the lock. The later cleanup path then\nfrees the tree data structure with the lock still held, triggering a\nheld lock freed warning.\n\nFix this by adding the missing hfs_find_exit(\u0026fd) call before jumping\nto the out_put_root error label. This ensures that tree-\u003etree_lock is\nproperly released on the error path.\n\nThe bug was originally detected on v6.13-rc1 using an experimental\nstatic analysis tool we are developing, and we have verified that the\nissue persists in the latest mainline kernel. The tool is specifically\ndesigned to detect memory management issues. It is currently under active\ndevelopment and not yet publicly available.\n\nWe confirmed the bug by runtime testing under QEMU with x86_64 defconfig,\nlockdep enabled, and CONFIG_HFSPLUS_FS=y. To trigger the error path, we\nused GDB to dynamically shrink the max_unistr_len parameter to 1 before\nhfsplus_asc2uni() is called. This forces hfsplus_asc2uni() to naturally\nreturn -ENAMETOOLONG, which propagates to hfsplus_cat_build_key() and\nexercises the faulty error path. The following warning was observed\nduring mount:\n\n\t=========================\n\tWARNING: held lock freed!\n\t7.0.0-rc3-00016-gb4f0dd314b39 #4 Not tainted\n\t-------------------------\n\tmount/174 is freeing memory ffff888103f92000-ffff888103f92fff, with a lock still held there!\n\tffff888103f920b0 (\u0026tree-\u003etree_lock){+.+.}-{4:4}, at: hfsplus_find_init+0x154/0x1e0\n\t2 locks held by mount/174:\n\t#0: ffff888103f960e0 (\u0026type-\u003es_umount_key#42/1){+.+.}-{4:4}, at: alloc_super.constprop.0+0x167/0xa40\n\t#1: ffff888103f920b0 (\u0026tree-\u003etree_lock){+.+.}-{4:4}, at: hfsplus_find_init+0x154/0x1e0\n\n\tstack backtrace:\n\tCPU: 2 UID: 0 PID: 174 Comm: mount Not tainted 7.0.0-rc3-00016-gb4f0dd314b39 #4 PREEMPT(lazy)\n\tHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014\n\tCall Trace:\n\t\u003cTASK\u003e\n\tdump_stack_lvl+0x82/0xd0\n\tdebug_check_no_locks_freed+0x13a/0x180\n\tkfree+0x16b/0x510\n\t? hfsplus_fill_super+0xcb4/0x18a0\n\thfsplus_fill_super+0xcb4/0x18a0\n\t? __pfx_hfsplus_fill_super+0x10/0x10\n\t? srso_return_thunk+0x5/0x5f\n\t? bdev_open+0x65f/0xc30\n\t? srso_return_thunk+0x5/0x5f\n\t? pointer+0x4ce/0xbf0\n\t? trace_contention_end+0x11c/0x150\n\t? __pfx_pointer+0x10/0x10\n\t? srso_return_thunk+0x5/0x5f\n\t? bdev_open+0x79b/0xc30\n\t? srso_return_thunk+0x5/0x5f\n\t? srso_return_thunk+0x5/0x5f\n\t? vsnprintf+0x6da/0x1270\n\t? srso_return_thunk+0x5/0x5f\n\t? __mutex_unlock_slowpath+0x157/0x740\n\t? __pfx_vsnprintf+0x10/0x10\n\t? srso_return_thunk+0x5/0x5f\n\t? srso_return_thunk+0x5/0x5f\n\t? mark_held_locks+0x49/0x80\n\t? srso_return_thunk+0x5/0x5f\n\t? srso_return_thunk+0x5/0x5f\n\t? irqentry_exit+0x17b/0x5e0\n\t? trace_irq_disable.constprop.0+0x116/0x150\n\t? __pfx_hfsplus_fill_super+0x10/0x10\n\t? __pfx_hfsplus_fill_super+0x10/0x10\n\tget_tree_bdev_flags+0x302/0x580\n\t? __pfx_get_tree_bdev_flags+0x10/0x10\n\t? vfs_parse_fs_qstr+0x129/0x1a0\n\t? __pfx_vfs_parse_fs_qstr+0x3/0x10\n\tvfs_get_tree+0x89/0x320\n\tfc_mount+0x10/0x1d0\n\tpath_mount+0x5c5/0x21c0\n\t? __pfx_path_mount+0x10/0x10\n\t? trace_irq_enable.constprop.0+0x116/0x150\n\t? trace_irq_enable.constprop.0+0x116/0x150\n\t? srso_return_thunk+0x5/0x5f\n\t? srso_return_thunk+0x5/0x5f\n\t? kmem_cache_free+0x307/0x540\n\t? user_path_at+0x51/0x60\n\t? __x64_sys_mount+0x212/0x280\n\t? srso_return_thunk+0x5/0x5f\n\t__x64_sys_mount+0x212/0x280\n\t? __pfx___x64_sys_mount+0x10/0x10\n\t? srso_return_thunk+0x5/0x5f\n\t? trace_irq_enable.constprop.0+0x116/0x150\n\t? srso_return_thunk+0x5/0x5f\n\tdo_syscall_64+0x111/0x680\n\tentry_SYSCALL_64_after_hwframe+0x77/0x7f\n\tRIP: 0033:0x7ffacad55eae\n\tCode: 48 8b 0d 85 1f 0f 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00 8\n\tRSP: 002b\n---truncated---"
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 7,
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-06-14T18:07:28.852Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/3ca80e3012c8be85b4f8d0d20eac8d3b17ff257e"
},
{
"url": "https://git.kernel.org/stable/c/041acda6d9f96006703466449c10c9a69590c8b9"
},
{
"url": "https://git.kernel.org/stable/c/d309d3308de658d87c42d97e044c89a226327526"
},
{
"url": "https://git.kernel.org/stable/c/bfbcce6a7b0552a390620d9b2c4d2bcb1825cbdc"
},
{
"url": "https://git.kernel.org/stable/c/90c500e4fd83fa33c09bc7ee23b6d9cc487ac733"
}
],
"title": "hfsplus: fix held lock freed on hfsplus_fill_super()",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-46299",
"datePublished": "2026-06-08T15:46:26.670Z",
"dateReserved": "2026-05-13T15:03:33.111Z",
"dateUpdated": "2026-06-14T18:07:28.852Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-46299",
"date": "2026-06-17",
"epss": "0.00113",
"percentile": "0.01707"
},
"nvd": "{\"cve\":{\"id\":\"CVE-2026-46299\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-06-08T17:16:48.393\",\"lastModified\":\"2026-06-14T06:16:23.387\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nhfsplus: fix held lock freed on hfsplus_fill_super()\\n\\nhfsplus_fill_super() calls hfs_find_init() to initialize a search\\nstructure, which acquires tree-\u003etree_lock. If the subsequent call to\\nhfsplus_cat_build_key() fails, the function jumps to the out_put_root\\nerror label without releasing the lock. The later cleanup path then\\nfrees the tree data structure with the lock still held, triggering a\\nheld lock freed warning.\\n\\nFix this by adding the missing hfs_find_exit(\u0026fd) call before jumping\\nto the out_put_root error label. This ensures that tree-\u003etree_lock is\\nproperly released on the error path.\\n\\nThe bug was originally detected on v6.13-rc1 using an experimental\\nstatic analysis tool we are developing, and we have verified that the\\nissue persists in the latest mainline kernel. The tool is specifically\\ndesigned to detect memory management issues. It is currently under active\\ndevelopment and not yet publicly available.\\n\\nWe confirmed the bug by runtime testing under QEMU with x86_64 defconfig,\\nlockdep enabled, and CONFIG_HFSPLUS_FS=y. To trigger the error path, we\\nused GDB to dynamically shrink the max_unistr_len parameter to 1 before\\nhfsplus_asc2uni() is called. This forces hfsplus_asc2uni() to naturally\\nreturn -ENAMETOOLONG, which propagates to hfsplus_cat_build_key() and\\nexercises the faulty error path. The following warning was observed\\nduring mount:\\n\\n\\t=========================\\n\\tWARNING: held lock freed!\\n\\t7.0.0-rc3-00016-gb4f0dd314b39 #4 Not tainted\\n\\t-------------------------\\n\\tmount/174 is freeing memory ffff888103f92000-ffff888103f92fff, with a lock still held there!\\n\\tffff888103f920b0 (\u0026tree-\u003etree_lock){+.+.}-{4:4}, at: hfsplus_find_init+0x154/0x1e0\\n\\t2 locks held by mount/174:\\n\\t#0: ffff888103f960e0 (\u0026type-\u003es_umount_key#42/1){+.+.}-{4:4}, at: alloc_super.constprop.0+0x167/0xa40\\n\\t#1: ffff888103f920b0 (\u0026tree-\u003etree_lock){+.+.}-{4:4}, at: hfsplus_find_init+0x154/0x1e0\\n\\n\\tstack backtrace:\\n\\tCPU: 2 UID: 0 PID: 174 Comm: mount Not tainted 7.0.0-rc3-00016-gb4f0dd314b39 #4 PREEMPT(lazy)\\n\\tHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014\\n\\tCall Trace:\\n\\t\u003cTASK\u003e\\n\\tdump_stack_lvl+0x82/0xd0\\n\\tdebug_check_no_locks_freed+0x13a/0x180\\n\\tkfree+0x16b/0x510\\n\\t? hfsplus_fill_super+0xcb4/0x18a0\\n\\thfsplus_fill_super+0xcb4/0x18a0\\n\\t? __pfx_hfsplus_fill_super+0x10/0x10\\n\\t? srso_return_thunk+0x5/0x5f\\n\\t? bdev_open+0x65f/0xc30\\n\\t? srso_return_thunk+0x5/0x5f\\n\\t? pointer+0x4ce/0xbf0\\n\\t? trace_contention_end+0x11c/0x150\\n\\t? __pfx_pointer+0x10/0x10\\n\\t? srso_return_thunk+0x5/0x5f\\n\\t? bdev_open+0x79b/0xc30\\n\\t? srso_return_thunk+0x5/0x5f\\n\\t? srso_return_thunk+0x5/0x5f\\n\\t? vsnprintf+0x6da/0x1270\\n\\t? srso_return_thunk+0x5/0x5f\\n\\t? __mutex_unlock_slowpath+0x157/0x740\\n\\t? __pfx_vsnprintf+0x10/0x10\\n\\t? srso_return_thunk+0x5/0x5f\\n\\t? srso_return_thunk+0x5/0x5f\\n\\t? mark_held_locks+0x49/0x80\\n\\t? srso_return_thunk+0x5/0x5f\\n\\t? srso_return_thunk+0x5/0x5f\\n\\t? irqentry_exit+0x17b/0x5e0\\n\\t? trace_irq_disable.constprop.0+0x116/0x150\\n\\t? __pfx_hfsplus_fill_super+0x10/0x10\\n\\t? __pfx_hfsplus_fill_super+0x10/0x10\\n\\tget_tree_bdev_flags+0x302/0x580\\n\\t? __pfx_get_tree_bdev_flags+0x10/0x10\\n\\t? vfs_parse_fs_qstr+0x129/0x1a0\\n\\t? __pfx_vfs_parse_fs_qstr+0x3/0x10\\n\\tvfs_get_tree+0x89/0x320\\n\\tfc_mount+0x10/0x1d0\\n\\tpath_mount+0x5c5/0x21c0\\n\\t? __pfx_path_mount+0x10/0x10\\n\\t? trace_irq_enable.constprop.0+0x116/0x150\\n\\t? trace_irq_enable.constprop.0+0x116/0x150\\n\\t? srso_return_thunk+0x5/0x5f\\n\\t? srso_return_thunk+0x5/0x5f\\n\\t? kmem_cache_free+0x307/0x540\\n\\t? user_path_at+0x51/0x60\\n\\t? __x64_sys_mount+0x212/0x280\\n\\t? srso_return_thunk+0x5/0x5f\\n\\t__x64_sys_mount+0x212/0x280\\n\\t? __pfx___x64_sys_mount+0x10/0x10\\n\\t? srso_return_thunk+0x5/0x5f\\n\\t? trace_irq_enable.constprop.0+0x116/0x150\\n\\t? srso_return_thunk+0x5/0x5f\\n\\tdo_syscall_64+0x111/0x680\\n\\tentry_SYSCALL_64_after_hwframe+0x77/0x7f\\n\\tRIP: 0033:0x7ffacad55eae\\n\\tCode: 48 8b 0d 85 1f 0f 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00 8\\n\\tRSP: 002b\\n---truncated---\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H\",\"baseScore\":7.0,\"baseSeverity\":\"HIGH\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"HIGH\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.0,\"impactScore\":5.9}]},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/041acda6d9f96006703466449c10c9a69590c8b9\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/3ca80e3012c8be85b4f8d0d20eac8d3b17ff257e\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/90c500e4fd83fa33c09bc7ee23b6d9cc487ac733\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/bfbcce6a7b0552a390620d9b2c4d2bcb1825cbdc\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/d309d3308de658d87c42d97e044c89a226327526\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
}
}
FKIE_CVE-2026-46299
Vulnerability from fkie_nvd - Published: 2026-06-08 17:16 - Updated: 2026-06-14 06:16| Vendor | Product | Version |
|---|
{
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix held lock freed on hfsplus_fill_super()\n\nhfsplus_fill_super() calls hfs_find_init() to initialize a search\nstructure, which acquires tree-\u003etree_lock. If the subsequent call to\nhfsplus_cat_build_key() fails, the function jumps to the out_put_root\nerror label without releasing the lock. The later cleanup path then\nfrees the tree data structure with the lock still held, triggering a\nheld lock freed warning.\n\nFix this by adding the missing hfs_find_exit(\u0026fd) call before jumping\nto the out_put_root error label. This ensures that tree-\u003etree_lock is\nproperly released on the error path.\n\nThe bug was originally detected on v6.13-rc1 using an experimental\nstatic analysis tool we are developing, and we have verified that the\nissue persists in the latest mainline kernel. The tool is specifically\ndesigned to detect memory management issues. It is currently under active\ndevelopment and not yet publicly available.\n\nWe confirmed the bug by runtime testing under QEMU with x86_64 defconfig,\nlockdep enabled, and CONFIG_HFSPLUS_FS=y. To trigger the error path, we\nused GDB to dynamically shrink the max_unistr_len parameter to 1 before\nhfsplus_asc2uni() is called. This forces hfsplus_asc2uni() to naturally\nreturn -ENAMETOOLONG, which propagates to hfsplus_cat_build_key() and\nexercises the faulty error path. The following warning was observed\nduring mount:\n\n\t=========================\n\tWARNING: held lock freed!\n\t7.0.0-rc3-00016-gb4f0dd314b39 #4 Not tainted\n\t-------------------------\n\tmount/174 is freeing memory ffff888103f92000-ffff888103f92fff, with a lock still held there!\n\tffff888103f920b0 (\u0026tree-\u003etree_lock){+.+.}-{4:4}, at: hfsplus_find_init+0x154/0x1e0\n\t2 locks held by mount/174:\n\t#0: ffff888103f960e0 (\u0026type-\u003es_umount_key#42/1){+.+.}-{4:4}, at: alloc_super.constprop.0+0x167/0xa40\n\t#1: ffff888103f920b0 (\u0026tree-\u003etree_lock){+.+.}-{4:4}, at: hfsplus_find_init+0x154/0x1e0\n\n\tstack backtrace:\n\tCPU: 2 UID: 0 PID: 174 Comm: mount Not tainted 7.0.0-rc3-00016-gb4f0dd314b39 #4 PREEMPT(lazy)\n\tHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014\n\tCall Trace:\n\t\u003cTASK\u003e\n\tdump_stack_lvl+0x82/0xd0\n\tdebug_check_no_locks_freed+0x13a/0x180\n\tkfree+0x16b/0x510\n\t? hfsplus_fill_super+0xcb4/0x18a0\n\thfsplus_fill_super+0xcb4/0x18a0\n\t? __pfx_hfsplus_fill_super+0x10/0x10\n\t? srso_return_thunk+0x5/0x5f\n\t? bdev_open+0x65f/0xc30\n\t? srso_return_thunk+0x5/0x5f\n\t? pointer+0x4ce/0xbf0\n\t? trace_contention_end+0x11c/0x150\n\t? __pfx_pointer+0x10/0x10\n\t? srso_return_thunk+0x5/0x5f\n\t? bdev_open+0x79b/0xc30\n\t? srso_return_thunk+0x5/0x5f\n\t? srso_return_thunk+0x5/0x5f\n\t? vsnprintf+0x6da/0x1270\n\t? srso_return_thunk+0x5/0x5f\n\t? __mutex_unlock_slowpath+0x157/0x740\n\t? __pfx_vsnprintf+0x10/0x10\n\t? srso_return_thunk+0x5/0x5f\n\t? srso_return_thunk+0x5/0x5f\n\t? mark_held_locks+0x49/0x80\n\t? srso_return_thunk+0x5/0x5f\n\t? srso_return_thunk+0x5/0x5f\n\t? irqentry_exit+0x17b/0x5e0\n\t? trace_irq_disable.constprop.0+0x116/0x150\n\t? __pfx_hfsplus_fill_super+0x10/0x10\n\t? __pfx_hfsplus_fill_super+0x10/0x10\n\tget_tree_bdev_flags+0x302/0x580\n\t? __pfx_get_tree_bdev_flags+0x10/0x10\n\t? vfs_parse_fs_qstr+0x129/0x1a0\n\t? __pfx_vfs_parse_fs_qstr+0x3/0x10\n\tvfs_get_tree+0x89/0x320\n\tfc_mount+0x10/0x1d0\n\tpath_mount+0x5c5/0x21c0\n\t? __pfx_path_mount+0x10/0x10\n\t? trace_irq_enable.constprop.0+0x116/0x150\n\t? trace_irq_enable.constprop.0+0x116/0x150\n\t? srso_return_thunk+0x5/0x5f\n\t? srso_return_thunk+0x5/0x5f\n\t? kmem_cache_free+0x307/0x540\n\t? user_path_at+0x51/0x60\n\t? __x64_sys_mount+0x212/0x280\n\t? srso_return_thunk+0x5/0x5f\n\t__x64_sys_mount+0x212/0x280\n\t? __pfx___x64_sys_mount+0x10/0x10\n\t? srso_return_thunk+0x5/0x5f\n\t? trace_irq_enable.constprop.0+0x116/0x150\n\t? srso_return_thunk+0x5/0x5f\n\tdo_syscall_64+0x111/0x680\n\tentry_SYSCALL_64_after_hwframe+0x77/0x7f\n\tRIP: 0033:0x7ffacad55eae\n\tCode: 48 8b 0d 85 1f 0f 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00 8\n\tRSP: 002b\n---truncated---"
}
],
"id": "CVE-2026-46299",
"lastModified": "2026-06-14T06:16:23.387",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "HIGH",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.0,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.0,
"impactScore": 5.9,
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"type": "Secondary"
}
]
},
"published": "2026-06-08T17:16:48.393",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/041acda6d9f96006703466449c10c9a69590c8b9"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/3ca80e3012c8be85b4f8d0d20eac8d3b17ff257e"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/90c500e4fd83fa33c09bc7ee23b6d9cc487ac733"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/bfbcce6a7b0552a390620d9b2c4d2bcb1825cbdc"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/d309d3308de658d87c42d97e044c89a226327526"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
GHSA-R7XR-JH3W-26WW
Vulnerability from github – Published: 2026-06-08 18:31 – Updated: 2026-06-14 06:30In the Linux kernel, the following vulnerability has been resolved:
hfsplus: fix held lock freed on hfsplus_fill_super()
hfsplus_fill_super() calls hfs_find_init() to initialize a search structure, which acquires tree->tree_lock. If the subsequent call to hfsplus_cat_build_key() fails, the function jumps to the out_put_root error label without releasing the lock. The later cleanup path then frees the tree data structure with the lock still held, triggering a held lock freed warning.
Fix this by adding the missing hfs_find_exit(&fd) call before jumping to the out_put_root error label. This ensures that tree->tree_lock is properly released on the error path.
The bug was originally detected on v6.13-rc1 using an experimental static analysis tool we are developing, and we have verified that the issue persists in the latest mainline kernel. The tool is specifically designed to detect memory management issues. It is currently under active development and not yet publicly available.
We confirmed the bug by runtime testing under QEMU with x86_64 defconfig, lockdep enabled, and CONFIG_HFSPLUS_FS=y. To trigger the error path, we used GDB to dynamically shrink the max_unistr_len parameter to 1 before hfsplus_asc2uni() is called. This forces hfsplus_asc2uni() to naturally return -ENAMETOOLONG, which propagates to hfsplus_cat_build_key() and exercises the faulty error path. The following warning was observed during mount:
=========================
WARNING: held lock freed!
7.0.0-rc3-00016-gb4f0dd314b39 #4 Not tainted
-------------------------
mount/174 is freeing memory ffff888103f92000-ffff888103f92fff, with a lock still held there!
ffff888103f920b0 (&tree->tree_lock){+.+.}-{4:4}, at: hfsplus_find_init+0x154/0x1e0
2 locks held by mount/174:
#0: ffff888103f960e0 (&type->s_umount_key#42/1){+.+.}-{4:4}, at: alloc_super.constprop.0+0x167/0xa40
#1: ffff888103f920b0 (&tree->tree_lock){+.+.}-{4:4}, at: hfsplus_find_init+0x154/0x1e0
stack backtrace:
CPU: 2 UID: 0 PID: 174 Comm: mount Not tainted 7.0.0-rc3-00016-gb4f0dd314b39 #4 PREEMPT(lazy)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014
Call Trace:
<TASK>
dump_stack_lvl+0x82/0xd0
debug_check_no_locks_freed+0x13a/0x180
kfree+0x16b/0x510
? hfsplus_fill_super+0xcb4/0x18a0
hfsplus_fill_super+0xcb4/0x18a0
? __pfx_hfsplus_fill_super+0x10/0x10
? srso_return_thunk+0x5/0x5f
? bdev_open+0x65f/0xc30
? srso_return_thunk+0x5/0x5f
? pointer+0x4ce/0xbf0
? trace_contention_end+0x11c/0x150
? __pfx_pointer+0x10/0x10
? srso_return_thunk+0x5/0x5f
? bdev_open+0x79b/0xc30
? srso_return_thunk+0x5/0x5f
? srso_return_thunk+0x5/0x5f
? vsnprintf+0x6da/0x1270
? srso_return_thunk+0x5/0x5f
? __mutex_unlock_slowpath+0x157/0x740
? __pfx_vsnprintf+0x10/0x10
? srso_return_thunk+0x5/0x5f
? srso_return_thunk+0x5/0x5f
? mark_held_locks+0x49/0x80
? srso_return_thunk+0x5/0x5f
? srso_return_thunk+0x5/0x5f
? irqentry_exit+0x17b/0x5e0
? trace_irq_disable.constprop.0+0x116/0x150
? __pfx_hfsplus_fill_super+0x10/0x10
? __pfx_hfsplus_fill_super+0x10/0x10
get_tree_bdev_flags+0x302/0x580
? __pfx_get_tree_bdev_flags+0x10/0x10
? vfs_parse_fs_qstr+0x129/0x1a0
? __pfx_vfs_parse_fs_qstr+0x3/0x10
vfs_get_tree+0x89/0x320
fc_mount+0x10/0x1d0
path_mount+0x5c5/0x21c0
? __pfx_path_mount+0x10/0x10
? trace_irq_enable.constprop.0+0x116/0x150
? trace_irq_enable.constprop.0+0x116/0x150
? srso_return_thunk+0x5/0x5f
? srso_return_thunk+0x5/0x5f
? kmem_cache_free+0x307/0x540
? user_path_at+0x51/0x60
? __x64_sys_mount+0x212/0x280
? srso_return_thunk+0x5/0x5f
__x64_sys_mount+0x212/0x280
? __pfx___x64_sys_mount+0x10/0x10
? srso_return_thunk+0x5/0x5f
? trace_irq_enable.constprop.0+0x116/0x150
? srso_return_thunk+0x5/0x5f
do_syscall_64+0x111/0x680
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7ffacad55eae
Code: 48 8b 0d 85 1f 0f 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00 8
RSP: 002b
---truncated---
{
"affected": [],
"aliases": [
"CVE-2026-46299"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-06-08T17:16:48Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix held lock freed on hfsplus_fill_super()\n\nhfsplus_fill_super() calls hfs_find_init() to initialize a search\nstructure, which acquires tree-\u003etree_lock. If the subsequent call to\nhfsplus_cat_build_key() fails, the function jumps to the out_put_root\nerror label without releasing the lock. The later cleanup path then\nfrees the tree data structure with the lock still held, triggering a\nheld lock freed warning.\n\nFix this by adding the missing hfs_find_exit(\u0026fd) call before jumping\nto the out_put_root error label. This ensures that tree-\u003etree_lock is\nproperly released on the error path.\n\nThe bug was originally detected on v6.13-rc1 using an experimental\nstatic analysis tool we are developing, and we have verified that the\nissue persists in the latest mainline kernel. The tool is specifically\ndesigned to detect memory management issues. It is currently under active\ndevelopment and not yet publicly available.\n\nWe confirmed the bug by runtime testing under QEMU with x86_64 defconfig,\nlockdep enabled, and CONFIG_HFSPLUS_FS=y. To trigger the error path, we\nused GDB to dynamically shrink the max_unistr_len parameter to 1 before\nhfsplus_asc2uni() is called. This forces hfsplus_asc2uni() to naturally\nreturn -ENAMETOOLONG, which propagates to hfsplus_cat_build_key() and\nexercises the faulty error path. The following warning was observed\nduring mount:\n\n\t=========================\n\tWARNING: held lock freed!\n\t7.0.0-rc3-00016-gb4f0dd314b39 #4 Not tainted\n\t-------------------------\n\tmount/174 is freeing memory ffff888103f92000-ffff888103f92fff, with a lock still held there!\n\tffff888103f920b0 (\u0026tree-\u003etree_lock){+.+.}-{4:4}, at: hfsplus_find_init+0x154/0x1e0\n\t2 locks held by mount/174:\n\t#0: ffff888103f960e0 (\u0026type-\u003es_umount_key#42/1){+.+.}-{4:4}, at: alloc_super.constprop.0+0x167/0xa40\n\t#1: ffff888103f920b0 (\u0026tree-\u003etree_lock){+.+.}-{4:4}, at: hfsplus_find_init+0x154/0x1e0\n\n\tstack backtrace:\n\tCPU: 2 UID: 0 PID: 174 Comm: mount Not tainted 7.0.0-rc3-00016-gb4f0dd314b39 #4 PREEMPT(lazy)\n\tHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014\n\tCall Trace:\n\t\u003cTASK\u003e\n\tdump_stack_lvl+0x82/0xd0\n\tdebug_check_no_locks_freed+0x13a/0x180\n\tkfree+0x16b/0x510\n\t? hfsplus_fill_super+0xcb4/0x18a0\n\thfsplus_fill_super+0xcb4/0x18a0\n\t? __pfx_hfsplus_fill_super+0x10/0x10\n\t? srso_return_thunk+0x5/0x5f\n\t? bdev_open+0x65f/0xc30\n\t? srso_return_thunk+0x5/0x5f\n\t? pointer+0x4ce/0xbf0\n\t? trace_contention_end+0x11c/0x150\n\t? __pfx_pointer+0x10/0x10\n\t? srso_return_thunk+0x5/0x5f\n\t? bdev_open+0x79b/0xc30\n\t? srso_return_thunk+0x5/0x5f\n\t? srso_return_thunk+0x5/0x5f\n\t? vsnprintf+0x6da/0x1270\n\t? srso_return_thunk+0x5/0x5f\n\t? __mutex_unlock_slowpath+0x157/0x740\n\t? __pfx_vsnprintf+0x10/0x10\n\t? srso_return_thunk+0x5/0x5f\n\t? srso_return_thunk+0x5/0x5f\n\t? mark_held_locks+0x49/0x80\n\t? srso_return_thunk+0x5/0x5f\n\t? srso_return_thunk+0x5/0x5f\n\t? irqentry_exit+0x17b/0x5e0\n\t? trace_irq_disable.constprop.0+0x116/0x150\n\t? __pfx_hfsplus_fill_super+0x10/0x10\n\t? __pfx_hfsplus_fill_super+0x10/0x10\n\tget_tree_bdev_flags+0x302/0x580\n\t? __pfx_get_tree_bdev_flags+0x10/0x10\n\t? vfs_parse_fs_qstr+0x129/0x1a0\n\t? __pfx_vfs_parse_fs_qstr+0x3/0x10\n\tvfs_get_tree+0x89/0x320\n\tfc_mount+0x10/0x1d0\n\tpath_mount+0x5c5/0x21c0\n\t? __pfx_path_mount+0x10/0x10\n\t? trace_irq_enable.constprop.0+0x116/0x150\n\t? trace_irq_enable.constprop.0+0x116/0x150\n\t? srso_return_thunk+0x5/0x5f\n\t? srso_return_thunk+0x5/0x5f\n\t? kmem_cache_free+0x307/0x540\n\t? user_path_at+0x51/0x60\n\t? __x64_sys_mount+0x212/0x280\n\t? srso_return_thunk+0x5/0x5f\n\t__x64_sys_mount+0x212/0x280\n\t? __pfx___x64_sys_mount+0x10/0x10\n\t? srso_return_thunk+0x5/0x5f\n\t? trace_irq_enable.constprop.0+0x116/0x150\n\t? srso_return_thunk+0x5/0x5f\n\tdo_syscall_64+0x111/0x680\n\tentry_SYSCALL_64_after_hwframe+0x77/0x7f\n\tRIP: 0033:0x7ffacad55eae\n\tCode: 48 8b 0d 85 1f 0f 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00 8\n\tRSP: 002b\n---truncated---",
"id": "GHSA-r7xr-jh3w-26ww",
"modified": "2026-06-14T06:30:23Z",
"published": "2026-06-08T18:31:52Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-46299"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/041acda6d9f96006703466449c10c9a69590c8b9"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/3ca80e3012c8be85b4f8d0d20eac8d3b17ff257e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/90c500e4fd83fa33c09bc7ee23b6d9cc487ac733"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/bfbcce6a7b0552a390620d9b2c4d2bcb1825cbdc"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d309d3308de658d87c42d97e044c89a226327526"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
MSRC_CVE-2026-46299
Vulnerability from csaf_microsoft - Published: 2026-06-02 00:00 - Updated: 2026-06-10 01:05| Product | Identifier | Version | Remediation |
|---|---|---|---|
| Unresolved product id: 17084-1 | — |
None Available
|
| URL | Category |
|---|---|
| https://msrc.microsoft.com/csaf/vex/2026/msrc_cve… | self |
| https://support.microsoft.com/lifecycle | external |
| https://www.first.org/cvss | external |
| https://msrc.microsoft.com/csaf/vex/2026/msrc_cve… | self |
{
"document": {
"category": "csaf_vex",
"csaf_version": "2.0",
"distribution": {
"text": "Public",
"tlp": {
"label": "WHITE",
"url": "https://www.first.org/tlp/"
}
},
"lang": "en-US",
"notes": [
{
"category": "general",
"text": "To determine the support lifecycle for your software, see the Microsoft Support Lifecycle: https://support.microsoft.com/lifecycle",
"title": "Additional Resources"
},
{
"category": "legal_disclaimer",
"text": "The information provided in the Microsoft Knowledge Base is provided \\\"as is\\\" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.",
"title": "Disclaimer"
}
],
"publisher": {
"category": "vendor",
"contact_details": "secure@microsoft.com",
"name": "Microsoft Security Response Center",
"namespace": "https://msrc.microsoft.com"
},
"references": [
{
"category": "self",
"summary": "CVE-2026-46299 hfsplus: fix held lock freed on hfsplus_fill_super() - VEX",
"url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-46299.json"
},
{
"category": "external",
"summary": "Microsoft Support Lifecycle",
"url": "https://support.microsoft.com/lifecycle"
},
{
"category": "external",
"summary": "Common Vulnerability Scoring System",
"url": "https://www.first.org/cvss"
}
],
"title": "hfsplus: fix held lock freed on hfsplus_fill_super()",
"tracking": {
"current_release_date": "2026-06-10T01:05:18.000Z",
"generator": {
"date": "2026-06-10T07:02:18.587Z",
"engine": {
"name": "MSRC Generator",
"version": "1.0"
}
},
"id": "msrc_CVE-2026-46299",
"initial_release_date": "2026-06-02T00:00:00.000Z",
"revision_history": [
{
"date": "2026-06-10T01:05:18.000Z",
"legacy_version": "1",
"number": "1",
"summary": "Information published."
}
],
"status": "final",
"version": "1"
}
},
"product_tree": {
"branches": [
{
"branches": [
{
"branches": [
{
"category": "product_version",
"name": "3.0",
"product": {
"name": "Azure Linux 3.0",
"product_id": "17084"
}
}
],
"category": "product_name",
"name": "Azure Linux"
},
{
"branches": [
{
"category": "product_version_range",
"name": "azl3 kernel 0:6.6.139.1-1.azl3",
"product": {
"name": "azl3 kernel 0:6.6.139.1-1.azl3",
"product_id": "1"
}
}
],
"category": "product_name",
"name": "kernel"
}
],
"category": "vendor",
"name": "Microsoft"
}
],
"relationships": [
{
"category": "default_component_of",
"full_product_name": {
"name": "azl3 kernel 0:6.6.139.1-1.azl3 as a component of Azure Linux 3.0",
"product_id": "17084-1"
},
"product_reference": "1",
"relates_to_product_reference": "17084"
}
]
},
"vulnerabilities": [
{
"cve": "CVE-2026-46299",
"notes": [
{
"category": "general",
"text": "Linux",
"title": "Assigning CNA"
}
],
"product_status": {
"known_affected": [
"17084-1"
]
},
"references": [
{
"category": "self",
"summary": "CVE-2026-46299 hfsplus: fix held lock freed on hfsplus_fill_super() - VEX",
"url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-46299.json"
}
],
"remediations": [
{
"category": "none_available",
"date": "2026-06-10T01:05:18.000Z",
"details": "There is no fix available for this vulnerability as of now",
"product_ids": [
"17084-1"
]
}
],
"title": "hfsplus: fix held lock freed on hfsplus_fill_super()"
}
]
}
WID-SEC-W-2026-1827
Vulnerability from csaf_certbund - Published: 2026-06-08 22:00 - Updated: 2026-06-14 22:00| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Open Source Linux Kernel
Open Source
|
cpe:/o:linux:linux_kernel:-
|
— | |
|
SUSE openSUSE
SUSE
|
cpe:/o:suse:opensuse:-
|
— |
{
"document": {
"aggregate_severity": {
"text": "hoch"
},
"category": "csaf_base",
"csaf_version": "2.0",
"distribution": {
"tlp": {
"label": "WHITE",
"url": "https://www.first.org/tlp/"
}
},
"lang": "de-DE",
"notes": [
{
"category": "legal_disclaimer",
"text": "Das BSI ist als Anbieter f\u00fcr die eigenen, zur Nutzung bereitgestellten Inhalte nach den allgemeinen Gesetzen verantwortlich. Nutzerinnen und Nutzer sind jedoch daf\u00fcr verantwortlich, die Verwendung und/oder die Umsetzung der mit den Inhalten bereitgestellten Informationen sorgf\u00e4ltig im Einzelfall zu pr\u00fcfen."
},
{
"category": "description",
"text": "Der Kernel stellt den Kern des Linux Betriebssystems dar.",
"title": "Produktbeschreibung"
},
{
"category": "summary",
"text": "Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuf\u00fchren oder nicht bekannte Auswirkungen zu erzielen.",
"title": "Angriff"
},
{
"category": "general",
"text": "- Linux",
"title": "Betroffene Betriebssysteme"
}
],
"publisher": {
"category": "other",
"contact_details": "csaf-provider@cert-bund.de",
"name": "Bundesamt f\u00fcr Sicherheit in der Informationstechnik",
"namespace": "https://www.bsi.bund.de"
},
"references": [
{
"category": "self",
"summary": "WID-SEC-W-2026-1827 - CSAF Version",
"url": "https://wid.cert-bund.de/.well-known/csaf/white/2026/wid-sec-w-2026-1827.json"
},
{
"category": "self",
"summary": "WID-SEC-2026-1827 - Portal Version",
"url": "https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2026-1827"
},
{
"category": "external",
"summary": "Kernel CVE Announce Mailingliste",
"url": "https://lore.kernel.org/linux-cve-announce/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2025-71315",
"url": "https://lore.kernel.org/linux-cve-announce/2026060801-CVE-2025-71315-ee7d@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46274",
"url": "https://lore.kernel.org/linux-cve-announce/2026060803-CVE-2026-46274-b5c3@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46275",
"url": "https://lore.kernel.org/linux-cve-announce/2026060803-CVE-2026-46275-9af6@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46276",
"url": "https://lore.kernel.org/linux-cve-announce/2026060839-CVE-2026-46276-1e60@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46277",
"url": "https://lore.kernel.org/linux-cve-announce/2026060841-CVE-2026-46277-f398@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46278",
"url": "https://lore.kernel.org/linux-cve-announce/2026060841-CVE-2026-46278-96c5@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46279",
"url": "https://lore.kernel.org/linux-cve-announce/2026060841-CVE-2026-46279-dc4a@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46280",
"url": "https://lore.kernel.org/linux-cve-announce/2026060841-CVE-2026-46280-13e3@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46281",
"url": "https://lore.kernel.org/linux-cve-announce/2026060842-CVE-2026-46281-60c8@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46282",
"url": "https://lore.kernel.org/linux-cve-announce/2026060842-CVE-2026-46282-f087@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46283",
"url": "https://lore.kernel.org/linux-cve-announce/2026060842-CVE-2026-46283-5142@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46284",
"url": "https://lore.kernel.org/linux-cve-announce/2026060842-CVE-2026-46284-229a@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46285",
"url": "https://lore.kernel.org/linux-cve-announce/2026060843-CVE-2026-46285-0239@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46286",
"url": "https://lore.kernel.org/linux-cve-announce/2026060843-CVE-2026-46286-b3d1@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46287",
"url": "https://lore.kernel.org/linux-cve-announce/2026060843-CVE-2026-46287-750d@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46288",
"url": "https://lore.kernel.org/linux-cve-announce/2026060844-CVE-2026-46288-76f3@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46289",
"url": "https://lore.kernel.org/linux-cve-announce/2026060856-CVE-2026-46289-1b28@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46290",
"url": "https://lore.kernel.org/linux-cve-announce/2026060856-CVE-2026-46290-18bf@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46291",
"url": "https://lore.kernel.org/linux-cve-announce/2026060857-CVE-2026-46291-cb3d@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46292",
"url": "https://lore.kernel.org/linux-cve-announce/2026060857-CVE-2026-46292-92c0@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46293",
"url": "https://lore.kernel.org/linux-cve-announce/2026060857-CVE-2026-46293-b59c@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46294",
"url": "https://lore.kernel.org/linux-cve-announce/2026060857-CVE-2026-46294-dcc8@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46295",
"url": "https://lore.kernel.org/linux-cve-announce/2026060858-CVE-2026-46295-a5d0@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46296",
"url": "https://lore.kernel.org/linux-cve-announce/2026060858-CVE-2026-46296-1408@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46297",
"url": "https://lore.kernel.org/linux-cve-announce/2026060858-CVE-2026-46297-975a@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46298",
"url": "https://lore.kernel.org/linux-cve-announce/2026060859-CVE-2026-46298-67ca@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46299",
"url": "https://lore.kernel.org/linux-cve-announce/2026060859-CVE-2026-46299-d660@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46301",
"url": "https://lore.kernel.org/linux-cve-announce/2026060859-CVE-2026-46301-5988@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46302",
"url": "https://lore.kernel.org/linux-cve-announce/2026060859-CVE-2026-46302-fd95@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46303",
"url": "https://lore.kernel.org/linux-cve-announce/2026060859-CVE-2026-46303-d951@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46304",
"url": "https://lore.kernel.org/linux-cve-announce/2026060800-CVE-2026-46304-be50@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46305",
"url": "https://lore.kernel.org/linux-cve-announce/2026060800-CVE-2026-46305-d3f2@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46306",
"url": "https://lore.kernel.org/linux-cve-announce/2026060800-CVE-2026-46306-503c@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46307",
"url": "https://lore.kernel.org/linux-cve-announce/2026060800-CVE-2026-46307-9ef9@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46308",
"url": "https://lore.kernel.org/linux-cve-announce/2026060801-CVE-2026-46308-d902@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46309",
"url": "https://lore.kernel.org/linux-cve-announce/2026060852-CVE-2026-46309-7f6b@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46310",
"url": "https://lore.kernel.org/linux-cve-announce/2026060852-CVE-2026-46310-5267@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46311",
"url": "https://lore.kernel.org/linux-cve-announce/2026060853-CVE-2026-46311-bf08@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46312",
"url": "https://lore.kernel.org/linux-cve-announce/2026060853-CVE-2026-46312-a367@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46313",
"url": "https://lore.kernel.org/linux-cve-announce/2026060853-CVE-2026-46313-a890@gregkh/"
},
{
"category": "external",
"summary": "Linux Kernel CVE Announcement CVE-2026-46314",
"url": "https://lore.kernel.org/linux-cve-announce/2026060854-CVE-2026-46314-2b40@gregkh/"
},
{
"category": "external",
"summary": "openSUSE Security Update OPENSUSE-SU-2026:11014-1 vom 2026-06-14",
"url": "https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/GUIIWLNGS7XPMWTUD7QE4YLQY7U22IJE/"
}
],
"source_lang": "en-US",
"title": "Linux Kernel: Mehrere Schwachstellen erm\u00f6glichen Denial of Service",
"tracking": {
"current_release_date": "2026-06-14T22:00:00.000+00:00",
"generator": {
"date": "2026-06-15T07:40:20.412+00:00",
"engine": {
"name": "BSI-WID",
"version": "1.6.0"
}
},
"id": "WID-SEC-W-2026-1827",
"initial_release_date": "2026-06-08T22:00:00.000+00:00",
"revision_history": [
{
"date": "2026-06-08T22:00:00.000+00:00",
"number": "1",
"summary": "Initiale Fassung"
},
{
"date": "2026-06-14T22:00:00.000+00:00",
"number": "2",
"summary": "Neue Updates von openSUSE aufgenommen"
}
],
"status": "final",
"version": "2"
}
},
"product_tree": {
"branches": [
{
"branches": [
{
"category": "product_name",
"name": "Open Source Linux Kernel",
"product": {
"name": "Open Source Linux Kernel",
"product_id": "T035270",
"product_identification_helper": {
"cpe": "cpe:/o:linux:linux_kernel:-"
}
}
}
],
"category": "vendor",
"name": "Open Source"
},
{
"branches": [
{
"category": "product_name",
"name": "SUSE openSUSE",
"product": {
"name": "SUSE openSUSE",
"product_id": "T027843",
"product_identification_helper": {
"cpe": "cpe:/o:suse:opensuse:-"
}
}
}
],
"category": "vendor",
"name": "SUSE"
}
]
},
"vulnerabilities": [
{
"cve": "CVE-2025-71315",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2025-71315"
},
{
"cve": "CVE-2026-46274",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46274"
},
{
"cve": "CVE-2026-46275",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46275"
},
{
"cve": "CVE-2026-46276",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46276"
},
{
"cve": "CVE-2026-46277",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46277"
},
{
"cve": "CVE-2026-46278",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46278"
},
{
"cve": "CVE-2026-46279",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46279"
},
{
"cve": "CVE-2026-46280",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46280"
},
{
"cve": "CVE-2026-46281",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46281"
},
{
"cve": "CVE-2026-46282",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46282"
},
{
"cve": "CVE-2026-46283",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46283"
},
{
"cve": "CVE-2026-46284",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46284"
},
{
"cve": "CVE-2026-46285",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46285"
},
{
"cve": "CVE-2026-46286",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46286"
},
{
"cve": "CVE-2026-46287",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46287"
},
{
"cve": "CVE-2026-46288",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46288"
},
{
"cve": "CVE-2026-46289",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46289"
},
{
"cve": "CVE-2026-46290",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46290"
},
{
"cve": "CVE-2026-46291",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46291"
},
{
"cve": "CVE-2026-46292",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46292"
},
{
"cve": "CVE-2026-46293",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46293"
},
{
"cve": "CVE-2026-46294",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46294"
},
{
"cve": "CVE-2026-46295",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46295"
},
{
"cve": "CVE-2026-46296",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46296"
},
{
"cve": "CVE-2026-46297",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46297"
},
{
"cve": "CVE-2026-46298",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46298"
},
{
"cve": "CVE-2026-46299",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46299"
},
{
"cve": "CVE-2026-46301",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46301"
},
{
"cve": "CVE-2026-46302",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46302"
},
{
"cve": "CVE-2026-46303",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46303"
},
{
"cve": "CVE-2026-46304",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46304"
},
{
"cve": "CVE-2026-46305",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46305"
},
{
"cve": "CVE-2026-46306",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46306"
},
{
"cve": "CVE-2026-46307",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46307"
},
{
"cve": "CVE-2026-46308",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46308"
},
{
"cve": "CVE-2026-46309",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46309"
},
{
"cve": "CVE-2026-46310",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46310"
},
{
"cve": "CVE-2026-46311",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46311"
},
{
"cve": "CVE-2026-46312",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46312"
},
{
"cve": "CVE-2026-46313",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46313"
},
{
"cve": "CVE-2026-46314",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46314"
},
{
"cve": "CVE-2026-46315",
"product_status": {
"known_affected": [
"T035270",
"T027843"
]
},
"release_date": "2026-06-08T22:00:00.000+00:00",
"title": "CVE-2026-46315"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.