CVE-2024-35830: media: tc358743: register v4l2 async device only after successful setup
First published: Fri May 17 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: media: tc358743: register v4l2 async device only after successful setup Ensure the device has been setup correctly before registering the v4l2 async device, thus allowing userspace to access.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| debian/linux | 5.10.223-1 5.10.226-1 6.1.123-1 6.1.128-1 6.12.12-1 6.12.15-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/17c2650de14842c25c569cbb2126c421489a3a24
- https://git.kernel.org/stable/c/4f1490a5d7a0472ee5d9f36547bc4ba46be755c7
- https://git.kernel.org/stable/c/610f20e5cf35ca9c0992693cae0dd8643ce932e7
- https://git.kernel.org/stable/c/87399f1ff92203d65f1febf5919429f4bb613a02
- https://git.kernel.org/stable/c/8ba8db9786b55047df5ad3db3e01dd886687a77d
- https://git.kernel.org/stable/c/b8505a1aee8f1edc9d16d72ae09c93de086e2a1a
- https://git.kernel.org/stable/c/c915c46a25c3efb084c4f5e69a053d7f7a635496
- https://git.kernel.org/stable/c/daf21394f9898fb9f0698c3e50de08132d2164e6
- https://git.kernel.org/stable/c/edbb3226c985469a2f8eb69885055c9f5550f468
- https://launchpad.net/bugs/cve/CVE-2024-35830
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-35830
- https://nvd.nist.gov/vuln/detail/CVE-2024-35830
- https://security-tracker.debian.org/tracker/CVE-2024-35830
- https://ubuntu.com/security/CVE-2024-35830
- https://lists.debian.org/debian-lts-announce/2024/06/msg00017.html
- https://lists.debian.org/debian-lts-announce/2024/06/msg00020.html
- https://git.kernel.org/linus/87399f1ff92203d65f1febf5919429f4bb613a02
Frequently Asked Questions
What is the severity of CVE-2024-35830?
CVE-2024-35830 has been classified as a moderate severity vulnerability due to its impact on the Linux kernel's media handling.
How do I fix CVE-2024-35830?
To remediate CVE-2024-35830, ensure you upgrade to the patched versions of the Linux kernel specified in the vulnerability description.
What is the impact of CVE-2024-35830?
The impact of CVE-2024-35830 is that it could potentially allow incorrect device registration in the Linux kernel, leading to improper userspace access.
Which versions of the Linux kernel are affected by CVE-2024-35830?
CVE-2024-35830 affects specific versions of the Linux kernel including 5.10.223-1, 5.10.226-1, 6.1.123-1, and others as listed in the documentation.
Is CVE-2024-35830 already fixed in some Linux kernel versions?
Yes, CVE-2024-35830 has been resolved in various updated versions of the Linux kernel.
- agent/title
- agent/severity
- agent/type
- collector/epss-latest
- source/FIRST
- agent/epss
- agent/remedy
- agent/first-publish-date
- collector/launchpad-cve
- source/Launchpad
- agent/author
- collector/nvd-api
- source/NVD
- collector/usn-cve
- source/Ubuntu
- agent/event
- collector/nvd-cve
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/references
- agent/description
- agent/trending
- agent/source
- agent/tags
- agent/softwarecombine
- collector/security-tracker-debian
- source/Debian
- package-manager/debian