CVE-2022-49626
published 2025-02-26CVE-2022-49626: In the Linux kernel, the following vulnerability has been resolved: sfc: fix use after free when disabling sriov Use after free is detected by kfence when…
PriorityP339high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.27%
19.1th percentile
In the Linux kernel, the following vulnerability has been resolved:
sfc: fix use after free when disabling sriov
Use after free is detected by kfence when disabling sriov. What was read
after being freed was vf->pci_dev: it was freed from pci_disable_sriov
and later read in efx_ef10_sriov_free_vf_vports, called from
efx_ef10_sriov_free_vf_vswitching.
Set the pointer to NULL at release time to not trying to read it later.
Reproducer and dmesg log (note that kfence doesn't detect it every time):
$ echo 1 > /sys/class/net/enp65s0f0np0/device/sriov_numvfs
$ echo 0 > /sys/class/net/enp65s0f0np0/device/sriov_numvfs
BUG: KFENCE: use-after-free read in efx_ef10_sriov_free_vf_vswitching+0x82/0x170 [sfc]
Use-after-free read at 0x00000000ff3c1ba5 (in kfence-#224):
efx_ef10_sriov_free_vf_vswitching+0x82/0x170 [sfc]
efx_ef10_pci_sriov_disable+0x38/0x70 [sfc]
efx_pci_sriov_configure+0x24/0x40 [sfc]
sriov_numvfs_store+0xfe/0x140
kernfs_fop_write_iter+0x11c/0x1b0
new_sync_write+0x11f/0x1b0
vfs_write+0x1eb/0x280
ksys_write+0x5f/0xe0
do_syscall_64+0x5c/0x80
entry_SYSCALL_64_after_hwframe+0x44/0xae
kfence-#224: 0x00000000edb8ef95-0x00000000671f5ce1, size=2792, cache=kmalloc-4k
allocated by task 6771 on cpu 10 at 3137.860196s:
pci_alloc_dev+0x21/0x60
pci_iov_add_virtfn+0x2a2/0x320
sriov_enable+0x212/0x3e0
efx_ef10_sriov_configure+0x67/0x80 [sfc]
efx_pci_sriov_configure+0x24/0x40 [sfc]
sriov_numvfs_store+0xba/0x140
kernfs_fop_write_iter+0x11c/0x1b0
new_sync_write+0x11f/0x1b0
vfs_write+0x1eb/0x280
ksys_write+0x5f/0xe0
do_syscall_64+0x5c/0x80
entry_SYSCALL_64_after_hwframe+0x44/0xae
freed by task 6771 on cpu 12 at 3170.991309s:
device_release+0x34/0x90
kobject_cleanup+0x3a/0x130
pci_iov_remove_virtfn+0xd9/0x120
sriov_disable+0x30/0xe0
efx_ef10_pci_sriov_disable+0x57/0x70 [sfc]
efx_pci_sriov_configure+0x24/0x40 [sfc]
sriov_numvfs_store+0xfe/0x140
kernfs_fop_write_iter+0x11c/0x1b0
new_sync_write+0x11f/0x1b0
vfs_write+0x1eb/0x280
ksys_write+0x5f/0xe0
do_syscall_64+0x5c/0x80
entry_SY
Affected
22 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.18.14-1 (bookworm) | linux 5.18.14-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 3c5eb87605e85146a78de589b5070a37862425db < 3199e34912d84cdfb8a93a984c5ae5c73fb13e84 | 3199e34912d84cdfb8a93a984c5ae5c73fb13e84 |
| linux | linux | >= 3c5eb87605e85146a78de589b5070a37862425db < c9e75bb22a26e391f189f5a5133dd63dcb57fdaa | c9e75bb22a26e391f189f5a5133dd63dcb57fdaa |
| linux | linux | >= 3c5eb87605e85146a78de589b5070a37862425db < 9c854ae512b89229aeee93849e9bd4c115b37909 | 9c854ae512b89229aeee93849e9bd4c115b37909 |
| linux | linux | >= 3c5eb87605e85146a78de589b5070a37862425db < bcad880865bfb421885364b1f0c7351280fe2b97 | bcad880865bfb421885364b1f0c7351280fe2b97 |
| linux | linux | >= 3c5eb87605e85146a78de589b5070a37862425db < c2240500817b3b4b996cdf2a461a3a5679f49b94 | c2240500817b3b4b996cdf2a461a3a5679f49b94 |
| linux | linux | >= 3c5eb87605e85146a78de589b5070a37862425db < 58d93e9d160c0de6d867c7eb4c2206671a351eb1 | 58d93e9d160c0de6d867c7eb4c2206671a351eb1 |
| linux | linux | >= 3c5eb87605e85146a78de589b5070a37862425db < e435c4aeeaa073091f7f3b7735af2ef5c97d63f2 | e435c4aeeaa073091f7f3b7735af2ef5c97d63f2 |
| linux | linux | >= 3c5eb87605e85146a78de589b5070a37862425db < ebe41da5d47ac0fff877e57bd14c54dccf168827 | ebe41da5d47ac0fff877e57bd14c54dccf168827 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.136-1 | 5.10.136-1 |
| linux | linux_kernel | >= 0 < 5.18.14-1 | 5.18.14-1 |
| linux | linux_kernel | >= 0 < 5.18.14-1 | 5.18.14-1 |
| linux | linux_kernel | >= 0 < 5.18.14-1 | 5.18.14-1 |
| linux | linux_kernel | >= 4.10 < 4.14.289 | 4.14.289 |
| linux | linux_kernel | >= 4.15 < 4.19.253 | 4.19.253 |
| linux | linux_kernel | >= 4.2 < 4.9.324 | 4.9.324 |
| linux | linux_kernel | >= 4.20 < 5.4.207 | 5.4.207 |
| linux | linux_kernel | >= 5.11 < 5.15.56 | 5.15.56 |
| linux | linux_kernel | >= 5.16 < 5.18.13 | 5.18.13 |
| linux | linux_kernel | >= 5.5 < 5.10.132 | 5.10.132 |
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.
Red Hat
kernel: sfc: fix use after free when disabling sriov
vendor_redhat·2025-02-26·CVSS 7.8
CVE-2022-49626 [HIGH] kernel: sfc: fix use after free when disabling sriov
kernel: sfc: fix use after free when disabling sriov
In the Linux kernel, the following vulnerability has been resolved:
sfc: fix use after free when disabling sriov
Use after free is detected by kfence when disabling sriov. What was read
after being freed was vf->pci_dev: it was freed from pci_disable_sriov
and later read in efx_ef10_sriov_free_vf_vports, called from
efx_ef10_sriov_free_vf_vswitching.
Set the pointer to NULL at release time to not trying to read it later.
Reproducer and dmesg log (note that kfence doesn't detect it every time):
$ echo 1 > /sys/class/net/enp65s0f0np0/device/sriov_numvfs
$ echo 0 > /sys/class/net/enp65s0f0np0/device/sriov_numvfs
BUG: KFENCE: use-after-free read in efx_ef10_sriov_free_vf_vswitching+0x82/0x170 [sfc]
Use-after-free read at 0x00000000ff3c1ba5
Debian
CVE-2022-49626: linux - In the Linux kernel, the following vulnerability has been resolved: sfc: fix us...
vendor_debian·2022·CVSS 7.8
CVE-2022-49626 [HIGH] CVE-2022-49626: linux - In the Linux kernel, the following vulnerability has been resolved: sfc: fix us...
In the Linux kernel, the following vulnerability has been resolved: sfc: fix use after free when disabling sriov Use after free is detected by kfence when disabling sriov. What was read after being freed was vf->pci_dev: it was freed from pci_disable_sriov and later read in efx_ef10_sriov_free_vf_vports, called from efx_ef10_sriov_free_vf_vswitching. Set the pointer to NULL at release time to not trying to read it later. Reproducer and dmesg log (note that kfence doesn't detect it every time): $ echo 1 > /sys/class/net/enp65s0f0np0/device/sriov_numvfs $ echo 0 > /sys/class/net/enp65s0f0np0/device/sriov_numvfs BUG: KFENCE: use-after-free read in efx_ef10_sriov_free_vf_vswitching+0x82/0x170 [sfc] Use-after-free read at 0x00000000ff3c1ba5 (in kfence-#224): efx_ef10_sriov_free_vf_vswitching+0x
GHSA
GHSA-fv97-qmwg-89pj: In the Linux kernel, the following vulnerability has been resolved:
sfc: fix use after free when disabling sriov
Use after free is detected by kfenc
ghsa_unreviewed·2025-02-27
CVE-2022-49626 [HIGH] CWE-416 GHSA-fv97-qmwg-89pj: In the Linux kernel, the following vulnerability has been resolved:
sfc: fix use after free when disabling sriov
Use after free is detected by kfenc
In the Linux kernel, the following vulnerability has been resolved:
sfc: fix use after free when disabling sriov
Use after free is detected by kfence when disabling sriov. What was read
after being freed was vf->pci_dev: it was freed from pci_disable_sriov
and later read in efx_ef10_sriov_free_vf_vports, called from
efx_ef10_sriov_free_vf_vswitching.
Set the pointer to NULL at release time to not trying to read it later.
Reproducer and dmesg log (note that kfence doesn't detect it every time):
$ echo 1 > /sys/class/net/enp65s0f0np0/device/sriov_numvfs
$ echo 0 > /sys/class/net/enp65s0f0np0/device/sriov_numvfs
BUG: KFENCE: use-after-free read in efx_ef10_sriov_free_vf_vswitching+0x82/0x170 [sfc]
Use-after-free read at 0x00000000ff3c1ba5 (in kfence-#224):
efx_ef10_sriov_free_vf_vswitch
OSV
CVE-2022-49626: In the Linux kernel, the following vulnerability has been resolved: sfc: fix use after free when disabling sriov Use after free is detected by kfence
osv·2025-02-26·CVSS 7.8
CVE-2022-49626 [HIGH] CVE-2022-49626: In the Linux kernel, the following vulnerability has been resolved: sfc: fix use after free when disabling sriov Use after free is detected by kfence
In the Linux kernel, the following vulnerability has been resolved: sfc: fix use after free when disabling sriov Use after free is detected by kfence when disabling sriov. What was read after being freed was vf->pci_dev: it was freed from pci_disable_sriov and later read in efx_ef10_sriov_free_vf_vports, called from efx_ef10_sriov_free_vf_vswitching. Set the pointer to NULL at release time to not trying to read it later. Reproducer and dmesg log (note that kfence doesn't detect it every time): $ echo 1 > /sys/class/net/enp65s0f0np0/device/sriov_numvfs $ echo 0 > /sys/class/net/enp65s0f0np0/device/sriov_numvfs BUG: KFENCE: use-after-free read in efx_ef10_sriov_free_vf_vswitching+0x82/0x170 [sfc] Use-after-free read at 0x00000000ff3c1ba5 (in kfence-#224): efx_ef10_sriov_free_vf_vswitching+0x
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/3199e34912d84cdfb8a93a984c5ae5c73fb13e84https://git.kernel.org/stable/c/58d93e9d160c0de6d867c7eb4c2206671a351eb1https://git.kernel.org/stable/c/9c854ae512b89229aeee93849e9bd4c115b37909https://git.kernel.org/stable/c/bcad880865bfb421885364b1f0c7351280fe2b97https://git.kernel.org/stable/c/c2240500817b3b4b996cdf2a461a3a5679f49b94https://git.kernel.org/stable/c/c9e75bb22a26e391f189f5a5133dd63dcb57fdaahttps://git.kernel.org/stable/c/e435c4aeeaa073091f7f3b7735af2ef5c97d63f2https://git.kernel.org/stable/c/ebe41da5d47ac0fff877e57bd14c54dccf168827
2025-02-26
Published