Skip to content
Heist/ feed
UnratedFix available

amt: fix use-after-free in AMT delayed works

Type: advisorySource: OSV1 source record

In the Linux kernel, the following vulnerability has been resolved: amt: fix use-after-free in AMT delayed works When an AMT device is removed, pending delayed works can still access the freed amt_dev structure, which may result in kernel crashes or memory corruption. amt_dev_stop() cancels req_wq and discovery_wq with cancel_delayed_work_sync(), but these works can be scheduled again from event_wq after the cancellation. This allows delayed works to access the freed amt_dev structure after the netdev has been released. The following is a simple race scenario: CPU0 CPU1 amt_dev_stop() cancel_delayed_work_sync() amt_event_work() mod_delayed_work(req_wq) free netdev req_wq accesses freed amt_dev Use disable_delayed_work_sync() in amt_dev_stop() to prevent req_wq and discovery_wq from being queued again and wait for running work items to complete. The delayed works are disabled after initialization in amt_newlink() and enabled only when the device is successfully opened. This keeps the delayed work lifecycle synchronized with the lifetime of the AMT device.

Announced Source revision 1
Original source ↗

CVE-2026-68152

Primary source · Revision 1

Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.

Security context

Source reference: osv:CVE-2026-68152

Kernel

Source reference: /affected/1/package/name

Affected versions
Not stated in this record
Fixed versions
6.12.101

Source reference: /affected/1/ranges

6.18.42

Source reference: /affected/1/ranges

7.1.6

Source reference: /affected/1/ranges

Prerequisites
Not stated in this record

Structured affected-version data

Original package identities and version rules from this source.

[
  {
    "ranges": [
      {
        "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
        "type": "GIT",
        "events": [
          {
            "introduced": "cbc21dc1cfe949e37b2a54c71511579f1899e8d4"
          },
          {
            "fixed": "a46bfa01e01df0f6f6dc4b0be18db002d6d2dbd2"
          },
          {
            "fixed": "1a644db2cf59f164cdf3c75995bab5aadc097528"
          },
          {
            "fixed": "006340cf06881b6ff49767d8b6f3c4f7b892670c"
          },
          {
            "fixed": "ea20c44935d6142daecfa9b39d635033a7553e1b"
          }
        ]
      }
    ],
    "database_specific": {
      "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-68152.json"
    }
  },
  {
    "ranges": [
      {
        "type": "ECOSYSTEM",
        "events": [
          {
            "introduced": "5.16.0"
          },
          {
            "fixed": "6.12.101"
          }
        ]
      },
      {
        "type": "ECOSYSTEM",
        "events": [
          {
            "introduced": "6.13.0"
          },
          {
            "fixed": "6.18.42"
          }
        ]
      },
      {
        "type": "ECOSYSTEM",
        "events": [
          {
            "introduced": "6.19.0"
          },
          {
            "fixed": "7.1.6"
          }
        ]
      }
    ],
    "package": {
      "name": "Kernel",
      "ecosystem": "Linux"
    },
    "database_specific": {
      "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-68152.json"
    }
  }
]
Related CVEs
CVE-2026-68152

Source reference: /id

Publisher severity

No explicit severity was provided.

Event
#50730 · Revision 1
Added to Heist Feed
Publisher date
Read the original announcement