LiveActive security incident?Get immediate response
CVE Record

CVE-2025-22122: block: fix adding folio to bio

In the Linux kernel, the following vulnerability has been resolved: block: fix adding folio to bio >4GB folio is possible on some ARCHs, such as aarch64, 16GB hugepage is supported, then 'offset' of folio can't be held in 'unsigned int', cause warning in bio_add_folio_nofail() and IO failure. Fix it by adjusting 'page' & trimming 'offset' so that `->bi_offset` won't be overflow, and folio can be added to bio successfully.

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

Security readout for executives and security teams

Plain-English summary

A Linux kernel block I/O bug can break I/O when very large memory folios are added to a bio. The source describes architectures such as aarch64 with 16GB hugepages. Business impact is reliability rather than confirmed compromise: affected systems may hit warnings and I/O failures under specific large-page conditions.

Executive priority

Treat as a targeted reliability patch, not an emergency breach response based on current evidence. Prioritize affected Linux infrastructure with large hugepage use, storage sensitivity, or aarch64 deployments, and fold remediation into the next kernel maintenance window unless vendor guidance raises urgency.

Technical view

The kernel block layer used an unsigned int-sized offset when adding a folio to a bio. For folios larger than 4GB, the offset can overflow bi_offset handling. The upstream fix adjusts the page and trims the offset so bio_add_folio_nofail() can add the folio without overflowing.

Likely exposure

Exposure appears limited to Linux systems on affected kernel versions/builds that can create folios over 4GB, especially architectures with very large hugepage support. Confirm against your distribution kernel, because distro backports may not match upstream version numbers.

Exploitation context

The provided sources do not report active exploitation, public exploit use, or CISA KEV listing. Evidence supports an operational failure condition, not a demonstrated attacker workflow. Severity and CVSS are not supplied.

Researcher notes

Key evidence is the upstream kernel fix text. The issue is offset width/overflow in block bio folio handling for >4GB folios. The bundle lacks CVSS, CWE, exploitability analysis, and exact downstream distro fixed versions, so risk scoring should remain cautious.

Mitigation direction

  • Update to a kernel or distro package containing the referenced stable fixes.
  • Prioritize aarch64 or hugepage-heavy systems that may create folios over 4GB.
  • Follow distribution advisories; do not infer fixed status from upstream version numbers alone.
  • If no packaged fix exists, seek vendor guidance for supported kernel options.
  • Monitor for kernel warnings and I/O failures related to bio_add_folio_nofail().

Validation and detection

  • Inventory kernel versions and map them to vendor advisories for CVE-2025-22122.
  • Check whether hosts use architectures and hugepage settings capable of folios over 4GB.
  • Review kernel logs for bio_add_folio_nofail() warnings or unexplained block I/O failures.
  • Confirm fixed kernels include one of the referenced stable commits or a vendor backport.
  • Retest affected storage workloads after patching to verify I/O completion.
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-2025-22122 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
0ADP providers
4Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxed9832bc08db29874600eb066b74918fe6fc2060, ed9832bc08db29874600eb066b74918fe6fc2060, ed9832bc08db29874600eb066b74918fe6fc2060unaffected
LinuxLinux6.12, 0, 6.12.33, 6.14.2, 6.15affected
Weakness

CWE details

No CWE listed

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