Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-26870: NFSv4.2: fix nfs4_listxattr kernel BUG at mm/usercopy.c:102

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.28% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 06e828b3f1b206de08ef520fc46a40b22e1869cb, 23bfecb4d852751d5e403557dd500bb563313baf, 251a658bbfceafb4d58c76b77682c8bf7bcfad65.
  • Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.

Low priority for now. Upgrade to Linux Linux 06e828b3f1b206de08ef520fc46a40b22e1869cb, 23bfecb4d852751d5e403557dd500bb563313baf, 251a658bbfceafb4d58c76b77682c8bf7bcfad65 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: NFSv4.2: fix nfs4_listxattr kernel BUG at mm/usercopy.c:102 A call to listxattr() with a buffer size = 0 returns the actual size of the buffer needed for a subsequent call. When size > 0, nfs4_listxattr() does not return an error because either generic_listxattr() or nfs4_listxattr_nfs4_label() consumes exactly all the bytes then size is 0 when calling nfs4_listxattr_nfs4_user() which then triggers the following kernel BUG: [ 99.403778] kernel BUG at mm/usercopy.c:102! [ 99.404063] Internal error: Oops - BUG: 00000000f2000800 [#1] SMP [ 99.408463] CPU: 0 PID: 3310 Comm: python3 Not tainted 6.6.0-61.fc40.aarch64 #1 [ 99.415827] Call trace: [ 99.415985] usercopy_abort+0x70/0xa0 [ 99.416227] __check_heap_object+0x134/0x158 [ 99.416505] check_heap_object+0x150/0x188 [ 99.416696] __check_object_size.part.0+0x78/0x168 [ 99.416886] __check_object_size+0x28/0x40 [ 99.417078] listxattr+0x8c/0x120 [ 99.417252] path_listxattr+0x78/0xe0 [ 99.417476] __arm64_sys_listxattr+0x28/0x40 [ 99.417723] invoke_syscall+0x78/0x100 [ 99.417929] el0_svc_common.constprop.0+0x48/0xf0 [ 99.418186] do_el0_svc+0x24/0x38 [ 99.418376] el0_svc+0x3c/0x110 [ 99.418554] el0t_64_sync_handler+0x120/0x130 [ 99.418788] el0t_64_sync+0x194/0x198 [ 99.418994] Code: aa0003e3 d000a3e0 91310000 97f49bdb (d4210000) Issue is reproduced when generic_listxattr() returns 'system.nfs4_acl', thus calling lisxattr() with size = 16 will trigger the bug. Add check on nfs4_listxattr() to return ERANGE error when it is called with size > 0 and the return value is greater than size.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Apr 17, 2024
Updated
Oct 15, 2026
EPSS
0.2% · 20th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · Linux
7.8
2.3 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-26870

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux10.0
  • linux linux kernel5.11 and later · before 5.15.153
  • linux linux kernel5.16 and later · before 6.1.83
  • linux linux kernel5.9 and later · before 5.10.214
  • linux linux kernel6.7 and later · before 6.7.11
  • linux linux kernel6.8 and later · before 6.8.2
  • linux linux kernel6.2 and later · before 6.6.23

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.9affected
    • 012a211abd5db098094ce429de5f046368391e68 and later · before 4403438eaca6e91f02d272211c4d6b045092396baffected · git
    • 012a211abd5db098094ce429de5f046368391e68 and later · before 9d52865ff28245fc2134da9f99baff603a24407aaffected · git
    • 012a211abd5db098094ce429de5f046368391e68 and later · before 06e828b3f1b206de08ef520fc46a40b22e1869cbaffected · git
    • 012a211abd5db098094ce429de5f046368391e68 and later · before 79cdcc765969d23f4e3d6ea115660c3333498768affected · git
    • 012a211abd5db098094ce429de5f046368391e68 and later · before 80365c9f96015bbf048fdd6c8705d3f8770132bfaffected · git
    • 012a211abd5db098094ce429de5f046368391e68 and later · before 23bfecb4d852751d5e403557dd500bb563313bafaffected · git
    • 012a211abd5db098094ce429de5f046368391e68 and later · before 251a658bbfceafb4d58c76b77682c8bf7bcfad65affected · git
    • before 5.9not affected · semver
    • 5.10.214 and later · up to and including 5.10.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.85-16.1.85-1
Debian:13linuxbefore 6.7.12-16.7.12-1
Red Hat:rhel_aus:8.6::baseosbpftoolbefore 0:4.18.0-372.115.1.el8_60:4.18.0-372.115.1.el8_6
Red Hat:rhel_aus:8.6::baseosbpftool-debuginfobefore 0:4.18.0-372.115.1.el8_60:4.18.0-372.115.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernelbefore 0:4.18.0-372.115.1.el8_60:4.18.0-372.115.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-abi-stablelistsbefore 0:4.18.0-372.115.1.el8_60:4.18.0-372.115.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-corebefore 0:4.18.0-372.115.1.el8_60:4.18.0-372.115.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debugbefore 0:4.18.0-372.115.1.el8_60:4.18.0-372.115.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-corebefore 0:4.18.0-372.115.1.el8_60:4.18.0-372.115.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-debuginfobefore 0:4.18.0-372.115.1.el8_60:4.18.0-372.115.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-develbefore 0:4.18.0-372.115.1.el8_60:4.18.0-372.115.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-modulesbefore 0:4.18.0-372.115.1.el8_60:4.18.0-372.115.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-modules-extrabefore 0:4.18.0-372.115.1.el8_60:4.18.0-372.115.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debuginfobefore 0:4.18.0-372.115.1.el8_60:4.18.0-372.115.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debuginfo-common-x86_64before 0:4.18.0-372.115.1.el8_60:4.18.0-372.115.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-develbefore 0:4.18.0-372.115.1.el8_60:4.18.0-372.115.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-docbefore 0:4.18.0-372.115.1.el8_60:4.18.0-372.115.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-modulesbefore 0:4.18.0-372.115.1.el8_60:4.18.0-372.115.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-modules-extrabefore 0:4.18.0-372.115.1.el8_60:4.18.0-372.115.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-toolsbefore 0:4.18.0-372.115.1.el8_60:4.18.0-372.115.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-tools-debuginfobefore 0:4.18.0-372.115.1.el8_60:4.18.0-372.115.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-tools-libsbefore 0:4.18.0-372.115.1.el8_60:4.18.0-372.115.1.el8_6
Red Hat:rhel_aus:8.6::baseosperfbefore 0:4.18.0-372.115.1.el8_60:4.18.0-372.115.1.el8_6
Red Hat:rhel_aus:8.6::baseosperf-debuginfobefore 0:4.18.0-372.115.1.el8_60:4.18.0-372.115.1.el8_6

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-26861Apr 17, 2024 · wireguard: receive: annotate data-race around receiving_counter.counter
    18Monitor
  • ← EarlierCVE-2024-26863Apr 17, 2024 · hsr: Fix uninit-value access in hsr_get_node()
    22Monitor
  • Later →CVE-2024-26872Apr 17, 2024 · RDMA/srpt: Do not register event handler until srpt device is fully setup
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux06e828b3f1b206de08ef520fc46a40b22e1869cbVendor (CNA)
Linux Linux23bfecb4d852751d5e403557dd500bb563313bafVendor (CNA)
Linux Linux251a658bbfceafb4d58c76b77682c8bf7bcfad65Vendor (CNA)
Linux Linux4403438eaca6e91f02d272211c4d6b045092396bVendor (CNA)
Linux Linux79cdcc765969d23f4e3d6ea115660c3333498768Vendor (CNA)
Linux Linux80365c9f96015bbf048fdd6c8705d3f8770132bfVendor (CNA)
Linux Linux9d52865ff28245fc2134da9f99baff603a24407aVendor (CNA)
debian:linux6.1.85-1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debug-devel0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debug-modules0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debug-modules-extra0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debuginfo0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records