LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48824: scsi: myrs: Fix crash in error case

In the Linux kernel, the following vulnerability has been resolved: scsi: myrs: Fix crash in error case In myrs_detect(), cs->disable_intr is NULL when privdata->hw_init() fails with non-zero. In this case, myrs_cleanup(cs) will call a NULL ptr and crash the kernel. [ 1.105606] myrs 0000:00:03.0: Unknown Initialization Error 5A [ 1.105872] myrs 0000:00:03.0: Failed to initialize Controller [ 1.106082] BUG: kernel NULL pointer dereference, address: 0000000000000000 [ 1.110774] Call Trace: [ 1.110950] myrs_cleanup+0xe4/0x150 [myrs] [ 1.111135] myrs_probe.cold+0x91/0x56a [myrs] [ 1.111302] ? DAC960_GEM_intr_handler+0x1f0/0x1f0 [myrs] [ 1.111500] local_pci_probe+0x48/0x90

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash a system during initialization of the myrs SCSI driver if hardware initialization fails. The documented impact is denial of service through a kernel crash, not data theft or remote code execution.

Executive priority

Treat as a targeted availability risk. Patch through normal kernel maintenance, faster for systems dependent on affected storage hardware or where reboot-time crashes would disrupt service recovery.

Technical view

In myrs_detect(), a failed privdata->hw_init() can leave cs->disable_intr unset. The cleanup path then calls myrs_cleanup(cs), dereferences the NULL function pointer, and triggers a kernel NULL pointer dereference.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions where the myrs SCSI driver is present and exercised during controller probing. Confirm distro kernel backports rather than relying only on upstream version numbers.

Exploitation context

The provided sources do not show active exploitation, and CISA KEV is false. The crash is shown in an error path during driver initialization after an unknown controller initialization error.

Researcher notes

Evidence supports a NULL function pointer call in the myrs cleanup path after hw_init failure. Sources do not provide CVSS, CWE, exploitability analysis, or a remote attack path, so exposure assessment depends on driver reachability and hardware context.

Mitigation direction

  • Update to a kernel containing the referenced stable fixes.
  • Check Linux distribution advisories for backported fixes.
  • Disable or avoid loading the myrs driver if unused and operationally safe.
  • Prioritize systems using affected storage controller paths.

Validation and detection

  • Inventory kernels and loaded modules for myrs exposure.
  • Review boot logs for myrs initialization failures or NULL dereference traces.
  • Map installed kernel builds to vendor-fixed packages or upstream stable commits.
  • Confirm storage controller dependencies before disabling any driver.
Prepared
Confidence
medium
Sources
7

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-48824 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
6Source 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
LinuxLinux77266186397c6c782a3f670d32808a9671806ec5, 77266186397c6c782a3f670d32808a9671806ec5, 77266186397c6c782a3f670d32808a9671806ec5, 77266186397c6c782a3f670d32808a9671806ec5, 77266186397c6c782a3f670d32808a9671806ec5unaffected
LinuxLinux4.20, 0, 5.4.180, 5.10.101, 5.15.24, 5.16.10, 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.