[Memory Safety] Memory Safety Analysis — 2026-03-16 — ✅ Clean Run

[github-actions[bot]]

Date: 2026-03-16
Commit: fe6efef (fe6efef8088bd437d6be10ede5a08da3970640c3) on branch master
Commit message: Add monthly Academic Citation & Research Trend Tracker workflow (#9007)
Triggered by: schedule (Memory Safety Analysis run #23122930100)
Report run: #23123615154

---

Executive Summary

Category	ASan	UBSan	Total
Buffer Overflow	0	—	0
Use-After-Free	0	—	0
Double-Free	0	—	0
Null Dereference	—	0	0
Integer Overflow	—	0	0
Undefined Behavior	—	0	0
Other	0	0	0
Total	0	0	0

✅ No sanitizer errors detected in this run. Both AddressSanitizer and UndefinedBehaviorSanitizer completed their test suites (unit tests + regression tests) without generating any error reports.

---

Trend

• New findings since last run: 0
• Resolved since last run: 0 (previous runs had unavailable artifact data)
• Unchanged: 0 known issues

Note on previous runs: Runs on 2026-03-13 and 2026-03-14 could not confirm findings because the artifact download infrastructure required GH_TOKEN to be passed to the agent step (network-firewalled environment). This run used GitHub MCP tools + job log parsing to confirm clean status directly from the runner output.

---

Critical Findings (Immediate Action Needed)

None. ✅

---

Important Findings (Should Fix)

None. ✅

---

Low-Severity / Informational

None. ✅

---

ASan Job Details

Job: ASan Build & Test #67160221589
Status: ✅ success
Duration: ~33 minutes (00:28:10 → 01:01:30 UTC)
ASAN_OPTIONS: detect_leaks=1:halt_on_error=0:print_stats=1:log_path=/tmp/asan

Test phases completed:

• Configure with ASan ✅
• Build Z3 with ASan ✅
• Run unit tests under ASan ✅
• Run SMT-LIB2 benchmarks under ASan ✅
• Run regression tests under ASan ✅

Artifact summary: summary.md contained: No ASan errors detected.

No asan.* error log files were generated, confirming zero memory safety violations.

UBSan Job Details

Job: UBSan Build & Test #67160221579
Status: ✅ success
Duration: ~34 minutes (00:28:10 → 01:02:24 UTC)
UBSAN_OPTIONS: print_stacktrace=1:halt_on_error=0:log_path=/tmp/ubsan

Test phases completed:

• Configure with UBSan ✅
• Build Z3 with UBSan ✅
• Run unit tests under UBSan ✅
• Run SMT-LIB2 benchmarks under UBSan ✅
• Run regression tests under UBSan ✅

Artifact summary: summary.md contained: No UBSan errors detected.

No ubsan.* error log files were generated, confirming zero undefined behavior violations.

---

Top Affected Files

No files affected — clean run.

---

Known Suppressions

Sanitizer	Suppression
UBSan	rational.h (null pointer in rational arithmetic, pre-existing)
UBSan	mpq.h (null pointer in GMP wrapper, pre-existing)

---

Recommendations

1. ✅ No immediate action required — the codebase is clean under both ASan and UBSan.
2. Continue scheduled memory safety runs to catch regressions early.
3. Consider enabling ASAN_OPTIONS=detect_stack_use_after_return=1 for deeper stack analysis in future scans.
4. Consider full_scan: true via workflow_dispatch periodically to exercise more code paths.

---

Raw Data / Infrastructure Notes

Artifact IDs:

• asan-reports → ID 5935634186 (317,501 bytes, SHA256: 265daa3c...)
• ubsan-reports → ID 5935641024 (317,483 bytes, SHA256: 3df01351...)

Analysis method: Artifact download URLs were obtained via GitHub MCP API but are inaccessible from the sandboxed agent environment (network firewall). Findings confirmed by parsing the raw GitHub Actions job logs (last 300 lines of each job), which captured the Collect *San reports step output. Both steps executed the echo "No *San errors detected." branch, confirming no error files were created.

Build environment:

• OS: Ubuntu 24.04.3 LTS
• Runner image: ubuntu-24.04 v20260302.42.1
• Azure region: eastus

Cache memory updated: memory-safety-results.json in /tmp/gh-aw/cache-memory/

AI generated by Memory Safety Analysis Report Generator · history

• expires on Mar 23, 2026, 1:07 AM UTC