LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48798: s390/cio: verify the driver availability for path_event call

In the Linux kernel, the following vulnerability has been resolved: s390/cio: verify the driver availability for path_event call If no driver is attached to a device or the driver does not provide the path_event function, an FCES path-event on this device could end up in a kernel-panic. Verify the driver availability before the path_event function call.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel reliability flaw on s390 systems. A specific channel I/O path event can trigger a kernel panic when a device has no attached driver, or the driver lacks the needed handler. Business impact is service disruption on affected IBM Z/Linux workloads, not documented data theft or privilege escalation.

Executive priority

Treat this as a targeted availability risk for s390 Linux estates. It deserves timely kernel maintenance where IBM Z workloads are business-critical, but the provided evidence does not support emergency internet-wide response.

Technical view

The s390/cio code could call a device driver's path_event function without first verifying driver availability or handler support. The resolved change adds checks before that call, preventing a null or unsupported callback path from causing a kernel panic during an FCES path event.

Likely exposure

Exposure appears limited to Linux systems using the s390 architecture and cio subsystem, especially kernels in the affected version range noted by CVE data. Non-s390 Linux deployments are not indicated as affected by the provided sources.

Exploitation context

The source bundle does not show active exploitation, public exploit details, KEV listing, CVSS scoring, or a remote attack path. The demonstrated impact is kernel panic availability loss when the relevant path-event condition occurs.

Researcher notes

Evidence is narrow: the CVE text identifies a missing driver and handler availability check before path_event, with stable kernel commit references. No CWE, CVSS, exploitability analysis, or distribution-specific package matrix is provided in the bundle.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable fix commits.
  • Check distribution advisories for fixed s390 kernel package versions.
  • Prioritize affected production IBM Z/Linux systems with high availability requirements.
  • Apply normal change control and reboot planning for kernel updates.
  • If patch timing is unclear, ask the vendor for s390/cio-specific guidance.

Validation and detection

  • Inventory Linux hosts running on s390 or IBM Z platforms.
  • Compare running kernel versions against vendor fixed package guidance.
  • Confirm whether deployed kernels include the referenced stable commits.
  • Review outage records for unexplained kernel panics on s390/cio systems.
  • Verify patched systems no longer match affected kernel builds.
Prepared
Confidence
medium
Sources
5

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-48798 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
4Source 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
LinuxLinux32ef938815c1fb42d65212aac860ab153a64de1a, 32ef938815c1fb42d65212aac860ab153a64de1a, 32ef938815c1fb42d65212aac860ab153a64de1aunaffected
LinuxLinux5.11, 0, 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.