Vulnerability-Lookup

GHSA-CJW9-X8QR-5WPF

Vulnerability from github – Published: 2025-04-16 15:34 – Updated: 2025-11-03 18:31

Details

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.

Severity

5.5 (Medium)


                  
                    CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2025-22122"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-04-16T15:16:06Z",
    "severity": "MODERATE"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nblock: fix adding folio to bio\n\n\u003e4GB folio is possible on some ARCHs, such as aarch64, 16GB hugepage\nis supported, then \u0027offset\u0027 of folio can\u0027t be held in \u0027unsigned int\u0027,\ncause warning in bio_add_folio_nofail() and IO failure.\n\nFix it by adjusting \u0027page\u0027 \u0026 trimming \u0027offset\u0027 so that `-\u003ebi_offset` won\u0027t\nbe overflow, and folio can be added to bio successfully.",
  "id": "GHSA-cjw9-x8qr-5wpf",
  "modified": "2025-11-03T18:31:15Z",
  "published": "2025-04-16T15:34:45Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-22122"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/0c60158ff14df04c92792dd9b1809372b095040f"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/26064d3e2b4d9a14df1072980e558c636fb023ea"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/b96e0af1b1c99cb7e6188b6fa4963a4e47beb01e"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ]
}

CVE-2025-22122 (GCVE-0-2025-22122)

Vulnerability from cvelistv5 – Published: 2025-04-16 14:13 – Updated: 2026-05-11 21:13

Title

block: fix adding folio to bio

Summary

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.

Severity

No CVSS data available.

Assigner

Linux CNA under the mitre root

CNA scorecard D 53/100 over 7018 records in the last 180 days details

References

3 references

URL	Tags
https://git.kernel.org/stable/c/0c60158ff14df04c9…
https://git.kernel.org/stable/c/b96e0af1b1c99cb7e…
https://git.kernel.org/stable/c/26064d3e2b4d9a14d…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: ed9832bc08db29874600eb066b74918fe6fc2060 , < 0c60158ff14df04c92792dd9b1809372b095040f (git) Affected: ed9832bc08db29874600eb066b74918fe6fc2060 , < b96e0af1b1c99cb7e6188b6fa4963a4e47beb01e (git) Affected: ed9832bc08db29874600eb066b74918fe6fc2060 , < 26064d3e2b4d9a14df1072980e558c636fb023ea (git)
Linux	Linux	Affected: 6.12 Unaffected: 0 , < 6.12 (semver) Unaffected: 6.12.33 , ≤ 6.12.* (semver) Unaffected: 6.14.2 , ≤ 6.14.* (semver) Unaffected: 6.15 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "block/bio.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "0c60158ff14df04c92792dd9b1809372b095040f",
              "status": "affected",
              "version": "ed9832bc08db29874600eb066b74918fe6fc2060",
              "versionType": "git"
            },
            {
              "lessThan": "b96e0af1b1c99cb7e6188b6fa4963a4e47beb01e",
              "status": "affected",
              "version": "ed9832bc08db29874600eb066b74918fe6fc2060",
              "versionType": "git"
            },
            {
              "lessThan": "26064d3e2b4d9a14df1072980e558c636fb023ea",
              "status": "affected",
              "version": "ed9832bc08db29874600eb066b74918fe6fc2060",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "block/bio.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.12"
            },
            {
              "lessThan": "6.12",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.33",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.14.*",
              "status": "unaffected",
              "version": "6.14.2",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.15",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.33",
                  "versionStartIncluding": "6.12",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.14.2",
                  "versionStartIncluding": "6.12",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.15",
                  "versionStartIncluding": "6.12",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nblock: fix adding folio to bio\n\n\u003e4GB folio is possible on some ARCHs, such as aarch64, 16GB hugepage\nis supported, then \u0027offset\u0027 of folio can\u0027t be held in \u0027unsigned int\u0027,\ncause warning in bio_add_folio_nofail() and IO failure.\n\nFix it by adjusting \u0027page\u0027 \u0026 trimming \u0027offset\u0027 so that `-\u003ebi_offset` won\u0027t\nbe overflow, and folio can be added to bio successfully."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-05-11T21:13:23.694Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/0c60158ff14df04c92792dd9b1809372b095040f"
        },
        {
          "url": "https://git.kernel.org/stable/c/b96e0af1b1c99cb7e6188b6fa4963a4e47beb01e"
        },
        {
          "url": "https://git.kernel.org/stable/c/26064d3e2b4d9a14df1072980e558c636fb023ea"
        }
      ],
      "title": "block: fix adding folio to bio",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2025-22122",
    "datePublished": "2025-04-16T14:13:06.509Z",
    "dateReserved": "2024-12-29T08:45:45.823Z",
    "dateUpdated": "2026-05-11T21:13:23.694Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

Order JSON

Publication & reservation Sightings KEV catalogs Other timestamps

Loading timeline…

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted