[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-DEBIAN-CVE-2023-52813":6},{"stargazers_count":4,"fetched_at":5},7,"2026-06-04T14:53:31.930Z",{"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":39},"DEBIAN-CVE-2023-52813","In the Linux kernel, the following vulnerability has been resolved:  crypto: pcrypt - Fix hungtask for PADATA_RESET  We found a hungtask bug in test_aead_vec_cfg as follows:  INFO: task cryptomgr_test:391009 blocked for more than 120 seconds. \"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message. Call trace:  __switch_to+0x98/0xe0  __schedule+0x6c4/0xf40  schedule+0xd8/0x1b4  schedule_timeout+0x474/0x560  wait_for_common+0x368/0x4e0  wait_for_completion+0x20/0x30  wait_for_completion+0x20/0x30  test_aead_vec_cfg+0xab4/0xd50  test_aead+0x144/0x1f0  alg_test_aead+0xd8/0x1e0  alg_test+0x634/0x890  cryptomgr_test+0x40/0x70  kthread+0x1e0/0x220  ret_from_fork+0x10/0x18  Kernel panic - not syncing: hung_task: blocked tasks  For padata_do_parallel, when the return err is 0 or -EBUSY, it will call wait_for_completion(&wait->completion) in test_aead_vec_cfg. In normal case, aead_request_complete() will be called in pcrypt_aead_serial and the return err is 0 for padata_do_parallel. But, when pinst->flags is PADATA_RESET, the return err is -EBUSY for padata_do_parallel, and it won't call aead_request_complete(). Therefore, test_aead_vec_cfg will hung at wait_for_completion(&wait->completion), which will cause hungtask.  The problem comes as following: (padata_do_parallel)                 |     rcu_read_lock_bh();              |     err = -EINVAL;                   |   (padata_replace)                                      |     pinst->flags |= PADATA_RESET;     err = -EBUSY                     |     if (pinst->flags & PADATA_RESET) |         rcu_read_unlock_bh()         |         return err  In order to resolve the problem, we replace the return err -EBUSY with -EAGAIN, which means parallel_data is changing, and the caller should call it again.  v3: remove retry and just change the return err. v2: introduce padata_try_do_parallel() in pcrypt_aead_encrypt and pcrypt_aead_decrypt to solve the hungtask.",null,[],[],[],[14],{"_key":15},"CVE-2023-52813",[],[],[],"2024-05-21T16:15:19.477Z","2026-04-28T20:26:46.796348Z",{"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-2023-52813",[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":37,"exploitabilityScore":38},5.5,"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",6,4.6,[40],{"ecosystem":41,"name":42,"vendor":43,"product":42,"cpe_part":9,"purl_type":44,"purl_namespace":43,"purl_name":42,"source":9,"versions":45},"Debian","linux","debian","deb",[46,52,55,58],{"version":47,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":50,"version_end_type":51,"fixed_in":9},"lt5_10_205_1",true,"ecosystem","5.10.205-1","excluding",{"version":53,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":54,"version_end_type":51,"fixed_in":9},"lt6_1_64_1","6.1.64-1",{"version":56,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":57,"version_end_type":51,"fixed_in":9},"lt6_6_8_1","6.6.8-1",{"version":56,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":57,"version_end_type":51,"fixed_in":9}]