Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-52444: f2fs: fix to avoid dirent corruption

Noroxi assessment

Priority: Monitor (action score 31/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.24% (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 02160112e6d45c2610b049df6eb693d7a2e57b46, 2fb4867f4405aea8c0519d7d188207f232a57862, 53edb549565f55ccd0bdf43be3d66ce4c2d48b28.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 02160112e6d45c2610b049df6eb693d7a2e57b46, 2fb4867f4405aea8c0519d7d188207f232a57862, 53edb549565f55ccd0bdf43be3d66ce4c2d48b28 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: f2fs: fix to avoid dirent corruption As Al reported in link[1]: f2fs_rename() ... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0); You want correct inumber in the ".." link. And cross-directory rename does move the source to new parent, even if you'd been asked to leave a whiteout in the old place. [1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/ With below testcase, it may cause dirent corruption, due to it missed to call f2fs_set_link() to update ".." link to new directory. - mkdir -p dir/foo - renameat2 -w dir/foo bar [ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for '..', parent parent ino is [0x3] [FSCK] other corrupted bugs [Fail]

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Feb 22, 2024
Updated
Oct 15, 2026
EPSS
0.2% · 15th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 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
7.8
CNA · Linux
7.8
agree

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-2023-52444

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

Affected versions

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

  • linux linux kernel4.2.0 and later · before 4.19.306
  • linux linux kernel4.20 and later · before 5.4.268
  • linux linux kernel5.5.0 and later · before 5.10.209
  • linux linux kernel5.11.0 and later · before 5.15.148
  • linux linux kernel5.16.0 and later · before 6.1.75
  • linux linux kernel6.2.0 and later · before 6.6.14
  • linux linux kernel6.7.0 and later · before 6.7.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

    • 4.2affected
    • 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 and later · before 02160112e6d45c2610b049df6eb693d7a2e57b46affected · git
    • 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 and later · before 5624a3c1b1ebc8991318e1cce2aa719542991024affected · git
    • 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 and later · before 6f866885e147d33efc497f1095f35b2ee5ec7310affected · git
    • 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 and later · before f100ba617d8be6c98a68f3744ef7617082975b77affected · git
    • 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 and later · before f0145860c20be6bae6785c7a2249577674702ac7affected · git
    • 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 and later · before d3c0b49aaa12a61d560528f5d605029ab57f0728affected · git
    • 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 and later · before 2fb4867f4405aea8c0519d7d188207f232a57862affected · git
    • 7e01e7ad746bc8198a8b46163ddc73a1c7d22339 and later · before 53edb549565f55ccd0bdf43be3d66ce4c2d48b28affected · git
    • before 4.2not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:10linuxbefore 4.19.316-14.19.316-1
Debian:10linux-5.10before 5.10.209-2~deb10u15.10.209-2~deb10u1
Debian:12linuxbefore 6.1.76-16.1.76-1
Debian:13linuxbefore 6.6.15-16.6.15-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-26591Feb 22, 2024 · bpf: Fix re-attachment branch in bpf_tracing_prog_attach
    22Monitor
  • ← EarlierCVE-2024-26592Feb 22, 2024 · ksmbd: fix UAF issue in ksmbd_tcp_new_connection()
    31Monitor
  • Later →CVE-2023-52447Feb 22, 2024 · bpf: Defer the free of inner map when necessary
    26Monitor

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 Linux02160112e6d45c2610b049df6eb693d7a2e57b46Vendor (CNA)
Linux Linux2fb4867f4405aea8c0519d7d188207f232a57862Vendor (CNA)
Linux Linux53edb549565f55ccd0bdf43be3d66ce4c2d48b28Vendor (CNA)
Linux Linux5624a3c1b1ebc8991318e1cce2aa719542991024Vendor (CNA)
Linux Linux6f866885e147d33efc497f1095f35b2ee5ec7310Vendor (CNA)
Linux Linuxd3c0b49aaa12a61d560528f5d605029ab57f0728Vendor (CNA)
Linux Linuxf0145860c20be6bae6785c7a2249577674702ac7Vendor (CNA)
Linux Linuxf100ba617d8be6c98a68f3744ef7617082975b77Vendor (CNA)
debian:linux6.1.76-1 · Debian:12Package registry (OSV)
debian:linux-5.105.10.209-2~deb10u1 · Debian:10Package 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.

  • CVE-2023-524401 days apartksmbd: fix slub overflow in ksmbd_decode_ntlmssp_auth_blob()
    38Monitor
  • CVE-2021-4734889 days apartdrm/amd/display: Avoid HDCP over-read and corruption
    36Monitor
  • CVE-2022-3640489 days apartLinux Kernel Bluetooth l2cap_core.c l2cap_conn_del use after free
    35Monitor
  • CVE-2023-524342 days apartsmb: client: fix potential OOBs in smb2_parse_contexts()
    32Monitor
  • CVE-2024-265880 days apartLoongArch: BPF: Prevent out-of-bounds memory access
    31Monitor
  • CVE-2024-265890 days apartbpf: Reject variable offset alu on PTR_TO_FLOW_KEYS
    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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-119 · Improper Restriction of Operations within the Bounds of a Memory Buffer

CVSS vector

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

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

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

References

Show all references (10 more)

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

All records