Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-90353: wifi: mt76: mt7915: fix ext PHY use-after-free on register error path

Noroxi assessment

Priority: Monitor (action score 28/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.14% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Linux Linux 15b960014f24dce5388d4a2e7274e6490cb3c421, 34058ad122f7524e33df8e38caba4b1d803b025a, 648f5f03ff50d4bd719106ace0cdf1d8be02cbdd.

Low priority for now. Upgrade to Linux Linux 15b960014f24dce5388d4a2e7274e6490cb3c421, 34058ad122f7524e33df8e38caba4b1d803b025a, 648f5f03ff50d4bd719106ace0cdf1d8be02cbdd 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: wifi: mt76: mt7915: fix ext PHY use-after-free on register error path After mt7915_register_ext_phy() succeeded, a failure of the main PHY mt7915_init_debugfs() or mt7915_coredump_register() unwound through free_phy2, which called ieee80211_free_hw() on the ext PHY hw while it was still registered with mac80211, since mt76_unregister_device() only unregisters the main hw. Unregister the ext PHY (thermal + phy + hw) first and skip the redundant free.

HighCVSS 7.0 · v3.1—No exploit Fix available
Published
Sep 17, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 3th percentile
CWE
—

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CNA vs NVD score

NVD
—
CNA · Linux
7.0
NVD has not scored this yet; the score shown is the CNA’s.

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-2026-90353

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.

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

    • 5.19affected
    • 7b8e1ae886e45aed9274048f2836a70b75ecfa40 and later · before aa55bec92ba7747dd08feff409f8074c5e052e71affected · git
    • 7b8e1ae886e45aed9274048f2836a70b75ecfa40 and later · before ad706fcf6255494613b94418e7243d98065dbeafaffected · git
    • 7b8e1ae886e45aed9274048f2836a70b75ecfa40 and later · before 34058ad122f7524e33df8e38caba4b1d803b025aaffected · git
    • 7b8e1ae886e45aed9274048f2836a70b75ecfa40 and later · before a7fd3bae8e11a7c00df6a5021d9ef248ae9f9bf5affected · git
    • 7b8e1ae886e45aed9274048f2836a70b75ecfa40 and later · before 648f5f03ff50d4bd719106ace0cdf1d8be02cbddaffected · git
    • 7b8e1ae886e45aed9274048f2836a70b75ecfa40 and later · before 15b960014f24dce5388d4a2e7274e6490cb3c421affected · git
    • before 5.19not affected · semver
    • 6.1.188 and later · up to and including 6.1.*not affected · semver
    • 6.6.157 and later · up to and including 6.6.*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.190-16.1.190-1
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

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-2026-90351Sep 17, 2026 · wifi: mt76: mt7996: do not attach hif2 WED when the main WED attach failed
    0Monitor
  • ← EarlierCVE-2026-90352Sep 17, 2026 · wifi: mt76: mt7915: release hif2 reference on probe IRQ failure
    0Monitor
  • Later →CVE-2026-90354Sep 17, 2026 · wifi: mt76: mt7915: fix double hif2 init on the non-WED path
    0Monitor

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 Linux15b960014f24dce5388d4a2e7274e6490cb3c421Vendor (CNA)
Linux Linux34058ad122f7524e33df8e38caba4b1d803b025aVendor (CNA)
Linux Linux648f5f03ff50d4bd719106ace0cdf1d8be02cbddVendor (CNA)
Linux Linuxa7fd3bae8e11a7c00df6a5021d9ef248ae9f9bf5Vendor (CNA)
Linux Linuxaa55bec92ba7747dd08feff409f8074c5e052e71Vendor (CNA)
Linux Linuxad706fcf6255494613b94418e7243d98065dbeafVendor (CNA)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
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.

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.
  • Special conditions such as timing or configuration are required.

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
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

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

All records