From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-72441][MODERATE REGULAR] ieee802154: fix kernel-infoleak in dgram_recvmsg() [ Upstream Date: Sat, 15 Aug 2026 05:04:43 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-72441 X-AL-KERNEL-Priority: MODERATE REGULAR X-AL-KERNEL-Severity: MODERATE REGULAR X-AL-KERNEL-Base-Severity: MODERATE X-AL-KERNEL-KPANIC: NO X-AL-KERNEL-ActionableScore: 2 X-AL-KERNEL-ActionableScore-Lower: 1 X-AL-KERNEL-Commit: a2ee1a038a16e286d084bc293a7522d010a59ec3 List-Id: CVE: CVE-2026-72441 Priority: MODERATE REGULAR AL-KERNEL base severity: MODERATE KPANIC flag: NO Patch: ieee802154: fix kernel-infoleak in dgram_recvmsg() [ Upstream Commit: a2ee1a038a16e286d084bc293a7522d010a59ec3 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a2ee1a038a16e286d084bc293a7522d010a59ec3 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72441 Analysis date: Sat, 15 Aug 2026 05:04:43 -0400 ActionableScore: 2 ActionableScore lower bound: 1 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-72441 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72441 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: MODERATE REGULAR 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-72441 MODERATE CHECK WITH IMPACT FROM ORIG NN LOW Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N';*CWE-200;*CWE-457;CWE-908;BEST CVSS score: '3.3';DESCR 'An IEEE802154 datagram receive path can leak uninitialized kernel stack bytes because ieee802154_hdr_get_addr left pan_id uninitialized when the address mode is IEEE802154_ADDR_NONE. The uninitialized pan_id can later be copied into sockaddr_ieee802154 in dgram_recvmsg and returned to userspace through recvmsg. For the CVSS the PR:L means a local unprivileged user or process must be able to receive IEEE802154 datagram traffic and call recvmsg. The issue is not directly network exploitable in the usual CVSS sense because the leaked bytes are delivered to the local receiving process, although an adjacent IEEE802154 sender may influence packet delivery. Impact is limited confidentiality exposure from a kernel infoleak, with no supported integrity or availability impact.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 2) YES KASAN OOB LEAK LINUS SYZBOT INCREASED_FROM_LOW_BASED_ON_REQUIREMANUALCHECK DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5 NO NO checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=2 ActionableScoreLower=1 1. ActionableScore * Conservative score: 1 * Paranoid score: 2 * Final recommended bucket: **Ordinary Moderate / Low-like** 2. Signal breakdown * Local unprivileged trigger: +1. A local process able to use IEEE802154 datagram sockets and call recvmsg can receive the leaked sockaddr data. * Confidentiality impact plausible: +1. KMSAN shows uninitialized kernel stack bytes copied to userspace through move_addr_to_user. * Rare AND difficult-to-reach subsystem/configuration: -1 in the conservative score. IEEE802154 is not a broadly deployed default networking path and usually needs relevant stack and device setup. * No generic memory corruption: +0. The patch fixes uninitialized data disclosure, not UAF, OOB write, double free, or type confusion. * No reliable kernel crash / strong DoS: +0. The described failure is information disclosure only. * No integrity impact: +0. There is no write primitive or policy bypass shown. 3. Reachability analysis A local user or process must be able to open or receive from IEEE802154 datagram traffic and call recvmsg. An adjacent IEEE802154 sender may influence packet contents and address mode, but the leak is delivered to the local receiving process, so this is not realistically remote exploitable in the usual network attacker sense. Namespaces may affect socket availability depending on system configuration, but the issue does not require CAP_SYS_ADMIN if the protocol sockets are available to the local user. The path is not common on general-purpose servers. 4. Severity interpretation This behaves like a low-end Moderate or Low-like kernel information leak. The vulnerability has a concrete confidentiality primitive, but it appears limited to a small uninitialized pan_id field copied into a userspace sockaddr. There is no supported evidence of memory corruption, privilege escalation, integrity impact, or availability impact. The paranoid score is only slightly higher because kernel stack disclosure deserves review, but it is not an Important-class candidate. 5. One-sentence report phrase An IEEE802154 datagram recvmsg path can disclose uninitialized kernel stack bytes because pan_id is not cleared for IEEE802154_ADDR_NONE before the socket address is copied to userspace. 6. Manual review recommendation MANUAL CHECK RECOMMENDED. This is a real kernel infoleak and should be confirmed for product exposure, but the practical impact is limited and it is not an actionable Important candidate. ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: ieee802154: fix kernel-infoleak in dgram_recvmsg() [ Upstream Commit: a2ee1a038a16e286d084bc293a7522d010a59ec3 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a2ee1a038a16e286d084bc293a7522d010a59ec3 Changed files: lib/usercopy.c:26 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=a2ee1a038a16e286d084bc293a7522d010a59ec3 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-72441 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72441 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: Not available The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N The Best / paranoid CVSS score: 3.3 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: 1 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: MODERATE KPANIC detected for this report: NO Published priority for this report (same as in Subject): MODERATE REGULAR 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).