Linux Kernel up to 7.2.4 qla2xxx qla2x00_dfs_fce_write null pointer dereference

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Linux Kernel up to 7.2.4 and classified as problematic. Affected is the function qla2x00_dfs_fce_write of the component qla2xxx. Such manipulation leads to null pointer dereference.
This vulnerability is listed as CVE-2026-89851. The attack must be carried out locally. There is no available exploit.
It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in Linux Kernel up to 7.2.4. Affected by this issue is the function qla2x00_dfs_fce_write of the component qla2xxx. 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 availability. CVE summarizes:
In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix FCE trace enable parsing in debugfs qla2x00_dfs_fce_write() called kstrtoul() with a NULL result pointer, so a successful parse would dereference NULL and oops. Worse, the int return value (0 on success, negative errno on failure) was assigned to the unsigned long enable flag, inverting the intended logic: a valid number was treated as "disable" while a parse failure enabled FCE. Parse the value into enable and propagate parse errors to userspace.
The advisory is shared for download at git.kernel.org. This vulnerability is handled as CVE-2026-89851 since 09/11/2026. The exploitation is known to be easy. The attack needs to be approached locally. Additional levels of successful authentication are necessary for exploitation. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available.
Upgrading to version 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.51, 7.2.5 or 7.3-rc1 eliminates this vulnerability. Applying the patch b0c08c08a08b6cca0e7e192bcbe0514e41fcc55f/9932cbd0b49d0a5ab8378d32650ffb51604ffa35/f5e245164d187d1ee227140c8b2e83b67f59c1fd/5762d992dddaf301e7fb78f797de407116847121/eff41f50461c238bd2c5cd20672a5b53e68d493a/7203d4aed8f444e7376c2dee8d93577b37cf9989/aac0d3cb9199121d2ce5906e06f94b793fac1052/b7368687e3d11f51392d3c4774ec0263d5fbf31f is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
- 5.10.269
- 5.15.220
- 6.1.187
- 6.6.156
- 6.12.109
- 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
- 6.18.44
- 6.18.45
- 6.18.46
- 6.18.47
- 6.18.48
- 6.18.49
- 6.18.50
- 7.2.0
- 7.2.1
- 7.2.2
- 7.2.3
- 7.2.4
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.2VulDB Meta Temp Score: 4.0
VulDB Base Score: 4.2
VulDB Temp Score: 4.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: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
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 5.10.270/5.15.221/6.1.188/6.6.157/6.12.110/6.18.51/7.2.5/7.3-rc1
Patch: b0c08c08a08b6cca0e7e192bcbe0514e41fcc55f/9932cbd0b49d0a5ab8378d32650ffb51604ffa35/f5e245164d187d1ee227140c8b2e83b67f59c1fd/5762d992dddaf301e7fb78f797de407116847121/eff41f50461c238bd2c5cd20672a5b53e68d493a/7203d4aed8f444e7376c2dee8d93577b37cf9989/aac0d3cb9199121d2ce5906e06f94b793fac1052/b7368687e3d11f51392d3c4774ec0263d5fbf31f
Timeline
09/11/2026 CVE reserved09/16/2026 Advisory disclosed
09/16/2026 VulDB entry created
09/16/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-89851 (🔒)
GCVE (CVE): GCVE-0-2026-89851
GCVE (VulDB): GCVE-100-405668
Entry
Created: 09/16/2026 13:29Changes: 09/16/2026 13:29 (59)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.