Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-57924: fs: relax assertions on failure to encode file handles

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.27% (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 73697928c806fe4689939722184a86fc1c1957b4, 974e3fe0ac61de85015bbe5a4990cf4127b304b2, adcde2872f8fc399b249758ae1990dcd53b694ea; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes.

Low priority for now. Upgrade to Linux Linux 73697928c806fe4689939722184a86fc1c1957b4, 974e3fe0ac61de85015bbe5a4990cf4127b304b2, adcde2872f8fc399b249758ae1990dcd53b694ea; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes 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: fs: relax assertions on failure to encode file handles Encoding file handles is usually performed by a filesystem >encode_fh() method that may fail for various reasons. The legacy users of exportfs_encode_fh(), namely, nfsd and name_to_handle_at(2) syscall are ready to cope with the possibility of failure to encode a file handle. There are a few other users of exportfs_encode_{fh,fid}() that currently have a WARN_ON() assertion when ->encode_fh() fails. Relax those assertions because they are wrong. The second linked bug report states commit 16aac5ad1fa9 ("ovl: support encoding non-decodable file handles") in v6.6 as the regressing commit, but this is not accurate. The aforementioned commit only increases the chances of the assertion and allows triggering the assertion with the reproducer using overlayfs, inotify and drop_caches. Triggering this assertion was always possible with other filesystems and other reasons of ->encode_fh() failures and more particularly, it was also possible with the exact same reproducer using overlayfs that is mounted with options index=on,nfs_export=on also on kernels < v6.6. Therefore, I am not listing the aforementioned commit as a Fixes commit. Backport hint: this patch will have a trivial conflict applying to v6.6.y, and other trivial conflicts applying to stable kernels < v6.6.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Jan 19, 2025
Updated
Nov 10, 2026
EPSS
0.2% · 20th 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.2%

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

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 kernelbefore 6.1.151
  • linux linux kernel6.2 and later · before 6.6.74
  • linux linux kernel6.7 and later · before 6.12.10
  • linux linux kernel6.13

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

    • 3.8affected
    • be77196b809cdce8603a5aadd5e3cfabd3cbef96 and later · before 73697928c806fe4689939722184a86fc1c1957b4affected · git
    • be77196b809cdce8603a5aadd5e3cfabd3cbef96 and later · before f47c834a9131ae64bee3c462f4e610c67b0a000faffected · git
    • be77196b809cdce8603a5aadd5e3cfabd3cbef96 and later · before adcde2872f8fc399b249758ae1990dcd53b694eaaffected · git
    • be77196b809cdce8603a5aadd5e3cfabd3cbef96 and later · before 974e3fe0ac61de85015bbe5a4990cf4127b304b2affected · git
    • before 3.8not affected · semver
    • 6.1.151 and later · up to and including 6.1.*not affected · semver
    • 6.6.74 and later · up to and including 6.6.*not affected · semver
    • 6.12.10 and later · up to and including 6.12.*not affected · semver
    • 6.13 and laternot affected · original_commit_for_fix

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:11linux-6.1before 6.1.153-1~deb11u16.1.153-1~deb11u1
Debian:12linuxbefore 6.1.153-16.1.153-1
Debian:13linuxbefore 6.12.10-16.12.10-1
openSUSE:Leap 15.6dtb-aarch64before 6.4.0-150600.23.50.16.4.0-150600.23.50.1
openSUSE:Leap 15.6kernel-64kbbefore 6.4.0-150600.23.50.16.4.0-150600.23.50.1
openSUSE:Leap 15.6kernel-azurebefore 6.4.0-150600.8.37.16.4.0-150600.8.37.1
openSUSE:Leap 15.6kernel-debugbefore 6.4.0-150600.23.50.16.4.0-150600.23.50.1
openSUSE:Leap 15.6kernel-defaultbefore 6.4.0-150600.23.50.16.4.0-150600.23.50.1
openSUSE:Leap 15.6kernel-default-basebefore 6.4.0-150600.23.50.1.150600.12.22.16.4.0-150600.23.50.1.150600.12.22.1
openSUSE:Leap 15.6kernel-docsbefore 6.4.0-150600.23.50.16.4.0-150600.23.50.1
openSUSE:Leap 15.6kernel-kvmsmallbefore 6.4.0-150600.23.50.16.4.0-150600.23.50.1
openSUSE:Leap 15.6kernel-obs-buildbefore 6.4.0-150600.23.50.16.4.0-150600.23.50.1
openSUSE:Leap 15.6kernel-obs-qabefore 6.4.0-150600.23.50.16.4.0-150600.23.50.1
openSUSE:Leap 15.6kernel-sourcebefore 6.4.0-150600.23.50.16.4.0-150600.23.50.1
openSUSE:Leap 15.6kernel-source-azurebefore 6.4.0-150600.8.37.16.4.0-150600.8.37.1
openSUSE:Leap 15.6kernel-symsbefore 6.4.0-150600.23.50.16.4.0-150600.23.50.1
openSUSE:Leap 15.6kernel-syms-azurebefore 6.4.0-150600.8.37.16.4.0-150600.8.37.1
openSUSE:Leap 15.6kernel-zfcpdumpbefore 6.4.0-150600.23.50.16.4.0-150600.23.50.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_11before 1-150600.13.3.11-150600.13.3.1
SUSE:Linux Enterprise Module for Basesystem 15 SP6kernel-64kbbefore 6.4.0-150600.23.50.16.4.0-150600.23.50.1
SUSE:Linux Enterprise Module for Basesystem 15 SP6kernel-defaultbefore 6.4.0-150600.23.50.16.4.0-150600.23.50.1
SUSE:Linux Enterprise Module for Basesystem 15 SP6kernel-default-basebefore 6.4.0-150600.23.50.1.150600.12.22.16.4.0-150600.23.50.1.150600.12.22.1
SUSE:Linux Enterprise Module for Basesystem 15 SP6kernel-sourcebefore 6.4.0-150600.23.50.16.4.0-150600.23.50.1
SUSE:Linux Enterprise Module for Basesystem 15 SP6kernel-zfcpdumpbefore 6.4.0-150600.23.50.16.4.0-150600.23.50.1

+14

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-57913Jan 19, 2025 · usb: gadget: f_fs: Remove WARN_ON in functionfs_bind
    18Monitor
  • ← EarlierCVE-2024-57917Jan 19, 2025 · topology: Keep the cpumask unchanged when printing cpumap
    31Monitor
  • Later →CVE-2024-57929Jan 19, 2025 · dm array: fix releasing a faulty array block twice in dm_array_cursor_end
    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 Linux73697928c806fe4689939722184a86fc1c1957b4Vendor (CNA)
Linux Linux974e3fe0ac61de85015bbe5a4990cf4127b304b2Vendor (CNA)
Linux Linuxadcde2872f8fc399b249758ae1990dcd53b694eaVendor (CNA)
Linux Linuxf47c834a9131ae64bee3c462f4e610c67b0a000fVendor (CNA)
cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0Release NotesMicrosoft (MSRC)
debian:linux6.1.153-1 · Debian:12Package registry (OSV)
debian:linux-6.16.1.153-1~deb11u1 · Debian:11Package registry (OSV)
opensuse:dtb-aarch646.4.0-150600.23.50.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-64kb6.4.0-150600.23.50.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-debug6.4.0-150600.23.50.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default6.4.0-150600.23.50.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default-base6.4.0-150600.23.50.1.150600.12.22.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-docs6.4.0-150600.23.50.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-kvmsmall6.4.0-150600.23.50.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-obs-build6.4.0-150600.23.50.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-obs-qa6.4.0-150600.23.50.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-source6.4.0-150600.23.50.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-syms6.4.0-150600.23.50.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-zfcpdump6.4.0-150600.23.50.1 · openSUSE:Leap 15.6Package registry (OSV)
suse:kernel-64kb6.4.0-150600.23.50.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)
suse:kernel-azure6.4.0-150600.8.37.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP6Package registry (OSV)
suse:kernel-default6.4.0-150600.23.50.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)
suse:kernel-default-base6.4.0-150600.23.50.1.150600.12.22.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)
suse:kernel-docs6.4.0-150600.23.50.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP6Package registry (OSV)
suse:kernel-livepatch-SLE15-SP6_Update_111-150600.13.3.1 · SUSE:Linux Enterprise Live Patching 15 SP6Package registry (OSV)
suse:kernel-obs-build6.4.0-150600.23.50.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP6Package registry (OSV)
suse:kernel-source6.4.0-150600.23.50.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)
suse:kernel-source-azure6.4.0-150600.8.37.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP6Package registry (OSV)
suse:kernel-syms6.4.0-150600.23.50.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP6Package registry (OSV)
suse:kernel-syms-azure6.4.0-150600.8.37.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP6Package 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.

  • CVE-2026-31739467 days apartcrypto: tegra - Add missing CRYPTO_ALG_ASYNC
    35Monitor
  • CVE-2026-52952521 days apartiommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset
    35Monitor
  • CVE-2025-39803239 days apartscsi: ufs: core: Remove WARN_ON_ONCE() call from ufshcd_uic_cmd_compl()
    31Monitor
  • CVE-2023-52621299 days apartbpf: Check rcu_read_lock_trace_held() before calling bpf map helpers
    31Monitor
  • CVE-2026-31398439 days apartmm/rmap: fix incorrect pte restoration for lazyfree folios
    31Monitor
  • CVE-2026-46117494 days apartRDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss()
    31Monitor

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-617 · Reachable Assertion

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