UBUNTU-CVE-2025-40118
In the Linux kernel, the following vulnerability has been resolved: scsi: pm80xx: Fix array-index-out-of-of-bounds on rmmod Since commit f7b705c238d1 ("scsi: pm80xx: Set phy_attached to zero when device is gone") UBSAN reports: UBSAN: array-index-out-of-bounds in drivers/scsi/pm8001/pm8001_sas.c:786:17 index 28 is out of range for type 'pm8001_phy [16]' on rmmod when using an expander. For a direct attached device, attached_phy contains the local phy id. For a device behind an expander, attached_phy contains the remote phy id, not the local phy id. I.e. while pm8001_ha will have pm8001_ha->chip->n_phy local phys, for a device behind an expander, attached_phy can be much larger than pm8001_ha->chip->n_phy (depending on the amount of phys of the expander). E.g. on my system pm8001_ha has 8 phys with phy ids 0-7. One of the ports has an expander connected. The expander has 31 phys with phy ids 0-30. The pm8001_ha->phy array only contains the phys of the HBA. It does not contain the phys of the expander. Thus, it is wrong to use attached_phy to index the pm8001_ha->phy array for a device behind an expander. Thus, we can only clear phy_attached for devices that are directly attached.
02 / AFFECTED SOFTWARE
Affected packages
11 explicit affected versions
78 explicit affected versions
50 explicit affected versions
6 explicit affected versions
12 explicit affected versions
19 explicit affected versions
10 explicit affected versions
6 explicit affected versions
88 explicit affected versions
24 explicit affected versions
73 explicit affected versions
73 explicit affected versions
79 explicit affected versions
68 explicit affected versions
10 explicit affected versions
30 explicit affected versions
26 explicit affected versions
80 explicit affected versions
7 explicit affected versions
77 explicit affected versions
34 explicit affected versions
13 explicit affected versions
37 explicit affected versions
35 explicit affected versions
40 explicit affected versions
38 explicit affected versions
18 explicit affected versions
35 explicit affected versions
64 explicit affected versions
39 explicit affected versions
13 explicit affected versions
4 explicit affected versions
23 explicit affected versions
45 explicit affected versions
1 explicit affected versions
21 explicit affected versions
16 explicit affected versions
10 explicit affected versions
12 explicit affected versions
41 explicit affected versions
8 explicit affected versions
7 explicit affected versions
12 explicit affected versions
11 explicit affected versions
7 explicit affected versions
12 explicit affected versions
14 explicit affected versions
10 explicit affected versions
1 explicit affected versions
7 explicit affected versions
12 explicit affected versions
1 explicit affected versions
12 explicit affected versions
34 explicit affected versions
34 explicit affected versions
16 explicit affected versions
9 explicit affected versions
27 explicit affected versions
10 explicit affected versions
37 explicit affected versions
1 explicit affected versions
13 explicit affected versions
33 explicit affected versions
3 explicit affected versions
10 explicit affected versions
11 explicit affected versions
55 explicit affected versions
26 explicit affected versions
5 explicit affected versions
13 explicit affected versions
27 explicit affected versions
29 explicit affected versions
13 explicit affected versions
12 explicit affected versions
85 explicit affected versions
34 explicit affected versions
34 explicit affected versions
80 explicit affected versions
43 explicit affected versions
33 explicit affected versions
23 explicit affected versions
49 explicit affected versions
10 explicit affected versions
13 explicit affected versions
12 explicit affected versions
11 explicit affected versions
5 explicit affected versions
12 explicit affected versions
1 explicit affected versions
7 explicit affected versions
12 explicit affected versions
8 explicit affected versions
5 explicit affected versions
65 explicit affected versions
81 explicit affected versions
10 explicit affected versions
26 explicit affected versions
32 explicit affected versions
57 explicit affected versions
28 explicit affected versions
40 explicit affected versions
11 explicit affected versions
1 explicit affected versions
13 explicit affected versions
39 explicit affected versions
16 explicit affected versions
79 explicit affected versions
43 explicit affected versions
3 explicit affected versions
7 explicit affected versions
7 explicit affected versions
51 explicit affected versions
8 explicit affected versions
18 explicit affected versions
35 explicit affected versions
12 explicit affected versions
66 explicit affected versions
68 explicit affected versions
1 explicit affected versions
27 explicit affected versions
54 explicit affected versions
36 explicit affected versions
8 explicit affected versions
45 explicit affected versions
5 explicit affected versions
8 explicit affected versions
10 explicit affected versions
7 explicit affected versions
39 explicit affected versions
13 explicit affected versions
13 explicit affected versions
7 explicit affected versions
10 explicit affected versions
12 explicit affected versions
9 explicit affected versions
28 explicit affected versions
44 explicit affected versions
16 explicit affected versions
3 explicit affected versions
13 explicit affected versions
26 explicit affected versions
45 explicit affected versions
37 explicit affected versions
44 explicit affected versions
14 explicit affected versions
38 explicit affected versions
9 explicit affected versions
9 explicit affected versions
11 explicit affected versions
32 explicit affected versions
15 explicit affected versions
6 explicit affected versions
81 explicit affected versions
7 explicit affected versions
4 explicit affected versions
70 explicit affected versions
1 explicit affected versions
79 explicit affected versions
70 explicit affected versions
69 explicit affected versions
13 explicit affected versions
43 explicit affected versions
6 explicit affected versions
10 explicit affected versions
8 explicit affected versions
38 explicit affected versions
14 explicit affected versions
4 explicit affected versions
78 explicit affected versions
6 explicit affected versions
11 explicit affected versions
1 explicit affected versions
12 explicit affected versions
32 explicit affected versions
69 explicit affected versions
03 / CONNECTIONS
Connected vulnerabilities
04 / EVIDENCE
Source records
In the Linux kernel, the following vulnerability has been resolved: scsi: pm80xx: Fix array-index-out-of-of-bounds on rmmod Since commit f7b705c238d1 ("scsi: pm80xx: Set phy_attached to zero when device is gone") UBSAN reports: UBSAN: array-index-out-of-bounds in drivers/scsi/pm8001/pm8001_sas.c:786:17 index 28 is out of range for type 'pm8001_phy [16]' on rmmod when using an expander. For a direct attached device, attached_phy contains the local phy id. For a device behind an expander, attached_phy contains the remote phy id, not the local phy id. I.e. while pm8001_ha will have pm8001_ha->chip->n_phy local phys, for a device behind an expander, attached_phy can be much larger than pm8001_ha->chip->n_phy (depending on the amount of phys of the expander). E.g. on my system pm8001_ha has 8 phys with phy ids 0-7. One of the ports has an expander connected. The expander has 31 phys with phy ids 0-30. The pm8001_ha->phy array only contains the phys of the HBA. It does not contain the phys of the expander. Thus, it is wrong to use attached_phy to index the pm8001_ha->phy array for a device behind an expander. Thus, we can only clear phy_attached for devices that are directly attached.
05 / REFERENCES
Further evidence
- https://git.kernel.org/linus/251be2f6037fb7ab399f68cd7428ff274133d693
- https://git.kernel.org/stable/c/251be2f6037fb7ab399f68cd7428ff274133d693
- https://git.kernel.org/stable/c/45acbf154befedd9bc135f5e031fe7855d1e6493
- https://git.kernel.org/stable/c/83ced3c206c292458e47c7fac54223abc7141585
- https://git.kernel.org/stable/c/9326a1541e1b7ed3efdbab72061b82cf01c6477a
- https://git.kernel.org/stable/c/9c671d4dbfbfb0d73cfdfb706afb36d9ad60a582
- https://git.kernel.org/stable/c/d94be0a6ae9ade706d4270e740bdb4f79953a7fc
- https://git.kernel.org/stable/c/e62251954a128a2d0fcbc19e5fa39e08935bb628
- https://git.kernel.org/stable/c/eef5ef400893f8e3dbb09342583be0cdc716d566
- https://ubuntu.com/security/CVE-2025-40118
- https://ubuntu.com/security/notices/USN-8029-1
- https://ubuntu.com/security/notices/USN-8029-2
- https://ubuntu.com/security/notices/USN-8029-3
- https://ubuntu.com/security/notices/USN-8030-1
- https://ubuntu.com/security/notices/USN-8033-1
- https://ubuntu.com/security/notices/USN-8033-2
- https://ubuntu.com/security/notices/USN-8033-3
- https://ubuntu.com/security/notices/USN-8033-4
- https://ubuntu.com/security/notices/USN-8033-5
- https://ubuntu.com/security/notices/USN-8033-6
- https://ubuntu.com/security/notices/USN-8033-7
- https://ubuntu.com/security/notices/USN-8033-8
- https://ubuntu.com/security/notices/USN-8034-1
- https://ubuntu.com/security/notices/USN-8034-2
- https://ubuntu.com/security/notices/USN-8048-1
- https://ubuntu.com/security/notices/USN-8095-1
- https://ubuntu.com/security/notices/USN-8095-2
- https://ubuntu.com/security/notices/USN-8095-3
- https://ubuntu.com/security/notices/USN-8095-4
- https://ubuntu.com/security/notices/USN-8095-5
- https://ubuntu.com/security/notices/USN-8100-1
- https://ubuntu.com/security/notices/USN-8125-1
- https://ubuntu.com/security/notices/USN-8126-1
- https://ubuntu.com/security/notices/USN-8141-1
- https://ubuntu.com/security/notices/USN-8163-1
- https://ubuntu.com/security/notices/USN-8163-2
- https://ubuntu.com/security/notices/USN-8165-1
- https://ubuntu.com/security/notices/USN-8243-1
- https://ubuntu.com/security/notices/USN-8261-1
- https://www.cve.org/CVERecord?id=CVE-2025-40118