LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53232: mt76: mt7921: fix kernel panic by accessing unallocated eeprom.data

In the Linux kernel, the following vulnerability has been resolved: mt76: mt7921: fix kernel panic by accessing unallocated eeprom.data The MT7921 driver no longer uses eeprom.data, but the relevant code has not been removed completely since commit 16d98b548365 ("mt76: mt7921: rely on mcu_get_nic_capability"). This could result in potential invalid memory access. To fix the kernel panic issue in mt7921, it is necessary to avoid accessing unallocated eeprom.data which can lead to invalid memory access. Furthermore, it is possible to entirely eliminate the mt7921_mcu_parse_eeprom function and solely depend on mt7921_mcu_parse_response to divide the RxD header. [2.702735] BUG: kernel NULL pointer dereference, address: 0000000000000550 [2.702740] #PF: supervisor write access in kernel mode [2.702741] #PF: error_code(0x0002) - not-present page [2.702743] PGD 0 P4D 0 [2.702747] Oops: 0002 [#1] PREEMPT SMP NOPTI [2.702755] RIP: 0010:mt7921_mcu_parse_response+0x147/0x170 [mt7921_common] [2.702758] RSP: 0018:ffffae7c00fef828 EFLAGS: 00010286 [2.702760] RAX: ffffa367f57be024 RBX: ffffa367cc7bf500 RCX: 0000000000000000 [2.702762] RDX: 0000000000000550 RSI: 0000000000000000 RDI: ffffa367cc7bf500 [2.702763] RBP: ffffae7c00fef840 R08: ffffa367cb167000 R09: 0000000000000005 [2.702764] R10: 0000000000000000 R11: ffffffffc04702e4 R12: ffffa367e8329f40 [2.702766] R13: 0000000000000000 R14: 0000000000000001 R15: ffffa367e8329f40 [2.702768] FS: 000079ee6cf20c40(0000) GS:ffffa36b2f940000(0000) knlGS:0000000000000000 [2.702769] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [2.702775] CR2: 0000000000000550 CR3: 00000001233c6004 CR4: 0000000000770ee0 [2.702776] PKRU: 55555554 [2.702777] Call Trace: [2.702782] mt76_mcu_skb_send_and_get_msg+0xc3/0x11e [mt76 <HASH:1bc4 5>] [2.702785] mt7921_run_firmware+0x241/0x853 [mt7921_common <HASH:6a2f 6>] [2.702789] mt7921e_mcu_init+0x2b/0x56 [mt7921e <HASH:d290 7>] [2.702792] mt7921_register_device+0x2eb/0x5a5 [mt7921_common <HASH:6a2f 6>] [2.702795] ? mt7921_irq_tasklet+0x1d4/0x1d4 [mt7921e <HASH:d290 7>] [2.702797] mt7921_pci_probe+0x2d6/0x319 [mt7921e <HASH:d290 7>] [2.702799] pci_device_probe+0x9f/0x12a

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash systems that load the MediaTek MT7921 Wi-Fi driver. The bug is an invalid memory access in driver initialization, not an internet-facing service flaw. Business urgency depends on whether Linux laptops or devices in your fleet use MT7921 hardware and affected kernels.

Executive priority

Handle through normal kernel patch management, with higher priority for fleets that rely on MT7921 Wi-Fi. This is not documented as actively exploited, but kernel panics can cause operational disruption on affected hardware.

Technical view

The mt76 MT7921 driver can access unallocated eeprom.data after earlier code changes made that data path obsolete. The resolved fix removes the stale parsing path and relies on mt7921_mcu_parse_response. The source shows a NULL pointer dereference and kernel panic during MT7921 PCI probe and firmware initialization.

Likely exposure

Exposure is likely limited to Linux systems using the mt76 MT7921 driver, typically devices with MediaTek MT7921 wireless hardware. Exact distro exposure requires checking kernel package versions and vendor backports against the upstream stable fixes.

Exploitation context

The provided sources do not show active exploitation, KEV listing, exploit availability, or remote attack conditions. Evidence supports a kernel panic from invalid memory access during driver initialization. Treat this primarily as an availability risk until vendor guidance says otherwise.

Researcher notes

Sources identify Linux kernel MT7921 driver invalid memory access after commit 16d98b548365. Public data lacks CVSS, CWE, exploit status, and complete distro-specific ranges. Analysis should avoid assuming remote reachability or privilege impact beyond the documented kernel panic.

Mitigation direction

  • Inventory Linux systems with MediaTek MT7921 Wi-Fi hardware or loaded mt7921 modules.
  • Update affected Linux kernels using vendor or distribution security packages.
  • Check whether your distribution backported the referenced upstream stable fixes.
  • Prioritize mobile endpoints or appliances where Wi-Fi driver crashes affect operations.
  • If updates are unavailable, follow vendor guidance for temporary driver or device workarounds.

Validation and detection

  • Confirm kernel versions against distribution advisories and upstream stable fix references.
  • Check systems for MT7921 hardware and mt76/mt7921 driver usage.
  • Review boot logs for mt7921 NULL pointer dereference or kernel panic traces.
  • Validate patched systems boot and initialize Wi-Fi without recurring driver crashes.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-53232 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
5Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux16d98b548365fcd6fc3fe2e1ae73c9e3cc5ee43d, 16d98b548365fcd6fc3fe2e1ae73c9e3cc5ee43d, 16d98b548365fcd6fc3fe2e1ae73c9e3cc5ee43d, 16d98b548365fcd6fc3fe2e1ae73c9e3cc5ee43dunaffected
LinuxLinux5.16, 0, 6.1.28, 6.2.15, 6.3.2, 6.4affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.