CVE-2022-49868: phy: ralink: mt7621-pci: add sentinel to quirks table
In the Linux kernel, the following vulnerability has been resolved:
phy: ralink: mt7621-pci: add sentinel to quirks table
With mt7621 soc_dev_attr fixed to register the soc as a device,
kernel will experience an oops in soc_device_match_attr
This quirk test was introduced in the staging driver in
commit 9445ccb3714c ("staging: mt7621-pci-phy: add quirks for 'E2'
revision using 'soc_device_attribute'"). The staging driver was removed,
and later re-added in commit d87da32372a0 ("phy: ralink: Add PHY driver
for MT7621 PCIe PHY") for kernel 5.11
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel reliability issue affecting systems using the Ralink/MediaTek MT7621 PCIe PHY driver. A missing end marker in a quirks table can cause a kernel oops after related SoC device registration behavior changed. The public data does not show business-impact details beyond crash risk.
Executive priority
Handle through normal kernel maintenance unless MT7621-based devices are operationally critical. There is no provided evidence of exploitation or remote compromise, but kernel oops conditions can affect availability on embedded infrastructure.
Technical view
The fix adds a sentinel to the MT7621 PCIe PHY quirks table. Without it, soc_device_match_attr can read past the intended table and trigger an oops. The issue traces to the driver reintroduced for Linux 5.11 and is addressed by referenced Linux stable commits.
Likely exposure
Exposure appears limited to Linux systems with affected kernel versions and MT7621 PCIe PHY driver/hardware paths. The source bundle lists Linux 5.11, 5.15.79, 6.0.9, and 6.1 as affected markers but does not provide distro package mapping.
Exploitation context
No active exploitation is supported by the provided sources. KEV is false, and the bundle contains no public exploit report, attacker model, or remote trigger details. Treat this as a kernel stability flaw unless vendor guidance says otherwise.
Researcher notes
The source data is sparse: no CVSS, CWE, exploitability analysis, or distro advisories are provided. The clearest technical signal is the missing sentinel in the quirks table causing soc_device_match_attr oops behavior after SoC device registration changes.
Mitigation direction
Update to a kernel containing the referenced Linux stable fixes.
Check distro or device-vendor advisories for patched kernel or firmware builds.
Prioritize MT7621-based routers, gateways, and embedded Linux appliances.
If patching is delayed, monitor for kernel oops events involving soc_device_match_attr.
Validation and detection
Inventory systems using Linux kernels in the affected range.
Identify MT7621 or Ralink PCIe PHY hardware and driver usage.
Confirm the running kernel includes one of the referenced stable commits.
Review kernel logs for oops traces around soc_device_match_attr.
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-2022-49868 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
May 1, 2025, 14:10 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.