Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-53089: ext4: fix task hung in ext4_xattr_delete_inode

MediumCVSS 5.5 · v3.1—No exploit Fix available

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.20% (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 0f7bfd6f8164be32dbbdf36aa1e5d00485c53cd7, 1aec41c98cce61d19ce89650895e51b9f3cdef13, 2c96c52aeaa6fd9163cfacdd98778b4a0398ef18.

Low priority for now. Upgrade to Linux Linux 0f7bfd6f8164be32dbbdf36aa1e5d00485c53cd7, 1aec41c98cce61d19ce89650895e51b9f3cdef13, 2c96c52aeaa6fd9163cfacdd98778b4a0398ef18 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 task hung in ext4_xattr_delete_inode Syzbot reported a hung task problem: ================================================================== INFO: task syz-executor232:5073 blocked for more than 143 seconds. Not tainted 6.2.0-rc2-syzkaller-00024-g512dee0c00ad #0 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:syz-exec232 state:D stack:21024 pid:5073 ppid:5072 flags:0x00004004 Call Trace: <TASK> context_switch kernel/sched/core.c:5244 [inline] __schedule+0x995/0xe20 kernel/sched/core.c:6555 schedule+0xcb/0x190 kernel/sched/core.c:6631 __wait_on_freeing_inode fs/inode.c:2196 [inline] find_inode_fast+0x35a/0x4c0 fs/inode.c:950 iget_locked+0xb1/0x830 fs/inode.c:1273 __ext4_iget+0x22e/0x3ed0 fs/ext4/inode.c:4861 ext4_xattr_inode_iget+0x68/0x4e0 fs/ext4/xattr.c:389 ext4_xattr_inode_dec_ref_all+0x1a7/0xe50 fs/ext4/xattr.c:1148 ext4_xattr_delete_inode+0xb04/0xcd0 fs/ext4/xattr.c:2880 ext4_evict_inode+0xd7c/0x10b0 fs/ext4/inode.c:296 evict+0x2a4/0x620 fs/inode.c:664 ext4_orphan_cleanup+0xb60/0x1340 fs/ext4/orphan.c:474 __ext4_fill_super fs/ext4/super.c:5516 [inline] ext4_fill_super+0x81cd/0x8700 fs/ext4/super.c:5644 get_tree_bdev+0x400/0x620 fs/super.c:1282 vfs_get_tree+0x88/0x270 fs/super.c:1489 do_new_mount+0x289/0xad0 fs/namespace.c:3145 do_mount fs/namespace.c:3488 [inline] __do_sys_mount fs/namespace.c:3697 [inline] __se_sys_mount+0x2d3/0x3c0 fs/namespace.c:3674 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7fa5406fd5ea RSP: 002b:00007ffc7232f968 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5 RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fa5406fd5ea RDX: 0000000020000440 RSI: 0000000020000000 RDI: 00007ffc7232f970 RBP: 00007ffc7232f970 R08: 00007ffc7232f9b0 R09: 0000000000000432 R10: 0000000000804a03 R11: 0000000000000202 R12: 0000000000000004 R13: 0000555556a7a2c0 R14: 00007ffc7232f9b0 R15: 0000000000000000 </TASK> ================================================================== The problem is that the inode contains an xattr entry with ea_inum of 15 when cleaning up an orphan inode <15>. When evict inode <15>, the reference counting of the corresponding EA inode is decreased. When EA inode <15> is found by find_inode_fast() in __ext4_iget(), it is found that the EA inode holds the I_FREEING flag and waits for the EA inode to complete deletion. As a result, when inode <15> is being deleted, we wait for inode <15> to complete the deletion, resulting in an infinite loop and triggering Hung Task. To solve this problem, we only need to check whether the ino of EA inode and parent is the same before getting EA inode.

Published
May 2, 2025
Updated
Nov 5, 2026
EPSS
0.2% · 10th 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%

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

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 every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE 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, at most 30 a day (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
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

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.13affected
    • e50e5129f384ae282adebfb561189cdb19b81cee and later · before efddc7e106fdf8d1f62d45e79de78f63b7c04fbaaffected · git
    • e50e5129f384ae282adebfb561189cdb19b81cee and later · before 64b72f5e7574020dea62ab733d88a54d903c42a1affected · git
    • e50e5129f384ae282adebfb561189cdb19b81cee and later · before 2c96c52aeaa6fd9163cfacdd98778b4a0398ef18affected · git
    • e50e5129f384ae282adebfb561189cdb19b81cee and later · before a98160d8f3e6242ca9b7f443f26e7ef3a61ba684affected · git
    • e50e5129f384ae282adebfb561189cdb19b81cee and later · before 1aec41c98cce61d19ce89650895e51b9f3cdef13affected · git
    • e50e5129f384ae282adebfb561189cdb19b81cee and later · before 94fd091576b12540924f6316ebc0678e84cb2800affected · git
    • e50e5129f384ae282adebfb561189cdb19b81cee and later · before 73f7987fe1b82596f1a380e85cd0097ebaae7e01affected · git
    • e50e5129f384ae282adebfb561189cdb19b81cee and later · before 0f7bfd6f8164be32dbbdf36aa1e5d00485c53cd7affected · git
    • before 4.13not 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.25-16.1.25-1

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-53087May 2, 2025 · drm/i915/active: Fix misuse of non-idle barriers as fence trackers
    22Monitor
  • ← EarlierCVE-2023-53088May 2, 2025 · mptcp: fix UaF in listener shutdown
    31Monitor
  • Later →CVE-2023-53090May 2, 2025 · drm/amdkfd: Fix an illegal memory access
    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 Linux0f7bfd6f8164be32dbbdf36aa1e5d00485c53cd7Vendor (CNA)
Linux Linux1aec41c98cce61d19ce89650895e51b9f3cdef13Vendor (CNA)
Linux Linux2c96c52aeaa6fd9163cfacdd98778b4a0398ef18Vendor (CNA)
Linux Linux64b72f5e7574020dea62ab733d88a54d903c42a1Vendor (CNA)
Linux Linux73f7987fe1b82596f1a380e85cd0097ebaae7e01Vendor (CNA)
Linux Linux94fd091576b12540924f6316ebc0678e84cb2800Vendor (CNA)
Linux Linuxa98160d8f3e6242ca9b7f443f26e7ef3a61ba684Vendor (CNA)
Linux Linuxefddc7e106fdf8d1f62d45e79de78f63b7c04fbaVendor (CNA)
debian:linux6.1.25-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.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-31448355 days apartext4: avoid infinite loops caused by residual data
    37Monitor
  • CVE-2026-63889443 days apartscsi: scsi_transport_fc: Widen FPIN pname walker counter to u32
    32Monitor
  • CVE-2026-52933418 days apartio_uring/poll: fix signed comparison in io_poll_get_ownership()
    31Monitor
  • CVE-2026-23451336 days apartbonding: prevent potential infinite loop in bond_header_parse()
    30Monitor
  • CVE-2026-31552357 days apartwifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom
    30Monitor
  • CVE-2026-46052390 days apartceph: only d_add() negative dentries when they are unhashed
    30Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

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

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.

References

All records