LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48854: net: arc_emac: Fix use after free in arc_mdio_probe()

In the Linux kernel, the following vulnerability has been resolved: net: arc_emac: Fix use after free in arc_mdio_probe() If bus->state is equal to MDIOBUS_ALLOCATED, mdiobus_free(bus) will free the "bus". But bus->name is still used in the next line, which will lead to a use after free. We can fix it by putting the name in a local variable and make the bus->name point to the rodata section "name",then use the name in the error message without referring to bus to avoid the uaf.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel use-after-free bug in the ARC EMAC network driver error path. The public record does not provide a CVSS score, business impact rating, or evidence of active exploitation. Risk depends on whether affected kernels and the arc_emac driver are present in your fleet.

Executive priority

Treat this as a kernel maintenance item until local exposure is proven. Prioritize embedded, appliance, or custom Linux systems using ARC EMAC hardware, and rely on vendor kernel updates rather than ad hoc fixes.

Technical view

In arc_mdio_probe(), mdiobus_free(bus) can free the MDIO bus when bus->state is MDIOBUS_ALLOCATED, but the following error message still references bus->name. The fix avoids referencing freed memory by using a stable local name value. Public sources identify Linux kernel versions around 5.16 and stable fix commits.

Likely exposure

Most exposure is likely on Linux systems using the arc_emac Ethernet driver and affected kernel builds. The sources do not enumerate distributions, devices, or configurations, so teams must map kernel versions and vendor backports locally.

Exploitation context

The CVE source bundle says KEV is false and provides no cited evidence of exploitation in the wild. The issue appears tied to a driver probe error path, not a documented remote attack path.

Researcher notes

The available record is narrow: a resolved Linux kernel use-after-free with two stable commit references, no CVSS, no CWE, and no exploitation evidence. Focus analysis on version lineage, vendor backports, driver reachability, and whether the probe error path is practically reachable.

Mitigation direction

  • Identify Linux assets running affected 5.16-era kernels or vendor backports.
  • Apply vendor kernel updates containing the referenced stable fixes.
  • Check distribution advisories for exact package versions and backport status.
  • If updating is delayed, assess whether arc_emac is present and required.
  • Do not disable network drivers without vendor and operations approval.

Validation and detection

  • Inventory running kernel versions across affected asset classes.
  • Check kernel build configuration or modules for arc_emac usage.
  • Confirm the relevant stable fix commit or vendor backport is present.
  • Review boot and kernel logs for arc_emac or MDIO probe errors.
  • Re-run normal network interface validation after kernel updates.
Prepared
Confidence
medium
Sources
4

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-2022-48854 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
2ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux95b5fc03c189e4ea5c63785274cc0b77fcc3a818, 95b5fc03c189e4ea5c63785274cc0b77fcc3a818unaffected
LinuxLinux5.16, 0, 5.16.15, 5.17affected
Weakness

CWE details

No CWE listed

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