Vulnerability in zfs-linux (UBUNTU-CVE-2026-79619)

Summary

Vulnerability in zfs-linux (UBUNTU-CVE-2026-79619). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.7.5-1ubuntu16.12+esm1 or later.

Original description

The description as published by the source.

On Linux, several OpenZFS ioctl authorization checks accept a capability held only within a user-created, unprivileged namespace as equivalent to real host privilege, allowing an unprivileged local user to perform operations that should require root. Affected operations include pool-administrative operations (eg create, import, destroy), pool event log access (zpool events) and fault injection (zinject). Exploiting the problem requires only that the local user is permitted to open /dev/zfs (governed by local device permissions) and that the kernel permits unprivileged user namespace creation. No prior access to the target pool or its underlying devices is needed.

Source: OSV.dev (Open Source Vulnerabilities) OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as UBUNTU-CVE-2026-79619 has been found in zfs-linux.
Risk of unauthorized operations or information disclosure.
What to do: upgrade zfs-linux to 0.7.5-1ubuntu16.12+esm1 or later.
If unsure, ask your IT team or search "zfs-linux UBUNTU-CVE-2026-79619" on the vendor's site.

UBUNTU-CVE-2026-79619 (zfs-linux)
Patched: 0.7.5-1ubuntu16.12+esm1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in zfs-linux.

📍 Affected scope

Check the vendor advisory for the affected versions of zfs-linux.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.7.5-1ubuntu16.12+esm1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'zfs-linux' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'zfs-linux' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で zfs-linux を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade zfs-linux to 0.7.5-1ubuntu16.12+esm1
```
ステージング環境で 0.7.5-1ubuntu16.12+esm1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Ubuntu:Pro:18.04:LTS zfs-linux

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.7.5-1ubuntu16.12+esm1"}]}]

Ubuntu:Pro:20.04:LTS zfs-linux

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.8.3-1ubuntu12.18+esm1"}]}]

Ubuntu:22.04:LTS zfs-linux

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.1.5-1ubuntu6~22.04.7"}]}]

Ubuntu:24.04:LTS zfs-linux

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.2-0ubuntu9.5"}]}]

Ubuntu:26.04:LTS zfs-linux

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.4.1-1ubuntu5.1"}]}]

References

advisory ubuntu.com
advisory ubuntu.com
report ubuntu.com
report cve.org
report github.com
report openwall.com
report github.com