CVE-2022-50315: ata: ahci: Match EM_MAX_SLOTS with SATA_PMP_MAX_PORTS
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1e41e693f458eef2d5728207dbd327cd3b16580a, 303d0f761431d848dd8d7ff9fd9b8c101879cabe, 383b7c50f5445ff8dbbf03080905648d6980c39d.
Low priority for now. Upgrade to Linux Linux 1e41e693f458eef2d5728207dbd327cd3b16580a, 303d0f761431d848dd8d7ff9fd9b8c101879cabe, 383b7c50f5445ff8dbbf03080905648d6980c39d or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.980721] kernel: <TASK> [ 1.980723] kernel: show_stack+0x52/0x58 [ 1.980729] kernel: dump_stack_lvl+0x4a/0x5f [ 1.980734] kernel: dump_stack+0x10/0x12 [ 1.980736] kernel: ubsan_epilogue+0x9/0x45 [ 1.980739] kernel: __ubsan_handle_out_of_bounds.cold+0x44/0x49 [ 1.980742] kernel: ahci_qc_issue+0x166/0x170 [libahci] [ 1.980748] kernel: ata_qc_issue+0x135/0x240 [ 1.980752] kernel: ata_exec_internal_sg+0x2c4/0x580 [ 1.980754] kernel: ? vprintk_default+0x1d/0x20 [ 1.980759] kernel: ata_exec_internal+0x67/0xa0 [ 1.980762] kernel: sata_pmp_read+0x8d/0xc0 [ 1.980765] kernel: sata_pmp_read_gscr+0x3c/0x90 [ 1.980768] kernel: sata_pmp_attach+0x8b/0x310 [ 1.980771] kernel: ata_eh_revalidate_and_attach+0x28c/0x4b0 [ 1.980775] kernel: ata_eh_recover+0x6b6/0xb30 [ 1.980778] kernel: ? ahci_do_hardreset+0x180/0x180 [libahci] [ 1.980783] kernel: ? ahci_stop_engine+0xb0/0xb0 [libahci] [ 1.980787] kernel: ? ahci_do_softreset+0x290/0x290 [libahci] [ 1.980792] kernel: ? trace_event_raw_event_ata_eh_link_autopsy_qc+0xe0/0xe0 [ 1.980795] kernel: sata_pmp_eh_recover.isra.0+0x214/0x560 [ 1.980799] kernel: sata_pmp_error_handler+0x23/0x40 [ 1.980802] kernel: ahci_error_handler+0x43/0x80 [libahci] [ 1.980806] kernel: ata_scsi_port_error_handler+0x2b1/0x600 [ 1.980810] kernel: ata_scsi_error+0x9c/0xd0 [ 1.980813] kernel: scsi_error_handler+0xa1/0x180 [ 1.980817] kernel: ? scsi_unjam_host+0x1c0/0x1c0 [ 1.980820] kernel: kthread+0x12a/0x150 [ 1.980823] kernel: ? set_kthread_struct+0x50/0x50 [ 1.980826] kernel: ret_from_fork+0x22/0x30 [ 1.980831] kernel: </TASK> This happens because sata_pmp_init_links() initialize link->pmp up to SATA_PMP_MAX_PORTS while em_priv is declared as 8 elements array. I can't find the maximum Enclosure Management ports specified in AHCI spec v1.3.1, but "12.2.1 LED message type" states that "Port Multiplier Information" can utilize 4 bits, which implies it can support up to 16 ports. Hence, use SATA_PMP_MAX_PORTS as EM_MAX_SLOTS to resolve the issue. BugLink: https://bugs.launchpad.net/bugs/1970074
- Published
- Sep 15, 2025
- Updated
- Oct 15, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- CWE-129
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 7.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 4.9.332
- linux linux kernel4.10 and later · before 4.14.298
- linux linux kernel4.15 and later · before 4.19.264
- linux linux kernel4.20 and later · before 5.4.221
- linux linux kernel5.5 and later · before 5.10.152
- linux linux kernel5.11 and later · before 5.15.76
- linux linux kernel5.16 and later · before 6.0.6
- linux linux kernel6.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.27affected
- 18f7ba4c2f4be6b37d925931f04d6cc28d88d1ee and later · before f70bd4339cb68bc7e206af4c922bc0d249244403affected · git
- 18f7ba4c2f4be6b37d925931f04d6cc28d88d1ee and later · before da2ea4a961d9f89ed248734e7032350c260dc3a3affected · git
- 18f7ba4c2f4be6b37d925931f04d6cc28d88d1ee and later · before 67a00c299c5c143817c948fbc7de1a2fa1af38fbaffected · git
- 18f7ba4c2f4be6b37d925931f04d6cc28d88d1ee and later · before 383b7c50f5445ff8dbbf03080905648d6980c39daffected · git
- 18f7ba4c2f4be6b37d925931f04d6cc28d88d1ee and later · before 303d0f761431d848dd8d7ff9fd9b8c101879cabeaffected · git
- 18f7ba4c2f4be6b37d925931f04d6cc28d88d1ee and later · before 8fbe13de1cc7cef2564be3cbf60400b33eee023baffected · git
- 18f7ba4c2f4be6b37d925931f04d6cc28d88d1ee and later · before d6314d5f68764550c84d732ce901ddd3ac6b415faffected · git
- 18f7ba4c2f4be6b37d925931f04d6cc28d88d1ee and later · before 1e41e693f458eef2d5728207dbd327cd3b16580aaffected · git
- before 2.6.27not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.0.6-1 | 6.0.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2022-50312Sep 15, 2025 · drivers: serial: jsm: fix some leaks in probe22Monitor
- ← EarlierCVE-2022-50314Sep 15, 2025 · nbd: Fix hung when signal interrupts nbd_start_device_ioctl()22Monitor
- Later →CVE-2022-50317Sep 15, 2025 · drm/bridge: megachips: Fix a null pointer dereference bug22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1e41e693f458eef2d5728207dbd327cd3b16580a | Vendor (CNA) |
| Linux Linux | 303d0f761431d848dd8d7ff9fd9b8c101879cabe | Vendor (CNA) |
| Linux Linux | 383b7c50f5445ff8dbbf03080905648d6980c39d | Vendor (CNA) |
| Linux Linux | 67a00c299c5c143817c948fbc7de1a2fa1af38fb | Vendor (CNA) |
| Linux Linux | 8fbe13de1cc7cef2564be3cbf60400b33eee023b | Vendor (CNA) |
| Linux Linux | d6314d5f68764550c84d732ce901ddd3ac6b415f | Vendor (CNA) |
| Linux Linux | da2ea4a961d9f89ed248734e7032350c260dc3a3 | Vendor (CNA) |
| Linux Linux | f70bd4339cb68bc7e206af4c922bc0d249244403 | Vendor (CNA) |
| debian:linux | 6.0.6-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2021-47548479 days apartethernet: hisilicon: hns: hns_dsaf_misc: fix a possible array overflow in hns_dsaf_ge_srst_by_port()39Monitor
- CVE-2026-64018307 days apartnet: mana: validate rx_req_idx to prevent out-of-bounds array access37Monitor
- CVE-2026-23246184 days apartwifi: mac80211: bounds-check link_id in ieee80211_ml_reconfiguration35Monitor
- CVE-2026-43110233 days apartwifi: brcmfmac: validate bsscfg indices in IF events35Monitor
- CVE-2026-43172233 days apartwifi: iwlwifi: fix 22000 series SMEM parsing35Monitor
- CVE-2023-531920 days apartvxlan: Fix nexthop hash size31Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-129 · Improper Validation of Array IndexCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/303d0f761431d848dd8d7ff9fd9b8c101879cabe
- git.kernel.org/stable/c/383b7c50f5445ff8dbbf03080905648d6980c39d
- git.kernel.org/stable/c/67a00c299c5c143817c948fbc7de1a2fa1af38fb
- git.kernel.org/stable/c/8fbe13de1cc7cef2564be3cbf60400b33eee023b
- git.kernel.org/stable/c/d6314d5f68764550c84d732ce901ddd3ac6b415f
- git.kernel.org/stable/c/da2ea4a961d9f89ed248734e7032350c260dc3a3
- git.kernel.org/stable/c/f70bd4339cb68bc7e206af4c922bc0d249244403
Vendor advisories and official records. Exploit/PoC links are deliberately left out.