NVD / CVE Program· CNA Linux

CVE-2024-42315: exfat: fix potential deadlock on __exfat_get_dentry_set

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.16% (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 1d1970493c289e3f44b9ec847ed26a5dbdf56a62, 5.10.232, 5.15.175.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 1d1970493c289e3f44b9ec847ed26a5dbdf56a62, 5.10.232, 5.15.175 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: exfat: fix potential deadlock on __exfat_get_dentry_set When accessing a file with more entries than ES_MAX_ENTRY_NUM, the bh-array is allocated in __exfat_get_entry_set. The problem is that the bh-array is allocated with GFP_KERNEL. It does not make sense. In the following cases, a deadlock for sbi->s_lock between the two processes may occur. CPU0 CPU1 ---- ---- kswapd balance_pgdat lock(fs_reclaim) exfat_iterate lock(&sbi->s_lock) exfat_readdir exfat_get_uniname_from_ext_entry exfat_get_dentry_set __exfat_get_dentry_set kmalloc_array ... lock(fs_reclaim) ... evict exfat_evict_inode lock(&sbi->s_lock) To fix this, let's allocate bh-array with GFP_NOFS.

MediumCVSS 5.5 · v3.1—No exploit Fix available

Denial of service

Published: Aug 17, 2024
Updated: Jun 17, 2026
EPSS: 0.1% · 5th percentile
CWE: CWE-667

Report tools

JSON

Action score

Monitor

Low priority for now.

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

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

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.

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.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_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.2 and later · before 6.6.44
linux linux kernel6.7 and later · before 6.10.3

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.2affected
- bd3bdb9e0d656f760b11d0c638d35d7f7068144d and later · before 632fb232b6bbf8277edcbe9ecd4b4d98ecb122ebaffected · git
- 92dcd7d6c6068bf4fd35a6f64d606e27d634807e and later · before c052f775ee6ccacd3c97e4cf41a2a657e63d4259affected · git
- d8fe01ad2d8ab33aaf8f2efad9e8f1dae11c4b0c and later · before cd1c7858641384191ff7033fb1fc65dfcd559c6faffected · git
- a3ff29a95fde16906304455aa8c0bd84eb770258 and later · before a7ac198f8dba791e3144c4da48a5a9b95773ee4baffected · git
- a3ff29a95fde16906304455aa8c0bd84eb770258 and later · before 1d1970493c289e3f44b9ec847ed26a5dbdf56a62affected · git
- a3ff29a95fde16906304455aa8c0bd84eb770258 and later · before 89fc548767a2155231128cb98726d6d2ea1256c9affected · git
- 5.10.190 and later · before 5.10.232affected · semver
- 5.15.150 and later · before 5.15.175affected · semver
- before 6.2not affected · semver

Package-level exposure

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

Ecosystem	Package	Affected range	Fix
Debian:11	linux	before 5.10.234-1	5.10.234-1
Debian:11	linux-6.1	before 6.1.128-1~deb11u1	6.1.128-1~deb11u1
Debian:12	linux	before 6.1.123-1	6.1.123-1
Debian:13	linux	before 6.10.3-1	6.10.3-1

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-42313Aug 17, 2024 · media: venus: fix use after free in vdec_close
31Monitor
← EarlierCVE-2024-42314Aug 17, 2024 · btrfs: fix extent map use-after-free when adding pages to compressed bio
31Monitor
Later →CVE-2024-42316Aug 17, 2024 · mm/mglru: fix div-by-zero in vmpressure_calc_level()
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 / package	Fixed version	Source
Linux Linux	1d1970493c289e3f44b9ec847ed26a5dbdf56a62	Vendor (CNA)
Linux Linux	5.10.232	Vendor (CNA)
Linux Linux	5.15.175	Vendor (CNA)
Linux Linux	632fb232b6bbf8277edcbe9ecd4b4d98ecb122eb	Vendor (CNA)
Linux Linux	89fc548767a2155231128cb98726d6d2ea1256c9	Vendor (CNA)
Linux Linux	a7ac198f8dba791e3144c4da48a5a9b95773ee4b	Vendor (CNA)
Linux Linux	c052f775ee6ccacd3c97e4cf41a2a657e63d4259	Vendor (CNA)
Linux Linux	cd1c7858641384191ff7033fb1fc65dfcd559c6f	Vendor (CNA)
debian:linux	6.1.123-1 · Debian:12	Package registry (OSV)
debian:linux-6.1	6.1.128-1~deb11u1 · Debian:11	Package 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).