CVE-2026-98658 (GCVE-0-2026-98658)

Vulnerability from cvelistv5 – Published: 2026-10-18 15:44 – Updated: 2026-10-19 09:23
VLAI
Title
iio: proximity: aw96103: validate firmware data length
Summary
In the Linux kernel, the following vulnerability has been resolved: iio: proximity: aw96103: validate firmware data length The firmware parser reads a length from the binary header and then uses it to walk six-byte register/value entries. A truncated firmware image can make the parser read beyond the copied firmware buffer. A value smaller than the four-byte count field also underflows, producing a very large length. Read the little-endian field with get_unaligned_le32(), as previously proposed by David Lechner. Validate the header size, reject an underflowed length, ensure the resulting payload is contained in the firmware image, and require it to contain whole register/value entries.
Severity
No CVSS data available.
Assigner
Linux CNA
Impacted products
Vendor Product Version
Linux Linux Affected: 07b241262dcad07671c444ca955903325de28e9e , < 4a9b9f2d4e26589afd0ac099c8e5593170dd5ac7 (git)
Affected: 07b241262dcad07671c444ca955903325de28e9e , < 6501b032be217ecf47e793b78a05078cf0b604ad (git)
Affected: 07b241262dcad07671c444ca955903325de28e9e , < 815ae0b73b69ace207b6bbf7ef428b06491c3ddb (git)
Affected: 07b241262dcad07671c444ca955903325de28e9e , < 1a7c522a35477d70320bd64aba8e9de0c1058c6f (git)
Create a notification for this product.
Linux Linux Affected: 6.12
Unaffected: 0 , < 6.12 (semver)
Unaffected: 6.12.113 , ≤ 6.12.* (semver)
Unaffected: 6.18.56 , ≤ 6.18.* (semver)
Unaffected: 7.2.10 , ≤ 7.2.* (semver)
Unaffected: 7.3 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/iio/proximity/aw96103.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "4a9b9f2d4e26589afd0ac099c8e5593170dd5ac7",
              "status": "affected",
              "version": "07b241262dcad07671c444ca955903325de28e9e",
              "versionType": "git"
            },
            {
              "lessThan": "6501b032be217ecf47e793b78a05078cf0b604ad",
              "status": "affected",
              "version": "07b241262dcad07671c444ca955903325de28e9e",
              "versionType": "git"
            },
            {
              "lessThan": "815ae0b73b69ace207b6bbf7ef428b06491c3ddb",
              "status": "affected",
              "version": "07b241262dcad07671c444ca955903325de28e9e",
              "versionType": "git"
            },
            {
              "lessThan": "1a7c522a35477d70320bd64aba8e9de0c1058c6f",
              "status": "affected",
              "version": "07b241262dcad07671c444ca955903325de28e9e",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/iio/proximity/aw96103.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.113",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.56",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.10",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.113",
                  "versionStartIncluding": "6.12",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.56",
                  "versionStartIncluding": "6.12",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.10",
                  "versionStartIncluding": "6.12",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3",
                  "versionStartIncluding": "6.12",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\niio: proximity: aw96103: validate firmware data length\n\nThe firmware parser reads a length from the binary header and then uses\nit to walk six-byte register/value entries. A truncated firmware image\ncan make the parser read beyond the copied firmware buffer. A value\nsmaller than the four-byte count field also underflows, producing a very\nlarge length.\n\nRead the little-endian field with get_unaligned_le32(), as previously\nproposed by David Lechner. Validate the header size, reject an\nunderflowed length, ensure the resulting payload is contained in the\nfirmware image, and require it to contain whole register/value entries."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-19T09:23:26.505Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/4a9b9f2d4e26589afd0ac099c8e5593170dd5ac7"
        },
        {
          "url": "https://git.kernel.org/stable/c/6501b032be217ecf47e793b78a05078cf0b604ad"
        },
        {
          "url": "https://git.kernel.org/stable/c/815ae0b73b69ace207b6bbf7ef428b06491c3ddb"
        },
        {
          "url": "https://git.kernel.org/stable/c/1a7c522a35477d70320bd64aba8e9de0c1058c6f"
        }
      ],
      "title": "iio: proximity: aw96103: validate firmware data length",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-98658",
    "datePublished": "2026-10-18T15:44:12.196Z",
    "dateReserved": "2026-09-25T10:25:14.362Z",
    "dateUpdated": "2026-10-19T09:23:26.505Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-98658",
      "date": "2026-11-19",
      "epss": "0.002",
      "percentile": "0.09983"
    },
    "microsoft_vex": {
      "current_release_date": "2026-11-12T17:49:56.000Z",
      "cve": "CVE-2026-98658",
      "id": "msrc_CVE-2026-98658",
      "initial_release_date": "2026-10-20T22:23:47.000Z",
      "product_status:fixed": "1",
      "product_status:known_affected": "1",
      "product_status:under_investigation": "1",
      "source": "Microsoft CSAF VEX",
      "status": "final",
      "title": "iio: proximity: aw96103: validate firmware data length",
      "url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-98658.json",
      "version": "3"
    },
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-11-07T11:31:23+00:00",
      "cve": "CVE-2026-98658",
      "id": "CVE-2026-98658",
      "initial_release_date": "2026-10-18T00:00:00+00:00",
      "product_status:known_not_affected": "203",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: iio: proximity: aw96103: validate firmware data length",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98658.json",
      "version": "3"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    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.