dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53041

HIGH · 7.1 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 5.10.258 / 5.15.209 or later.
See remediation →
73/100
Remediation priority · Elevated
Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix listxattr handling when the buffer is full [BUG] If an OCFS2 inode has both inline and block-based xattrs, listxattr() can return a size larger than the caller's buffer when the inline names consume that buffer exactly. kernel BUG at mm/usercopy.c:102! Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI RIP: 0010:usercopy_abort+0xb7/0xd0 mm/usercopy.c:102 Call Trace: __check_heap_object+0xe3/0x120 mm/slub.c:8243 check_heap_object mm/usercopy.c:196 [inline] __check_object_size mm/usercopy.c:250 [inline] __check_object_size+0x5c5/0x780 mm/usercopy.c:215 check_object_size include/linux/ucopysize.h:22 [inline] check_copy_size include/linux/ucopysize.h:59 [inline] copy_to_user include/linux/uaccess.h:219 [inline] listxattr+0xb0/0x170 fs/xattr.c:926 filename_listxattr fs/xattr.c:958 [inline] path_listxattrat+0x137/0x320 fs/xattr.c:988 __do_sys_listxattr fs/xattr.c:1001 [inline] __se_sys_listxattr fs/xattr.c:998 [inline] __x64_sys_listxattr+0x7f/0xd0 fs/xattr.c:998 ... [CAUSE] Commit 936b8834366e ("ocfs2: Refactor xattr list and remove ocfs2_xattr_handler().") replaced the old per-handler list accounting with ocfs2_xattr_list_entry(), but it kept using size == 0 to detect probe mode. That assumption stops being true once ocfs2_listxattr() finishes the inline-xattr pass. If the inline names fill the caller buffer exactly, the block-xattr pass runs with a non-NULL buffer and a remaining size of zero. ocfs2_xattr_list_entry() then skips the bounds check, keeps counting block names, and returns a positive size larger than the supplied buffer. [FIX] Detect probe mode by testing whether the destination buffer pointer is NULL instead of whether the remaining size is zero. That restores the pre-refactor behavior and matches the OCFS2 getxattr helpers. Once the remaining buffer reaches zero while more names are left, the block-xattr pass now returns -ERANGE instead of reporting a size larger than the allocated list buffer.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In OCFS2 filesystem, listxattr() can return a size larger than the caller's buffer when inline xattr names fill the buffer exactly, causing a kernel BUG at usercopy.c (invalid opcode). The root cause is that commit 936b8834366e used size == 0 to detect probe mode instead of checking if the buffer pointer is NULL. When inline xattrs consume the entire buffer, the block-xattr pass runs with zero remaining space but a non-NULL buffer, causing ocfs2_xattr_list_entry() to skip bounds checking and return an oversized length.

MitigationApply the kernel patch that changes probe mode detection from checking remaining size to checking for NULL buffer pointer, or update to a kernel version containing this fix.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 2.6.28, < 5.10.258>= 5.11, < 5.15.209>= 5.16, < 6.1.175>= 6.2, < 6.6.141>= 6.7, < 6.12.91>= 6.13, < 6.18.33>= 6.19, < 7.0.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if OCFS2 filesystem is in use
    Check mounted filesystems by running 'mount | grep ocfs2' or 'cat /proc/mounts | grep ocfs2'
    Affected if No OCFS2 filesystems are mounted, the kernel component is not actively used
  2. Check if OCFS2 kernel module is loaded
    Run 'lsmod | grep ocfs2' or check 'cat /sys/module/ocfs2/version' if the module is loaded
    Affected if OCFS2 module is not loaded and OCFS2 is not compiled into the kernel, the vulnerability is not reachable
  3. Determine the running kernel version
    Run 'uname -r' to get the kernel version and compare it against the affected ranges: >= 2.6.28 and < 5.10.258; >= 5.11 and < 5.15.209; >= 5.16 and < 6.1.175; >= 6.2 and < 6.6.141; >= 6.7 and < 6.12.91; >= 6.13 and < 6.18.33; >= 6.19 and < 7.0.10
    Affected if The kernel version falls within any of the affected version ranges and OCFS2 is in use

User is affected if they are running a kernel version within the affected ranges AND have an OCFS2 filesystem mounted or the OCFS2 module loaded, with inline xattrs present that can fill the buffer exactly.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.10.258 / 5.15.209 / 6.1.175 or later
Fixed in 5.10.2585.15.2096.1.175
Interim mitigation

Apply the kernel patch that changes probe mode detection from checking remaining size to checking for NULL buffer pointer, or update to a kernel version containing this fix.

Recommended fix High confidence

Linux kernel >= 5.10.258 (for 5.10.x), >= 5.15.209 (for 5.11-5.15.x), >= 6.1.175 (for 5.16-6.1.x), or >= 6.6.141 (for 6.2-6.6.x) depending on your current branch

  1. Identify the currently running Linux kernel version using `uname -r`
  2. Determine which vulnerable version range your kernel falls into from: >= 2.6.28, < 5.10.258; >= 5.11, < 5.15.209; >= 5.16, < 6.1.175; >= 6.2, < 6.6.141
  3. Upgrade the Linux kernel to a version beyond the applicable threshold for your major version branch
  4. For kernels in the 5.10.x branch, upgrade to >= 5.10.258
  5. For kernels in the 5.11-5.15.x branch, upgrade to >= 5.15.209
  6. For kernels in the 5.16-6.1.x branch, upgrade to >= 6.1.175
  7. For kernels in the 6.2-6.6.x branch, upgrade to >= 6.6.141
  8. Reboot the system to load the patched kernel
Caveat Kernel upgrades may require updates to kernel modules or system configuration; ensure compatibility with installed drivers and software before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53041 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53041 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data