Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-53826: ubi: Fix UAF wear-leveling entry in eraseblk_count_seq_show()

Noroxi assessment

Priority: Monitor (action score 0/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.25% (FIRST EPSS).
  • Fixed version: Linux Linux 1cb14c06d6035539ef4215c4ba0871aea71d7c38, 3f9b63dfce44a7c3c095dd93d910408e07ab1845, 79548ccdd992707879b4b683b7251c58ddf26f12.

Low priority for now. Upgrade to Linux Linux 1cb14c06d6035539ef4215c4ba0871aea71d7c38, 3f9b63dfce44a7c3c095dd93d910408e07ab1845, 79548ccdd992707879b4b683b7251c58ddf26f12 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: ubi: Fix UAF wear-leveling entry in eraseblk_count_seq_show() Wear-leveling entry could be freed in error path, which may be accessed again in eraseblk_count_seq_show(), for example: __erase_worker eraseblk_count_seq_show wl = ubi->lookuptbl[*block_number] if (wl) wl_entry_destroy ubi->lookuptbl[e->pnum] = NULL kmem_cache_free(ubi_wl_entry_slab, e) erase_count = wl->ec // UAF! Wear-leveling entry updating/accessing in ubi->lookuptbl should be protected by ubi->wl_lock, fix it by adding ubi->wl_lock to serialize wl entry accessing between wl_entry_destroy() and eraseblk_count_seq_show(). Fetch a reproducer in [Link].

—No exploit Fix available
Published
Dec 9, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 16th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
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-2023-53826

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.

—

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

    • 2.6.22affected
    • 801c135ce73d5df1caf3eca35b66a10824ae0707 and later · before 3f9b63dfce44a7c3c095dd93d910408e07ab1845affected · git
    • 801c135ce73d5df1caf3eca35b66a10824ae0707 and later · before 84250da1c63cb7d421a3b4812b5c2ce2e47d31a1affected · git
    • 801c135ce73d5df1caf3eca35b66a10824ae0707 and later · before 1cb14c06d6035539ef4215c4ba0871aea71d7c38affected · git
    • 801c135ce73d5df1caf3eca35b66a10824ae0707 and later · before 9d448dd6bcb61a508204b57ea1f454ba9bac2f24affected · git
    • 801c135ce73d5df1caf3eca35b66a10824ae0707 and later · before 79548ccdd992707879b4b683b7251c58ddf26f12affected · git
    • 801c135ce73d5df1caf3eca35b66a10824ae0707 and later · before 84253f3c2dad6be10d30c92626c763d9a9f512adaffected · git
    • 801c135ce73d5df1caf3eca35b66a10824ae0707 and later · before a100de2974d208cfca032179b02ed4d1a0a7f143affected · git
    • 801c135ce73d5df1caf3eca35b66a10824ae0707 and later · before a240bc5c43130c6aa50831d7caaa02a1d84e1bceaffected · git
    • before 2.6.22not 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.20-16.1.20-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2023-53821Dec 9, 2025 · ip6_vti: fix slab-use-after-free in decode_session6
    0Monitor
  • ← EarlierCVE-2023-53825Dec 9, 2025 · kcm: Fix error handling for SOCK_DGRAM in kcm_sendmsg().
    0Monitor
  • Later →CVE-2023-53829Dec 9, 2025 · f2fs: flush inode if atomic file is aborted
    31Monitor

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 Linux1cb14c06d6035539ef4215c4ba0871aea71d7c38Vendor (CNA)
Linux Linux3f9b63dfce44a7c3c095dd93d910408e07ab1845Vendor (CNA)
Linux Linux79548ccdd992707879b4b683b7251c58ddf26f12Vendor (CNA)
Linux Linux84250da1c63cb7d421a3b4812b5c2ce2e47d31a1Vendor (CNA)
Linux Linux84253f3c2dad6be10d30c92626c763d9a9f512adVendor (CNA)
Linux Linux9d448dd6bcb61a508204b57ea1f454ba9bac2f24Vendor (CNA)
Linux Linuxa100de2974d208cfca032179b02ed4d1a0a7f143Vendor (CNA)
Linux Linuxa240bc5c43130c6aa50831d7caaa02a1d84e1bceVendor (CNA)
debian:linux6.1.20-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

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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

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

All records