Linux Kernel up to 6.6.150/6.12.102/6.18.43/7.1.7 iblock iblock_execute_pr_out null pointer dereference

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in Linux Kernel up to 6.6.150/6.12.102/6.18.43/7.1.7. Affected by this issue is the function iblock_execute_pr_out of the component iblock. Such manipulation leads to null pointer dereference.
This vulnerability is referenced as CVE-2026-80691. It is possible to launch the attack remotely. No exploit is available.
You should upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in Linux Kernel up to 6.6.150/6.12.102/6.18.43/7.1.7. Affected by this issue is the function iblock_execute_pr_out of the component iblock. The manipulation with an unknown input leads to a null pointer dereference vulnerability. Using CWE to declare the problem leads to CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. Impacted is confidentiality, integrity, and availability. CVE summarizes:
In the Linux kernel, the following vulnerability has been resolved: scsi: target: iblock: Fix wrong PR ops NULL check for PREEMPT/RELEASE In the iblock_execute_pr_out() function, PRO_PREEMPT, PRO_PREEMPT_AND_ABORT, and PRO_RELEASE all perform callback capability checks through ops->pr_clear. The error check allows unimplemented hooks to pass through the gate, resulting dereferencing a NULL function pointer. Check whether the hooks that need to be called are supported.
The advisory is available at git.kernel.org. This vulnerability is handled as CVE-2026-80691 since 08/26/2026. The exploitation is known to be easy. The attack may be launched remotely. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 08/30/2026).
Upgrading to version 6.6.151, 6.12.103, 6.18.44 or 7.1.8 eliminates this vulnerability. Applying the patch 3c60a8b4037dc35e365658fcbcb349a5d742ff49/a326b19cfb7775378b50acaa8d836ba44e29b4c2/bdd8a1297ef101bb5ac57e53b4fbe5e364afd8b1/f15bcf9a99b1b2683fcfa005b9b3680b5600581f/9c33222bd387312874fbe36ca8002e5c945b9653 is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-3075). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Affected
- Open Source Linux Kernel
Product
Type
Vendor
Name
Version
- 6.6.150
- 6.12.102
- 6.18.0
- 6.18.1
- 6.18.2
- 6.18.3
- 6.18.4
- 6.18.5
- 6.18.6
- 6.18.7
- 6.18.8
- 6.18.9
- 6.18.10
- 6.18.11
- 6.18.12
- 6.18.13
- 6.18.14
- 6.18.15
- 6.18.16
- 6.18.17
- 6.18.18
- 6.18.19
- 6.18.20
- 6.18.21
- 6.18.22
- 6.18.23
- 6.18.24
- 6.18.25
- 6.18.26
- 6.18.27
- 6.18.28
- 6.18.29
- 6.18.30
- 6.18.31
- 6.18.32
- 6.18.33
- 6.18.34
- 6.18.35
- 6.18.36
- 6.18.37
- 6.18.38
- 6.18.39
- 6.18.40
- 6.18.41
- 6.18.42
- 6.18.43
- 7.1.0
- 7.1.1
- 7.1.2
- 7.1.3
- 7.1.4
- 7.1.5
- 7.1.6
- 7.1.7
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Null pointer dereferenceCWE: CWE-476 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 6.6.151/6.12.103/6.18.44/7.1.8
Patch: 3c60a8b4037dc35e365658fcbcb349a5d742ff49/a326b19cfb7775378b50acaa8d836ba44e29b4c2/bdd8a1297ef101bb5ac57e53b4fbe5e364afd8b1/f15bcf9a99b1b2683fcfa005b9b3680b5600581f/9c33222bd387312874fbe36ca8002e5c945b9653
Timeline
08/26/2026 CVE reserved08/28/2026 Advisory disclosed
08/28/2026 VulDB entry created
08/30/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-80691 (🔒)
GCVE (CVE): GCVE-0-2026-80691
GCVE (VulDB): GCVE-100-396650
CERT Bund: WID-SEC-2026-3075 - Linux Kernel: Mehrere Schwachstellen
Entry
Created: 08/28/2026 11:05Updated: 08/30/2026 00:13
Changes: 08/28/2026 11:05 (59), 08/30/2026 00:13 (7)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.