Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-26868: nfs: fix panic when nfs4_ff_layout_prepare_ds() fails

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.61% (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 31db25e3141b20e2a76a9f219eeca52e3cab126c, 5ada9016b1217498fad876a3d5b07645cc955608, 719fcafe07c12646691bd62d7f8d94d657fa0766.
  • Severity is disputed: the assigning authority (CNA) scores it 7.5, NVD 5.5.

Low priority for now. Upgrade to Linux Linux 31db25e3141b20e2a76a9f219eeca52e3cab126c, 5ada9016b1217498fad876a3d5b07645cc955608, 719fcafe07c12646691bd62d7f8d94d657fa0766 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: nfs: fix panic when nfs4_ff_layout_prepare_ds() fails We've been seeing the following panic in production BUG: kernel NULL pointer dereference, address: 0000000000000065 PGD 2f485f067 P4D 2f485f067 PUD 2cc5d8067 PMD 0 RIP: 0010:ff_layout_cancel_io+0x3a/0x90 [nfs_layout_flexfiles] Call Trace: <TASK> ? __die+0x78/0xc0 ? page_fault_oops+0x286/0x380 ? __rpc_execute+0x2c3/0x470 [sunrpc] ? rpc_new_task+0x42/0x1c0 [sunrpc] ? exc_page_fault+0x5d/0x110 ? asm_exc_page_fault+0x22/0x30 ? ff_layout_free_layoutreturn+0x110/0x110 [nfs_layout_flexfiles] ? ff_layout_cancel_io+0x3a/0x90 [nfs_layout_flexfiles] ? ff_layout_cancel_io+0x6f/0x90 [nfs_layout_flexfiles] pnfs_mark_matching_lsegs_return+0x1b0/0x360 [nfsv4] pnfs_error_mark_layout_for_return+0x9e/0x110 [nfsv4] ? ff_layout_send_layouterror+0x50/0x160 [nfs_layout_flexfiles] nfs4_ff_layout_prepare_ds+0x11f/0x290 [nfs_layout_flexfiles] ff_layout_pg_init_write+0xf0/0x1f0 [nfs_layout_flexfiles] __nfs_pageio_add_request+0x154/0x6c0 [nfs] nfs_pageio_add_request+0x26b/0x380 [nfs] nfs_do_writepage+0x111/0x1e0 [nfs] nfs_writepages_callback+0xf/0x30 [nfs] write_cache_pages+0x17f/0x380 ? nfs_pageio_init_write+0x50/0x50 [nfs] ? nfs_writepages+0x6d/0x210 [nfs] ? nfs_writepages+0x6d/0x210 [nfs] nfs_writepages+0x125/0x210 [nfs] do_writepages+0x67/0x220 ? generic_perform_write+0x14b/0x210 filemap_fdatawrite_wbc+0x5b/0x80 file_write_and_wait_range+0x6d/0xc0 nfs_file_fsync+0x81/0x170 [nfs] ? nfs_file_mmap+0x60/0x60 [nfs] __x64_sys_fsync+0x53/0x90 do_syscall_64+0x3d/0x90 entry_SYSCALL_64_after_hwframe+0x46/0xb0 Inspecting the core with drgn I was able to pull this >>> prog.crashed_thread().stack_trace()[0] #0 at 0xffffffffa079657a (ff_layout_cancel_io+0x3a/0x84) in ff_layout_cancel_io at fs/nfs/flexfilelayout/flexfilelayout.c:2021:27 >>> prog.crashed_thread().stack_trace()[0]['idx'] (u32)1 >>> prog.crashed_thread().stack_trace()[0]['flseg'].mirror_array[1].mirror_ds (struct nfs4_ff_layout_ds *)0xffffffffffffffed This is clear from the stack trace, we call nfs4_ff_layout_prepare_ds() which could error out initializing the mirror_ds, and then we go to clean it all up and our check is only for if (!mirror->mirror_ds). This is inconsistent with the rest of the users of mirror_ds, which have if (IS_ERR_OR_NULL(mirror_ds)) to keep from tripping over this exact scenario. Fix this up in ff_layout_cancel_io() to make sure we don't panic when we get an error. I also spot checked all the other instances of checking mirror_ds and we appear to be doing the correct checks everywhere, only unconditionally dereferencing mirror_ds when we know it would be valid.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Apr 17, 2024
Updated
Aug 5, 2026
EPSS
0.6% · 49th percentile

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.6%

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.5
2.0 point gap

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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-26868

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

  • 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
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

Affected versions

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

  • linux linux kernel6.1 and later · before 6.1.83
  • linux linux kernel6.2 and later · before 6.6.23
  • linux linux kernel6.7 and later · before 6.7.11
  • linux linux kernel6.8 and later · before 6.8.2

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

    • 6.1affected
    • b739a5bd9d9f18cc69dced8db128ef7206e000cd and later · before 31db25e3141b20e2a76a9f219eeca52e3cab126caffected · git
    • b739a5bd9d9f18cc69dced8db128ef7206e000cd and later · before 7ca651b4ec4a049f5a46a0e5ff921b86b91c47c5affected · git
    • b739a5bd9d9f18cc69dced8db128ef7206e000cd and later · before 5ada9016b1217498fad876a3d5b07645cc955608affected · git
    • b739a5bd9d9f18cc69dced8db128ef7206e000cd and later · before dac068f164ad05b35e7c0be13f138c3f6adca58faffected · git
    • b739a5bd9d9f18cc69dced8db128ef7206e000cd and later · before 719fcafe07c12646691bd62d7f8d94d657fa0766affected · git
    • before 6.1not affected · semver
    • 6.1.83 and later · up to and including 6.1.*not affected · semver
    • 6.6.23 and later · up to and including 6.6.*not affected · semver
    • 6.7.11 and later · up to and including 6.7.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:9bpftoolbefore 7.3.0-427.31.1.el9_47.3.0-427.31.1.el9_4
AlmaLinux:9kernelbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64kbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-corebefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-debugbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-develbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-corebefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-cross-headersbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-debugbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-debug-corebefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-debug-develbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-427.31.1.el9_45.14.0-427.31.1.el9_4

+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-26865Apr 17, 2024 · rds: tcp: Fix use-after-free of net in reqsk_timer_handler().
    31Monitor
  • ← EarlierCVE-2024-26867Apr 17, 2024 · comedi: comedi_8255: Correct error in subdevice initialization
    22Monitor
  • Later →CVE-2024-26871Apr 17, 2024 · f2fs: fix NULL pointer dereference in f2fs_submit_page_write()
    22Monitor

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 Linux31db25e3141b20e2a76a9f219eeca52e3cab126cVendor (CNA)
Linux Linux5ada9016b1217498fad876a3d5b07645cc955608Vendor (CNA)
Linux Linux719fcafe07c12646691bd62d7f8d94d657fa0766Vendor (CNA)
Linux Linux7ca651b4ec4a049f5a46a0e5ff921b86b91c47c5Vendor (CNA)
Linux Linuxdac068f164ad05b35e7c0be13f138c3f6adca58fVendor (CNA)
almalinux:bpftool7.3.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-427.31.1.el9_4 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.85-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.3.0-427.31.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-427.31.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-427.31.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-427.31.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-427.31.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-427.31.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-427.31.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-427.31.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-427.31.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-427.31.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-427.31.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-427.31.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+1

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)

CWE-476 · NULL Pointer Dereference

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 (4 more)

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

All records