Vulnerability · Published Feb 26, 2025 · Assigned by Linux
CVE-2022-49390macsec: fix UAF bug for real_dev
High 7.8
In plain English
A high-severity use-after-free in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 19% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: macsec: fix UAF bug for real_dev Create a new macsec device but not get reference to real_dev. That can not ensure that real_dev is freed after macsec. That will trigger the UAF bug for real_dev as following: ================================================================== BUG: KASAN: use-after-free in macsec_get_iflink+0x5f/0x70 drivers/net/macsec.c:3662 Call Trace: ... macsec_get_iflink+0x5f/0x70 drivers/net/macsec.c:3662 dev_get_iflink+0x73/0xe0 net/core/dev.c:637 default_operstate net/core/link_watch.c:42 [inline] rfc2863_policy+0x233/0x2d0 net/core/link_watch.c:54 linkwatch_do_dev+0x2a/0x150 net/core/link_watch.c:161 Allocated by task 22209: ... alloc_netdev_mqs+0x98/0x1100 net/core/dev.c:10549 rtnl_create_link+0x9d7/0xc00 net/core/rtnetlink.c:3235 veth_newlink+0x20e/0xa90 drivers/net/veth.c:1748 Freed by task 8: ... kfree+0xd6/0x4d0 mm/slub.c:4552 kvfree+0x42/0x50 mm/util.c:615 device_release+0x9f/0x240 drivers/base/core.c:2229 kobject_cleanup lib/kobject.c:673 [inline] kobject_release lib/kobject.c:704 [inline] kref_put include/linux/kref.h:65 [inline] kobject_put+0x1c8/0x540 lib/kobject.c:721 netdev_run_todo+0x72e/0x10b0 net/core/dev.c:10327 After commit faab39f63c1f ("net: allow out-of-order netdev unregistration") and commit e5f80fcf869a ("ipv6: give an IPv6 dev to blackhole_netdev"), we can add dev_hold_track() in macsec_dev_init() and dev_put_track() in macsec_free_netdev() to fix the problem.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 5.18.5-1 | DEBIAN-CVE-2022-49390 |
| Debian:13 | linux | 5.18.5-1 | DEBIAN-CVE-2022-49390 |
| Debian:14 | linux | 5.18.5-1 | DEBIAN-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux | 5.15.0-164.174 | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux | 5.15.0-164.174 | USN-7928-1 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1098.105 | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1098.105 | USN-7928-1 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1102.111 | USN-7928-1 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1102.111 | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1102.111.1 | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1098.107 | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1098.107 | USN-7928-1 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1094.100 | USN-7928-1 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1094.100 | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1081.89 | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1081.89 | USN-7928-1 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1092.95 | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1092.95 | USN-7928-1 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1093.99 | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1093.99 | USN-7928-1 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1090.95 | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1090.95 | USN-7928-5 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-164.174 | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-164.174 | USN-7928-1 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1093.94 | USN-7928-1 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1093.94 | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1050.50 | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1050.50 | USN-7928-1 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1039.39 | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1039.39 | USN-7928-1 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1095.101 | USN-7928-1 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1095.101 | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1092.95 | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1092.95 | USN-7928-4 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1062.66 | UBUNTU-CVE-2022-49390 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1062.66 | USN-7928-1 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 2bce1ebed17da54c65042ec2b962e3234bad5b47 – before 78933cbc143b82d02330e00900d2fd08f2682f4e2bce1ebed17da54c65042ec2b962e3234bad5b47 – before d130282179aa6051449ac8f8df1115769998a6652bce1ebed17da54c65042ec2b962e3234bad5b47 – before 196a888ca6571deb344468e1d7138e32732063351861904a6092ed411203c6a02c75bfc45b27cc3c3a2675a2d97a68332fa5c33043038bfeb31455a8b0add6db3d5ec4561cab257358871a9d3df7f0a34.14.154 – before 4.154.19.84 – before 4.20 |
| Linux | Linux | 5.4 |
Weakness: CWE-416 · Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H