Well, if you are the third AP owner in your neighborhood that has a network name Linksys or Home Network, you should not get into trouble.
If you named you network Logan Airport because you wanted to gain access to passengers computers, you would be breakting the law in most countries.
If you named you network Logan Airport because you were curious to find out how many would connect to it, well I am not a lawyer, but I would say you were on thin ice.
The problem with faked DHCP-servers is not so much that it can take advantage of bash vulnerabilities, most clients should now be updated and not use Bash. It is worse that they can give you bad DNS-servers. That means that the attacker can then do a MITM attack on every single connection, you make. Encryption helps, but not everything is encrypted, and many user would accept a fake SSL certificate.
If you are worried about fake DHCP servers you should configure your DHCP client to use fixed DNS servers (I use http://censurfridns.dk/). You would still be vulnerable to fake accesspoints and fake DHCP-servers that also gave you a fake gateway, but not to bad DNS-servers.
Unfortunately many networks rely on using DNS to implement captive portals for login and advertizing, so you cannot do it for all networks.