CVE-2026-25701

N/A Unknown

📋 TL;DR

An insecure temporary file vulnerability in openSUSE sdbootutil allows local users to pre-create directories to manipulate sensitive data. This can lead to information disclosure, data integrity violations, or system file overwrites. The vulnerability affects local users on systems running vulnerable versions of sdbootutil.

💻 Affected Systems

Products:
  • openSUSE sdbootutil
Versions: All versions before commit 5880246d3a02642dc68f5c8cb474bf63cdb56bca
Operating Systems: openSUSE Linux
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects systems where sdbootutil is installed and used.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Local attackers could overwrite protected system files, potentially compromising system integrity or gaining elevated privileges.

🟠

Likely Case

Local users could access private information from /var/lib/pcrlock.d or manipulate backup data integrity.

🟢

If Mitigated

With proper file permissions and access controls, impact is limited to authorized local users only.

🌐 Internet-Facing: LOW - This is a local vulnerability requiring local access to exploit.
🏢 Internal Only: MEDIUM - Internal users with local access could exploit this to access sensitive data or manipulate system files.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires local access and knowledge of the vulnerable temporary file handling.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Version containing commit 5880246d3a02642dc68f5c8cb474bf63cdb56bca

Vendor Advisory: https://bugzilla.suse.com/show_bug.cgi?id=1258241

Restart Required: No

Instructions:

1. Update sdbootutil package via system package manager. 2. Verify the fix is applied by checking package version or commit hash.

🔧 Temporary Workarounds

Restrict temporary directory permissions

linux

Set strict permissions on /tmp/pcrlock.d.bak directory to prevent unauthorized access

chmod 700 /tmp/pcrlock.d.bak
chown root:root /tmp/pcrlock.d.bak

🧯 If You Can't Patch

  • Implement strict file permissions on /tmp/pcrlock.d.bak and /var/lib/pcrlock.d directories
  • Monitor for suspicious file creation or symlink activity in temporary directories

🔍 How to Verify

Check if Vulnerable:

Check sdbootutil version or commit hash. If before commit 5880246d3a02642dc68f5c8cb474bf63cdb56bca, system is vulnerable.

Check Version:

rpm -q sdbootutil

Verify Fix Applied:

Verify sdbootutil package version includes commit 5880246d3a02642dc68f5c8cb474bf63cdb56bca

📡 Detection & Monitoring

Log Indicators:

  • Unusual file creation in /tmp/pcrlock.d.bak
  • Symlink creation in temporary directories by non-root users

Network Indicators:

  • None - this is a local file system vulnerability

SIEM Query:

File creation events in /tmp/pcrlock.d.bak by non-root users OR symlink creation in /tmp directories

🔗 References

📤 Share & Export