CVE-2026-53235 (GCVE-0-2026-53235)
Vulnerability from cvelistv5
Published
2026-06-25 08:39
Modified
2026-08-05 12:34
Summary
In the Linux kernel, the following vulnerability has been resolved: net: add pskb_may_pull() to skb_gro_receive_list() skb_gro_receive_list() calls skb_pull(skb, skb_gro_offset(skb)) without first ensuring the data is in the linear area via pskb_may_pull(). When the skb arrives via napi_gro_frags(), skb_headlen can be 0 (all data in page fragments) while skb_gro_offset is non-zero (after IP+TCP header parsing). The skb_pull() then decrements skb->len by skb_gro_offset but skb->data_len stays unchanged, hitting BUG_ON(skb->len < skb->data_len) in __skb_pull(). The UDP fraglist GRO path already contains this guard at udp_offload.c:749. Adding it to skb_gro_receive_list() itself provides centralized protection for all callers (TCP, UDP, and any future protocols), and ensures the precondition of skb_pull() is satisfied before it is called. On pskb_may_pull() failure, set NAPI_GRO_CB(skb)->flush = 1 so the skb is not held as a new GRO head and is instead delivered through the normal receive path, matching the UDP handling.
Impacted products
Vendor Product Version
Linux Linux Version: 8d95dc474f85481652a0e422d2f1f079de81f63c
Version: 8d95dc474f85481652a0e422d2f1f079de81f63c
Version: 8d95dc474f85481652a0e422d2f1f079de81f63c
Version: 8d95dc474f85481652a0e422d2f1f079de81f63c
Create a notification for this product.
Show details on NVD website


{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "net/core/gro.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "9e636c995b7beeb74ea882968248752821c244c4",
              "status": "affected",
              "version": "8d95dc474f85481652a0e422d2f1f079de81f63c",
              "versionType": "git"
            },
            {
              "lessThan": "0cde3a004119db637b401c54e77536e4145fc0b4",
              "status": "affected",
              "version": "8d95dc474f85481652a0e422d2f1f079de81f63c",
              "versionType": "git"
            },
            {
              "lessThan": "848571dcbbbea7ba44dd4f7ebe1fbb274afe08ac",
              "status": "affected",
              "version": "8d95dc474f85481652a0e422d2f1f079de81f63c",
              "versionType": "git"
            },
            {
              "lessThan": "f2bb3434544454099a5b6dec213567267b05d79d",
              "status": "affected",
              "version": "8d95dc474f85481652a0e422d2f1f079de81f63c",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "net/core/gro.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.10"
            },
            {
              "lessThan": "6.10",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.94",
              "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.12.94",
                  "versionStartIncluding": "6.10",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.36",
                  "versionStartIncluding": "6.10",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.0.13",
                  "versionStartIncluding": "6.10",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1",
                  "versionStartIncluding": "6.10",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: add pskb_may_pull() to skb_gro_receive_list()\n\nskb_gro_receive_list() calls skb_pull(skb, skb_gro_offset(skb)) without\nfirst ensuring the data is in the linear area via pskb_may_pull(). When\nthe skb arrives via napi_gro_frags(), skb_headlen can be 0 (all data in\npage fragments) while skb_gro_offset is non-zero (after IP+TCP header\nparsing). The skb_pull() then decrements skb-\u003elen by skb_gro_offset\nbut skb-\u003edata_len stays unchanged, hitting BUG_ON(skb-\u003elen \u003c skb-\u003edata_len)\nin __skb_pull().\n\nThe UDP fraglist GRO path already contains this guard at\nudp_offload.c:749. Adding it to skb_gro_receive_list() itself provides\ncentralized protection for all callers (TCP, UDP, and any future\nprotocols), and ensures the precondition of skb_pull() is satisfied\nbefore it is called.\n\nOn pskb_may_pull() failure, set NAPI_GRO_CB(skb)-\u003eflush = 1 so the\nskb is not held as a new GRO head and is instead delivered through the\nnormal receive path, matching the UDP handling."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.5,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:N - The vulnerable GRO path processes received IPv4/IPv6 TCP packets in the network stack before socket authentication or routing decisions. A remote peer can send crafted same-flow packets to an exposed interface with fraglist GRO enabled.\nAC:L - Given a vulnerable deployment with rx-gro-list enabled, the attacker controls the packet stream, header layout, checksums, and sequencing needed to reach skb_gro_receive_list(). No race or victim state outside the attacker\u2019s packet timing is required.\nPR:N - The code runs on unauthenticated packet receive before any application or TCP connection authorization. No local account or kernel capability is required for a remote sender.\nUI:N - Exploitation only requires packet delivery to the target network interface. No victim user action is needed.\nS:U - The impact is within the kernel/network stack security authority of the targeted system. There is no VM, IOMMU, or sandbox boundary crossing.\nC:N - The bug triggers an internal skb length invariant failure in __skb_pull() and immediately BUGs. I found no out-of-bounds read, use-after-free, or usable information disclosure primitive before the crash.\nI:N - The vulnerable operation corrupts skb metadata only enough to trip the immediate BUG_ON path. It does not provide an attacker-controlled write or persistent data modification primitive.\nA:H - The reachable failure is BUG() in __skb_pull(), causing a kernel oops/panic or loss of system availability. A remote attacker can repeat the packet sequence to repeatedly crash affected deployments."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T12:34:24.581Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/9e636c995b7beeb74ea882968248752821c244c4"
        },
        {
          "url": "https://git.kernel.org/stable/c/0cde3a004119db637b401c54e77536e4145fc0b4"
        },
        {
          "url": "https://git.kernel.org/stable/c/848571dcbbbea7ba44dd4f7ebe1fbb274afe08ac"
        },
        {
          "url": "https://git.kernel.org/stable/c/f2bb3434544454099a5b6dec213567267b05d79d"
        }
      ],
      "title": "net: add pskb_may_pull() to skb_gro_receive_list()",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-53235",
    "datePublished": "2026-06-25T08:39:32.518Z",
    "dateReserved": "2026-06-09T07:44:35.393Z",
    "dateUpdated": "2026-08-05T12:34:24.581Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.


Loading…

Loading…