SECUFOCUSNOW
Home›CVE index›CVE-2022-50315
Review reviewHigh

CVE-2022-50315

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: ata: ahci: Match EM_MAX_SLOTS with SATA_PMP_MAX_PORTS UBSAN complains about array-index-out-of-bounds: [ 1.980703] kernel: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 [ 1.980709] kernel: index 15 is out of range for type 'ahci_em_priv [8]' [ 1.980713] kernel: CPU: 0 PID: 209 Comm: scsi_eh_8 Not tainted 5.15.0-25-generic #25-Ubuntu [ 1.980716] kernel: Hardware name: System manufacturer System Product Name/P5Q3, BIOS 1102 06/11/2010 [ 1.980718] kernel: Call Trace: [ 1.9807...

CVSS
7.8
EPSS
-
- percentile
CISA KEV
Not listed
Published
2025.09.16
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: ata: ahci: Match EM_MAX_SLOTS with SATA_PMP_MAX_PORTS UBSAN complains about array-index-out-of-bounds: [ 1.980703] kernel: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 [ 1.980709] kernel: index 15 is out of range for type 'ahci_em_priv [8]' [ 1.980713] kernel: CPU: 0 PID: 209 Comm: scsi_eh_8 Not tainted 5.15.0-25-generic #25-Ubuntu [ 1.980716] kernel: Hardware name: System manufacturer System Product Name/P5Q3, BIOS 1102 06/11/2010 [ 1.980718] kernel: Call Trace: [ 1.9807...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 18f7ba4c2f4be6b37d925931f04d6cc28d88d1ee < f70bd4339cb68bc7e206af4c922bc0d249244403, >= 18f7ba4c2f4be6b37d925931f04d6cc28d88d1ee < da2ea4a961d9f89ed248734e7032350c260dc3a3, >= 18f7ba4c2f4be6b37d925931f04d6cc28d88d1ee < 67a00c299c5c143817c948fbc7de1a2fa1af38fb, >= 18f7ba4c2f4be6b37d925931f04d6cc28d88d1ee < 383b7c50f5445ff8dbbf03080905648d6980c39d, >= 18f7ba4c2f4be6b37d925931f04d6cc28d88d1ee < 303d0f761431d848dd8d7ff9fd9b8c101879cabe, >= 18f7ba4c2f4be6b37d925931f04d6cc28d88d1ee < 8fbe13de1cc7cef2564be3cbf60400b33eee023b, >= 18f7ba4c2f4be6b37d925931f04d6cc28d88d1ee < d6314d5f68764550c84d732ce901ddd3ac6b415f, >= 18f7ba4c2f4be6b37d925931f04d6cc28d88d1ee < 1e41e693f458eef2d5728207dbd327cd3b16580a, >= 2.6.27, < 4.9.332, >= 4.10 < 4.14.298, >= 4.15 < 4.19.264, >= 4.20 < 5.4.221, >= 5.5 < 5.10.152, >= 5.11 < 5.15.76, >= 5.16 < 6.0.6, 6.1
Fixed versions
4.9.332, 4.14.298, 4.19.264, 5.4.221, 5.10.152, 5.15.76, 6.0.6

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-129