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

Vulnerability from cvelistv5 – Published: 2026-10-23 11:54 – Updated: 2026-10-26 06:56
VLAI
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 6637 records in the last 180 days details
References
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: 2ea1cbac267e2a39546982612fc00084b6d93e40 , < 3883898ddc26308497dbba8068951ab5eddbd111 (git)
Affected: 2ea1cbac267e2a39546982612fc00084b6d93e40 , < b5a6462f4646687c922931133a2478da94addc87 (git)
Affected: 2ea1cbac267e2a39546982612fc00084b6d93e40 , < aa97f11a76e545ed73cc455bcdd1ece4b480b507 (git)
guessed Create a notification for this product.
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)
guessed Create a notification for this product.
Show details on NVD website
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",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-98906",
      "date": "2026-11-04",
      "epss": "0.00172",
      "percentile": "0.06652"
    },
    "microsoft_vex": {
      "current_release_date": "2026-11-01T15:00:17.000Z",
      "cve": "CVE-2026-98906",
      "id": "msrc_CVE-2026-98906",
      "initial_release_date": "2026-10-24T01:02:35.000Z",
      "product_status:known_affected": "2",
      "product_status:under_investigation": "1",
      "source": "Microsoft CSAF VEX",
      "status": "final",
      "title": "net: lan966x: restore RX state on reload failure",
      "url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-98906.json",
      "version": "3"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "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"
                  }
                ]
              }
            ],
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
          }
        ],
        "cveTags": [],
        "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."
          }
        ],
        "id": "CVE-2026-98906",
        "lastModified": "2026-10-26T07:17:15.960",
        "metrics": {},
        "published": "2026-10-23T12:18:24.680",
        "references": [
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/3883898ddc26308497dbba8068951ab5eddbd111"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/aa97f11a76e545ed73cc455bcdd1ece4b480b507"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/b5a6462f4646687c922931133a2478da94addc87"
          }
        ],
        "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "vulnStatus": "Received"
      }
    },
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-10-27T04:08:34+00:00",
      "cve": "CVE-2026-98906",
      "id": "CVE-2026-98906",
      "initial_release_date": "2026-10-23T00:00:00+00:00",
      "product_status:known_not_affected": "278",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: net: lan966x: restore RX state on reload failure",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98906.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-10-27T00:42:49Z",
      "cve": "CVE-2026-98906",
      "id": "CVE-2026-98906",
      "initial_release_date": "2026-10-23T23:53:35Z",
      "product_status:known_affected": "62",
      "product_status:known_not_affected": "286",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2026-98906",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/2026/cve-2026-98906.json",
      "version": "4"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

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

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    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.