[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-DEBIAN-CVE-2023-53503":6},{"stargazers_count":4,"fetched_at":5},7,"2026-06-04T08:53:30.047Z",{"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-53503","In the Linux kernel, the following vulnerability has been resolved:  ext4: allow ext4_get_group_info() to fail  Previously, ext4_get_group_info() would treat an invalid group number as BUG(), since in theory it should never happen.  However, if a malicious attaker (or fuzzer) modifies the superblock via the block device while it is the file system is mounted, it is possible for s_first_data_block to get set to a very large number.  In that case, when calculating the block group of some block number (such as the starting block of a preallocation region), could result in an underflow and very large block group number.  Then the BUG_ON check in ext4_get_group_info() would fire, resutling in a denial of service attack that can be triggered by root or someone with write access to the block device.  For a quality of implementation perspective, it's best that even if the system administrator does something that they shouldn't, that it will not trigger a BUG.  So instead of BUG'ing, ext4_get_group_info() will call ext4_error and return NULL.  We also add fallback code in all of the callers of ext4_get_group_info() that it might NULL.  Also, since ext4_get_group_info() was already borderline to be an inline function, un-inline it.  The results in a next reduction of the compiled text size of ext4 by roughly 2k.",null,[],[],[],[14],{"_key":15},"CVE-2023-53503",[],[],[],"2025-10-01T12:15:53.917Z","2026-04-28T20:27:02.598728Z",{"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-53503",[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_191_1",true,"ecosystem","5.10.191-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_37_1","6.1.37-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_3_7_1","6.3.7-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}]