From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-72031][LOW] ata: libata-core: Add NOLPM quirk for PNY CS900 1TB SSD Date: Sat, 15 Aug 2026 02:58:13 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-72031 X-AL-KERNEL-Priority: LOW X-AL-KERNEL-Severity: LOW X-AL-KERNEL-Base-Severity: LOW X-AL-KERNEL-KPANIC: NO X-AL-KERNEL-ActionableScore: 2 X-AL-KERNEL-ActionableScore-Lower: unknown X-AL-KERNEL-Commit: 299739909c486bcea7445f5c3b066fdbc0d2df96 List-Id: CVE: CVE-2026-72031 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: ata: libata-core: Add NOLPM quirk for PNY CS900 1TB SSD Commit: 299739909c486bcea7445f5c3b066fdbc0d2df96 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=299739909c486bcea7445f5c3b066fdbc0d2df96 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72031 Analysis date: Sat, 15 Aug 2026 02:58:13 -0400 ActionableScore: 2 ActionableScore lower bound: unknown Actionable bucket: Ordinary Moderate / Low-like Manual review required: NO Summary: No one-sentence report phrase was found. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-72031 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72031 The original announcement does not normally provide a security severity estimate, CVSS assessment, or enough information to determine whether the reported kernel bug represents a practically relevant security issue. This report was generated by AL-KERNEL, an AI-assisted Linux kernel vulnerability analysis system developed by Alexander Larkin. It combines an autonomous classifier with LLM-assisted technical analysis and a separate ActionableScore mechanism. The purpose of this report is to prioritize Linux kernel CVEs before manual review, identify cases that require prompt investigation, and support automatic closure of issues that are unlikely to have meaningful security impact. Published priority for this report: LOW Manual review required: NO A detailed explanation of the methodology and priority rules is included at the end of this message. ====================================================================== AL-KERNEL CLASSIFICATION RESULT ====================================================================== CVE-2026-72031 LOW CHECK WITH IMPACT FROM ORIG NN LOW Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';CWE-754;CWE-703;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.7';DESCR 'The issue is a hardware specific ATA link power management failure for the PNY CS900 1TB SSD. When Device Initiated Slumber is used with the default med_power_with_dipm policy, the drive may drop off the SATA bus after idle time and the link may not recover, which can force the filesystem into read only mode. For the CVSS the PR:L is used because reliable triggering would require a local user or local workload able to influence idle and storage activity on an already affected host. The issue is not network reachable and does not indicate memory corruption, information disclosure, or privilege escalation. Impact is availability only, with higher operational impact if the affected SSD hosts critical filesystems.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 2) YES SIMPLEFIX HARDWARE LINUS NO NO checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=2 1. ActionableScore * Conservative score: 2 * Paranoid score: 2 * Final recommended bucket: **Ordinary Moderate / Low-like** 2. Signal breakdown * Reliable kernel crash / strong DoS: +1. The SSD can drop off the SATA bus and force the filesystem read-only, which is a real availability failure. * Availability impact realistic: +1. The impact can persist until recovery or reboot if the affected disk hosts an active filesystem. * Important filesystem/storage path: +1. The issue affects ATA storage link stability and can impact mounted filesystems. * Physical-only or rare hardware-only condition: -2. The issue is specific to PNY CS900 1TB SSD hardware and its DIPM/LPM behavior. * Hard or configuration-dependent trigger: -1. It depends on the affected SSD, idle transition into Device-Initiated Slumber, and the med_power_with_dipm policy. * No memory corruption, UAF, OOB, privilege escalation, confidentiality, or integrity primitive is supported by the patch. 3. Reachability analysis A local workload may influence disk activity and idle timing, but the core trigger is a hardware power-management failure rather than a normal attacker-controlled kernel interface. It is not remotely reachable and is not namespace/container amplified. The affected path is only relevant on systems using the specific PNY CS900 1TB SSD with SATA LPM/DIPM enabled. 4. Severity interpretation This behaves like a hardware-specific reliability and availability issue, not an Important-class kernel vulnerability. The realistic impact is filesystem read-only remount or storage outage. There is no evidence of memory corruption, privilege escalation, data disclosure, or attacker-controlled corruption of filesystem contents. 5. One-sentence report phrase A hardware-specific SATA LPM failure on PNY CS900 1TB SSDs can cause the drive to drop off the bus after DIPM idle state and force filesystems read-only, resulting in local availability impact only. 6. Manual review recommendation NO MANUAL CHECK NEEDED. This can be autoclosable for security triage because the patch is a device-specific NOLPM quirk with no supported memory-corruption or privilege-escalation primitive. ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: ata: libata-core: Add NOLPM quirk for PNY CS900 1TB SSD Commit: 299739909c486bcea7445f5c3b066fdbc0d2df96 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=299739909c486bcea7445f5c3b066fdbc0d2df96 Commit description: The PNY CS900 1TB SSD (Phison PS3111-S11, DRAM-less) drops off the bus after entering Device-Initiated Slumber during idle. With the default med_power_with_dipm policy the link goes down (SStatus 1 SControl 300) and does not recover, forcing the filesystem read-only. Forcing max_performance keeps the link stable across prolonged idle. Add a NOLPM quirk so link power management is disabled for this drive specifically, leaving it intact for other devices on the host. Cc: stable@vger.kernel.org Signed-off-by: Bryam Vargas Reviewed-by: Niklas Cassel Signed-off-by: Damien Le Moal Signed-off-by: Greg Kroah-Hartman Changed files: drivers/ata/libata-core.c Diff excerpt: Not included in this email. See the upstream URL for the full patch. Full patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=299739909c486bcea7445f5c3b066fdbc0d2df96 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-72031 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72031 The original CVE announcement normally does not include a security-level estimate. In particular, it may not contain a CVSS assessment, an impact level, or enough information to determine whether the reported bug is a practically relevant security issue. One purpose of this parallel CVE list is to provide that missing technical and prioritization information. The original goal of the AL-KERNEL project was to prioritize Linux kernel CVE analysis automatically before manual review. The system can also help identify non-security issues that may be suitable for automatic closure. This report was generated by AL-KERNEL, an AI-assisted Linux kernel vulnerability analysis system developed by Alexander Larkin. The first analysis stage combines an autonomous classifier with additional LLM-based analysis. The autonomous classifier runs locally on a CPU and is based on a backpropagation neural network. Together, these mechanisms produce a technical vulnerability description, identify likely weakness types, estimate CVSS severity, and provide input for ActionableScore. Two CVSS estimates are retained because incomplete kernel vulnerability information often permits more than one defensible interpretation: Conservative CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H The Best / paranoid CVSS score: 4.7 The conservative vector represents a lower-impact interpretation. The Best/paranoid vector intentionally represents a plausible upper-bound interpretation and should not automatically be treated as demonstrated real-world impact. CVSS may also need to be adjusted for a particular Linux deployment, because actual reachability, privileges, enabled kernel configuration, hardware, namespaces, exposed device nodes, and other environmental conditions can differ significantly between systems. A separate ActionableScore mechanism evaluates practical remediation urgency. Its analysis may include reachability, attack prerequisites, subsystem exposure, memory-corruption characteristics, denial-of-service reliability, and possible confidentiality, integrity, or privilege-escalation impact. Conservative ActionableScore: unknown Paranoid ActionableScore: 2 The final base severity is taken directly from the second tab-separated field of the AL-KERNEL classification result. ActionableScore does not replace or independently override that final AL-KERNEL decision, and if ActionableScore adjusted impact level of ALKERNEL, then you would see self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7. For an AL-KERNEL result of MODERATE, this report uses the following additional presentation split: ActionableScore below 5 -> MODERATE REGULAR ActionableScore 5 or more -> MODERATE 7.0 The distinction between MODERATE REGULAR and MODERATE 7.0 makes it possible to identify Moderate issues that should receive manual analysis and fixes before lower-priority MODERATE REGULAR issues. In many cases, MODERATE REGULAR fixes may wait for a later rebase or routine update. There is one override in which MODERATE REGULAR becomes MODERATE 7.0 even when the ActionableScore is below 5. When the AL-KERNEL result contains the KPANIC flag, a MODERATE result is always presented as MODERATE 7.0. The KPANIC flag selected with few regexps without usage of AI at all, so it helps to detect cases when Kernel Crash happens and similar (to filter False-Negative results from the LLM usage). KPANIC indicates that a reliable kernel crash, kernel panic, or similarly serious kernel availability impact was identified by the classification workflow. AL-KERNEL base severity for this report: LOW KPANIC detected for this report: NO Published priority for this report (same as in Subject): LOW These results are intended to support engineering triage. They are machine-generated estimates, and cases marked for manual review should be validated by a human security engineer before final disposition. For more info read docs linked from here: https://kernelcve.org/ (and you can submit you own patch there to generate such a report for non-existant CVE-id yet). Note that in many cases this AI tool selects higher severity, than real is (means you can expect Importants instead of Moderate 7.0 or Moderates 7.0 instead of regular Moderates). If you see such cases, please use reply email interface to add additional manual analyses info to this particular CVE. And please, please, let me know when you see Lows instead of Importants or Important instead of Low (because particular for such cases I need to tune this AI tool to make it better for this one and next similar). My contact email for such notifications is alexanjelausa@gmail.com (and both send reply to CVE record itself too and see "reply" button below for howto reply).