Answer in brief
CVE-2022-50747 records a High severity (CVSS 7.8) vulnerability in hfs: Fix OOB Write in hfs_asc2mac. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2022-50747 records a High severity (CVSS 7.8) vulnerability in hfs: Fix OOB Write in hfs_asc2mac. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=328b9227865026268261a24a97a578907b280415 <8399318b13dc9e0569dee07ba2994098926d4fb2 || >=328b9227865026268261a24a97a578907b280415 <95040de81c629cd8d3c6ab5b50a8bd5088068303 || >=328b9227865026268261a24a97a578907b280415 <ba8f0ca386dd15acf5a93cbac932392c7818eab4 || >=328b9227865026268261a24a97a578907b280415 <6a95b17e4d4cd2d8278559f930b447f8c9c8cff9 || >=328b9227865026268261a24a97a578907b280415 <cff9fefdfbf5744afbb6d70bff2b49ec2065d23d || >=328b9227865026268261a24a97a578907b280415 <7af9cb8cbb81308ce4b06cc7164267faccbf75dd || >=328b9227865026268261a24a97a578907b280415 <ae21b03f904736eb2aa9bd119d2a14e741f1681f || >=328b9227865026268261a24a97a578907b280415 <88579c158e026860c61c4192531e8bc42f4bc642 || >=328b9227865026268261a24a97a578907b280415 <c53ed55cb275344086e32a7080a6b19cb183650b | 8399318b13dc9e0569dee07ba2994098926d4fb2, 95040de81c629cd8d3c6ab5b50a8bd5088068303, ba8f0ca386dd15acf5a93cbac932392c7818eab4, 6a95b17e4d4cd2d8278559f930b447f8c9c8cff9, cff9fefdfbf5744afbb6d70bff2b49ec2065d23d, 7af9cb8cbb81308ce4b06cc7164267faccbf75dd, ae21b03f904736eb2aa9bd119d2a14e741f1681f, 88579c158e026860c61c4192531e8bc42f4bc642, c53ed55cb275344086e32a7080a6b19cb183650b |
| Linux/Linuxgeneric | 2.6.14 | Not reported |
Published upstream
Dec 24, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: hfs: Fix OOB Write in hfs_asc2mac Syzbot reported a OOB Write bug: loop0: detected capacity change from 0 to 64 ================================================================== BUG: KASAN: slab-out-of-bounds in hfs_asc2mac+0x467/0x9a0 fs/hfs/trans.c:133 Write of size 1 at addr ffff88801848314e by task syz-executor391/3632 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106 print_address_description+0x74/0x340 mm/kasan/report.c:284 print_report+0x107/0x1f0 mm/kasan/report.c:395 kasan_report+0xcd/0x100 mm/kasan/report.c:495 hfs_asc2mac+0x467/0x9a0 fs/hfs/trans.c:133 hfs_cat_build_key+0x92/0x170 fs/hfs/catalog.c:28 hfs_lookup+0x1ab/0x2c0 fs/hfs/dir.c:31 lookup_open fs/namei.c:3391 [inline] open_last_lookups fs/namei.c:3481 [inline] path_openat+0x10e6/0x2df0 fs/namei.c:3710 do_filp_open+0x264/0x4f0 fs/namei.c:3740 If in->len is much larger than HFS_NAMELEN(31) which is the maximum length of an HFS filename, a OOB write could occur in hfs_asc2mac(). In that case, when the dst reaches the boundary, the srclen is still greater than 0, which causes a OOB write. Fix this by adding a check on dstlen in while() before writing to dst address.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=328b9227865026268261a24a97a578907b280415 <8399318b13dc9e0569dee07ba2994098926d4fb2 || >=328b9227865026268261a24a97a578907b280415 <95040de81c629cd8d3c6ab5b50a8bd5088068303 || >=328b9227865026268261a24a97a578907b280415 <ba8f0ca386dd15acf5a93cbac932392c7818eab4 || >=328b9227865026268261a24a97a578907b280415 <6a95b17e4d4cd2d8278559f930b447f8c9c8cff9 || >=328b9227865026268261a24a97a578907b280415 <cff9fefdfbf5744afbb6d70bff2b49ec2065d23d || >=328b9227865026268261a24a97a578907b280415 <7af9cb8cbb81308ce4b06cc7164267faccbf75dd || >=328b9227865026268261a24a97a578907b280415 <ae21b03f904736eb2aa9bd119d2a14e741f1681f || >=328b9227865026268261a24a97a578907b280415 <88579c158e026860c61c4192531e8bc42f4bc642 || >=328b9227865026268261a24a97a578907b280415 <c53ed55cb275344086e32a7080a6b19cb183650b | 8399318b13dc9e0569dee07ba2994098926d4fb2, 95040de81c629cd8d3c6ab5b50a8bd5088068303, ba8f0ca386dd15acf5a93cbac932392c7818eab4, 6a95b17e4d4cd2d8278559f930b447f8c9c8cff9, cff9fefdfbf5744afbb6d70bff2b49ec2065d23d, 7af9cb8cbb81308ce4b06cc7164267faccbf75dd, ae21b03f904736eb2aa9bd119d2a14e741f1681f, 88579c158e026860c61c4192531e8bc42f4bc642, c53ed55cb275344086e32a7080a6b19cb183650b |
| Linux/Linuxgeneric | 2.6.14 | Not reported |
Published upstream
Dec 24, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: hfs: Fix OOB Write in hfs_asc2mac Syzbot reported a OOB Write bug: loop0: detected capacity change from 0 to 64 ================================================================== BUG: KASAN: slab-out-of-bounds in hfs_asc2mac+0x467/0x9a0 fs/hfs/trans.c:133 Write of size 1 at addr ffff88801848314e by task syz-executor391/3632 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106 print_address_description+0x74/0x340 mm/kasan/report.c:284 print_report+0x107/0x1f0 mm/kasan/report.c:395 kasan_report+0xcd/0x100 mm/kasan/report.c:495 hfs_asc2mac+0x467/0x9a0 fs/hfs/trans.c:133 hfs_cat_build_key+0x92/0x170 fs/hfs/catalog.c:28 hfs_lookup+0x1ab/0x2c0 fs/hfs/dir.c:31 lookup_open fs/namei.c:3391 [inline] open_last_lookups fs/namei.c:3481 [inline] path_openat+0x10e6/0x2df0 fs/namei.c:3710 do_filp_open+0x264/0x4f0 fs/namei.c:3740 If in->len is much larger than HFS_NAMELEN(31) which is the maximum length of an HFS filename, a OOB write could occur in hfs_asc2mac(). In that case, when the dst reaches the boundary, the srclen is still greater than 0, which causes a OOB write. Fix this by adding a check on dstlen in while() before writing to dst address.
Quoted source text, attributed separately from HOL analysis.