LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49385: driver: base: fix UAF when driver_attach failed

In the Linux kernel, the following vulnerability has been resolved: driver: base: fix UAF when driver_attach failed When driver_attach(drv); failed, the driver_private will be freed. But it has been added to the bus, which caused a UAF. To fix it, we need to delete it from the bus when failed.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Linux kernel flaw is a use-after-free bug in driver attachment failure handling. A local low-privileged user may be able to trigger kernel memory corruption with high confidentiality, integrity, and availability impact. It is not described as remotely exploitable in the provided sources.

Executive priority

Treat as high priority for Linux fleets with local users or untrusted workloads. It is less urgent than remotely exploitable KEV-listed issues, but kernel memory corruption can materially affect host isolation and service reliability.

Technical view

When driver_attach(drv) fails, driver_private can be freed while still linked to the bus, creating a use-after-free condition. The kernel fix removes it from the bus on failure. The CVSS vector is local, low complexity, low privileges, no user interaction, with high CIA impact.

Likely exposure

Exposure is most relevant on systems running affected Linux kernel versions, especially shared servers, developer workstations, container hosts, and environments where low-privileged local users or workloads can execute code.

Exploitation context

The provided bundle marks CISA KEV as false and gives no cited evidence of active exploitation. Exploitation requires local low-privileged access; remote-only exposure is not supported by the supplied sources.

Researcher notes

The source evidence identifies CWE-416 and stable kernel commits but does not provide exploit details or clear distro package mappings. Validation should focus on kernel provenance, branch backports, and whether local attack preconditions exist.

Mitigation direction

  • Apply Linux kernel updates containing the referenced stable fixes.
  • Use distribution vendor advisories to map fixes to packaged kernel versions.
  • Prioritize multi-user, container, and externally managed workload hosts.
  • Restrict untrusted local shell or workload access where patching is delayed.
  • Monitor vendor guidance if no packaged fix is available.

Validation and detection

  • Inventory Linux kernel versions across servers, workstations, and images.
  • Compare running kernels with vendor advisories for CVE-2022-49385.
  • Confirm patched builds include the referenced stable kernel commits.
  • Review high-risk hosts allowing local untrusted code execution.
  • Verify reboot into the updated kernel after patch deployment.
Prepared
Confidence
medium
Sources
8

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.

cwe · low confidence lookup

CWE-416: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-49385 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

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

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.

1CVSS vectors
3Timeline events
1ADP providers
7Source links

SSVC decision data

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2022-49385Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux190888ac01d059e38ffe77a2291d44cafa9016fb, 190888ac01d059e38ffe77a2291d44cafa9016fb, 190888ac01d059e38ffe77a2291d44cafa9016fb, 190888ac01d059e38ffe77a2291d44cafa9016fb, 190888ac01d059e38ffe77a2291d44cafa9016fb, 190888ac01d059e38ffe77a2291d44cafa9016fbunaffected
LinuxLinux3.9, 0, 5.4.198, 5.10.122, 5.15.47, 5.17.15, 5.18.4, 5.19affected
Weakness

CWE details

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

CWE-416 · source CWE mapping

Use After Free

Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.