Skip to main content
VulnerabilityPublished

CVE-2026-99428: Linux kernel · ocfs2: snapshot dentry names in file and setattr traces

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in f976692490bbdf670d4cc241b8951c8cfddb1583 : update Linux kernel when convenient.

Data as of 19 Nov 2026, 14:49 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in f976692490bbdf670d4cc241b8951c8cfddb1583, d2052367cbdad321d131e6280f41c4be5a1b5c96, 84908981fbda3c133b60e75568d853d3191f9fb2 +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade Linux kernel to f976692490bbdf670d4cc241b8951c8cfddb1583, d2052367cbdad321d131e6280f41c4be5a1b5c96, 84908981fbda3c133b60e75568d853d3191f9fb2 or 8cd3ff30659775a6831c66687a69d2b83d163591.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 468eedde23d6c9335935773f4f5764267d5a7763, < f976692490bbdf670d4cc241b8951c8cfddb1583
Fixed in
  • f976692490bbdf670d4cc241b8951c8cfddb1583
LinuxLinuxAffected
  • ≥ 468eedde23d6c9335935773f4f5764267d5a7763, < d2052367cbdad321d131e6280f41c4be5a1b5c96
Fixed in
  • d2052367cbdad321d131e6280f41c4be5a1b5c96
LinuxLinuxAffected
  • ≥ 468eedde23d6c9335935773f4f5764267d5a7763, < 84908981fbda3c133b60e75568d853d3191f9fb2
Fixed in
  • 84908981fbda3c133b60e75568d853d3191f9fb2
LinuxLinuxAffected
  • ≥ 468eedde23d6c9335935773f4f5764267d5a7763, < 8cd3ff30659775a6831c66687a69d2b83d163591
Fixed in
  • 8cd3ff30659775a6831c66687a69d2b83d163591
LinuxLinuxAffected
  • =2.6.39
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: ocfs2: snapshot dentry names in file and setattr traces Patch series "ocfs2: stabilize dentry names in file and setattr traces", v4. Snapshot names at all six users of ocfs2__file_ops and at the separate setattr event. Patch 1 handles the five ordinary file-operation callers and setattr. Patch 2 handles release separately to preserve its locked open-count sample and take the snapshot outside that critical section. The release explanation distinguishes its existing RCU lifetime coverage from name/length consistency. It does not claim that the ordinary callers' external-name UAF interleaving crosses the held inode spinlock. The release source change is unchanged from v3. Patch 1 also removes the read callback's redundant NULL-inode check. The two patches apply independently and leave trace formats unchanged. This patch (of 2): The open, fsync, read, write and splice-read trace calls pass the live dentry name and length to the shared ocfs2__file_ops event class. ocfs2_setattr() passes the same unprotected arguments to its own event. Both events size and copy a __string field separately. A reference to the dentry does not pin the external storage backing an individual name. With an event enabled, a caller can be preempted after loading the name pointer. A long-to-short rename can then replace the name and reclaim its old external allocation before the trace callback sizes or copies it, provided no other snapshot retains that allocation. The setattr inode lock does not exclude every rename: a same-directory rename of a source directory need not take that directory's inode lock. It can therefore change the dentry name while setattr records its event. Inline names and separately loaded lengths can also change during trace record sizing and copying. Take a dentry name snapshot around each of these six trace calls and pass both the string and length from the snapshot. Check event enablement before taking a snapshot. Keep the event classes and formats unchanged. Also remove the redundant NULL-inode check in the read callback. file_inode() returns the open file's inode, which is already used by the trace call above the check. The historical report below is from the read path. KASAN report as below: BUG: KASAN: slab-use-after-free in strlen+0x85/0xa0 Read of size 1 at addr ffff88810a5b2b18 by task python3/496 [CPU and host details omitted.] Call Trace: <TASK> dump_stack_lvl+0x93/0xd0 print_report+0xce/0x630 ? strlen+0x85/0xa0 ? srso_alias_return_thunk+0x5/0xfbef5 ? __virt_addr_valid+0x20e/0x420 ? strlen+0x85/0xa0 kasan_report+0xe0/0x110 ? strlen+0x85/0xa0 strlen+0x85/0xa0 trace_event_raw_event_ocfs2__file_ops+0xf0/0x480 ? __pfx_trace_event_raw_event_ocfs2__file_ops+0x10/0x10 ? srso_alias_return_thunk+0x5/0xfbef5 ? pmbd_probe_hit_cookie+0xe7/0x1c0 ? srso_alias_return_thunk+0x5/0xfbef5 ? __pfx_pmbd_probe_hit_cookie+0x10/0x10 ocfs2_file_read_iter+0x6cd/0xb30 ? __pfx_ocfs2_file_read_iter+0x10/0x10 ? selinux_file_permission+0x11d/0x540 ? srso_alias_return_thunk+0x5/0xfbef5 ? security_file_permission+0x26/0x80 vfs_read+0x7d2/0xc20 ? __pfx_vfs_read+0x10/0x10 ? srso_alias_return_thunk+0x5/0xfbef5 ? __pfx_do_sys_openat2+0x10/0x10 ksys_read+0x111/0x200 ? __pfx_ksys_read+0x10/0x10 ? irqentry_exit+0xbe/0x820 ? srso_alias_return_thunk+0x5/0xfbef5 ? trace_hardirqs_on_prepare+0x11d/0x150 ? srso_alias_return_thunk+0x5/0xfbef5 do_syscall_64+0x114/0x620 entry_SYSCALL_64_after_hwframe+0x77/0x7f [User register dump omitted.] </TASK> Allocated by task 489: kasan_save_stack+0x33/0x60 kasan_save_track+0x14/0x30 __kasan_kmalloc+0xaa/0xb0 __kmalloc_noprof+0x2de/0x780 __d_alloc+0x5fc/0x8c0 d_alloc_parallel+0x106/0x11d0 lookup_open+0x3ff/0 ---truncated---

References

Community reviews

Loading reviews…