CVE-2021-47339
published 2024-05-21CVE-2021-47339: In the Linux kernel, the following vulnerability has been resolved: media: v4l2-core: explicitly clear ioctl input data As seen from a recent syzbot bug…
PriorityP421medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.24%
14.6th percentile
In the Linux kernel, the following vulnerability has been resolved:
media: v4l2-core: explicitly clear ioctl input data
As seen from a recent syzbot bug report, mistakes in the compat ioctl
implementation can lead to uninitialized kernel stack data getting used
as input for driver ioctl handlers.
The reported bug is now fixed, but it's possible that other related
bugs are still present or get added in the future. As the drivers need
to check user input already, the possible impact is fairly low, but it
might still cause an information leak.
To be on the safe side, always clear the entire ioctl buffer before
calling the conversion handler functions that are meant to initialize
them.
Affected
10 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.14.6-1 (bookworm) | linux 5.14.6-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 8dbcc3fa387c16abfc88a628cf528c439c91b332 < dc02c0b2bd6096f2f3ce63e1fc317aeda05f74d8 | dc02c0b2bd6096f2f3ce63e1fc317aeda05f74d8 |
| linux | linux | >= 8dbcc3fa387c16abfc88a628cf528c439c91b332 < bfb48b54db25c3b4ef4bef5e0691464ebc4aa335 | bfb48b54db25c3b4ef4bef5e0691464ebc4aa335 |
| linux | linux | >= 8dbcc3fa387c16abfc88a628cf528c439c91b332 < 7b53cca764f9b291b7907fcd39d9e66ad728ee0b | 7b53cca764f9b291b7907fcd39d9e66ad728ee0b |
| linux | linux_kernel | < 5.12.18 | 5.12.18 |
| linux | linux_kernel | >= 0 < 5.14.6-1 | 5.14.6-1 |
| linux | linux_kernel | >= 0 < 5.14.6-1 | 5.14.6-1 |
| linux | linux_kernel | >= 0 < 5.14.6-1 | 5.14.6-1 |
| linux | linux_kernel | >= 5.13 < 5.13.3 | 5.13.3 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: media: v4l2-core: explicitly clear ioctl input data
vendor_redhat·2024-05-21·CVSS 5.5
CVE-2021-47339 [MEDIUM] CWE-401 kernel: media: v4l2-core: explicitly clear ioctl input data
kernel: media: v4l2-core: explicitly clear ioctl input data
In the Linux kernel, the following vulnerability has been resolved:
media: v4l2-core: explicitly clear ioctl input data
As seen from a recent syzbot bug report, mistakes in the compat ioctl
implementation can lead to uninitialized kernel stack data getting used
as input for driver ioctl handlers.
The reported bug is now fixed, but it's possible that other related
bugs are still present or get added in the future. As the drivers need
to check user input already, the possible impact is fairly low, but it
might still cause an information leak.
To be on the safe side, always clear the entire ioctl buffer before
calling the conversion handler functions that are meant to initialize
them.
Package: kernel (Red Hat Enterprise Linux 6) -
Debian
CVE-2021-47339: linux - In the Linux kernel, the following vulnerability has been resolved: media: v4l2...
vendor_debian·2021·CVSS 5.5
CVE-2021-47339 [MEDIUM] CVE-2021-47339: linux - In the Linux kernel, the following vulnerability has been resolved: media: v4l2...
In the Linux kernel, the following vulnerability has been resolved: media: v4l2-core: explicitly clear ioctl input data As seen from a recent syzbot bug report, mistakes in the compat ioctl implementation can lead to uninitialized kernel stack data getting used as input for driver ioctl handlers. The reported bug is now fixed, but it's possible that other related bugs are still present or get added in the future. As the drivers need to check user input already, the possible impact is fairly low, but it might still cause an information leak. To be on the safe side, always clear the entire ioctl buffer before calling the conversion handler functions that are meant to initialize them.
Scope: local
bookworm: resolved (fixed in 5.14.6-1)
bullseye: resolved
forky: resolved (fixed in 5.14.6-1)
si
OSV
CVE-2021-47339: In the Linux kernel, the following vulnerability has been resolved: media: v4l2-core: explicitly clear ioctl input data As seen from a recent syzbot b
osv·2024-05-21·CVSS 5.5
CVE-2021-47339 [MEDIUM] CVE-2021-47339: In the Linux kernel, the following vulnerability has been resolved: media: v4l2-core: explicitly clear ioctl input data As seen from a recent syzbot b
In the Linux kernel, the following vulnerability has been resolved: media: v4l2-core: explicitly clear ioctl input data As seen from a recent syzbot bug report, mistakes in the compat ioctl implementation can lead to uninitialized kernel stack data getting used as input for driver ioctl handlers. The reported bug is now fixed, but it's possible that other related bugs are still present or get added in the future. As the drivers need to check user input already, the possible impact is fairly low, but it might still cause an information leak. To be on the safe side, always clear the entire ioctl buffer before calling the conversion handler functions that are meant to initialize them.
GHSA
GHSA-3p2v-4qj8-6w5f: In the Linux kernel, the following vulnerability has been resolved:
media: v4l2-core: explicitly clear ioctl input data
As seen from a recent syzbot
ghsa_unreviewed·2024-05-21
CVE-2021-47339 [MEDIUM] CWE-908 GHSA-3p2v-4qj8-6w5f: In the Linux kernel, the following vulnerability has been resolved:
media: v4l2-core: explicitly clear ioctl input data
As seen from a recent syzbot
In the Linux kernel, the following vulnerability has been resolved:
media: v4l2-core: explicitly clear ioctl input data
As seen from a recent syzbot bug report, mistakes in the compat ioctl
implementation can lead to uninitialized kernel stack data getting used
as input for driver ioctl handlers.
The reported bug is now fixed, but it's possible that other related
bugs are still present or get added in the future. As the drivers need
to check user input already, the possible impact is fairly low, but it
might still cause an information leak.
To be on the safe side, always clear the entire ioctl buffer before
calling the conversion handler functions that are meant to initialize
them.
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/7b53cca764f9b291b7907fcd39d9e66ad728ee0bhttps://git.kernel.org/stable/c/bfb48b54db25c3b4ef4bef5e0691464ebc4aa335https://git.kernel.org/stable/c/dc02c0b2bd6096f2f3ce63e1fc317aeda05f74d8https://git.kernel.org/stable/c/7b53cca764f9b291b7907fcd39d9e66ad728ee0bhttps://git.kernel.org/stable/c/bfb48b54db25c3b4ef4bef5e0691464ebc4aa335https://git.kernel.org/stable/c/dc02c0b2bd6096f2f3ce63e1fc317aeda05f74d8
2024-05-21
Published