CVE-2023-23005

What it actually does

In mm/memory-tiers.c, alloc_memory_type return value is misinterpreted (expects NULL on error but receives an error pointer), potentially leading to invalid pointer use or memory corruption.

Why it matters to the business

May result in local denial of service via system instability or crashes on older Linux kernels using memory tiers, though third-party analysis indicates minimal real-world exposure and no realistic trigger conditions.

How an attack unfolds

A local attacker would attempt to force the alloc_memory_type error path to trigger misinterpretation of the returned error pointer, but the flaw is disputed as unreachable in practice with no known exploitation or threat actor involvement.

How to fix it

Update torvalds/linux to a version containing commit 4a625ceee8a0ab0273534cb6b432ce6b331db5ee.

How to confirm the fix worked

Confirm kernel source includes the referenced commit; inspect mm/memory-tiers.c for correct error pointer checking on alloc_memory_type.

Typical attack path

1. Obtain local user access on an affected Linux system
2. Attempt to reach the disputed error condition in memory tier allocation
3. Trigger misinterpretation of the error pointer to induce instability

How to detect it

Review kernel logs and crash dumps for memory-tiers related faults; no confirmed exploitation artifacts exist due to disputed reachability.

What your security team should do

• Apply the referenced kernel commit or later release
• Evaluate memory tier usage in deployments for any residual risk
• Track updates to the disputed status for any change in exposure