FKIE_CVE-2026-89938

Vulnerability from fkie_nvd - Published: 2026-09-16 11:17 - Updated: 2026-10-19 09:18
Severity
7.8 (High) - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Summary
In the Linux kernel, the following vulnerability has been resolved: iio: chemical: atlas-sensor: use iio_trigger_poll_nested() to fix remove UAF The atlas driver requests its hardware data-ready IRQ with devm_request_threaded_irq(); its threaded handler queues an irq_work, atlas_work_handler(), that calls iio_trigger_poll(data->trig). The IRQ is devm-managed, so free_irq() runs from the devres unwind after atlas_remove() returns without flushing that irq_work. Once a buffer is enabled, conversion-complete IRQs keep firing and queueing it; a pending irq_work can therefore run after the unwind has freed atlas_data/indio_dev and the trigger, when atlas_work_handler() derives the atlas_data pointer via container_of() and dereferences data->trig, a use-after-free. Call iio_trigger_poll_nested() directly from the threaded handler instead of bouncing through irq_work. free_irq() then drains the threaded handler, closing the window; other iio drivers with a threaded data-ready IRQ do the same (e.g. bmi270). This issue was found by an in-house static analysis tool.
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/2071624c3d0f497ca91da78858e6f30d7112fea6
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/30b0d44c978bbc857bd68b71dab371805653de70
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/91e12b0fbd7047d02bf4ef4dbc491b9ef0159250
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/be61c8c6252671ecf1fee0ad90f87669e0be1e20
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/f64b437641b5a70c18bb0fd38da2b69d8926c871
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/iio/chemical/atlas-sensor.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "f64b437641b5a70c18bb0fd38da2b69d8926c871",
              "status": "affected",
              "version": "7103b99b031cb0ff6979331757bfc4893f37ae9e",
              "versionType": "git"
            },
            {
              "lessThan": "91e12b0fbd7047d02bf4ef4dbc491b9ef0159250",
              "status": "affected",
              "version": "7103b99b031cb0ff6979331757bfc4893f37ae9e",
              "versionType": "git"
            },
            {
              "lessThan": "2071624c3d0f497ca91da78858e6f30d7112fea6",
              "status": "affected",
              "version": "7103b99b031cb0ff6979331757bfc4893f37ae9e",
              "versionType": "git"
            },
            {
              "lessThan": "30b0d44c978bbc857bd68b71dab371805653de70",
              "status": "affected",
              "version": "7103b99b031cb0ff6979331757bfc4893f37ae9e",
              "versionType": "git"
            },
            {
              "lessThan": "be61c8c6252671ecf1fee0ad90f87669e0be1e20",
              "status": "affected",
              "version": "7103b99b031cb0ff6979331757bfc4893f37ae9e",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/iio/chemical/atlas-sensor.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "4.8"
            },
            {
              "lessThan": "4.8",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.157",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.110",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.51",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.5",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3",
              "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\niio: chemical: atlas-sensor: use iio_trigger_poll_nested() to fix remove UAF\n\nThe atlas driver requests its hardware data-ready IRQ with\ndevm_request_threaded_irq(); its threaded handler queues an irq_work,\natlas_work_handler(), that calls iio_trigger_poll(data-\u003etrig).\n\nThe IRQ is devm-managed, so free_irq() runs from the devres unwind after\natlas_remove() returns without flushing that irq_work.  Once a buffer is\nenabled, conversion-complete IRQs keep firing and queueing it; a pending\nirq_work can therefore run after the unwind has freed atlas_data/indio_dev\nand the trigger, when atlas_work_handler() derives the atlas_data pointer\nvia container_of() and dereferences data-\u003etrig, a use-after-free.\n\nCall iio_trigger_poll_nested() directly from the threaded handler instead\nof bouncing through irq_work.  free_irq() then drains the threaded handler,\nclosing the window; other iio drivers with a threaded data-ready IRQ do the\nsame (e.g. bmi270).\n\nThis issue was found by an in-house static analysis tool."
    }
  ],
  "id": "CVE-2026-89938",
  "lastModified": "2026-10-19T09:18:39.557",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "LOCAL",
          "availabilityImpact": "HIGH",
          "baseScore": 7.8,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "privilegesRequired": "LOW",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
          "version": "3.1"
        },
        "exploitabilityScore": 1.8,
        "impactScore": 5.9,
        "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "type": "Secondary"
      }
    ]
  },
  "published": "2026-09-16T11:17:03.323",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/2071624c3d0f497ca91da78858e6f30d7112fea6"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/30b0d44c978bbc857bd68b71dab371805653de70"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/91e12b0fbd7047d02bf4ef4dbc491b9ef0159250"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/be61c8c6252671ecf1fee0ad90f87669e0be1e20"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/f64b437641b5a70c18bb0fd38da2b69d8926c871"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Received"
}



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.