Description
In the Linux kernel, the following vulnerability has been resolved:
RISC-V: Make port I/O string accessors actually work
Fix port I/O string accessors such as `insb', `outsb', etc. which use
the physical PCI port I/O address rather than the corresponding memory
mapping to get at the requested location, which in turn breaks at least
accesses made by our parport driver to a PCIe parallel port such as:
PCI parallel port detected: 1415:c118, I/O at 0x1000(0x1008), IRQ 20
parport0: PC-style at 0x1000 (0x1008), irq 20, using FIFO [PCSPP,TRISTATE,COMPAT,EPP,ECP]
causing a memory access fault:
Unable to handle kernel access to user memory without uaccess routines at virtual address 0000000000001008
Oops [#1]
Modules linked in:
CPU: 1 PID: 350 Comm: cat Not tainted 6.0.0-rc2-00283-g10d4879f9ef0-dirty #23
Hardware name: SiFive HiFive Unmatched A00 (DT)
epc : parport_pc_fifo_write_block_pio+0x266/0x416
ra : parport_pc_fifo_write_block_pio+0xb4/0x416
epc : ffffffff80542c3e ra : ffffffff80542a8c sp : ffffffd88899fc60
gp : ffffffff80fa2700 tp : ffffffd882b1e900 t0 : ffffffd883d0b000
t1 : ffffffffff000002 t2 : 4646393043330a38 s0 : ffffffd88899fcf0
s1 : 0000000000001000 a0 : 0000000000000010 a1 : 0000000000000000
a2 : ffffffd883d0a010 a3 : 0000000000000023 a4 : 00000000ffff8fbb
a5 : ffffffd883d0a001 a6 : 0000000100000000 a7 : ffffffc800000000
s2 : ffffffffff000002 s3 : ffffffff80d28880 s4 : ffffffff80fa1f50
s5 : 0000000000001008 s6 : 0000000000000008 s7 : ffffffd883d0a000
s8 : 0004000000000000 s9 : ffffffff80dc1d80 s10: ffffffd8807e4000
s11: 0000000000000000 t3 : 00000000000000ff t4 : 393044410a303930
t5 : 0000000000001000 t6 : 0000000000040000
status: 0000000200000120 badaddr: 0000000000001008 cause: 000000000000000f
[<ffffffff80543212>] parport_pc_compat_write_block_pio+0xfe/0x200
[<ffffffff8053bbc0>] parport_write+0x46/0xf8
[<ffffffff8050530e>] lp_write+0x158/0x2d2
[<ffffffff80185716>] vfs_write+0x8e/0x2c2
[<ffffffff80185a74>] ksys_write+0x52/0xc2
[<ffffffff80185af2>] sys_write+0xe/0x16
[<ffffffff80003770>] ret_from_syscall+0x0/0x2
---[ end trace 0000000000000000 ]---
For simplicity address the problem by adding PCI_IOBASE to the physical
address requested in the respective wrapper macros only, observing that
the raw accessors such as `__insb', `__outsb', etc. are not supposed to
be used other than by said macros. Remove the cast to `long' that is no
longer needed on `addr' now that it is used as an offset from PCI_IOBASE
and add parentheses around `addr' needed for predictable evaluation in
macro expansion. No need to make said adjustments in separate changes
given that current code is gravely broken and does not ever work.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| Linux | Linux | 4.15 | 5.4.220 |
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.3-1 | — |
| Debian 13 | linux | 6.0.3-1 | — |
| Debian 12 | linux | 6.0.3-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-riscv +10 | 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 | 5.4.0-139.156 | — |
| Ubuntu 20.04 LTS | linux-aws | 5.4.0-1096.104 | — |
| Ubuntu 20.04 LTS | linux-aws-5.15 | 5.15.0-1030.34~20.04.1 | — |
| Ubuntu 20.04 LTS | linux-azure | 5.4.0-1103.109 | — |
| Ubuntu 20.04 LTS | linux-azure-5.15 | 5.15.0-1033.40~20.04.1 | — |
| Ubuntu 20.04 LTS | linux-bluefield | 5.4.0-1058.64 | — |
| Ubuntu 20.04 LTS | linux-gcp | 5.4.0-1100.109 | — |
| 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-ibm | 5.4.0-1044.49 | — |
| Ubuntu 20.04 LTS | linux-intel-iotg-5.15 | 5.15.0-1025.30~20.04.1 | — |
| Ubuntu 20.04 LTS | linux-iot | 5.4.0-1012.14 | — |
| Ubuntu 20.04 LTS | linux-kvm | 5.4.0-1086.92 | — |
| Ubuntu 20.04 LTS | linux-oracle | 5.4.0-1093.102 | — |
| Ubuntu 20.04 LTS | linux-oracle-5.15 | 5.15.0-1029.35~20.04.1 | — |
| Ubuntu 20.04 LTS | linux-raspi | 5.4.0-1080.91 | — |
| Ubuntu 20.04 LTS | linux-riscv-5.15 | 5.15.0-1029.33~20.04.1 | — |
| Ubuntu 20.04 LTS | linux-xilinx-zynqmp | 5.4.0-1021.25 | — |
| Ubuntu 18.04 LTS | linux-aws-5.4 | 5.4.0-1096.104~18.04.1 | — |
| Ubuntu 18.04 LTS | linux-azure-5.4 | 5.4.0-1103.109~18.04.1 | — |
| Ubuntu 18.04 LTS | linux-gcp +14 | No fix yet | — |
| Ubuntu 18.04 LTS | linux-gcp-5.4 | 5.4.0-1100.109~18.04.1 | — |
| Ubuntu 18.04 LTS | linux-hwe-5.4 | 5.4.0-139.156~18.04.1 | — |
| Ubuntu 18.04 LTS | linux-ibm-5.4 | 5.4.0-1044.49~18.04.1 | — |
| Ubuntu 18.04 LTS | linux-oracle-5.4 | 5.4.0-1093.102~18.04.1 | — |
| Ubuntu 18.04 LTS | linux-raspi-5.4 | 5.4.0-1080.91~18.04.1 | — |
Show 8 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 18.04 LTS | linux-fips +3 | No fix yet | — |
| Ubuntu Pro FIPS-updates 20.04 LTS | linux-aws-fips | 5.4.0-1096.104+fips1 | — |
| Ubuntu Pro FIPS-updates 20.04 LTS | linux-azure-fips | 5.4.0-1103.109+fips1 | — |
| Ubuntu Pro FIPS-updates 20.04 LTS | linux-fips | 5.4.0-1072.81 | — |
| Ubuntu Pro FIPS-updates 20.04 LTS | linux-gcp-fips | 5.4.0-1100.109+fips1 | — |
| Ubuntu Pro FIPS-updates 18.04 LTS | linux-fips +3 | No fix yet | — |
| Ubuntu Pro 18.04 LTS | linux +5 | No fix yet | — |
| Ubuntu Pro 16.04 LTS | linux-gcp +4 | No fix yet | — |
| Ubuntu Pro 14.04 LTS | linux-azure | No fix yet | — |
Advisories 1
- WID-SEC-2025-2765 Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service BSI CERT-Bund (WID) · Nov 12, 2026
References
- https://git.kernel.org/stable/c/2c60db6869fe5213471fcf4fe5704dc29da8b5ee
- https://git.kernel.org/stable/c/2ce9fab94b8db61f014e43ddf80dd1524ae6dff4
- https://git.kernel.org/stable/c/dc235db7b79a352d07d62e8757ad856dbf1564c1
- https://git.kernel.org/stable/c/140b2b92dbefffa7f4f7211a1fd399a6e79e71c4
- https://git.kernel.org/stable/c/1acee4616930fc07265cb8e539753a8062daa8e0
- https://git.kernel.org/stable/c/9cc205e3c17d5716da7ebb7fa0c985555e95d009