Vulnerability-Lookup

GHSA-2FW9-6RFH-9Q85

Vulnerability from github – Published: 2026-10-23 12:31 – Updated: 2026-10-23 12:31

Details

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

net: lan966x: restore RX state on reload failure

lan966x_fdma_reload() backs up rx->page_pool and rx->fdma before reallocating the RX resources for the new MTU. If the allocation fails, the restore path puts these fields back before restarting RX.

However, the reload path also updates rx->page_order and rx->max_mtu before calling lan966x_fdma_rx_alloc(). These fields are not restored on failure, so RX can be restarted with the old pages, old FDMA state and old page pool, but with the page geometry from the failed new MTU.

This can make the XDP path advertise a frame size derived from the new page_order while the actual RX pages still come from the old allocation. For example, after a failed reload to a jumbo MTU, xdp_init_buff() may be called with a frame size larger than the restored RX pages.

lan966x_fdma_rx_alloc_page_pool() also registers the newly allocated page pool with each port's XDP RXQ before fdma_alloc_coherent() is called. If fdma_alloc_coherent() fails, the new page pool is destroyed, but the rollback path does not restore the per-port XDP RXQ mem model registration either.

Save and restore rx->page_order and rx->max_mtu, and restore the old page pool registration for each port's XDP RXQ before RX is started again. This keeps the restored RX state consistent after a failed reload.

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-98906"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-10-23T12:18:24Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: lan966x: restore RX state on reload failure\n\nlan966x_fdma_reload() backs up rx-\u003epage_pool and rx-\u003efdma before\nreallocating the RX resources for the new MTU. If the allocation fails,\nthe restore path puts these fields back before restarting RX.\n\nHowever, the reload path also updates rx-\u003epage_order and rx-\u003emax_mtu\nbefore calling lan966x_fdma_rx_alloc(). These fields are not restored on\nfailure, so RX can be restarted with the old pages, old FDMA state and\nold page pool, but with the page geometry from the failed new MTU.\n\nThis can make the XDP path advertise a frame size derived from the new\npage_order while the actual RX pages still come from the old allocation.\nFor example, after a failed reload to a jumbo MTU, xdp_init_buff() may be\ncalled with a frame size larger than the restored RX pages.\n\nlan966x_fdma_rx_alloc_page_pool() also registers the newly allocated page\npool with each port\u0027s XDP RXQ before fdma_alloc_coherent() is called. If\nfdma_alloc_coherent() fails, the new page pool is destroyed, but the\nrollback path does not restore the per-port XDP RXQ mem model\nregistration either.\n\nSave and restore rx-\u003epage_order and rx-\u003emax_mtu, and restore the old page\npool registration for each port\u0027s XDP RXQ before RX is started again.\nThis keeps the restored RX state consistent after a failed reload.",
  "id": "GHSA-2fw9-6rfh-9q85",
  "modified": "2026-10-23T12:31:37Z",
  "published": "2026-10-23T12:31:37Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98906"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/3883898ddc26308497dbba8068951ab5eddbd111"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/aa97f11a76e545ed73cc455bcdd1ece4b480b507"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/b5a6462f4646687c922931133a2478da94addc87"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

CVE-2026-98906 (GCVE-0-2026-98906)

Vulnerability from cvelistv5 – Published: 2026-10-23 11:54 – Updated: 2026-10-26 06:56

Title

net: lan966x: restore RX state on reload failure

Summary

In the Linux kernel, the following vulnerability has been resolved: net: lan966x: restore RX state on reload failure lan966x_fdma_reload() backs up rx->page_pool and rx->fdma before reallocating the RX resources for the new MTU. If the allocation fails, the restore path puts these fields back before restarting RX. However, the reload path also updates rx->page_order and rx->max_mtu before calling lan966x_fdma_rx_alloc(). These fields are not restored on failure, so RX can be restarted with the old pages, old FDMA state and old page pool, but with the page geometry from the failed new MTU. This can make the XDP path advertise a frame size derived from the new page_order while the actual RX pages still come from the old allocation. For example, after a failed reload to a jumbo MTU, xdp_init_buff() may be called with a frame size larger than the restored RX pages. lan966x_fdma_rx_alloc_page_pool() also registers the newly allocated page pool with each port's XDP RXQ before fdma_alloc_coherent() is called. If fdma_alloc_coherent() fails, the new page pool is destroyed, but the rollback path does not restore the per-port XDP RXQ mem model registration either. Save and restore rx->page_order and rx->max_mtu, and restore the old page pool registration for each port's XDP RXQ before RX is started again. This keeps the restored RX state consistent after a failed reload.

Severity

No CVSS data available.

Assigner

Linux CNA under the mitre root

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

References

3 references

URL	Tags
https://git.kernel.org/stable/c/3883898ddc2630849…
https://git.kernel.org/stable/c/b5a6462f4646687c9…
https://git.kernel.org/stable/c/aa97f11a76e545ed7…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: 2ea1cbac267e2a39546982612fc00084b6d93e40 , < 3883898ddc26308497dbba8068951ab5eddbd111 (git) Affected: 2ea1cbac267e2a39546982612fc00084b6d93e40 , < b5a6462f4646687c922931133a2478da94addc87 (git) Affected: 2ea1cbac267e2a39546982612fc00084b6d93e40 , < aa97f11a76e545ed73cc455bcdd1ece4b480b507 (git)
Linux	Linux	Affected: 5.19 Unaffected: 0 , < 5.19 (semver) Unaffected: 6.12.111 , ≤ 6.12.* (semver) Unaffected: 6.18.53 , ≤ 6.18.* (semver) Unaffected: 7.2 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/net/ethernet/microchip/lan966x/lan966x_fdma.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "3883898ddc26308497dbba8068951ab5eddbd111",
              "status": "affected",
              "version": "2ea1cbac267e2a39546982612fc00084b6d93e40",
              "versionType": "git"
            },
            {
              "lessThan": "b5a6462f4646687c922931133a2478da94addc87",
              "status": "affected",
              "version": "2ea1cbac267e2a39546982612fc00084b6d93e40",
              "versionType": "git"
            },
            {
              "lessThan": "aa97f11a76e545ed73cc455bcdd1ece4b480b507",
              "status": "affected",
              "version": "2ea1cbac267e2a39546982612fc00084b6d93e40",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/net/ethernet/microchip/lan966x/lan966x_fdma.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.19"
            },
            {
              "lessThan": "5.19",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.111",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.53",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.2",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.111",
                  "versionStartIncluding": "5.19",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.53",
                  "versionStartIncluding": "5.19",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2",
                  "versionStartIncluding": "5.19",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: lan966x: restore RX state on reload failure\n\nlan966x_fdma_reload() backs up rx-\u003epage_pool and rx-\u003efdma before\nreallocating the RX resources for the new MTU. If the allocation fails,\nthe restore path puts these fields back before restarting RX.\n\nHowever, the reload path also updates rx-\u003epage_order and rx-\u003emax_mtu\nbefore calling lan966x_fdma_rx_alloc(). These fields are not restored on\nfailure, so RX can be restarted with the old pages, old FDMA state and\nold page pool, but with the page geometry from the failed new MTU.\n\nThis can make the XDP path advertise a frame size derived from the new\npage_order while the actual RX pages still come from the old allocation.\nFor example, after a failed reload to a jumbo MTU, xdp_init_buff() may be\ncalled with a frame size larger than the restored RX pages.\n\nlan966x_fdma_rx_alloc_page_pool() also registers the newly allocated page\npool with each port\u0027s XDP RXQ before fdma_alloc_coherent() is called. If\nfdma_alloc_coherent() fails, the new page pool is destroyed, but the\nrollback path does not restore the per-port XDP RXQ mem model\nregistration either.\n\nSave and restore rx-\u003epage_order and rx-\u003emax_mtu, and restore the old page\npool registration for each port\u0027s XDP RXQ before RX is started again.\nThis keeps the restored RX state consistent after a failed reload."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-26T06:56:35.317Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/3883898ddc26308497dbba8068951ab5eddbd111"
        },
        {
          "url": "https://git.kernel.org/stable/c/b5a6462f4646687c922931133a2478da94addc87"
        },
        {
          "url": "https://git.kernel.org/stable/c/aa97f11a76e545ed73cc455bcdd1ece4b480b507"
        }
      ],
      "title": "net: lan966x: restore RX state on reload failure",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-98906",
    "datePublished": "2026-10-23T11:54:42.697Z",
    "dateReserved": "2026-09-25T10:25:14.379Z",
    "dateUpdated": "2026-10-26T06:56:35.317Z",
    "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