CVE-2022-48822
published 2024-07-16CVE-2022-48822: In the Linux kernel, the following vulnerability has been resolved: usb: f_fs: Fix use-after-free for epfile Consider a case where ffs_func_eps_disable is…
PriorityP340high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.27%
19.2th percentile
In the Linux kernel, the following vulnerability has been resolved:
usb: f_fs: Fix use-after-free for epfile
Consider a case where ffs_func_eps_disable is called from
ffs_func_disable as part of composition switch and at the
same time ffs_epfile_release get called from userspace.
ffs_epfile_release will free up the read buffer and call
ffs_data_closed which in turn destroys ffs->epfiles and
mark it as NULL. While this was happening the driver has
already initialized the local epfile in ffs_func_eps_disable
which is now freed and waiting to acquire the spinlock. Once
spinlock is acquired the driver proceeds with the stale value
of epfile and tries to free the already freed read buffer
causing use-after-free.
Following is the illustration of the race:
CPU1 CPU2
ffs_func_eps_disable
epfiles (local copy)
ffs_epfile_release
ffs_data_closed
if (last file closed)
ffs_data_reset
ffs_data_clear
ffs_epfiles_destroy
spin_lock
dereference epfiles
Fix this races by taking epfiles local copy & assigning it under
spinlock and if epfiles(local) is null then update it in ffs->epfiles
then finally destroy it.
Extending the scope further from the race, protecting the ep related
structures, and concurrent accesses.
Affected
21 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.16.10-1 (bookworm) | linux 5.16.10-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | >= 4.8.10 < 4.9 | 4.9 |
| linux | linux | >= a9e6f83c2df199187a5248f824f31b6787ae23ae < 32048f4be071f9a6966744243f1786f45bb22dc2 | 32048f4be071f9a6966744243f1786f45bb22dc2 |
| linux | linux | >= a9e6f83c2df199187a5248f824f31b6787ae23ae < cfe5f6fd335d882bcc829a1c8a7d462a455c626e | cfe5f6fd335d882bcc829a1c8a7d462a455c626e |
| linux | linux | >= a9e6f83c2df199187a5248f824f31b6787ae23ae < c9fc422c9a43e3d58d246334a71f3390401781dc | c9fc422c9a43e3d58d246334a71f3390401781dc |
| linux | linux | >= a9e6f83c2df199187a5248f824f31b6787ae23ae < 0042178a69eb77a979e36a50dcce9794a3140ef8 | 0042178a69eb77a979e36a50dcce9794a3140ef8 |
| linux | linux | >= a9e6f83c2df199187a5248f824f31b6787ae23ae < 72a8aee863af099d4434314c4536d6c9a61dcf3c | 72a8aee863af099d4434314c4536d6c9a61dcf3c |
| linux | linux | >= a9e6f83c2df199187a5248f824f31b6787ae23ae < 3e078b18753669615301d946297bafd69294ad2c | 3e078b18753669615301d946297bafd69294ad2c |
| linux | linux | >= a9e6f83c2df199187a5248f824f31b6787ae23ae < ebe2b1add1055b903e2acd86b290a85297edc0b3 | ebe2b1add1055b903e2acd86b290a85297edc0b3 |
| linux | linux_kernel | >= 0 < 5.10.103-1 | 5.10.103-1 |
| linux | linux_kernel | >= 0 < 5.16.10-1 | 5.16.10-1 |
| linux | linux_kernel | >= 0 < 5.16.10-1 | 5.16.10-1 |
| linux | linux_kernel | >= 0 < 5.16.10-1 | 5.16.10-1 |
| linux | linux_kernel | >= 4.15 < 4.19.230 | 4.19.230 |
| linux | linux_kernel | >= 4.20 < 5.4.180 | 5.4.180 |
| linux | linux_kernel | >= 4.9 < 4.14.267 | 4.14.267 |
| linux | linux_kernel | >= 5.11 < 5.15.24 | 5.15.24 |
| linux | linux_kernel | >= 5.16 < 5.16.10 | 5.16.10 |
| linux | linux_kernel | >= 5.5 < 5.10.101 | 5.10.101 |
CVSS provenance
nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
osv7.8HIGH
vendor_debian7.8HIGH
vendor_redhat7.8HIGH
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.
OSV
CVE-2022-48822: In the Linux kernel, the following vulnerability has been resolved: usb: f_fs: Fix use-after-free for epfile Consider a case where ffs_func_eps_disabl
osv·2024-07-16·CVSS 7.8
CVE-2022-48822 [HIGH] CVE-2022-48822: In the Linux kernel, the following vulnerability has been resolved: usb: f_fs: Fix use-after-free for epfile Consider a case where ffs_func_eps_disabl
In the Linux kernel, the following vulnerability has been resolved: usb: f_fs: Fix use-after-free for epfile Consider a case where ffs_func_eps_disable is called from ffs_func_disable as part of composition switch and at the same time ffs_epfile_release get called from userspace. ffs_epfile_release will free up the read buffer and call ffs_data_closed which in turn destroys ffs->epfiles and mark it as NULL. While this was happening the driver has already initialized the local epfile in ffs_func_eps_disable which is now freed and waiting to acquire the spinlock. Once spinlock is acquired the driver proceeds with the stale value of epfile and tries to free the already freed read buffer causing use-after-free. Following is the illustration of the race: CPU1 CPU2 ffs_func_eps_disable epfiles (
GHSA
GHSA-f7jr-76rm-f753: In the Linux kernel, the following vulnerability has been resolved:
usb: f_fs: Fix use-after-free for epfile
Consider a case where ffs_func_eps_disa
ghsa_unreviewed·2024-07-16
CVE-2022-48822 [HIGH] CWE-416 GHSA-f7jr-76rm-f753: In the Linux kernel, the following vulnerability has been resolved:
usb: f_fs: Fix use-after-free for epfile
Consider a case where ffs_func_eps_disa
In the Linux kernel, the following vulnerability has been resolved:
usb: f_fs: Fix use-after-free for epfile
Consider a case where ffs_func_eps_disable is called from
ffs_func_disable as part of composition switch and at the
same time ffs_epfile_release get called from userspace.
ffs_epfile_release will free up the read buffer and call
ffs_data_closed which in turn destroys ffs->epfiles and
mark it as NULL. While this was happening the driver has
already initialized the local epfile in ffs_func_eps_disable
which is now freed and waiting to acquire the spinlock. Once
spinlock is acquired the driver proceeds with the stale value
of epfile and tries to free the already freed read buffer
causing use-after-free.
Following is the illustration of the race:
CPU1 CPU2
ffs_func_eps_disable
epfi
Red Hat
kernel: usb: f_fs: Fix use-after-free for epfile
vendor_redhat·2024-07-16·CVSS 7.8
CVE-2022-48822 [HIGH] CWE-416 kernel: usb: f_fs: Fix use-after-free for epfile
kernel: usb: f_fs: Fix use-after-free for epfile
In the Linux kernel, the following vulnerability has been resolved:
usb: f_fs: Fix use-after-free for epfile
Consider a case where ffs_func_eps_disable is called from
ffs_func_disable as part of composition switch and at the
same time ffs_epfile_release get called from userspace.
ffs_epfile_release will free up the read buffer and call
ffs_data_closed which in turn destroys ffs->epfiles and
mark it as NULL. While this was happening the driver has
already initialized the local epfile in ffs_func_eps_disable
which is now freed and waiting to acquire the spinlock. Once
spinlock is acquired the driver proceeds with the stale value
of epfile and tries to free the already freed read buffer
causing use-after-free.
Following is the illustration of
Debian
CVE-2022-48822: linux - In the Linux kernel, the following vulnerability has been resolved: usb: f_fs: ...
vendor_debian·2022·CVSS 7.8
CVE-2022-48822 [HIGH] CVE-2022-48822: linux - In the Linux kernel, the following vulnerability has been resolved: usb: f_fs: ...
In the Linux kernel, the following vulnerability has been resolved: usb: f_fs: Fix use-after-free for epfile Consider a case where ffs_func_eps_disable is called from ffs_func_disable as part of composition switch and at the same time ffs_epfile_release get called from userspace. ffs_epfile_release will free up the read buffer and call ffs_data_closed which in turn destroys ffs->epfiles and mark it as NULL. While this was happening the driver has already initialized the local epfile in ffs_func_eps_disable which is now freed and waiting to acquire the spinlock. Once spinlock is acquired the driver proceeds with the stale value of epfile and tries to free the already freed read buffer causing use-after-free. Following is the illustration of the race: CPU1 CPU2 ffs_func_eps_disable epfiles (
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://git.kernel.org/stable/c/0042178a69eb77a979e36a50dcce9794a3140ef8https://git.kernel.org/stable/c/32048f4be071f9a6966744243f1786f45bb22dc2https://git.kernel.org/stable/c/3e078b18753669615301d946297bafd69294ad2chttps://git.kernel.org/stable/c/72a8aee863af099d4434314c4536d6c9a61dcf3chttps://git.kernel.org/stable/c/c9fc422c9a43e3d58d246334a71f3390401781dchttps://git.kernel.org/stable/c/cfe5f6fd335d882bcc829a1c8a7d462a455c626ehttps://git.kernel.org/stable/c/ebe2b1add1055b903e2acd86b290a85297edc0b3https://git.kernel.org/stable/c/0042178a69eb77a979e36a50dcce9794a3140ef8https://git.kernel.org/stable/c/32048f4be071f9a6966744243f1786f45bb22dc2https://git.kernel.org/stable/c/3e078b18753669615301d946297bafd69294ad2chttps://git.kernel.org/stable/c/72a8aee863af099d4434314c4536d6c9a61dcf3chttps://git.kernel.org/stable/c/c9fc422c9a43e3d58d246334a71f3390401781dchttps://git.kernel.org/stable/c/cfe5f6fd335d882bcc829a1c8a7d462a455c626ehttps://git.kernel.org/stable/c/ebe2b1add1055b903e2acd86b290a85297edc0b3
2024-07-16
Published