{ "dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": { "cveId": "CVE-2026-89522", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "state": "PUBLISHED", "assignerShortName": "Linux", "dateReserved": "2026-09-11T19:38:34.718Z", "datePublished": "2026-09-11T19:44:04.052Z", "dateUpdated": "2026-10-19T08:48:13.544Z" }, "containers": { "cna": { "providerMetadata": { "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-10-19T08:48:13.544Z" }, "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: staging/ipu7: fix async notifier UAF on probe error path\n\nisys_register_devices() registers the V4L2 async notifier via\nisys_notifier_init(). If a subsequent probe step such as\nisys_fw_log_init() fails, isys_probe() jumps to the out_cleanup label\nwhich only calls isys_unregister_devices(). That helper tears down the\nvideo devices, subdevices, V4L2 device and media device, but never\nunregisters or cleans up the async notifier.\n\nAs a result the notifier stays chained in the global notifier_list while\nthe enclosing struct ipu7_isys is freed by devres, leading to list\ncorruption and a use-after-free the next time the list is walked.\n\nThe remove path already does the right thing by calling\nisys_notifier_cleanup() before isys_unregister_devices(). Mirror that on\nthe probe error path so the notifier is unregistered and cleaned up\nbefore the device is torn down." } ], "metrics": [ { "cvssV3_1": { "version": "3.1", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "baseScore": 7.8, "baseSeverity": "HIGH" }, "scenarios": [ { "lang": "en", "value": "AV:L - The flaw is in isys_probe() of the Intel IPU7 ISYS auxiliary driver (PCI IDs 0x645d/0xb05d on Meteor Lake/Arrow Lake/Lunar Lake laptops). It is reached only via local driver bind of the onboard MIPI camera ISP, not via network packets, Bluetooth, or USB attachment.\nAC:L - The missing isys_notifier_cleanup() on the out_cleanup path is deterministic. A local attacker can force the subsequent 2 MiB FW_LOG_BUF_SIZE kzalloc in isys_fw_log_init() to fail under memory pressure, and the UAF is then hit the next time notifier_list is walked, with no race the attacker must win.\nPR:L - After probe failure leaves the notifier on the global notifier_list, ACPI camera sensors typical of IPU7 laptops (ov02c10, ov08x40, and similar) call v4l2_async_register_subdev_sensor() and walk that list without capabilities. Per CNA guidance, Low is used when probe/bind privilege gating is ambiguous.\nUI:N - No victim action such as opening /dev/video*, mounting a filesystem, or plugging a device is required. The dangling notifier is planted on the probe error path and consumed automatically when a sensor or other V4L2 async client registers.\nS:U - Impact is host-kernel slab use-after-free and list corruption inside the IPU7/V4L2 async core. This is standard kernel privilege-escalation territory and does not cross a VM, IOMMU, or sandbox security boundary.\nC:H - The notifier is embedded in struct ipu7_isys, which devres frees while it remains linked on notifier_list. A later walk reads freed notifier fields and ops; per kernel CNA UAF guidance that reuse primitive enables arbitrary kernel memory disclosure.\nI:H - Walking or unlinking the dangling notifier_entry corrupts kernel lists, and a reclaimed object can redirect notifier->ops (bound/complete) to attacker-controlled function pointers, yielding an arbitrary-write and control-flow hijack primitive.\nA:H - The next notifier_list walk or bound callback on the freed ipu7_isys object causes a kernel oops or panic, and use-after-free heap corruption inherently denies availability even without a full exploit." } ] } ], "affected": [ { "product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": [ "drivers/staging/media/ipu7/ipu7-isys.c" ], "versions": [ { "version": "a516d36bdc3d8373f904af57c95e76d6f921cf1c", "lessThan": "2a8dd9fd12f3f6b21207cec8f50c92cd428e6b81", "status": "affected", "versionType": "git" }, { "version": "a516d36bdc3d8373f904af57c95e76d6f921cf1c", "lessThan": "323c411fb63122e8cef5b833032d69d59a838559", "status": "affected", "versionType": "git" }, { "version": "a516d36bdc3d8373f904af57c95e76d6f921cf1c", "lessThan": "d7f48aa7d60c65d3e6d5312c27f17d5525a245fb", "status": "affected", "versionType": "git" } ] }, { "product": "Linux", "vendor": "Linux", "defaultStatus": "affected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": [ "drivers/staging/media/ipu7/ipu7-isys.c" ], "versions": [ { "version": "6.17", "status": "affected" }, { "version": "0", "lessThan": "6.17", "status": "unaffected", "versionType": "semver" }, { "version": "6.18.50", "lessThanOrEqual": "6.18.*", "status": "unaffected", "versionType": "semver" }, { "version": "7.2.4", "lessThanOrEqual": "7.2.*", "status": "unaffected", "versionType": "semver" }, { "version": "7.3", "lessThanOrEqual": "*", "status": "unaffected", "versionType": "original_commit_for_fix" } ] } ], "cpeApplicability": [ { "nodes": [ { "operator": "OR", "negate": false, "cpeMatch": [ { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.17", "versionEndExcluding": "6.18.50" }, { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.17", "versionEndExcluding": "7.2.4" }, { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.17", "versionEndExcluding": "7.3" } ] } ] } ], "references": [ { "url": "https://git.kernel.org/stable/c/2a8dd9fd12f3f6b21207cec8f50c92cd428e6b81" }, { "url": "https://git.kernel.org/stable/c/323c411fb63122e8cef5b833032d69d59a838559" }, { "url": "https://git.kernel.org/stable/c/d7f48aa7d60c65d3e6d5312c27f17d5525a245fb" } ], "title": "media: staging/ipu7: fix async notifier UAF on probe error path", "x_generator": { "engine": "bippy-1.2.0" } } } }