[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-DEBIAN-CVE-2026-31533":6},{"stargazers_count":4,"fetched_at":5},7,"2026-07-30T21:17:53.703Z",{"id":7,"descriptions":8,"cisa":9,"weaknesses":10,"exploits":11,"aliases":12,"duplicate_of":9,"upstream":13,"downstream":16,"duplicates":17,"related":18,"reserved_at":9,"published_at":19,"modified_at":20,"state":9,"summary":21,"references_raw":23,"kevs":30,"epss":9,"epss_history":31,"metrics":32,"affected":38},"DEBIAN-CVE-2026-31533","In the Linux kernel, the following vulnerability has been resolved:  net/tls: fix use-after-free in -EBUSY error path of tls_do_encryption  The -EBUSY handling in tls_do_encryption(), introduced by commit 859054147318 (\"net: tls: handle backlogging of crypto requests\"), has a use-after-free due to double cleanup of encrypt_pending and the scatterlist entry.  When crypto_aead_encrypt() returns -EBUSY, the request is enqueued to the cryptd backlog and the async callback tls_encrypt_done() will be invoked upon completion. That callback unconditionally restores the scatterlist entry (sge->offset, sge->length) and decrements ctx->encrypt_pending. However, if tls_encrypt_async_wait() returns an error, the synchronous error path in tls_do_encryption() performs the same cleanup again, double-decrementing encrypt_pending and double-restoring the scatterlist.  The double-decrement corrupts the encrypt_pending sentinel (initialized to 1), making tls_encrypt_async_wait() permanently skip the wait for pending async callbacks. A subsequent sendmsg can then free the tls_rec via bpf_exec_tx_verdict() while a cryptd callback is still pending, resulting in a use-after-free when the callback fires on the freed record.  Fix this by skipping the synchronous cleanup when the -EBUSY async wait returns an error, since the callback has already handled encrypt_pending and sge restoration.",null,[],[],[],[14],{"_key":15},"CVE-2026-31533",[],[],[],"2026-04-23T18:16:26.857Z","2026-06-15T19:06:16.164854001Z",{"cisa_kev":22,"cisa_ransomware":22,"cisa_vendor":9,"epss_severity":9,"epss_score":9,"severity":9,"severity_score":9,"severity_version":9,"severity_source":9,"severity_vector":9,"severity_status":9},false,[24],{"url":25,"sources":26,"tags":28},"https://security-tracker.debian.org/tracker/CVE-2026-31533",[27],"osv_debian",[29],"Advisory",[],[],[33],{"source":27,"cvss_v2_0":9,"cvss_v3_0":9,"cvss_v3_1":34,"cvss_v4_0":9},{"baseScore":35,"baseSeverity":9,"vectorString":36,"impactScore":35,"exploitabilityScore":37},9.8,"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",10,[39,61],{"ecosystem":40,"name":41,"vendor":42,"product":41,"cpe_part":9,"purl_type":43,"purl_namespace":42,"purl_name":41,"source":9,"versions":44},"Debian","linux","debian","deb",[45,49,50,51,55,58],{"version":46,"is_range":47,"range_type":48,"version_start":9,"version_start_type":9,"version_end":9,"version_end_type":9,"fixed_in":9},"all",true,"ecosystem",{"version":46,"is_range":47,"range_type":48,"version_start":9,"version_start_type":9,"version_end":9,"version_end_type":9,"fixed_in":9},{"version":46,"is_range":47,"range_type":48,"version_start":9,"version_start_type":9,"version_end":9,"version_end_type":9,"fixed_in":9},{"version":52,"is_range":47,"range_type":48,"version_start":9,"version_start_type":9,"version_end":53,"version_end_type":54,"fixed_in":9},"lt6_1_170_1","6.1.170-1","excluding",{"version":56,"is_range":47,"range_type":48,"version_start":9,"version_start_type":9,"version_end":57,"version_end_type":54,"fixed_in":9},"lt6_12_85_1","6.12.85-1",{"version":59,"is_range":47,"range_type":48,"version_start":9,"version_start_type":9,"version_end":60,"version_end_type":54,"fixed_in":9},"lt6_19_13_1","6.19.13-1",{"ecosystem":40,"name":62,"vendor":42,"product":62,"cpe_part":9,"purl_type":43,"purl_namespace":42,"purl_name":62,"source":9,"versions":63},"linux-6.1",[64],{"version":65,"is_range":47,"range_type":48,"version_start":9,"version_start_type":9,"version_end":66,"version_end_type":54,"fixed_in":9},"lt6_1_170_1~deb11u1","6.1.170-1~deb11u1"]