In the Linux kernel, the following vulnerability has been resolved:
LoongArch: mm: Add p?d_leaf() definitions
When I do LTP test, LTP test case ksm06 caused panic at
break_ksm_pmd_entry
-> pmd_leaf (Huge page table but False)
-> pte_present (panic)
The reason is pmd_leaf() is not defined, So like commit 501b81046701
("mips: mm: add p?d_leaf() definitions") add p?d_leaf() definition for
LoongArch.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel reliability issue affecting LoongArch systems. A local, low-privileged user can trigger a kernel panic in memory-management paths, causing service outage. The sources do not indicate data theft, privilege escalation, or remote attack capability.
Executive priority
Treat as a targeted availability risk. It is not a broad internet-facing emergency, but unpatched LoongArch systems with local users or hosted workloads should be patched on the normal security cycle.
Technical view
LoongArch kernel memory-management code lacked p?d_leaf() definitions. In the reported path, KSM testing reached break_ksm_pmd_entry, pmd_leaf returned false for a huge page table, and pte_present triggered a panic. CVSS is 5.5 with local access, low complexity, low privileges, and high availability impact.
Likely exposure
Exposure appears limited to Linux deployments on LoongArch architecture running affected kernel versions or unpatched downstream kernels. General x86 or Arm Linux fleets are not indicated as affected by the supplied sources.
Exploitation context
The bundle says the issue was observed during LTP ksm06 testing and does not report active exploitation. KEV is false. The attack model is local, authenticated access causing denial of service, not remote compromise.
Researcher notes
Evidence is concise and kernel-focused. The root cause and panic path are described, but the bundle does not provide broad affected-distribution mapping, exploit reports, or operational mitigations beyond applying the stable fixes.
Mitigation direction
Upgrade to a kernel or vendor package containing the referenced LoongArch p?d_leaf() fixes.
Prioritize externally hosted or multi-tenant LoongArch systems where local users can run workloads.
Check distribution advisories because downstream kernels may backport fixes without changing major versions.
If immediate patching is blocked, consult vendor guidance for risk-reduction options.
Validation and detection
Inventory LoongArch hosts and record exact kernel package versions.
Compare deployed kernels with CVE and distribution advisory status.
Confirm the kernel source or package includes the referenced LoongArch p?d_leaf() change.
Review kernel panic logs for KSM, huge page, or break_ksm_pmd_entry signatures.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2023-53361 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.