Skip to content
Noroxi
CVE-2026-93049· NVD / CVE Program· CNA Linux

mtd: mtdswap: Avoid freeing registered blktrans device twice

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.21% (FIRST EPSS).
  • Fixed version: Linux Linux 0ce48c6ddea1a8e675a2eb0221b62a9950788f3c, 37be7bc2c2d09c18e939da20224405864a0090b9, 5c349c533e72af2313c3be0f80a24d7407fa4777.

Low priority for now. Upgrade to Linux Linux 0ce48c6ddea1a8e675a2eb0221b62a9950788f3c, 37be7bc2c2d09c18e939da20224405864a0090b9, 5c349c533e72af2313c3be0f80a24d7407fa4777 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

In the Linux kernel, the following vulnerability has been resolved: mtd: mtdswap: Avoid freeing registered blktrans device twice In mtdswap_add_mtd(), debugfs setup failure after successful blktrans registration can free mbd_dev twice. add_mtd_blktrans_dev() initializes the blktrans device reference and publishes the disk. Once that succeeds, del_mtd_blktrans_dev() tears the disk down and drops the blktrans reference; when that reference reaches zero, blktrans_dev_release() frees the mtd_blktrans_dev. The debugfs failure path called del_mtd_blktrans_dev(mbd_dev), then fell through the common cleanup label and called kfree(mbd_dev) again. Clear the local pointer after deregistration so the common cleanup can still release the mtdswap state without freeing the blktrans object twice. This issue was found by a static analysis checker and confirmed by manual source review.

—No exploit Fix available
Published
Sep 17, 2026
Updated
Sep 17, 2026
EPSS
0.2% · 10th 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-2026-93049

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
  • Port scanning: 5 full scans a day (members only)
  • Uptime monitoring: 1 site, instant email when it goes down
  • Verify your domain: subdomains and takeover risk scanned every week
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
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

    • 4.14affected
    • e8e3edb95ce6a146bc774b6cfad3553f4383edc8 and later · before ecadb9137aeaa0615183f8d23eabea2b45c862f1affected · git
    • e8e3edb95ce6a146bc774b6cfad3553f4383edc8 and later · before eec130fc9ffbbd08a5d5432683122b79aca2a726affected · git
    • e8e3edb95ce6a146bc774b6cfad3553f4383edc8 and later · before d5086911d532b82ca070d944aa08ddde00baefe4affected · git
    • e8e3edb95ce6a146bc774b6cfad3553f4383edc8 and later · before 0ce48c6ddea1a8e675a2eb0221b62a9950788f3caffected · git
    • e8e3edb95ce6a146bc774b6cfad3553f4383edc8 and later · before a82d93fcfdfd26af17049c34319dfdd079cd1901affected · git
    • e8e3edb95ce6a146bc774b6cfad3553f4383edc8 and later · before 5c349c533e72af2313c3be0f80a24d7407fa4777affected · git
    • e8e3edb95ce6a146bc774b6cfad3553f4383edc8 and later · before 37be7bc2c2d09c18e939da20224405864a0090b9affected · git
    • e8e3edb95ce6a146bc774b6cfad3553f4383edc8 and later · before 779aa4c66a96bf43d2d62982ea1a9096a9128d87affected · git
    • before 4.14not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxall versions—
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.2.6-17.2.6-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
  • CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler
    40Plan
  • CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index
    40Plan
  • CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index
    40Plan

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 Linux0ce48c6ddea1a8e675a2eb0221b62a9950788f3cVendor (CNA)
Linux Linux37be7bc2c2d09c18e939da20224405864a0090b9Vendor (CNA)
Linux Linux5c349c533e72af2313c3be0f80a24d7407fa4777Vendor (CNA)
Linux Linux779aa4c66a96bf43d2d62982ea1a9096a9128d87Vendor (CNA)
Linux Linuxa82d93fcfdfd26af17049c34319dfdd079cd1901Vendor (CNA)
Linux Linuxd5086911d532b82ca070d944aa08ddde00baefe4Vendor (CNA)
Linux Linuxecadb9137aeaa0615183f8d23eabea2b45c862f1Vendor (CNA)
Linux Linuxeec130fc9ffbbd08a5d5432683122b79aca2a726Vendor (CNA)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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