LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48801: iio: buffer: Fix file related error handling in IIO_BUFFER_GET_FD_IOCTL

In the Linux kernel, the following vulnerability has been resolved: iio: buffer: Fix file related error handling in IIO_BUFFER_GET_FD_IOCTL If we fail to copy the just created file descriptor to userland, we try to clean up by putting back 'fd' and freeing 'ib'. The code uses put_unused_fd() for the former which is wrong, as the file descriptor was already published by fd_install() which gets called internally by anon_inode_getfd(). This makes the error handling code leaving a half cleaned up file descriptor table around and a partially destructed 'file' object, allowing userland to play use-after-free tricks on us, by abusing the still usable fd and making the code operate on a dangling 'file->private_data' pointer. Instead of leaving the kernel in a partially corrupted state, don't attempt to explicitly clean up and leave this to the process exit path that'll release any still valid fds, including the one created by the previous call to anon_inode_getfd(). Simply return -EFAULT to indicate the error.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-48801 is a Linux kernel flaw in the Industrial I/O buffer interface. A failed file-descriptor copy can leave kernel cleanup in an unsafe state, creating a use-after-free condition. This is most relevant to systems where local users or software can access the affected IIO buffer ioctl path.

Executive priority

Treat as a routine but important Linux kernel patching item. It is not reported as actively exploited in the provided sources, but kernel use-after-free bugs can affect system integrity when reachable by local users or workloads.

Technical view

The issue is in IIO_BUFFER_GET_FD_IOCTL error handling. After anon_inode_getfd() publishes a file descriptor, the code incorrectly uses put_unused_fd() during cleanup if copying the descriptor to user space fails. That can leave a usable fd tied to partially destructed file private data, enabling use-after-free behavior.

Likely exposure

Exposure appears local to Linux systems running affected kernel versions with access to the Industrial I/O buffer interface. The CVE record lists Linux kernel versions around 5.13 and fixes in stable kernel commits. Distribution backports may change version-based exposure, so validate against vendor kernel packages.

Exploitation context

The public CVE text describes a userland-triggerable use-after-free scenario but provides no CVSS score and no cited evidence of active exploitation. CISA KEV status is false in the provided bundle. Exploitation would require access to the affected kernel interface rather than remote network access.

Researcher notes

Evidence is limited to the CVE record and upstream stable commits. The vulnerability is an error-path cleanup bug after fd publication. The provided data does not include exploitability assessment, affected distributions, CVSS, or practical prerequisites beyond the IIO buffer ioctl path.

Mitigation direction

  • Update to a vendor-supported kernel containing the referenced stable fixes.
  • Prioritize systems exposing Industrial I/O interfaces to local users or applications.
  • Check Linux distribution advisories for backported fixes and package names.
  • If patching is delayed, restrict untrusted local access where feasible.

Validation and detection

  • Inventory Linux kernel versions across affected assets.
  • Map distribution kernel packages to the referenced upstream stable commits.
  • Review whether systems use or expose Industrial I/O buffer functionality.
  • Confirm vulnerability status through vendor advisories, not upstream version alone.
  • Monitor CVE and kernel stable references for later corrections.
Prepared
Confidence
medium
Sources
5

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-48801 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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf73f7f4da581875f9b1f2fb8ebd1ab15ed634488, f73f7f4da581875f9b1f2fb8ebd1ab15ed634488, f73f7f4da581875f9b1f2fb8ebd1ab15ed634488unaffected
LinuxLinux5.13, 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.