FreeBSD Kernel up to p0.x/p6/p10/p15 Ktls Ocf ktls_ocf_tls_cbc_decrypt uninitialized resource
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 1.29- |
Summary
A vulnerability was found in FreeBSD Kernel up to p0.x/p6/p10/p15. It has been rated as critical. Affected by this issue is the function ktls_ocf_tls_cbc_decrypt of the component Ktls Ocf. The manipulation leads to uninitialized resource.
This vulnerability is uniquely identified as CVE-2026-49423. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability, which was classified as critical, has been found in FreeBSD Kernel up to p0.x/p6/p10/p15. This issue affects the function ktls_ocf_tls_cbc_decrypt of the component Ktls Ocf. The manipulation with an unknown input leads to a uninitialized resource vulnerability. Using CWE to declare the problem leads to CWE-908. The product uses or accesses a resource that has not been initialized. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
When building the iovec array for a received TLS 1.2 CBC record, ktls_ocf_tls_cbc_decrypt() incremented the iovec index for every mbuf in the chain, including mbufs that were skipped because they contained only TLS header bytes. This left uninitialized entries in the iovec array. The iovec array was allocated without zeroing. A remote TLS peer can cause the kernel to read from uninitialized iovec entries during HMAC computation, resulting in a kernel panic. The peer must be able to control TCP segmentation such that the first mbuf of a CBC record contains only the 5-byte TLS record header.
It is possible to read the advisory at security.freebsd.org. The identification of this vulnerability is CVE-2026-49423 since 05/29/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version p1, p7, p11 or p16 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.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: Uninitialized resourceCWE: CWE-908
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 p1/p7/p11/p16
Timeline
05/29/2026 CVE reserved08/19/2026 Advisory disclosed
08/19/2026 VulDB entry created
08/19/2026 VulDB entry last update
Sources
Advisory: security.freebsd.orgStatus: Confirmed
CVE: CVE-2026-49423 (🔒)
GCVE (CVE): GCVE-0-2026-49423
GCVE (VulDB): GCVE-100-392987
Entry
Created: 08/19/2026 09:29Changes: 08/19/2026 09:29 (56)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.