BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2022-49846High confidence

udf: Fix a slab-out-of-bounds write bug in udf_find_entry()

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.24% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

6 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.0.10-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.0.10-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.0.10-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.0.10-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2022-49846 · CSAF 2.0 · revision 63 · interimSUSE Product Security TeamCVE-2022-49846
134 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-source as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
Summary
In the Linux kernel, the following vulnerability has been resolved: udf: Fix a slab-out-of-bounds write bug in udf_find_entry() Syzbot reported a slab-out-of-bounds Write bug: loop0: detected capacity change from 0 to 2048 ================================================================== BUG: KASAN: slab-out-of-bounds in udf_find_entry+0x8a5/0x14f0 fs/udf/namei.c:253 Write of size 105 at addr ffff8880123ff896 by task syz-executor323/3610 CPU: 0 PID: 3610 Comm: syz-executor323 Not tainted 6.1.0-rc2-syzkaller-00105-gb229b6ca5abb #0 Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106 print_address_description+0x74/0x340 mm/kasan/report.c:284 print_report+0x107/0x1f0 mm/kasan/report.c:395 kasan_report+0xcd/0x100 mm/kasan/report.c:495 kasan_check_range+0x2a7/0x2e0 mm/kasan/generic.c:189 memcpy+0x3c/0x60 mm/kasan/shadow.c:66 udf_find_entry+0x8a5/0x14f0 fs/udf/namei.c:253 udf_lookup+0xef/0x340 fs/udf/namei.c:309 lookup_open fs/namei.c:3391 [inline] open_last_lookups fs/namei.c:3481 [inline] path_openat+0x10e6/0x2df0 fs/namei.c:3710 do_filp_open+0x264/0x4f0 fs/namei.c:3740 do_sys_openat2+0x124/0x4e0 fs/open.c:1310 do_sys_open fs/open.c:1326 [inline] __do_sys_creat fs/open.c:1402 [inline] __se_sys_creat fs/open.c:1396 [inline] __x64_sys_creat+0x11f/0x160 fs/open.c:1396 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 RIP: 0033:0x7ffab0d164d9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffe1a7e6bb8 EFLAGS: 00000246 ORIG_RAX: 0000000000000055 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007ffab0d164d9 RDX: 00007ffab0d164d9 RSI: 0000000000000000 RDI: 0000000020000180 RBP: 00007ffab0cd5a10 R08: 0000000000000000 R09: 0000000000000000 R10: 00005555573552c0 R11: 0000000000000246 R12: 00007ffab0cd5aa0 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 Allocated by task 3610: kasan_save_stack mm/kasan/common.c:45 [inline] kasan_set_track+0x3d/0x60 mm/kasan/common.c:52 ____kasan_kmalloc mm/kasan/common.c:371 [inline] __kasan_kmalloc+0x97/0xb0 mm/kasan/common.c:380 kmalloc include/linux/slab.h:576 [inline] udf_find_entry+0x7b6/0x14f0 fs/udf/namei.c:243 udf_lookup+0xef/0x340 fs/udf/namei.c:309 lookup_open fs/namei.c:3391 [inline] open_last_lookups fs/namei.c:3481 [inline] path_openat+0x10e6/0x2df0 fs/namei.c:3710 do_filp_open+0x264/0x4f0 fs/namei.c:3740 do_sys_openat2+0x124/0x4e0 fs/open.c:1310 do_sys_open fs/open.c:1326 [inline] __do_sys_creat fs/open.c:1402 [inline] __se_sys_creat fs/open.c:1396 [inline] __x64_sys_creat+0x11f/0x160 fs/open.c:1396 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 The buggy address belongs to the object at ffff8880123ff800 which belongs to the cache kmalloc-256 of size 256 The buggy address is located 150 bytes inside of 256-byte region [ffff8880123ff800, ffff8880123ff900) The buggy address belongs to the physical page: page:ffffea000048ff80 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x123fe head:ffffea000048ff80 order:1 compound_mapcount:0 compound_pincount:0 flags: 0xfff00000010200(slab|head|node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000010200 ffffea00004b8500 dead000000000003 ffff888012041b40 raw: 0000000000000000 0000000080100010 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected page_owner tracks the page as allocated page last allocated via order 0, migratetype Unmovable, gfp_mask 0x0(), pid 1, tgid 1 (swapper/0), ts 1841222404, free_ts 0 create_dummy_stack mm/page_owner.c: ---truncated---
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-12915

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: udf: Fix a slab-out-of-bounds write bug in udf_find_entry() Syzbot reported a slab-out-of-bounds Write bug: loop0: detected capacity change from 0 to 2048 ================================================================== BUG: KASAN: slab-out-of-bounds in udf_find_entry+0x8a5/0x14f0 fs/udf/namei.c:253 Write of size 105 at addr ffff8880123ff896 by task syz-executor323/3610 CPU: 0 PID: 3610 Comm: syz-executor323 Not tainted 6.1.0-rc2-syzkaller-00105-gb229b6ca5abb #0 Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106 print_address_description+0x74/0x340 mm/kasan/report.c:284 print_report+0x107/0x1f0 mm/kasan/report.c:395 kasan_report+0xcd/0x100 mm/kasan/report.c:495 kasan_check_range+0x2a7/0x2e0 mm/kasan/generic.c:189 memcpy+0x3c/0x60 mm/kasan/shadow.c:66 udf_find_entry+0x8a5/0x14f0 fs/udf/namei.c:253 udf_lookup+0xef/0x340 fs/udf/namei.c:309 lookup_open fs/namei.c:3391 [inline] open_last_lookups fs/namei.c:3481 [inline] path_openat+0x10e6/0x2df0 fs/namei.c:3710 do_filp_open+0x264/0x4f0 fs/namei.c:3740 do_sys_openat2+0x124/0x4e0 fs/open.c:1310 do_sys_open fs/open.c:1326 [inline] __do_sys_creat fs/open.c:1402 [inline] __se_sys_creat fs/open.c:1396 [inline] __x64_sys_creat+0x11f/0x160 fs/open.c:1396 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 RIP: 0033:0x7ffab0d164d9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffe1a7e6bb8 EFLAGS: 00000246 ORIG_RAX: 0000000000000055 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007ffab0d164d9 RDX: 00007ffab0d164d9 RSI: 0000000000000000 RDI: 0000000020000180 RBP: 00007ffab0cd5a10 R08: 0000000000000000 R09: 0000000000000000 R10: 00005555573552c0 R11: 0000000000000246 R12: 00007ffab0cd5aa0 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 </TASK> Allocated by task 3610: kasan_save_stack mm/kasan/common.c:45 [inline] kasan_set_track+0x3d/0x60 mm/kasan/common.c:52 ____kasan_kmalloc mm/kasan/common.c:371 [inline] __kasan_kmalloc+0x97/0xb0 mm/kasan/common.c:380 kmalloc include/linux/slab.h:576 [inline] udf_find_entry+0x7b6/0x14f0 fs/udf/namei.c:243 udf_lookup+0xef/0x340 fs/udf/namei.c:309 lookup_open fs/namei.c:3391 [inline] open_last_lookups fs/namei.c:3481 [inline] path_openat+0x10e6/0x2df0 fs/namei.c:3710 do_filp_open+0x264/0x4f0 fs/namei.c:3740 do_sys_openat2+0x124/0x4e0 fs/open.c:1310 do_sys_open fs/open.c:1326 [inline] __do_sys_creat fs/open.c:1402 [inline] __se_sys_creat fs/open.c:1396 [inline] __x64_sys_creat+0x11f/0x160 fs/open.c:1396 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 The buggy address belongs to the object at ffff8880123ff800 which belongs to the cache kmalloc-256 of size 256 The buggy address is located 150 bytes inside of 256-byte region [ffff8880123ff800, ffff8880123ff900) The buggy address belongs to the physical page: page:ffffea000048ff80 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x123fe head:ffffea000048ff80 order:1 compound_mapcount:0 compound_pincount:0 flags: 0xfff00000010200(slab|head|node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000010200 ffffea00004b8500 dead000000000003 ffff888012041b40 raw: 0000000000000000 0000000080100010 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected page_owner tracks the page as allocated page last allocated via order 0, migratetype Unmovable, gfp_mask 0x0(), pid 1, tgid 1 (swapper/0), ts 1841222404, free_ts 0 create_dummy_stack mm/page_owner.c: ---truncated---

What

In the Linux kernel, the following vulnerability has been resolved: udf: Fix a slab-out-of-bounds write bug in udf_find_entry() Syzbot reported a slab-out-of-bounds Write bug: loop0: detected capacity change from 0 to 2048 ================================================================== BUG: KASAN: slab-out-of-bounds in udf_find_entry+0x8a5/0x14f0 fs/udf/namei.c:253 Write of size 105 at addr ffff8880123ff896 by task syz-executor323/3610 CPU: 0 PID: 3610 Comm: syz-executor323 Not tainted 6.1.0-rc2-syzkaller-00105-gb229b6ca5abb #0 Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106 print_address_description+0x74/0x340 mm/kasan/report.c:284 print_report+0x107/0x1f0 mm/kasan/report.c:395 kasan_report+0xcd/0x100 mm/kasan/report.c:495 kasan_check_range+0x2a7/0x2e0 mm/kasan/generic.c:189 memcpy+0x3c/0x60 mm/kasan/shadow.c:66 udf_find_entry+0x8a5/0x14f0 fs/udf/namei.c:253 udf_lookup+0xef/0x340 fs/udf/namei.c:309 lookup_open fs/namei.c:3391 [inline] open_last_lookups fs/namei.c:3481 [inline] path_openat+0x10e6/0x2df0 fs/namei.c:3710 do_filp_open+0x264/0x4f0 fs/namei.c:3740 do_sys_openat2+0x124/0x4e0 fs/open.c:1310 do_sys_open fs/open.c:1326 [inline] __do_sys_creat fs/open.c:1402 [inline] __se_sys_creat fs/open.c:1396 [inline] __x64_sys_creat+0x11f/0x160 fs/open.c:1396 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 RIP: 0033:0x7ffab0d164d9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffe1a7e6bb8 EFLAGS: 00000246 ORIG_RAX: 0000000000000055 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007ffab0d164d9 RDX: 00007ffab0d164d9 RSI: 0000000000000000 RDI: 0000000020000180 RBP: 00007ffab0cd5a10 R08: 0000000000000000 R09: 0000000000000000 R10: 00005555573552c0 R11: 0000000000000246 R12: 00007ffab0cd5aa0 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 </TASK> Allocated by task 3610: kasan_save_stack mm/kasan/common.c:45 [inline] kasan_set_track+0x3d/0x60 mm/kasan/common.c:52 ____kasan_kmalloc mm/kasan/common.c:371 [inline] __kasan_kmalloc+0x97/0xb0 mm/kasan/common.c:380 kmalloc include/linux/slab.h:576 [inline] udf_find_entry+0x7b6/0x14f0 fs/udf/namei.c:243 udf_lookup+0xef/0x340 fs/udf/namei.c:309 lookup_open fs/namei.c:3391 [inline] open_last_lookups fs/namei.c:3481 [inline] path_openat+0x10e6/0x2df0 fs/namei.c:3710 do_filp_open+0x264/0x4f0 fs/namei.c:3740 do_sys_openat2+0x124/0x4e0 fs/open.c:1310 do_sys_open fs/open.c:1326 [inline] __do_sys_creat fs/open.c:1402 [inline] __se_sys_creat fs/open.c:1396 [inline] __x64_sys_creat+0x11f/0x160 fs/open.c:1396 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 The buggy address belongs to the object at ffff8880123ff800 which belongs to the cache kmalloc-256 of size 256 The buggy address is located 150 bytes inside of 256-byte region [ffff8880123ff800, ffff8880123ff900) The buggy address belongs to the physical page: page:ffffea000048ff80 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x123fe head:ffffea000048ff80 order:1 compound_mapcount:0 compound_pincount:0 flags: 0xfff00000010200(slab|head|node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000010200 ffffea00004b8500 dead000000000003 ffff888012041b40 raw: 0000000000000000 0000000080100010 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected page_owner tracks the page as allocated page last allocated via order 0, migratetype Unmovable, gfp_mask 0x0(), pid 1, tgid 1 (swapper/0), ts 1841222404, free_ts 0 create_dummy_stack mm/page_owner.c: ---truncated---

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: udf: Fix a slab-out-of-bounds write bug in udf_find_entry() Syzbot reported a slab-out-of-bounds Write bug: loop0: detected capacity change from 0 to 2048 ================================================================== BUG: KASAN: slab-out-of-bounds in udf_find_entry+0x8a5/0x14f0 fs/udf/namei.c:253 Write of size 105 at addr ffff8880123ff896 by task syz-executor323/3610 CPU: 0 PID: 3610 Comm: syz-executor323 Not tainted 6.1.0-rc2-syzkaller-00105-gb229b6ca5abb #0 Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106 print_address_description+0x74/0x340 mm/kasan/report.c:284 print_report+0x107/0x1f0 mm/kasan/report.c:395 kasan_report+0xcd/0x100 mm/kasan/report.c:495 kasan_check_range+0x2a7/0x2e0 mm/kasan/generic.c:189 memcpy+0x3c/0x60 mm/kasan/shadow.c:66 udf_find_entry+0x8a5/0x14f0 fs/udf/namei.c:253 udf_lookup+0xef/0x340 fs/udf/namei.c:309 lookup_open fs/namei.c:3391 [inline] open_last_lookups fs/namei.c:3481 [inline] path_openat+0x10e6/0x2df0 fs/namei.c:3710 do_filp_open+0x264/0x4f0 fs/namei.c:3740 do_sys_openat2+0x124/0x4e0 fs/open.c:1310 do_sys_open fs/open.c:1326 [inline] __do_sys_creat fs/open.c:1402 [inline] __se_sys_creat fs/open.c:1396 [inline] __x64_sys_creat+0x11f/0x160 fs/open.c:1396 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 RIP: 0033:0x7ffab0d164d9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffe1a7e6bb8 EFLAGS: 00000246 ORIG_RAX: 0000000000000055 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007ffab0d164d9 RDX: 00007ffab0d164d9 RSI: 0000000000000000 RDI: 0000000020000180 RBP: 00007ffab0cd5a10 R08: 0000000000000000 R09: 0000000000000000 R10: 00005555573552c0 R11: 0000000000000246 R12: 00007ffab0cd5aa0 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 </TASK> Allocated by task 3610: kasan_save_stack mm/kasan/common.c:45 [inline] kasan_set_track+0x3d/0x60 mm/kasan/common.c:52 ____kasan_kmalloc mm/kasan/common.c:371 [inline] __kasan_kmalloc+0x97/0xb0 mm/kasan/common.c:380 kmalloc include/linux/slab.h:576 [inline] udf_find_entry+0x7b6/0x14f0 fs/udf/namei.c:243 udf_lookup+0xef/0x340 fs/udf/namei.c:309 lookup_open fs/namei.c:3391 [inline] open_last_lookups fs/namei.c:3481 [inline] path_openat+0x10e6/0x2df0 fs/namei.c:3710 do_filp_open+0x264/0x4f0 fs/namei.c:3740 do_sys_openat2+0x124/0x4e0 fs/open.c:1310 do_sys_open fs/open.c:1326 [inline] __do_sys_creat fs/open.c:1402 [inline] __se_sys_creat fs/open.c:1396 [inline] __x64_sys_creat+0x11f/0x160 fs/open.c:1396 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 The buggy address belongs to the object at ffff8880123ff800 which belongs to the cache kmalloc-256 of size 256 The buggy address is located 150 bytes inside of 256-byte region [ffff8880123ff800, ffff8880123ff900) The buggy address belongs to the physical page: page:ffffea000048ff80 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x123fe head:ffffea000048ff80 order:1 compound_mapcount:0 compound_pincount:0 flags: 0xfff00000010200(slab|head|node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000010200 ffffea00004b8500 dead000000000003 ffff888012041b40 raw: 0000000000000000 0000000080100010 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected page_owner tracks the page as allocated page last allocated via order 0, migratetype Unmovable, gfp_mask 0x0(), pid 1, tgid 1 (swapper/0), ts 1841222404, free_ts 0 create_dummy_stack mm/page_owner.c: ---truncated---

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Out-of-bounds Write → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-787 ↗

CWE-787: Out-of-bounds Write. The product writes data past the end, or before the beginning, of the intended buffer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-787
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2025-1905IBM QRadar SIEM Komponente: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM Komponenten ausnutzen, um Daten zu manipulieren, um einen Denial of Service Angriff durchzuführen, um beliebigen Programmcode auszuführen, um Sicherheitsvorkehrungen zu umgehen, und um Informationen offenzulegen.

Official advisory ↗
BSI · German · WID-SEC-2025-1549Linux Kernel: Schwachstelle ermöglicht Privilegieneskalation und DoS

Ein lokaler Angreifer kann eine Schwachstelle in Linux Kernel und Red Hat Enterprise Linux ausnutzen, um seine Privilegien zu erhöhen oder einen Denial of Service zu verursachen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250507Security Bulletin 07 May 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 07 May 2025, published on 7 May 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0081Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49830 Référence CVE CVE-2022-49832 https://www.cve.org/CVERecord?id=CVE-2022-49832 Référence CVE CVE-2022-49834 https://www.cve.org/CVERecord?id=CVE-2022-49834 Référence CVE CVE-2022-49835 https://www.cve.org/CVERecord?id=CVE-2022-49835 Référence CVE CVE-2022-49836 https://www.cve.org/CVERecord?id=CVE-2022-49836 Référence CVE CVE-2022-49839 https://www.cve.org/CVERecord?id=CVE-2022-49839 Référence CVE CVE-2022-49841 https://www.cve.org/CVERecord?id=CVE-2022-49841 Référence CVE CVE-2022-49842 https://www.cve.org/CVERecord?id=CVE-2022-49842 Référence CVE CVE-2022-49845 https://www.cve.org/CVERecord?id=CVE-2022-49845 Référence CVE CVE-2022-49846 https://www.cve.org/CVERecord?id=CVE-2022-49846 Référence CVE CVE-2022-49850 https://www.cve.org/CVERecord?id=CVE-2022-49850 Référence CVE CVE-2022-49853 https://www.cve.org/CVERecord?id=CVE-2022-49853 Référence CVE CVE-2022-49858 https://www.cve.org/CVERecord?id=CVE-2022-49858 Référence CVE CVE-2022-49860 https://www.cve.org/CVERecord?id=CVE-2022-49860 Référence CVE CVE-2022-49861 https://www.cve.org/CVERecord?id=CVE-2022-49861 Référence CVE CVE-2022-49863 https://www.cve.org/CVERecord?id=CVE-2022-49863 Référence CVE CVE-2022-49864 https://www.cve.org/CVERecord?id=CVE-2022-49864 Référence CVE CVE-2022-49865 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1009Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49832 Référence CVE CVE-2022-49834 https://www.cve.org/CVERecord?id=CVE-2022-49834 Référence CVE CVE-2022-49835 https://www.cve.org/CVERecord?id=CVE-2022-49835 Référence CVE CVE-2022-49836 https://www.cve.org/CVERecord?id=CVE-2022-49836 Référence CVE CVE-2022-49837 https://www.cve.org/CVERecord?id=CVE-2022-49837 Référence CVE CVE-2022-49839 https://www.cve.org/CVERecord?id=CVE-2022-49839 Référence CVE CVE-2022-49841 https://www.cve.org/CVERecord?id=CVE-2022-49841 Référence CVE CVE-2022-49842 https://www.cve.org/CVERecord?id=CVE-2022-49842 Référence CVE CVE-2022-49845 https://www.cve.org/CVERecord?id=CVE-2022-49845 Référence CVE CVE-2022-49846 https://www.cve.org/CVERecord?id=CVE-2022-49846 Référence CVE CVE-2022-49850 https://www.cve.org/CVERecord?id=CVE-2022-49850 Référence CVE CVE-2022-49853 https://www.cve.org/CVERecord?id=CVE-2022-49853 Référence CVE CVE-2022-49858 https://www.cve.org/CVERecord?id=CVE-2022-49858 Référence CVE CVE-2022-49860 https://www.cve.org/CVERecord?id=CVE-2022-49860 Référence CVE CVE-2022-49861 https://www.cve.org/CVERecord?id=CVE-2022-49861 Référence CVE CVE-2022-49863 https://www.cve.org/CVERecord?id=CVE-2022-49863 Référence CVE CVE-2022-49864 https://www.cve.org/CVERecord?id=CVE-2022-49864 Référence CVE CVE-2022-49865 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0760Multiples vulnérabilités dans les produits IBM

CVERecord?id=CVE-2022-24823 Référence CVE CVE-2022-2625 https://www.cve.org/CVERecord?id=CVE-2022-2625 Référence CVE CVE-2022-31129 https://www.cve.org/CVERecord?id=CVE-2022-31129 Référence CVE CVE-2022-3171 https://www.cve.org/CVERecord?id=CVE-2022-3171 Référence CVE CVE-2022-3509 https://www.cve.org/CVERecord?id=CVE-2022-3509 Référence CVE CVE-2022-3510 https://www.cve.org/CVERecord?id=CVE-2022-3510 Référence CVE CVE-2022-36364 https://www.cve.org/CVERecord?id=CVE-2022-36364 Référence CVE CVE-2022-41862 https://www.cve.org/CVERecord?id=CVE-2022-41862 Référence CVE CVE-2022-41881 https://www.cve.org/CVERecord?id=CVE-2022-41881 Référence CVE CVE-2022-49846 https://www.cve.org/CVERecord?id=CVE-2022-49846 Référence CVE CVE-2023-1370 https://www.cve.org/CVERecord?id=CVE-2023-1370 Référence CVE CVE-2023-22467 https://www.cve.org/CVERecord?id=CVE-2023-22467 Référence CVE CVE-2023-2454 https://www.cve.org/CVERecord?id=CVE-2023-2454 Référence CVE CVE-2023-2455 https://www.cve.org/CVERecord?id=CVE-2023-2455 Référence CVE CVE-2023-26133 https://www.cve.org/CVERecord?id=CVE-2023-26133 Référence CVE CVE-2023-2976 https://www.cve.org/CVERecord?id=CVE-2023-2976 Référence CVE CVE-2023-32305 https://www.cve.org/CVERecord?id=CVE-2023-32305 Référence CVE CVE-2023-34462 https://www.cve.org/CVERecord?id=CVE-2023

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0746Multiples vulnérabilités dans les produits IBM

3373 Bulletin de sécurité IBM 7243411 du 28 août 2025 https://www.ibm.com/support/pages/node/7243411 Référence CVE CVE-2019-17543 https://www.cve.org/CVERecord?id=CVE-2019-17543 Référence CVE CVE-2019-5427 https://www.cve.org/CVERecord?id=CVE-2019-5427 Référence CVE CVE-2020-5260 https://www.cve.org/CVERecord?id=CVE-2020-5260 Référence CVE CVE-2022-49058 https://www.cve.org/CVERecord?id=CVE-2022-49058 Référence CVE CVE-2022-49111 https://www.cve.org/CVERecord?id=CVE-2022-49111 Référence CVE CVE-2022-49136 https://www.cve.org/CVERecord?id=CVE-2022-49136 Référence CVE CVE-2022-49788 https://www.cve.org/CVERecord?id=CVE-2022-49788 Référence CVE CVE-2022-49846 https://www.cve.org/CVERecord?id=CVE-2022-49846 Référence CVE CVE-2022-49977 https://www.cve.org/CVERecord?id=CVE-2022-49977 Référence CVE CVE-2022-50020 https://www.cve.org/CVERecord?id=CVE-2022-50020 Référence CVE CVE-2024-10917 https://www.cve.org/CVERecord?id=CVE-2024-10917 Référence CVE CVE-2024-13009 https://www.cve.org/CVERecord?id=CVE-2024-13009 Référence CVE CVE-2024-21131 https://www.cve.org/CVERecord?id=CVE-2024-21131 Référence CVE CVE-2024-21144 https://www.cve.org/CVERecord?id=CVE-2024-21144 Référence CVE CVE-2024-23337 https://www.cve.org/CVERecord?id=CVE-2024-23337 Référence CVE CVE-2024-28956 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0606Multiples vulnérabilités dans le noyau Linux de Red Hat

De multiples vulnérabilités ont été découvertes dans le noyau Linux de Red Hat. Certaines d'entre elles permettent à un attaquant de provoquer une atteinte à la confidentialité des données, une atteinte à l'intégrité des données et un contournement de la politique de sécurité.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0588Multiples vulnérabilités dans le noyau Linux de Red Hat

09 juillet 2025 https://access.redhat.com/errata/RHSA-2025:10673 Bulletin de sécurité Red Hat RHSA-2025:10675 du 09 juillet 2025 https://access.redhat.com/errata/RHSA-2025:10675 Bulletin de sécurité Red Hat RHSA-2025:10701 du 09 juillet 2025 https://access.redhat.com/errata/RHSA-2025:10701 Bulletin de sécurité Red Hat RHSA-2025:10761 du 10 juillet 2025 https://access.redhat.com/errata/RHSA-2025:10761 Référence CVE CVE-2022-49111 https://www.cve.org/CVERecord?id=CVE-2022-49111 Référence CVE CVE-2022-49136 https://www.cve.org/CVERecord?id=CVE-2022-49136 Référence CVE CVE-2022-49395 https://www.cve.org/CVERecord?id=CVE-2022-49395 Référence CVE CVE-2022-49846 https://www.cve.org/CVERecord?id=CVE-2022-49846 Référence CVE CVE-2022-50066 https://www.cve.org/CVERecord?id=CVE-2022-50066 Référence CVE CVE-2023-1652 https://www.cve.org/CVERecord?id=CVE-2023-1652 Référence CVE CVE-2023-52477 https://www.cve.org/CVERecord?id=CVE-2023-52477 Référence CVE CVE-2023-52565 https://www.cve.org/CVERecord?id=CVE-2023-52565 Référence CVE CVE-2023-52595 https://www.cve.org/CVERecord?id=CVE-2023-52595 Référence CVE CVE-2023-52781 https://www.cve.org/CVERecord?id=CVE-2023-52781 Référence CVE CVE-2023-52834 https://www.cve.org/CVERecord?id=CVE-2023-52834 Référence CVE CVE-2023-52933 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0587Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49830 Référence CVE CVE-2022-49832 https://www.cve.org/CVERecord?id=CVE-2022-49832 Référence CVE CVE-2022-49834 https://www.cve.org/CVERecord?id=CVE-2022-49834 Référence CVE CVE-2022-49835 https://www.cve.org/CVERecord?id=CVE-2022-49835 Référence CVE CVE-2022-49836 https://www.cve.org/CVERecord?id=CVE-2022-49836 Référence CVE CVE-2022-49839 https://www.cve.org/CVERecord?id=CVE-2022-49839 Référence CVE CVE-2022-49841 https://www.cve.org/CVERecord?id=CVE-2022-49841 Référence CVE CVE-2022-49842 https://www.cve.org/CVERecord?id=CVE-2022-49842 Référence CVE CVE-2022-49845 https://www.cve.org/CVERecord?id=CVE-2022-49845 Référence CVE CVE-2022-49846 https://www.cve.org/CVERecord?id=CVE-2022-49846 Référence CVE CVE-2022-49850 https://www.cve.org/CVERecord?id=CVE-2022-49850 Référence CVE CVE-2022-49853 https://www.cve.org/CVERecord?id=CVE-2022-49853 Référence CVE CVE-2022-49858 https://www.cve.org/CVERecord?id=CVE-2022-49858 Référence CVE CVE-2022-49860 https://www.cve.org/CVERecord?id=CVE-2022-49860 Référence CVE CVE-2022-49861 https://www.cve.org/CVERecord?id=CVE-2022-49861 Référence CVE CVE-2022-49863 https://www.cve.org/CVERecord?id=CVE-2022-49863 Référence CVE CVE-2022-49864 https://www.cve.org/CVERecord?id=CVE-2022-49864 Référence CVE CVE-2022-49865 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0560Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49832 Référence CVE CVE-2022-49834 https://www.cve.org/CVERecord?id=CVE-2022-49834 Référence CVE CVE-2022-49835 https://www.cve.org/CVERecord?id=CVE-2022-49835 Référence CVE CVE-2022-49836 https://www.cve.org/CVERecord?id=CVE-2022-49836 Référence CVE CVE-2022-49837 https://www.cve.org/CVERecord?id=CVE-2022-49837 Référence CVE CVE-2022-49839 https://www.cve.org/CVERecord?id=CVE-2022-49839 Référence CVE CVE-2022-49841 https://www.cve.org/CVERecord?id=CVE-2022-49841 Référence CVE CVE-2022-49842 https://www.cve.org/CVERecord?id=CVE-2022-49842 Référence CVE CVE-2022-49845 https://www.cve.org/CVERecord?id=CVE-2022-49845 Référence CVE CVE-2022-49846 https://www.cve.org/CVERecord?id=CVE-2022-49846 Référence CVE CVE-2022-49850 https://www.cve.org/CVERecord?id=CVE-2022-49850 Référence CVE CVE-2022-49853 https://www.cve.org/CVERecord?id=CVE-2022-49853 Référence CVE CVE-2022-49858 https://www.cve.org/CVERecord?id=CVE-2022-49858 Référence CVE CVE-2022-49860 https://www.cve.org/CVERecord?id=CVE-2022-49860 Référence CVE CVE-2022-49861 https://www.cve.org/CVERecord?id=CVE-2022-49861 Référence CVE CVE-2022-49863 https://www.cve.org/CVERecord?id=CVE-2022-49863 Référence CVE CVE-2022-49864 https://www.cve.org/CVERecord?id=CVE-2022-49864 Référence CVE CVE-2022-49865 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0529Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49834 Référence CVE CVE-2022-49835 https://www.cve.org/CVERecord?id=CVE-2022-49835 Référence CVE CVE-2022-49836 https://www.cve.org/CVERecord?id=CVE-2022-49836 Référence CVE CVE-2022-49837 https://www.cve.org/CVERecord?id=CVE-2022-49837 Référence CVE CVE-2022-49839 https://www.cve.org/CVERecord?id=CVE-2022-49839 Référence CVE CVE-2022-49840 https://www.cve.org/CVERecord?id=CVE-2022-49840 Référence CVE CVE-2022-49841 https://www.cve.org/CVERecord?id=CVE-2022-49841 Référence CVE CVE-2022-49842 https://www.cve.org/CVERecord?id=CVE-2022-49842 Référence CVE CVE-2022-49845 https://www.cve.org/CVERecord?id=CVE-2022-49845 Référence CVE CVE-2022-49846 https://www.cve.org/CVERecord?id=CVE-2022-49846 Référence CVE CVE-2022-49850 https://www.cve.org/CVERecord?id=CVE-2022-49850 Référence CVE CVE-2022-49853 https://www.cve.org/CVERecord?id=CVE-2022-49853 Référence CVE CVE-2022-49858 https://www.cve.org/CVERecord?id=CVE-2022-49858 Référence CVE CVE-2022-49860 https://www.cve.org/CVERecord?id=CVE-2022-49860 Référence CVE CVE-2022-49861 https://www.cve.org/CVERecord?id=CVE-2022-49861 Référence CVE CVE-2022-49862 https://www.cve.org/CVERecord?id=CVE-2022-49862 Référence CVE CVE-2022-49863 https://www.cve.org/CVERecord?id=CVE-2022-49863 Référence CVE CVE-2022-49864 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0509Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-49830 Référence CVE CVE-2022-49832 https://www.cve.org/CVERecord?id=CVE-2022-49832 Référence CVE CVE-2022-49834 https://www.cve.org/CVERecord?id=CVE-2022-49834 Référence CVE CVE-2022-49835 https://www.cve.org/CVERecord?id=CVE-2022-49835 Référence CVE CVE-2022-49836 https://www.cve.org/CVERecord?id=CVE-2022-49836 Référence CVE CVE-2022-49839 https://www.cve.org/CVERecord?id=CVE-2022-49839 Référence CVE CVE-2022-49841 https://www.cve.org/CVERecord?id=CVE-2022-49841 Référence CVE CVE-2022-49842 https://www.cve.org/CVERecord?id=CVE-2022-49842 Référence CVE CVE-2022-49845 https://www.cve.org/CVERecord?id=CVE-2022-49845 Référence CVE CVE-2022-49846 https://www.cve.org/CVERecord?id=CVE-2022-49846 Référence CVE CVE-2022-49850 https://www.cve.org/CVERecord?id=CVE-2022-49850 Référence CVE CVE-2022-49853 https://www.cve.org/CVERecord?id=CVE-2022-49853 Référence CVE CVE-2022-49858 https://www.cve.org/CVERecord?id=CVE-2022-49858 Référence CVE CVE-2022-49860 https://www.cve.org/CVERecord?id=CVE-2022-49860 Référence CVE CVE-2022-49861 https://www.cve.org/CVERecord?id=CVE-2022-49861 Référence CVE CVE-2022-49863 https://www.cve.org/CVERecord?id=CVE-2022-49863 Référence CVE CVE-2022-49864 https://www.cve.org/CVERecord?id=CVE-2022-49864 Référence CVE CVE-2022-49865 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2022-026136Linux の Linux Kernel における境界外書き込みに関する脆弱性

Linux の Linux Kernel には、境界外書き込みに関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 4.6, 4.9.334 ≤ 4.9.*, 4.14.300 ≤ 4.14.*, 4.19.267 ≤ 4.19.*, 5.4.225 ≤ 5.4.*, 5.10.155 ≤ 5.10.*, 5.15.79 ≤ 5.15.*, 6.0.9 ≤ 6.0.*, 6.1 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 1 May 2025 · Last source change 5 Aug 2026, 08:56 UTC · CWE-787 · Out-of-bounds Write

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-12915
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCISA ADP
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2025-12915↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2022-49846 · cve.blacktree.nl