LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53710: wifi: mt76: mt7921: fix error code of return in mt7921_acpi_read

In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7921: fix error code of return in mt7921_acpi_read Kernel NULL pointer dereference when ACPI SAR table isn't implemented well. Fix the error code of return to mark the ACPI SAR table as invalid. [ 5.077128] mt7921e 0000:06:00.0: sar cnt = 0 [ 5.077381] BUG: kernel NULL pointer dereference, address: 0000000000000004 [ 5.077630] #PF: supervisor read access in kernel mode [ 5.077883] #PF: error_code(0x0000) - not-present page [ 5.078138] PGD 0 P4D 0 [ 5.078398] Oops: 0000 [#1] PREEMPT SMP NOPTI [ 5.079202] RIP: 0010:mt7921_init_acpi_sar+0x106/0x220 [mt7921_common] ... [ 5.080786] Call Trace: [ 5.080786] <TASK> [ 5.080786] mt7921_register_device+0x37d/0x490 [mt7921_common] [ 5.080786] mt7921_pci_probe.part.0+0x2ee/0x310 [mt7921e] [ 5.080786] mt7921_pci_probe+0x52/0x70 [mt7921e] [ 5.080786] local_pci_probe+0x47/0x90 [ 5.080786] pci_call_probe+0x55/0x190 [ 5.080786] pci_device_probe+0x84/0x120

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

Security readout for executives and security teams

Plain-English summary

CVE-2023-53710 is a Linux kernel crash issue in the mt76/mt7921 Wi-Fi driver. If the system’s ACPI SAR table is invalid or poorly implemented, driver initialization can hit a NULL pointer dereference and kernel oops. The provided sources do not show data theft, privilege escalation, or active exploitation.

Executive priority

Handle through normal kernel patch management, with higher priority for fleets using mt7921 Wi-Fi hardware. Current evidence supports stability risk, not confirmed compromise risk, and severity remains unspecified in the supplied sources.

Technical view

The flaw is in mt7921_acpi_read error handling. A bad ACPI SAR table can be treated incorrectly, leading mt7921_init_acpi_sar to dereference NULL during mt7921 PCI probe and device registration. The Linux stable commits change the return behavior so the SAR table is marked invalid instead of continuing into the crash path.

Likely exposure

Exposure is likely limited to Linux systems loading the mt76 mt7921 Wi-Fi driver, especially hardware where ACPI SAR data is absent or malformed. The bundle lists Linux as affected, but exact version-range semantics are incomplete.

Exploitation context

The source bundle provides a kernel boot/probe crash trace, not a public exploit. CISA KEV status is false, and no cited source reports active exploitation. Treat this primarily as an availability and reliability risk unless vendor advisories add more impact detail.

Researcher notes

Evidence is narrow: a Linux kernel NULL pointer dereference during mt7921 PCI probe when ACPI SAR data is invalid. No CWE, CVSS, exploit maturity, or complete version-range data is supplied. Avoid extrapolating beyond denial-of-service style kernel crash impact.

Mitigation direction

  • Update to a Linux kernel containing the referenced stable fixes.
  • Check distribution advisories for backported kernel packages.
  • Prioritize systems with mt76/mt7921 Wi-Fi hardware.
  • Use vendor guidance if kernel upgrades are constrained.
  • Track future CVE/NVD updates for severity clarification.

Validation and detection

  • Inventory Linux endpoints for mt7921 or mt76 driver usage.
  • Confirm running kernel includes one of the referenced fixes or a distro backport.
  • Review boot logs for mt7921 ACPI SAR or NULL dereference errors.
  • Validate patched systems boot and initialize Wi-Fi normally.
  • Document affected hardware models and kernel versions.
Prepared
Confidence
medium
Sources
5

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-53710 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
4Source 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
LinuxLinuxf965333e491e36adb0fa91e389fba8685b704fb6, f965333e491e36adb0fa91e389fba8685b704fb6, f965333e491e36adb0fa91e389fba8685b704fb6unaffected
LinuxLinux6.0, 0, 6.1.16, 6.2.3, 6.3affected
Weakness

CWE details

No CWE listed

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