# CVE-2026-12364: Information disclosure in zephyr

> Missing pointer validation in Zephyr RTOS logging syscall allows unprivileged users to read kernel memory or crash the system.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-h7rf-g9mg-g23f

## What is CVE-2026-12364?

CVE-2026-12364 is a high-severity vulnerability in zephyrproject zephyr, published on 14 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The user-space system-call verifier z_vrfy_z_log_msg_static_create() in subsys/logging/log_msg.c was a pure pass-through: it forwarded the caller-supplied source, desc, package, and data arguments directly to the kernel-mode implementation z_impl_z_log_msg_static_create() without performing any of the mandatory K_SYSCALL_* checks. Because z_log_msg_static_create() is declared __syscall, under CONFIG_USERSPACE any unprivileged user-mode thread can invoke it directly with fully attacker-controlled arguments.

The kernel-mode handler dereferences each of these untrusted values: frontend_runtime_filtering() reads through the source pointer as a struct log_source_dynamic_data, cbprintf_package_copy() reads desc.package_len bytes from the package pointer, and z_log_msg_finalize() performs a memcpy() of desc.data_len bytes from the data pointer. With no verification, a user thread can supply arbitrary kernel addresses and arbitrary lengths, and the kernel will read from them.

The impact is a kernel-mode denial of service (the kernel faults dereferencing an attacker-chosen pointer) and, where a log backend output is observable to the attacker, disclosure of arbitrary kernel memory copied into the emitted log message — a confidentiality breach across the user/kernel boundary that the userspace sandbox is meant to enforce. The reads do not corrupt kernel memory, so there is no out-of-bounds write primitive.

The fix adds the required validation to the verifier: it bounds desc.package_len against Z_LOG_MSG_MAX_PACKAGE, rejects non-NULL/length mismatches, and applies K_SYSCALL_MEMORY_READ() to package, data, and (when runtime filtering with a frontend is enabled) source, so any out-of-bounds or kernel pointer now raises K_OOPS instead of being honored.

Weakness: CWE-822 (Untrusted Pointer Dereference)

## Which versions are affected by CVE-2026-12364?


## How do I fix CVE-2026-12364?

No fix has been published for CVE-2026-12364 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-12364 being exploited?

There is no known exploitation of CVE-2026-12364 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-12364 and fix it if it is affected.

What it is: CVE-2026-12364 is a high-severity vulnerability in zephyrproject zephyr, published on 14 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-12364 in the wild and no public exploit code.

Affected product: zephyrproject zephyr. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-12364/ (Markdown: https://insights.sbomify.com/CVE-2026-12364/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-12364
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-12364
- OSV: https://osv.dev/vulnerability/CVE-2026-12364

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-12364/
Summaries are generated and may contain mistakes; the official description above is the record.