Vulnerability-Lookup

GHSA-7XF9-R6GC-X4CM

Vulnerability from github – Published: 2026-07-10 12:31 – Updated: 2026-07-18 09:32

Details

In the Linux kernel, the following vulnerability has been resolved:

xfrm: iptfs: preserve shared-frag marker in iptfs_consume_frags()

iptfs_consume_frags() transfers paged fragments from one socket buffer to another but fails to propagate the SKBFL_SHARED_FRAG flag. This is the same class of bug that was fixed in skb_try_coalesce() for CVE-2026-46300: when fragments backed by read-only page-cache pages are merged, the marker indicating their shared nature must be preserved so that ESP can decide correctly whether in-place encryption is safe.

Apply the same two-line fix used in skb_try_coalesce() to iptfs_consume_frags().

Severity

9.8 (Critical)


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

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-53363"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-07-10T12:17:22Z",
    "severity": "CRITICAL"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: iptfs: preserve shared-frag marker in iptfs_consume_frags()\n\niptfs_consume_frags() transfers paged fragments from one socket buffer\nto another but fails to propagate the SKBFL_SHARED_FRAG flag. This is\nthe same class of bug that was fixed in skb_try_coalesce() for\nCVE-2026-46300: when fragments backed by read-only page-cache pages are\nmerged, the marker indicating their shared nature must be preserved so\nthat ESP can decide correctly whether in-place encryption is safe.\n\nApply the same two-line fix used in skb_try_coalesce() to\niptfs_consume_frags().",
  "id": "GHSA-7xf9-r6gc-x4cm",
  "modified": "2026-07-18T09:32:16Z",
  "published": "2026-07-10T12:31:44Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-53363"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/c885d111ed9f5a0a1f3cc4e87a50db6518abaa6c"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/dd66f7f6e360ee82cd905517726f8e9091265de5"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/e9096a5a170e7ecd6467bc2e08668ec39897cda7"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}

CVE-2026-53363 (GCVE-0-2026-53363)

Vulnerability from cvelistv5 – Published: 2026-07-10 11:55 – Updated: 2026-08-05 12:35

Title

xfrm: iptfs: preserve shared-frag marker in iptfs_consume_frags()

Summary

In the Linux kernel, the following vulnerability has been resolved: xfrm: iptfs: preserve shared-frag marker in iptfs_consume_frags() iptfs_consume_frags() transfers paged fragments from one socket buffer to another but fails to propagate the SKBFL_SHARED_FRAG flag. This is the same class of bug that was fixed in skb_try_coalesce() for CVE-2026-46300: when fragments backed by read-only page-cache pages are merged, the marker indicating their shared nature must be preserved so that ESP can decide correctly whether in-place encryption is safe. Apply the same two-line fix used in skb_try_coalesce() to iptfs_consume_frags().

Severity

9.8 (Critical)


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

Assigner

Linux mitre root Scorecard

References

3 references

URL	Tags
https://git.kernel.org/stable/c/dd66f7f6e360ee82c…
https://git.kernel.org/stable/c/c885d111ed9f5a0a1…
https://git.kernel.org/stable/c/e9096a5a170e7ecd6…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: b96ba312e21c9b7ac1526829b9640ddc06695c0b , < dd66f7f6e360ee82cd905517726f8e9091265de5 (git) Affected: b96ba312e21c9b7ac1526829b9640ddc06695c0b , < c885d111ed9f5a0a1f3cc4e87a50db6518abaa6c (git) Affected: b96ba312e21c9b7ac1526829b9640ddc06695c0b , < e9096a5a170e7ecd6467bc2e08668ec39897cda7 (git)
Linux	Linux	Affected: 6.14 Unaffected: 0 , < 6.14 (semver) Unaffected: 6.18.36 , ≤ 6.18.* (semver) Unaffected: 7.0.13 , ≤ 7.0.* (semver) Unaffected: 7.1 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "net/xfrm/xfrm_iptfs.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "dd66f7f6e360ee82cd905517726f8e9091265de5",
              "status": "affected",
              "version": "b96ba312e21c9b7ac1526829b9640ddc06695c0b",
              "versionType": "git"
            },
            {
              "lessThan": "c885d111ed9f5a0a1f3cc4e87a50db6518abaa6c",
              "status": "affected",
              "version": "b96ba312e21c9b7ac1526829b9640ddc06695c0b",
              "versionType": "git"
            },
            {
              "lessThan": "e9096a5a170e7ecd6467bc2e08668ec39897cda7",
              "status": "affected",
              "version": "b96ba312e21c9b7ac1526829b9640ddc06695c0b",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "net/xfrm/xfrm_iptfs.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.14"
            },
            {
              "lessThan": "6.14",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.36",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.0.*",
              "status": "unaffected",
              "version": "7.0.13",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.36",
                  "versionStartIncluding": "6.14",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.0.13",
                  "versionStartIncluding": "6.14",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1",
                  "versionStartIncluding": "6.14",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: iptfs: preserve shared-frag marker in iptfs_consume_frags()\n\niptfs_consume_frags() transfers paged fragments from one socket buffer\nto another but fails to propagate the SKBFL_SHARED_FRAG flag. This is\nthe same class of bug that was fixed in skb_try_coalesce() for\nCVE-2026-46300: when fragments backed by read-only page-cache pages are\nmerged, the marker indicating their shared nature must be preserved so\nthat ESP can decide correctly whether in-place encryption is safe.\n\nApply the same two-line fix used in skb_try_coalesce() to\niptfs_consume_frags()."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 9.8,
            "baseSeverity": "CRITICAL",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:N - An unauthenticated remote peer can trigger the vulnerable outbound IP-TFS ESP aggregation path by causing a network service to send file-backed splice/sendfile data through an already configured IP-TFS tunnel. A local user namespace setup is also possible, but Network is the higher defensible vector.\nAC:L - No race or uncontrollable timing is required; the attacker can shape request sizes and traffic volume so shared-frag skbs are aggregated before ESP processing. The required IP-TFS configuration is the vulnerable operating mode, not an exploitation complexity barrier.\nPR:N - The remote-service scenario requires no attacker privileges once the target already uses IP-TFS/IPsec for that traffic. Although creating XFRM state requires CAP_NET_ADMIN, that gate is not crossed by the remote attacker and is also namespace-reachable for local reproduction.\nUI:N - No human action is needed after the affected tunnel/service is running. Packets and service responses drive the vulnerable path automatically.\nS:U - The corruption occurs within the same kernel/system security authority and does not cross a VM, IOMMU, or separate sandbox boundary. Standard kernel or page-cache compromise remains Scope Unchanged.\nC:H - The lost marker permits ESP crypto to operate on externally owned/page-cache-backed fragments as if privately owned, creating cross-object memory corruption in kernel-managed cache pages. Under the required higher-severity assumption, that corruption can support sensitive data exposure or further exploitation.\nI:H - Similar shared-frag fixes explicitly describe writes into the page cache of root-owned read-only files; this bug preserves that class of externally backed page corruption through IP-TFS aggregation. That is a high-integrity impact because attacker-influenced crypto output can modify data outside the skb\u2019s ownership.\nA:H - Corrupting page-cache-backed executable, library, or service data can crash or destabilize privileged processes and repeatedly disrupt the affected system. Kernel-managed memory corruption is therefore a high availability impact."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T12:35:13.152Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/dd66f7f6e360ee82cd905517726f8e9091265de5"
        },
        {
          "url": "https://git.kernel.org/stable/c/c885d111ed9f5a0a1f3cc4e87a50db6518abaa6c"
        },
        {
          "url": "https://git.kernel.org/stable/c/e9096a5a170e7ecd6467bc2e08668ec39897cda7"
        }
      ],
      "title": "xfrm: iptfs: preserve shared-frag marker in iptfs_consume_frags()",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-53363",
    "datePublished": "2026-07-10T11:55:31.820Z",
    "dateReserved": "2026-06-09T07:44:35.400Z",
    "dateUpdated": "2026-08-05T12:35:13.152Z",
    "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.

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

GHSA-7XF9-R6GC-X4CM

CVE-2026-53363 (GCVE-0-2026-53363)

Tags

Sightings

Nomenclature

Related by attack behaviour