Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-53224: ext4: Fix function prototype mismatch for ext4_feat_ktype

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 0a1394e07c5d6bf1bfc25db8589ff1b1bfb6f46a, 118901ad1f25d2334255b3d50512fa20591531cd, 1ba10d3640e9783dad811fe4e24d55465c37c64d.

Low priority for now. Upgrade to Linux Linux 0a1394e07c5d6bf1bfc25db8589ff1b1bfb6f46a, 118901ad1f25d2334255b3d50512fa20591531cd, 1ba10d3640e9783dad811fe4e24d55465c37c64d 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: ext4: Fix function prototype mismatch for ext4_feat_ktype With clang's kernel control flow integrity (kCFI, CONFIG_CFI_CLANG), indirect call targets are validated against the expected function pointer prototype to make sure the call target is valid to help mitigate ROP attacks. If they are not identical, there is a failure at run time, which manifests as either a kernel panic or thread getting killed. ext4_feat_ktype was setting the "release" handler to "kfree", which doesn't have a matching function prototype. Add a simple wrapper with the correct prototype. This was found as a result of Clang's new -Wcast-function-type-strict flag, which is more sensitive than the simpler -Wcast-function-type, which only checks for type width mismatches. Note that this code is only reached when ext4 is a loadable module and it is being unloaded: CFI failure at kobject_put+0xbb/0x1b0 (target: kfree+0x0/0x180; expected type: 0x7c4aa698) ... RIP: 0010:kobject_put+0xbb/0x1b0 ... Call Trace: <TASK> ext4_exit_sysfs+0x14/0x60 [ext4] cleanup_module+0x67/0xedb [ext4]

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Sep 15, 2025
Updated
Jun 17, 2026
EPSS
0.1% · 5th 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.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.

Follow CVE-2023-53224

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 kernel4.16 and later · before 4.19.274
  • linux linux kernel4.20 and later · before 5.4.233
  • linux linux kernel5.5 and later · before 5.10.170
  • linux linux kernel5.11 and later · before 5.15.96
  • linux linux kernel5.16 and later · before 6.1.14
  • linux linux kernel6.2 and later · before 6.2.1

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.16affected
    • b99fee58a20ab8e0557cce87b6f187e325993142 and later · before 2b69cdd9f9a7f596e3dd31f05f9852940d177924affected · git
    • b99fee58a20ab8e0557cce87b6f187e325993142 and later · before 99e3fd21f8fc975c95e8cf76fbf6a3d2656f8f71affected · git
    • b99fee58a20ab8e0557cce87b6f187e325993142 and later · before 1ba10d3640e9783dad811fe4e24d55465c37c64daffected · git
    • b99fee58a20ab8e0557cce87b6f187e325993142 and later · before c98077f7598a562f51051eec043be0cb3e1b1b5eaffected · git
    • b99fee58a20ab8e0557cce87b6f187e325993142 and later · before 0a1394e07c5d6bf1bfc25db8589ff1b1bfb6f46aaffected · git
    • b99fee58a20ab8e0557cce87b6f187e325993142 and later · before 94d8de83286fb1827340eba35b61c308f6b46eadaffected · git
    • b99fee58a20ab8e0557cce87b6f187e325993142 and later · before 118901ad1f25d2334255b3d50512fa20591531cdaffected · git
    • before 4.16not affected · semver
    • 4.19.274 and later · up to and including 4.19.*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.15-16.1.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-2023-53222Sep 15, 2025 · jfs: jfs_dmap: Validate db_l2nbperpage while mounting
    28Monitor
  • ← EarlierCVE-2023-53223Sep 15, 2025 · drm/msm/dsi: Add missing check for alloc_ordered_workqueue
    22Monitor
  • Later →CVE-2023-53225Sep 15, 2025 · spi: imx: Don't skip cleanup in remove's error path
    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 Linux0a1394e07c5d6bf1bfc25db8589ff1b1bfb6f46aVendor (CNA)
Linux Linux118901ad1f25d2334255b3d50512fa20591531cdVendor (CNA)
Linux Linux1ba10d3640e9783dad811fe4e24d55465c37c64dVendor (CNA)
Linux Linux2b69cdd9f9a7f596e3dd31f05f9852940d177924Vendor (CNA)
Linux Linux94d8de83286fb1827340eba35b61c308f6b46eadVendor (CNA)
Linux Linux99e3fd21f8fc975c95e8cf76fbf6a3d2656f8f71Vendor (CNA)
Linux Linuxc98077f7598a562f51051eec043be0cb3e1b1b5eVendor (CNA)
debian:linux6.1.15-1 · Debian:12Package 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)

CWE-401 · Missing Release of Memory after Effective Lifetime

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

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

All records