Description
In the Linux kernel, the following vulnerability has been resolved:
i2c: piix4: Fix adapter not be removed in piix4_remove()
In piix4_probe(), the piix4 adapter will be registered in:
piix4_probe()
piix4_add_adapters_sb800() / piix4_add_adapter()
i2c_add_adapter()
Based on the probed device type, piix4_add_adapters_sb800() or single
piix4_add_adapter() will be called.
For the former case, piix4_adapter_count is set as the number of adapters,
while for antoher case it is not set and kept default *zero*.
When piix4 is removed, piix4_remove() removes the adapters added in
piix4_probe(), basing on the piix4_adapter_count value.
Because the count is zero for the single adapter case, the adapter won't
be removed and makes the sources allocated for adapter leaked, such as
the i2c client and device.
These sources can still be accessed by i2c or bus and cause problems.
An easily reproduced case is that if a new adapter is registered, i2c
will get the leaked adapter and try to call smbus_algorithm, which was
already freed:
Triggered by: rmmod i2c_piix4 && modprobe max31730
BUG: unable to handle page fault for address: ffffffffc053d860
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 3752 Comm: modprobe Tainted: G
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996)
RIP: 0010:i2c_default_probe (drivers/i2c/i2c-core-base.c:2259) i2c_core
RSP: 0018:ffff888107477710 EFLAGS: 00000246
...
<TASK>
i2c_detect (drivers/i2c/i2c-core-base.c:2302) i2c_core
__process_new_driver (drivers/i2c/i2c-core-base.c:1336) i2c_core
bus_for_each_dev (drivers/base/bus.c:301)
i2c_for_each_dev (drivers/i2c/i2c-core-base.c:1823) i2c_core
i2c_register_driver (drivers/i2c/i2c-core-base.c:1861) i2c_core
do_one_initcall (init/main.c:1296)
do_init_module (kernel/module/main.c:2455)
...
</TASK>
---[ end trace 0000000000000000 ]---
Fix this problem by correctly set piix4_adapter_count as 1 for the
single adapter so it can be normally removed.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| Linux | Linux | 5.4 | 5.10.154 |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Debian
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian 14 | linux | 6.0.8-1 | — |
| Debian 13 | linux | 6.0.8-1 | — |
| Debian 12 | linux | 6.0.8-1 | — |
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu Nvidia-BlueField 22.04 LTS | linux-bluefield | 5.15.0-1014.16 | — |
| Ubuntu 24.04 LTS | linux-realtime +1 | No fix yet | — |
| Ubuntu 22.04 LTS | linux +1 | 5.15.0-60.66 | — |
| Ubuntu 22.04 LTS | linux-aws | 5.15.0-1030.34 | — |
| Ubuntu 22.04 LTS | linux-azure | 5.15.0-1033.40 | — |
| Ubuntu 22.04 LTS | linux-azure-fde | 5.15.0-1033.40.1 | — |
| Ubuntu 22.04 LTS | linux-gcp | 5.15.0-1029.36 | — |
| Ubuntu 22.04 LTS | linux-gke | 5.15.0-1027.32 | — |
| Ubuntu 22.04 LTS | linux-gkeop | 5.15.0-1015.19 | — |
| Ubuntu 22.04 LTS | linux-ibm | 5.15.0-1025.28 | — |
| Ubuntu 22.04 LTS | linux-intel-iotg | 5.15.0-1025.30 | — |
| Ubuntu 22.04 LTS | linux-kvm | 5.15.0-1028.33 | — |
| Ubuntu 22.04 LTS | linux-nvidia | 5.15.0-1017.17 | — |
| Ubuntu 22.04 LTS | linux-oracle | 5.15.0-1029.35 | — |
| Ubuntu 22.04 LTS | linux-raspi | 5.15.0-1024.26 | — |
| Ubuntu 22.04 LTS | linux-riscv +32 | No fix yet | — |
| Ubuntu 20.04 LTS | linux-aws-5.15 | 5.15.0-1030.34~20.04.1 | — |
| Ubuntu 20.04 LTS | linux-azure-5.15 | 5.15.0-1033.40~20.04.1 | — |
| Ubuntu 20.04 LTS | linux-gcp-5.15 | 5.15.0-1029.36~20.04.1 | — |
| Ubuntu 20.04 LTS | linux-gke +28 | No fix yet | — |
| Ubuntu 20.04 LTS | linux-hwe-5.15 +1 | 5.15.0-60.66~20.04.1 | — |
| Ubuntu 20.04 LTS | linux-intel-iotg-5.15 | 5.15.0-1025.30~20.04.1 | — |
| Ubuntu 20.04 LTS | linux-oracle-5.15 | 5.15.0-1029.35~20.04.1 | — |
| Ubuntu 20.04 LTS | linux-riscv-5.15 | 5.15.0-1029.33~20.04.1 | — |
| Ubuntu 18.04 LTS | linux-gcp +14 | No fix yet | — |
Show 5 more (older releases, extended support, other products)Fewer releases
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 16.04 LTS | linux-hwe-edge | No fix yet | — |
| Ubuntu Pro FIPS 20.04 LTS | linux-fips +3 | No fix yet | — |
| Ubuntu Pro FIPS-updates 20.04 LTS | linux-fips +3 | No fix yet | — |
| Ubuntu Pro 20.04 LTS | linux +10 | No fix yet | — |
| Ubuntu Pro 18.04 LTS | linux-aws-5.4 +6 | No fix yet | — |
SUSE
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| SLES 15 SP5 | kernel-64kb +6 | 5.14.21-150500.55.110.1 | SUSE-SU-2025:02173-1 |
| SLES 15 SP5 | kernel-default-base | 5.14.21-150500.55.110.1.150500.6.51.3 | SUSE-SU-2025:02173-1 |
| SLES 15 SP4 | kernel-64kb +6 | 5.14.21-150400.24.167.1 | SUSE-SU-2025:02262-1 |
| SLES 15 SP4 | kernel-default-base | 5.14.21-150400.24.167.1.150400.24.84.1 | SUSE-SU-2025:02262-1 |
Show 11 more (older releases, extended support, other products)Fewer releases
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| SLES for SAP 15 SP5 | kernel-default-base | 5.14.21-150500.55.110.1.150500.6.51.3 | SUSE-SU-2025:02173-1 |
| SLES for SAP 15 SP5 | kernel-docs +4 | 5.14.21-150500.55.110.1 | SUSE-SU-2025:02173-1 |
| SLES for SAP 15 SP4 | kernel-default-base | 5.14.21-150400.24.167.1.150400.24.84.1 | SUSE-SU-2025:02262-1 |
| SLES for SAP 15 SP4 | kernel-docs +4 | 5.14.21-150400.24.167.1 | SUSE-SU-2025:02262-1 |
| SLE Micro 5.5 | kernel-default-base | 5.14.21-150500.55.110.1.150500.6.51.3 | SUSE-SU-2025:02173-1 |
| SLE Micro 5.5 | kernel-rt +1 | 5.14.21-150500.13.97.1 | SUSE-SU-2025:01966-1 |
| SLE Micro 5.5 | kernel-source +1 | 5.14.21-150500.55.110.1 | SUSE-SU-2025:02173-1 |
| SLE Micro 5.4 | kernel-default | 5.14.21-150400.24.167.1 | SUSE-SU-2025:02262-1 |
| SLE Micro 5.4 | kernel-default-base | 5.14.21-150400.24.167.1.150400.24.84.1 | SUSE-SU-2025:02262-1 |
| SLE Micro 5.4 | kernel-rt +1 | 5.14.21-150400.15.121.1 | SUSE-SU-2025:01918-1 |
| SLE Micro 5.3 | kernel-default | 5.14.21-150400.24.167.1 | SUSE-SU-2025:02262-1 |
| SLE Micro 5.3 | kernel-default-base | 5.14.21-150400.24.167.1.150400.24.84.1 | SUSE-SU-2025:02262-1 |
| SLE Micro 5.3 | kernel-rt +1 | 5.14.21-150400.15.121.1 | SUSE-SU-2025:01918-1 |
| SLE Live Patching 15 SP5 | kernel-default | 5.14.21-150500.55.110.1 | SUSE-SU-2025:02173-1 |
| SLE Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_27 | 1-150500.11.7.1 | SUSE-SU-2025:02173-1 |
| SLE Live Patching 15 SP4 | kernel-default | 5.14.21-150400.24.167.1 | SUSE-SU-2025:02262-1 |
| SLE Live Patching 15 SP4 | kernel-livepatch-SLE15-SP4_Update_41 | 1-150400.9.3.1 | SUSE-SU-2025:02262-1 |
| SLE HPC 15 SP5 | kernel-64kb +5 | 5.14.21-150500.55.110.1 | SUSE-SU-2025:02173-1 |
| SLE HPC 15 SP5 | kernel-default-base | 5.14.21-150500.55.110.1.150500.6.51.3 | SUSE-SU-2025:02173-1 |
| SLE HPC 15 SP4 | kernel-64kb +5 | 5.14.21-150400.24.167.1 | SUSE-SU-2025:02262-1 |
| SLE HPC 15 SP4 | kernel-default-base | 5.14.21-150400.24.167.1.150400.24.84.1 | SUSE-SU-2025:02262-1 |
| SUSE Manager Server 4.3 | kernel-default-base | 5.14.21-150400.24.167.1.150400.24.84.1 | SUSE-SU-2025:02262-1 |
| SUSE Manager Server 4.3 | kernel-syms +3 | 5.14.21-150400.24.167.1 | SUSE-SU-2025:02262-1 |
| SUSE Manager Proxy 4.3 | kernel-default-base | 5.14.21-150400.24.167.1.150400.24.84.1 | SUSE-SU-2025:02262-1 |
| SUSE Manager Proxy 4.3 | kernel-syms +2 | 5.14.21-150400.24.167.1 | SUSE-SU-2025:02262-1 |
Advisories 5
- WID-SEC-2025-0922 Linux Kernel: Mehrere Schwachstellen BSI CERT-Bund (WID) · Nov 9, 2026
- SUSE-SU-2025:02262-1 Security update for the Linux Kernel SUSE / openSUSE Security Updates · Feb 4, 2026
- SUSE-SU-2025:01918-1 Security update for the Linux Kernel SUSE / openSUSE Security Updates · Feb 4, 2026
- SUSE-SU-2025:02173-1 Security update for the Linux Kernel SUSE / openSUSE Security Updates · Feb 4, 2026
- SUSE-SU-2025:01966-1 Security update for the Linux Kernel SUSE / openSUSE Security Updates · Feb 4, 2026