LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48891: regulator: da9211: Use irq handler when ready

In the Linux kernel, the following vulnerability has been resolved: regulator: da9211: Use irq handler when ready If the system does not come from reset (like when it is kexec()), the regulator might have an IRQ waiting for us. If we enable the IRQ handler before its structures are ready, we crash. This patch fixes: [ 1.141839] Unable to handle kernel read from unreadable memory at virtual address 0000000000000078 [ 1.316096] Call trace: [ 1.316101] blocking_notifier_call_chain+0x20/0xa8 [ 1.322757] cpu cpu0: dummy supplies not allowed for exclusive requests [ 1.327823] regulator_notifier_call_chain+0x1c/0x2c [ 1.327825] da9211_irq_handler+0x68/0xf8 [ 1.327829] irq_thread+0x11c/0x234 [ 1.327833] kthread+0x13c/0x154

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-48891 is a Linux kernel crash bug in the DA9211 regulator driver. On systems that boot without a full reset, such as kexec, a pending interrupt can fire before driver structures are ready, causing a kernel crash. The evidence points to availability risk, not data theft.

Executive priority

Treat as a targeted availability issue. Patch through normal kernel maintenance, but accelerate for embedded, appliance, or high-availability systems where kexec is used and unexpected reboot crashes would affect operations.

Technical view

The DA9211 regulator driver enabled its IRQ handler before initialization data was ready. If an IRQ was already pending after a non-reset boot path, the handler could dereference unprepared state and trigger a kernel fault. Kernel stable commits reorder readiness around IRQ handling.

Likely exposure

Exposure appears limited to Linux systems using the DA9211 regulator driver on affected kernel builds, especially environments using kexec or other non-reset boot flows. General-purpose systems without this hardware or driver path are less likely to be exposed based on the provided sources.

Exploitation context

No KEV listing or cited source reports active exploitation. The described condition is a kernel crash from a pending hardware IRQ during driver initialization, not a remotely exploitable application flaw in the provided evidence.

Researcher notes

The source bundle does not provide CVSS, CWE, exploitability analysis, or distribution-specific fixed versions. The strongest evidence is the Linux kernel fix description and stable commit references. Avoid broad claims beyond DA9211, affected Linux builds, pending IRQ state, and crash impact.

Mitigation direction

  • Update to a Linux stable kernel containing the referenced DA9211 regulator fix.
  • Check distribution or device-vendor advisories for fixed package versions.
  • Prioritize affected systems using kexec or non-reset reboot workflows.
  • Avoid unnecessary kexec-based reboots on exposed systems until patched.

Validation and detection

  • Check whether deployed kernels include the referenced stable fix commits.
  • Identify systems loading or building the DA9211 regulator driver.
  • Review reboot architecture for kexec or non-reset boot paths.
  • Search kernel logs for DA9211 IRQ-handler crash traces.
Prepared
Confidence
medium
Sources
9

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-48891 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
1ADP providers
8Source 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

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1028a37daa148cc6cf85aa2aecb4390ddf1e1e56, 1028a37daa148cc6cf85aa2aecb4390ddf1e1e56, 1028a37daa148cc6cf85aa2aecb4390ddf1e1e56, 1028a37daa148cc6cf85aa2aecb4390ddf1e1e56, 1028a37daa148cc6cf85aa2aecb4390ddf1e1e56, 1028a37daa148cc6cf85aa2aecb4390ddf1e1e56, 1028a37daa148cc6cf85aa2aecb4390ddf1e1e56unaffected
LinuxLinux3.17, 0, 4.14.303, 4.19.270, 5.4.229, 5.10.164, 5.15.89, 6.1.7, 6.2affected
Weakness

CWE details

No CWE listed

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