vdpa: use generic driver_override infrastructure
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.160, 6.12.114, 6.18.33, 7.0.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: vdpa: use generic driver_override infrastructure When a driver is probed through __driver_attach(), the bus' match() callback is called without the device lock held, thus accessing the driver_override field without a lock, which can cause a UAF. Fix this by using the driver-core driver_override infrastructure taking care of proper locking internally. Note that calling match() from __driver_attach() without the device lock held is intentional. [1]
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 539fec78edb4e084e7c532affc56cc42d4ceea4b · fixed in 4005cb89139f7c9af85046b241dcf3fa2e1b3559; From 539fec78edb4e084e7c532affc56cc42d4ceea4b · fixed in 4eab1a74a498f0bf19f102f9362e9deef9307aea; From 539fec78edb4e084e7c532affc56cc42d4ceea4b · fixed in 654ef9c33e138ede6734ac286282df9faf83cd11; From 539fec78edb4e084e7c532affc56cc42d4ceea4b · fixed in fb5cb4913ce333cc4647722e8c2b8378e12f2464; From 539fec78edb4e084e7c532affc56cc42d4ceea4b · fixed in 85bb534ff12aab6916058897b39c748940a7a4c6
- Linux Linux
5.17
- KernelLinux
From 5.17.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.114; From 6.13.0 · fixed in 6.18.33; From 6.19.0 · fixed in 7.0.10